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
Systems / Infrastructure Engineer (Software)
- Design evidence-grounded infrastructure changes. - Review reliability, capacity, security, interoperability, and cost. - Prepare staged implementation, validation, and rollback plans.
Read the fileOverview
Systems / Infrastructure Engineer (Software) Overview
ONET describes computer systems engineers and architects as designing complex system solutions, integrating systems, monitoring operation, verifying security and scalability, testing.
Read the fileWorkflow
Systems / Infrastructure Engineer (Software) Source-Aware Triage
1. State the requested decision or deliverable. 2. Inventory evidence: architecture and inventory, configuration and infrastructure code, SLO and capacity requirements, identity and network.
Read the fileTemplate
Infrastructure change and reliability 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 Systems / Infrastructure Engineer (Software) work, plus teams reviewing its decisions and outputs
- Teams working in Information technology, Software
When to use it
- A Systems / Infrastructure Engineer (Software) 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 infrastructure changes without fabricated environment facts.
- Connect incidents and SLOs to reviewable improvements.
- Prepare rollback-aware production decisions.
What it helps produce
- Infrastructure change and reliability 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 Systems / Infrastructure Engineer (Software) work by producing Infrastructure change and reliability brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1299.08, then confirm that the reference is current and applicable. Inspect Systems / Infrastructure Engineer (Software) before drafting.
Context path: bundles/roles/systems-infrastructure-engineer-software
What the bundle includes
Frameworks
- source-evidence matrix
- infrastructure-evidence matrix
- qualified-review gate
Evaluations
- Systems / Infrastructure Engineer (Software) source-awareness 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
- Environment-specific work requires current architecture, configuration, policy, telemetry, incident, and cost evidence.
- This bundle does not certify security or availability.
- Do not infer topology, capacity, cost, incident cause, or production state.
Safety notes
- Protect secrets, credentials, network details, and sensitive telemetry.
- Require confirmation before access, infrastructure, network, data, or production changes.
- Route security, continuity, privacy, and compliance decisions to accountable reviewers.