Senior Site Reliability Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Formation Bio" (company description) then "About The Position". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: About Formation Bio (company overview) maybe not needed? The instruction says use headings like About the role, Responsibilities, etc. "About Formation Bio" is not one of those headings; but we could treat as "About the role"? Actually "About The Position" is similar to "About the role". So we can use

About the role

and put the description of the position (the paragraph after "About The Position"). We also have Responsibilities (list). We have About You (requirements/qualifications). We have Total Compensation Range: $185,500 - $232,000 (Pay). Also mention equity, benefits, perks but not specific benefits list. So we can include Pay section with that range. Benefits? Not specific list; we have "comprehensive benefits, and generous perks" but not enumerated; we should not create Benefits section unless posting actually states them. It says "comprehensive benefits" but not specific; maybe we can include Benefits section with that statement? The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation range, so Pay is okay. Benefits: they mention "comprehensive benefits, and generous perks" but not enumerated; that might be considered vague. Safer to omit Benefits section. Schedule: they mention hybrid model requiring 3 days per week in office. That's schedule info. So we can include Schedule section with that detail. We also have location info: "Where We Hire" etc. That could be part of Schedule? Not exactly. Could be part of About the role? Might be extra. But we can include a short paragraph for location under About the role or separate? The instruction: only use those headings; we could add a

for location inside About the role or as its own paragraph without heading? Probably we can include location info within About the role paragraph. We must remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, scam-warning, duplicated lines. Also remove "You Can Read More At The Following Links Our Vision for AI in PharmaOur Current Drug PortfolioOur Technology & Platform" etc. Also remove "Formation Bio is an AI-native engineering organization." Actually that's part of About The Position; we keep. We need to preserve all substantive information. So we need to include: - About the role: description of Senior Site Reliability Engineer role: building and operate infrastructure, etc. Also mention AI-native engineering organization, using modern AI tools, partnering with Product Engineering, Data Engineering, Data Science. - Responsibilities: list bullet points. - About You (requirements): list bullet points. - Pay: compensation range. - Schedule: hybrid model 3 days per week in office, location preferences (NYC, Boston, Research Triangle, SF Bay Area). Could also mention willingness to relocate. We should not include "About Formation Bio" company overview? It's substantive but not under allowed headings. Could we treat as "About the role"? No. Could we include as a

without heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings? Safer to stick to those headings only. But we need to preserve all substantive information; if we omit company overview, we lose info. However maybe the company overview is considered boilerplate? It's substantive about Formation Bio. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include it. Where to put? Could be a

before the headings, without a heading. That's allowed: we can have prose

elements not under headings. The instruction only says use

for section headings (e.g. About the role, Responsibilities...). It doesn't say we cannot have other headings, but we should follow that pattern for sections. We can have an introductory

about the company. Thus output:

About Formation Bio ...

then

About the role

...

then

Responsibilities

...

then

About You

...

then

Pay

Total Compensation Range: $185,500 - $232,000

then

Schedule

Hybrid model requiring 3 days per week in office; hiring prioritized in New York City and Boston metro areas, with consideration for Research Triangle (NC) and San Francisco Bay Area applicants; willingness to relocate expected.

