FedRAMP now defines compliance as a set of Key Security Indicators (KSIs); measurable security outcomes that automation validates continuously. Holding an estate at that standard day after day is an operations job. Coalfire organizes its delivery engineering into capability-focused teams, and the Run teams keep authorized client environments available and provably compliant long after the build team leaves. As a Senior Site Reliability Engineer you own one operational capability, such as remidation, monitoring and alerting or backup and recovery, and you design how Coalfire observes a client estate and holds it in a compliant state. You own the automation and the procedure that each managed environment inherits, you carry escalation for the hardest operational problems, and you set and continually raise the engineering bar for the engineers around you. If you are driven by a desire to innovate, excel at operational excellence, and thrive in a collaborative environment, come be part of a team committed to making the world a more secure and complaint place.
Own one operational capability for the managed estate, such as monitoring and alerting or backup and recovery, including its automation, its runbooks, and the service standard each managed environment inherits.
Design how Coalfire observes a regulated cloud environment: telemetry and log pipelines, service-level objectives, alert quality, and the escalation paths behind them. Make alerts useful and actionable.
Build and maintain the continuous-monitoring evidence pipeline so you can prove the authorized state each day, in machine-readable form where the framework allows it.
Own backup and recovery engineering for your capability: recovery procedure you have tested, recovery objectives you can measure, and the automation that runs them during an outage.
Serve as the senior escalation point in client environments. Diagnose and troubleshoot beyond the runbook, resolve the incident, then fix the runbook so the next engineer on call does not repeat the diagnosis.
Lead incident and problem management for your domain, including incident command on major events, blameless post-incident review, and corrective action that closes the problem out.
Automate operational toil out of the estate with infrastructure-as-code, pipelines, and scripting. Decide what Coalfire automates once for the whole estate and what stays specific to one client.
Partner with Engagement Architects and the Build teams on transition into managed operations: operational readiness review, monitoring and runbook coverage, and the service commitments Coalfire can meet at go-live.
Hold on-call for your capability and improve the rotation: coverage, alert actionability, and the load it places on the team.
Represent operational posture in front of clients, and support renewals and expansions with a credible account of what Coalfire operates for them and at what cost.
Mentor and lead Site Reliability Engineers and junior staff: review designs as well as changes, set operational standards, and grow named individuals in your domain.
Author and peer review code, runbooks, operational design documentation, and the compliance artifacts that evidence continuous monitoring, inclusive of vendor best practices.
Automation-first mindset with deep Infrastructure-as-Code (Terraform or equivalent), CI/CD, and scripting (Python, Go, or similar); working use of policy-as-code
Deep operational command of at least one major cloud platform (AWS, Azure, or GCP) and its native monitoring, logging, and recovery services, with working knowledge of a second
Observability engineering depth: metrics, logging and log pipelines, distributed tracing, SLI and SLO definition, and alert design that produces action
Demonstrated incident response and incident command capability, and the discipline to convert a resolved incident into automation or procedure
Backup, recovery, and resilience engineering, including tested recovery procedure against stated recovery objectives
Working command of NIST 800-53, FedRAMP, or comparable security control frameworks, and the judgment to map continuous-monitoring obligations to real operational design
Ability to lead technical conversations with clients about operational posture, risk, and trade-offs with both engineers and executives
The instinct to solve a problem once and package the solution so it works across the managed estate
Demonstrated ability to mentor engineers and improve the output of a team
Excellent communication, organizational, and problem-solving skills
Effective documentation skills, including technical diagrams, runbooks, and written descriptions
Ability to work independently and as part of a team with a professional attitude and demeanor
Critical thinking, and the ability to balance security and availability requirements against mission needs
BS or above in a related Information Technology field or equivalent combination of education and experience
5+ years in site reliability engineering, cloud operations, platform engineering, or managed services
5+ years operating production cloud environments in AWS, Azure, or GCP, including monitoring, incident response, and automation
Demonstrated experience owning an operational capability, monitoring platform, or reusable automation used by multiple teams or clients
Experience as the senior operational escalation point on client-facing managed services, including incident command on major events
Advanced experience with Infrastructure-as-Code and orchestration/automation tools such as Terraform and Ansible
Experience transitioning environments from build into steady-state operations
✓Own one operational capability for the managed estate, such as monitoring and alerting or backup and recovery, including its automation, its runbooks, and the service standard each managed environment inherits.
✓Design how Coalfire observes a regulated cloud environment: telemetry and log pipelines, service-level objectives, alert quality, and the escalation paths behind them. Make alerts useful and actionable.
✓Build and maintain the continuous-monitoring evidence pipeline so you can prove the authorized state each day, in machine-readable form where the framework allows it.
✓Own backup and recovery engineering for your capability: recovery procedure you have tested, recovery objectives you can measure, and the automation that runs them during an outage.
✓Serve as the senior escalation point in client environments. Diagnose and troubleshoot beyond the runbook, resolve the incident, then fix the runbook so the next engineer on call does not repeat the diagnosis.
✓Lead incident and problem management for your domain, including incident command on major events, blameless post-incident review, and corrective action that closes the problem out.
✓Automate operational toil out of the estate with infrastructure-as-code, pipelines, and scripting. Decide what Coalfire automates once for the whole estate and what stays specific to one client.
✓Partner with Engagement Architects and the Build teams on transition into managed operations: operational readiness review, monitoring and runbook coverage, and the service commitments Coalfire can meet at go-live.
✓Hold on-call for your capability and improve the rotation: coverage, alert actionability, and the load it places on the team.
✓Represent operational posture in front of clients, and support renewals and expansions with a credible account of what Coalfire operates for them and at what cost.
✓Mentor and lead Site Reliability Engineers and junior staff: review designs as well as changes, set operational standards, and grow named individuals in your domain.
✓Author and peer review code, runbooks, operational design documentation, and the compliance artifacts that evidence continuous monitoring, inclusive of vendor best practices.
✓Automation-first mindset with deep Infrastructure-as-Code (Terraform or equivalent), CI/CD, and scripting (Python, Go, or similar); working use of policy-as-code
✓Deep operational command of at least one major cloud platform (AWS, Azure, or GCP) and its native monitoring, logging, and recovery services, with working knowledge of a second
✓Observability engineering depth: metrics, logging and log pipelines, distributed tracing, SLI and SLO definition, and alert design that produces action
✓Demonstrated incident response and incident command capability, and the discipline to convert a resolved incident into automation or procedure
✓Backup, recovery, and resilience engineering, including tested recovery procedure against stated recovery objectives
✓Working command of NIST 800-53, FedRAMP, or comparable security control frameworks, and the judgment to map continuous-monitoring obligations to real operational design
✓Ability to lead technical conversations with clients about operational posture, risk, and trade-offs with both engineers and executives
✓The instinct to solve a problem once and package the solution so it works across the managed estate
✓Demonstrated ability to mentor engineers and improve the output of a team
✓Excellent communication, organizational, and problem-solving skills
✓Effective documentation skills, including technical diagrams, runbooks, and written descriptions
✓Ability to work independently and as part of a team with a professional attitude and demeanor
✓Critical thinking, and the ability to balance security and availability requirements against mission needs
✓BS or above in a related Information Technology field or equivalent combination of education and experience
✓5+ years in site reliability engineering, cloud operations, platform engineering, or managed services
✓5+ years operating production cloud environments in AWS, Azure, or GCP, including monitoring, incident response, and automation
✓Demonstrated experience owning an operational capability, monitoring platform, or reusable automation used by multiple teams or clients
✓Experience as the senior operational escalation point on client-facing managed services, including incident command on major events
✓Advanced experience with Infrastructure-as-Code and orchestration/automation tools such as Terraform and Ansible
✓Experience transitioning environments from build into steady-state operations