Sr. Site Reliability Engineer

Veeam Software · United States · 1 mo ago

RemoteRemoteEngineering$152k–$253k/yrFull-time

We need to output HTML fragment with sections: About the role (maybe "About The Role" heading), Responsibilities (maybe "What You'll Do"), Requirements/Qualifications (maybe "What You'll Bring"), Benefits (maybe "Why Join?" and "What You'll Get"), Pay (Compensation Transparency), Schedule? Not present. Also maybe "Technologies we work with" could be part of Requirements or separate? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We should not repeat job title. We need to include sections only when posting has real specific content. So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Technologies we work with" could be under Skills or Requirements. But we can include a separate "Technologies" if we want but not in list; better to incorporate into Skills or Requirements. The instruction says prefer few substantive sections over many thin ones. So we can combine. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO etc. So we need to strip those. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. First paragraph: Veeam is the Data and AI Trust Company... This is company overview. Could be part of About the role? Actually "About The Role" heading is present later. The initial paragraph is more about company. Could be part of About the role? Might be considered "About the role" but it's more about company. However we can include it under About the role as introductory prose. Then "About The Role" heading with description. That's content for About the role. Then "What You'll Do" with bullet points (Discovery & Documentation etc). That's Responsibilities. Then "Technologies we work with" list. Then "What You'll Bring" with bullet points (experience etc). That's Requirements/Qualifications/Skills. Then "Bonus Skills" list. Then "Why Join?" paragraph. Then "What You'll Get" list of benefits. Then "Compensation Transparency" with pay ranges. Then EEO etc to remove. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We could have:

About the role

... company overview + role description ...

Responsibilities

... each bullet from What You'll Do ...

Requirements

... maybe combine What You'll Bring and Bonus Skills? But we need separate sections? Could do Requirements (core) and Qualifications (maybe same). But we can combine. Better:

Requirements

... core requirements ...

Skills

... technologies list ...

But the instruction says use those headings as examples; we can use them if we have content. We need to avoid empty sections. We have content for: - About the role: yes. - Responsibilities: yes (What You'll Do). - Requirements: yes (What You'll Bring core). - Qualifications: maybe same as Requirements; but we could skip Qualifications to avoid thin. - Skills: yes (Technologies we work with, plus programming languages, observability, IaC, CI/CD, etc). Could be separate. - Benefits: yes (Why Join? and What You'll Get). Could combine. - Pay: yes (Compensation Transparency). Schedule: not present, so omit. We need to preserve all substantive detail. So we need to include all bullet points from What You'll Do, What You'll Bring, Bonus Skills, Technologies we work with, Benefits list, Pay ranges. We must not include boilerplate like EEO, legal, etc. We need to ensure we don't repeat content. Let's extract each piece. **About the role** content: The initial paragraph plus the "About The Role" section. Initial paragraph: "Veeam is the Data and AI Trust Company, specializing in helping organizations ensure their data and AI are fully understood, secured, and resilient to enable the acceleration of safe AI at scale. As the market leader in both data resilience and data security posture management, Veeam is built for the convergence of identity, data, security, and AI risk. Headquartered in Seattle with offices in more than 30 countries, Veeam protects over 550,000 customers worldwide, who trust Veeam to keep their businesses running. Join us as we go fearlessly forward together, growing, learning, and making a real impact for some of the world’s biggest brands." Then "About The Role" paragraph: "Veeam is building a global SRE function to support the Veeam Data Cloud, our new SaaS platform. This role focuses on our Government and Sovereign Cloud environment. Due to clearance and access requirements, this team operates with restricted access to GOV infrastructure. That means you'll be part of a small team responsible for the full platform stack — including all VDC workloads. You won't always be able to hand off problems to other teams; you need to understand the entire architecture well enough to own it. You'll need to get up to speed on the platform quickly, often by reading code, docs, and architecture artifacts rather than getting direct access to environments from day one. This is a ground-up role — you'll help define how reliability engineering works here by mapping systems, writing runbooks, setting baselines, and building the practices this team will run on going forward." Combine into one

maybe two paragraphs. **Responsibilities** (What You'll Do): It has headings: Discovery & Documentation, Reliability & Incident Response, Observability, Infrastructure & Delivery, Collaboration. Under each heading there are bullet-like sentences. We need to capture each as

. Let's extract: Discovery & Documentation: - Get up to speed on the full platform — all VDC workloads, dependencies, and risk areas. Much of this will happen through code, docs, and conversations rather than direct environment access. - Work with SMEs across the org to fill knowledge gaps and build onboarding material for the team. - Write and maintain runbooks, architecture docs, and operational guides. Reliability & Incident Response: - Design infrastructure for high availability and fault tolerance on Azure (including Azure Government). - Define SLIs, SLOs, and error budgets where none exist today. - Run incident response and blameless postmortems. - Turn incidents into improvements. - Identify reliability risks across modern and legacy workloads and build practical remediation plans that work within compliance constraints. Observability: - Close observability gaps — define instrumentation requirements and drive implementation. - Set alerting, telemetry, and monitoring standards with partner teams. - Build automation to reduce toil and support fleet management. - Participate in on-call rotations. Infrastructure & Delivery: - Work with IaC, CI/CD, deployment automation, and config management — including in air-gapped or compliance-restricted environments. - Build and maintain testing, canary deployment, and release validation pipelines. - Integrate chaos engineering and monitoring tools, adapting choices to meet regulatory requirements. Collaboration: - Work across product, platform, security, legal, compliance, and operations teams. - Own problems end-to-end — identify gaps, drive solutions, don't wait for direction. - Mentor other engineers and help spread SRE practices across the org. We'll put each as

under a single

for any list of duties/requirements/benefits. Could have multiple

Sr. Site Reliability Engineer

About the role

Responsibilities

Requirements

Requirements

Skills

Similar jobs