Site Reliability Engineering Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like cookie/navigation/legal/EEO etc. Must not include sections with filler like "commensurate with experience". We need to extract content from posting.
Let's parse the posting:
- Intro: "Consequential Work. Dedicated People. About Onebrief Onebrief builds collaboration and AI-powered workflow software for military planning and operational coordination...." This is about company. Not a section heading but could be considered "About the company". Not required heading list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include "About the role" as heading for the role description. The "About Onebrief" could be placed maybe as a paragraph before sections? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings? It says use for section headings (e.g. those). Likely we should only use those headings if we have content. Could also include "About Onebrief" as a paragraph without heading? Probably we can include it as a
for section headings (e.g. those). Likely we should only use those headings if we have content. Could also include "About Onebrief" as a paragraph without heading? Probably we can include it as a
before sections. We must not repeat job title as heading. Job title is "Site Reliability Engineering Manager". Not to be used as heading. We need sections: - About the role: content from "About The Role" paragraph. - Responsibilities: from "What You'll Do" bullet list. - Requirements: from "What We Look For" list (including clearance, years experience, etc). Could also include "Technical background:" etc as part of Requirements or Skills? Might split into Requirements and Skills. The instruction: Use headings for those categories if we have content. We can have Requirements (including experience, clearance, etc) and Skills (technical background). Or combine. - Benefits: The posting mentions relocation assistance, maybe other benefits? It says "Onebrief provides relocation assistance." Also mentions investors etc but not benefits like health. No explicit benefits besides relocation assistance. Should we include Benefits section only if posting actually states them. It does state relocation assistance. So we can include Benefits with that. - Pay: Not mentioned. No pay info. So omit Pay section. - Schedule: Not mentioned. Omit. - Qualifications: Could be similar to Requirements. Might combine. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: The "Notice to Third Party Recruitment Agencies" etc is boilerplate; remove. Also remove "Security Clearance, Location, and Onsite Notice" maybe part of Requirements? It says: "This role requires regularly working on-site at customer locations. If you are not currently within commuting distance, you must be willing to relocate. Onebrief provides relocation assistance. Active Secret Clearance Required." That's location/clearance info. Could be part of Requirements. We need to preserve all substantive information. So include that. Now produce HTML: Start with maybe a
about Onebrief (intro). Then
About the role
...
ThenResponsibilities
- ... each bullet from "What You'll Do". Need to capture each bullet.
Let's extract bullets from "What You'll Do":
- Lead and develop the SRE team: Hire, coach, and support engineers across infrastructure, operations, and application reliability. Set expectations, manage performance, support career development, and build the skills and coverage the team needs.
- Own capacity and work planning: Maintain a clear view of incoming requests, ongoing support needs, and planned engineering work. Break initiatives into manageable tasks with the team, establish ownership, sequence work, and adjust commitments as priorities or capacity change.
- Coordinate delivery across teams: Manage dependencies with platform engineering, application engineering, security, and customer success. Identify blockers early, resolve competing priorities, and communicate progress, risks, and decisions to stakeholders.
- Set the reliability roadmap: Translate customer needs, production data, incident patterns, and operational risks into a prioritized improvement plan. Protect capacity for work that reduces recurring failures and makes deployments easier to operate.
- Establish operational ownership: Ensure production deployments have clear support responsibilities, escalation paths, and readiness criteria. Plan with partner teams for new deployments, releases, and ongoing customer support.
- Support team-led incident response: Establish sustainable on-call coverage and clear incident response expectations. Coach engineers who serve as incident commanders and lead blameless postmortems / After Action Reviews (AARs). Help the team assess corrective actions, assign ownership, and schedule follow-through.
- Guide technical priorities: Work with engineers and technical leads to evaluate approaches to infrastructure, automation, observability, and application reliability. Ensure plans account for operability, security requirements, and the constraints of on-prem and air-gapped environments.
- Make reliability and workload visible: Guide the team's use of SLIs, SLOs, and operational metrics. Use service health, support demand, and delivery progress to explain where investment is needed and whether improvements are working.
- Reduce operational toil: Give engineers time and support to automate repetitive deployment, maintenance, troubleshooting, and recovery work. Help turn lessons from individual customer environments into reusable improvements.
Now Requirements/Qualifications: from "What We Look For" and preceding lines.
List:
- An active Secret clearance
- 5+ years in Site Reliability Engineering, Platform Engineering, DevOps, or a related role, with substantial infrastructure and operations experience
- Experience directly managing engineers, including coaching, performance management, career development, and hiring
- Experience planning team capacity, prioritizing competing requests, and coordinating engineering work across teams
- A track record of delivering reliability improvements while managing ongoing operational responsibilities
- Experience with incident response and post-incident review practices, including helping engineers develop leadership and ownership
- Technical judgment sufficient to evaluate engineering proposals, understand operational risks, and guide prioritization
- Clear communication, including the ability to explain constraints and negotiate scope, timing, and commitments with stakeholders
- Technical background: You should have practical experience operating production systems and enough breadth to guide engineers working across these areas:
- Infrastructure and automation: Infrastructure as Code, configuration management, and scripting, using tools such as Terraform, Ansible, Python, Go, or Bash
- Containers and orchestration: Kubernetes deployment, troubleshooting, and operations
- Delivery practices: CI/CD pipelines, release safety, and repeatable deployments
- Cloud and on-prem environments: Operating software across AWS or AWS GovCloud and customer-managed infrastructure
- Observability: Monitoring, logging, and actionable alerting using tools such as the Grafana stack, ELK, or Datadog
- Networking and security: Core protocols, secure configuration, and connectivity troubleshooting
- Application reliability: Working with software engineers to diagnose application failures and evaluate infrastructure or code changes
- We value depth in relevant areas and the ability to guide specialists across the rest.
- Bonus points (nice to have):
- Experience leading teams supporting mission-critical customer deployments
- Experience managing engineering programs or coordinating delivery across multiple customer environments
- Experience operating in DoD, classified, or air-gapped environments
- Familiarity with RMF, STIGs, and ICD 503
- Experience implementing SLIs, SLOs, and error budgets for distributed systems
- GitOps practices and toolchains
- On-prem virtualization experience with VMware, Proxmox, Nutanix, Hyper-V, or similar platforms
- Application development experience, especially TypeScript or Node.js
- Relevant certifications, such as AWS DevOps Engineer or CKA/CKAD
- Active Security+ or another DoD 8570.01-approved security credential, or the ability to obtain one within 3 months of employment
Also location/clearance notice: "This role requires regularly working on-site at customer locations. If you are not currently within commuting distance, you must be willing to relocate. Onebrief provides relocation assistance. Active Secret Clearance Required."
We already have Active Secret Clearance in requirements; location/relocation can be in Benefits or Requirements. We'll put relocation assistance in Benefits.
Now Benefits: "Onebrief provides relocation assistance." Possibly also mention "Some team members work remotely, while others work directly alongside customers in operational environments around the world." That's more about work arrangement but not benefit. We'll keep relocation assistance.
Now we need to avoid duplication: The Active Secret Clearance appears both in notice and requirements; we should include once.
Now produce HTML.
Structure:
About Onebrief ...
About the role
... (the About The Role paragraph)
Responsibilities
- ...
Requirements
- ...
Skills
for technical background list. But we could incorporate technical background into Requirements as sub-bullets. However instruction: Use headings for sections like Skills if we have content. We have technical background list; could be Skills. Thus:Skills
- ... technical background items ...
Bonus Qualifications
but not in allowed headings list. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Bonus points not listed; we could incorporate into Requirements or Qualifications. Better to put under Requirements as additional bullet points. Qualifications heading also allowed. Could use Qualifications for the experience/clearance etc, and Skills for technical background. Let's do:Qualifications
- ... core qualifications (clearance, years experience, managing engineers, capacity planning, track record, incident response, technical judgment, communication)
Skills
- ... technical background list ...
. Now About The Role paragraph: "We're hiring a Site Reliability Engineering Manager to lead our SRE team within Infrastructure & Security. You'll work closely with platform engineering, application engineering, security, and customer success to ensure Onebrief's mission-critical deployments are reliable, secure, and well supported across on-prem DoD and AWS environments. You'll lead a team whose work spans customer-facing operations, infrastructure, observability, automation, and application reliability. Most of the team focuses on deploying and operating Onebrief in demanding customer environments. You'll own the team's priorities, planning, execution, and development. A significant part of this role is coordinating work: understanding demand, balancing capacity, sequencing tasks, managing dependencies, and keeping commitments realistic as customer needs change. You'll help the team