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
Back-End Developer source-backed Guide
Defines source-backed back-end engineering, evidence handling, and action boundaries.
Read the fileOverview
Back-End Developer overview
Use this bundle to prepare source-backed back-end engineering analysis and a review-ready back-end engineering delivery brief.
Read the fileWorkflow
Back-End Developer source-backed triage
1. State the requested decision or artifact. 2. Inventory evidence: requirements and acceptance criteria; runtime, framework, repository, and environment versions; API contracts and.
Read the fileTemplate
back-end engineering delivery brief
Review-ready artifact for back-end engineering, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Back-End Developer work, plus teams reviewing its decisions and outputs
- Teams working in Software engineering, Technology
When to use it
- A Back-End Developer 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
- Prepare a back-end engineering delivery brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready recommendation with explicit verification and approval boundaries.
What it helps produce
- back-end engineering delivery 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 Back-End Developer work by producing back-end engineering delivery brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1254.00, then confirm that the reference is current and applicable. Inspect Back-End Developer source-backed Guide before drafting.
Context path: bundles/roles/back-end-developer
What the bundle includes
Frameworks
- source-evidence matrix
- back-end engineering review matrix
- qualified-review gate
Evaluations
- Back-End Developer 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
- Use the cited official, originator, standards, or professional sources for general back-end engineering context; local facts, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for requirements and acceptance criteria; runtime, framework, repository, and environment versions; API contracts and authentication; data models, migrations, and retention; dependencies and security findings; tests, observability, deployment, and rollback evidence.
- Do not infer API behavior, authorization, schema compatibility, test results, performance, or production state.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, and other sensitive data.
- Require explicit confirmation before deploying code, changing schemas or access, rotating secrets, or modifying production.
- Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to an evidenced accountable reviewer.