We need to ensure we don't include filler like "commensurate with experience". Not present. We need to ensure we don't repeat job title as heading. We didn't. We need to not include Job ID/requisition numbers. We need to remove EEO etc. Let's craft the About Formation Bio paragraph: summarizing the company description: "Formation Bio is a tech and AI driven pharma company differentiated by radically more efficient drug development. Advancements in AI and drug discovery are creating more candidate drugs than the industry can progress because of the high cost and time of clinical trials. Recognizing that this development bottleneck may ultimately limit the number of new medicines that can reach patients, Formation Bio, founded in 2016 as TrialSpark Inc., has built technology platforms, processes, and capabilities to accelerate all aspects of drug development and clinical trials. Formation Bio partners, acquires, or in-licenses drugs from pharma companies, research organizations, and biotechs to develop programs past clinical proof of concept and beyond, ultimately helping to bring new medicines to patients. The company is backed by investors across pharma and tech, including a16z, Sequoia, Sanofi, Thrive Capital, John Doerr, Spark Capital, SV Angel Growth, and others." We can keep that. About the role paragraph: "As a Senior Site Reliability Engineer at Formation Bio, you will build and operate the infrastructure, delivery systems, and operational practices that allow our engineering organization to ship reliable software quickly and safely. You will work across cloud infrastructure, developer platforms, observability, and production workloads, including product applications, internal tools, data systems, and ML and AI workloads, taking problems from initial diagnosis through implementation and production adoption. Formation Bio is an AI-native engineering organization. You will use modern AI tools, including agentic coding systems, as part of your daily engineering practice while applying the judgment needed to validate their output and operate reliable production systems. You will partner closely with Product Engineering, Data Engineering, and Data Science to design, build, and develop the infrastructure and operational platform that supports product software, data systems, and ML and AI workloads, with the opportunity to shape how the broader organization builds and operates AI-native systems." Responsibilities list: each bullet from the posting. Let's extract: - Own the infrastructure and operational platform for shared engineering workloads, including compute, runtime environments, orchestration, deployment, observability, access controls, and reliability. - Build and operate secure, observable, reliable infrastructure for product applications, containerized services, internal tools, data systems, ML pipelines, inference, and agentic software. - Research, develop, and maintain core aws infrastructure and additional cloud outposts for services across development, staging, and production, including compute, networking, databases, load balancers, and secrets management. - Create, review, maintain, and optimize infrastructure as code, CI/CD pipelines, and reusable platform patterns. - Establish strong operational practices, including SLOs, monitoring, alerting, runbooks, incident response, advanced diagnostics, root cause analysis, and post-incident follow-through. - Work with Product engineering, Data Engineering, and Data Science to evaluate, negotiate, and implement architecture and infrastructure for product software, data systems, model training, and inference based on functional requirements - Use AI tools to accelerate infrastructure development, investigate incidents, improve documentation, build automation, and make operational improvements while validating their output. - Participate in the support rotation and incident response. Maintain a strong bias for automation, the patience for ClickOps, and the experience to know when each is appropriate. - Write and review requirements, design documents, and operating procedures. Share knowledge and mentor engineers on infrastructure and SRE fundamentals. About You (requirements) list: - 5+ years of relevant experience in Site Reliability Engineering, infrastructure, systems, DevOps, or a similar discipline. - Production experience operating cloud infrastructure and distributed systems, with strong operational and reliability judgment. - Experience with advanced diagnostics, incident response, root cause analysis, observability, and automation. - Experience with AWS and Snowflake. Experience with Azure, GCP, and/or Vercel is a plus. - Working experience with Docker, GitHub, Kubernetes, Python, Terraform or OpenTofu, and virtual networking. Terragrunt is a plus - Experience supporting production ML or AI workloads, MLOps infrastructure, workflow orchestration, model serving, or a related platform is a plus. - Strong SRE and infrastructure fundamentals are the core requirements. - Experience managing shared COTS and FOSS software applications in addition to our internal software and tools - Daily fluency with AI tools, including LLMs and agentic coding systems, paired with strong engineering judgment and a high bar for validation. - Exceptional collaboration and communication skills across engineering, Data Science, Data Engineering, Security, and non-technical partners. - Experience operating infrastructure in a regulated or validated environment is a plus. Pay: "Total Compensation Range: $185,500 - $232,000". Also mention equity, comprehensive benefits, generous perks but we can keep as a sentence maybe in Pay section? The Pay section could include that sentence: "In addition to base salary, we offer equity, comprehensive benefits, and generous perks." That's substantive. Schedule: "Where We Hire Formation Bio is prioritizing hiring in key hubs, primarily the New York City and Boston metro areas, with a hybrid model requiring 3 days per week in office. Applicants from the Research Triangle (NC) and San Francisco Bay Area may also be considered. Please apply only if you reside in these locations or are willing to relocate." We'll put that in Schedule section. Now ensure we don't include any boilerplate like Equal Opportunity etc. Now output HTML fragment. We'll wrap sections in appropriate tags. Let's craft:

About Formation Bio ...

About the role

As a Senior Site Reliability Engineer ...

Responsibilities

• Own the infrastructure and operational platform for shared engineering workloads, including compute, runtime environments, orchestration, deployment, observability, access controls, and reliability.
• Build and operate secure, observable, reliable infrastructure for product applications, containerized services, internal tools, data systems, ML pipelines, inference, and agentic software.
• Research, develop, and maintain core aws infrastructure and additional cloud outposts for services across development, staging, and production, including compute, networking, databases, load balancers, and secrets management.
• Create, review, maintain, and optimize infrastructure as code, CI/CD pipelines, and reusable platform patterns.
• Establish strong operational practices, including SLOs, monitoring, alerting