Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Software Developer / Software Engineer
- Translate requirements into scoped software changes. - Inspect architecture, code, interfaces, tests, and runtime evidence. - Prepare implementation, review, release, and rollback plans.
Read the fileOverview
Software Developer / Software Engineer Overview
ONET describes software developers as researching, designing, developing, and testing software; analyzing user needs; modifying systems; and documenting specifications.
Read the fileWorkflow
Software Developer / Software Engineer source-backed Triage
1. State the requested decision or deliverable. 2. Inventory evidence: requirements and acceptance criteria, repository and revision state, architecture and interface contracts, dependency.
Read the fileTemplate
Software change implementation and review brief
State the direct answer, recommendation, or draft purpose.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Software Developer / Software Engineer work, plus teams reviewing its decisions and outputs
- Teams working in Software, Information technology
When to use it
- A Software Developer / Software Engineer task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Plan code changes without fabricated repository facts.
- Produce reviewable implementation and validation plans.
- Keep production claims tied to executed evidence.
What it helps produce
- Software change implementation and review brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Software Developer / Software Engineer work by producing Software change implementation and review brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1252.00, then confirm that the reference is current and applicable. Inspect Software Developer / Software Engineer before drafting.
Context path: bundles/roles/software-developer-software-engineer
What the bundle includes
Frameworks
- source-evidence matrix
- software-change evidence matrix
- qualified-review gate
Evaluations
- Software Developer / Software Engineer source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Codebase-specific work requires current repository, contract, dependency, test, telemetry, and environment evidence.
- This bundle does not prove security or reliability.
- Do not infer code paths, behavior, test outcomes, incidents, or deployment state.
Safety notes
- Protect secrets, credentials, personal data, and proprietary source.
- Require confirmation before destructive changes, migrations, releases, or production actions.
- Route security, privacy, safety-critical, and architectural decisions to qualified reviewers.