Manager, Site Reliability Engineering

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Delinea" (company description) but we should not repeat job title as heading. We need sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only sections that have real specific content. We need to parse the posting: It has "About Delinea" (company overview). Then "Summary" (role description). Then "What You Will Do" (responsibilities). Then "What You Will Need" (requirements/qualifications). Then "We Would Love to See" (nice-to-have). Then "Why work at Delinea?" (benefits/culture). Then details about benefits: competitive salaries, bonus program, excellent benefits including healthcare insurance, pension/retirement matching, life insurance, EAP, time off plans, paid company holidays. Also mention core values etc. No explicit Pay or Schedule specifics. No explicit schedule mentioned besides on-call participation required, meeting team inside their working hours expectation, willingness to work across time zones. No explicit schedule like full-time, remote, etc. So we may not create Schedule section unless explicit. Pay: not specific numbers, just "competitive salaries". The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: they do state benefits (healthcare insurance, pension/retirement matching, life insurance, EAP, time off plans, paid company holidays). So we can include Benefits section. We also need About the role? The posting includes "Summary" which is a brief description of role. Could treat as About the role. Or we could combine Summary and What You Will Do? But we need headings only when there is real specific content. We'll include: - About the role (from Summary) - Responsibilities (What You Will Do) - Requirements (What You Will Need) - Preferred Qualifications (We Would Love to See) maybe as Skills? But we can treat as Additional Qualifications or Preferred Skills. The allowed headings list includes Skills, Qualifications, Benefits, Pay, Schedule. We can use Qualifications for requirements, and Skills for preferred? Or we could combine requirements and preferred into Qualifications. But we need to preserve all substantive info; we can split into Requirements and Preferred Qualifications using headings not in list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should stick to those headings. So we can map: - About the role: summary. - Responsibilities: What You Will Do. - Requirements: What You Will Need (mandatory). - Skills: We Would Love to See (nice-to-have). - Benefits: Why work at Delinea? (benefits description). We should not include Pay or Schedule as no specifics. We need to remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "About Delinea" company description? That's not about the role; but we might include it as part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The company description "About Delinea" is not a heading we need; we could incorporate into About the role paragraph? But we have separate About the role heading for role summary. The company description could be considered part of About the role? Might be okay to include as a paragraph under About the role. However the instruction says "Preserve ALL substantive information". So we need to keep the company description somewhere. Could put it under About the role as a paragraph before the summary. Or we could create a separate section "About Delinea" but that's not in allowed headings. Better to fold into About the role. Thus About the role section will contain: company description paragraph + summary paragraph. Now we need to format lists: For responsibilities, requirements, skills, benefits we need

• . For prose we use

  . We must not include any markdown fences, just raw HTML. Let's extract content. Company description (About Delinea): "Delinea is a pioneer in securing human and machine identities through intelligent, centralized authorization, empowering organizations to seamlessly govern their interactions across the modern enterprise. Leveraging AI-powered intelligence, Delinea’s leading cloud-native Identity Security Platform applies context throughout the entire identity lifecycle – across cloud and traditional infrastructure, data, SaaS applications, and AI. It is the only platform that enables you to discover all identities – including workforce, IT administrator, developers, and machines – assign appropriate access levels, detect irregularities, and respond to threats in real-time. With deployment in weeks, not months, 90% fewer resources to manage than the nearest competitor, and a 99.995% uptime, Delinea delivers robust security and operational efficiency without compromise. Learn more about Delinea on Delinea.com, LinkedIn, X, and YouTube. Join our passionate, global team at Delinea and help us make the world a safer and more secure place. Our success is driven by world-class product leadership, outstanding engineers, and strategic investment from TPG. We value diversity, innovation, and a culture of respect and fairness. If you're ready to push boundaries and challenge the status quo in security, we want to hear from you. Apply today to help us achieve our mission." We can keep that as a paragraph. Summary: "Delinea is looking for a hands-on Manager of Site Reliability Engineering to lead the SRE and DevOps engineers supporting the Delinea products. This is a working manager role. You will be expected to lead people and lead work: writing and reviewing automation, digging into AKS and Azure telemetry, commanding Sev1 and Sev2 incidents, and improving the observability and deployment practices your team depends on. The initial scope is the Platform SRE and DevOps team. Over time, the role is expected to expand to cover our FedRAMP High environment and the broader Commercial Platform footprint, so comfort operating in a regulated environment and a willingness to grow scope are essential. You will lead a blended team of full-time engineers and contractors distributed across multiple time zones. Meeting your team inside their working hours is an expectation of the role. On-call participation is required." We'll put that as paragraph(s) under About the role. Responsibilities (What You Will Do) list: - Lead hands-on. Spend a meaningful portion of your week in the environment: reviewing pull requests, validating pipeline changes, tuning monitors and dashboards, running queries in Datadog, and troubleshooting production issues alongside your engineers. This role does not sit above the work. - Own availability and performance of the Delinea Platform production environments across Azure and AWS, including AKS workloads, ingress and networking, data services, messaging, and CDN or WAF layers. - Manage a blended team. Hire, onboard, coach, and develop full-time SRE engineers. Direct and manage contractor resources, including scoping work, setting quality expectations, and reviewing deliverables. - Lead a distributed team. Run one-on-ones, standups, and planning sessions at times that work for engineers in other geographies. - Participate in on-call. Carry the pager as part of the rotation, act as incident commander for Sev1 and Sev2 events, drive engagement of the right responders, and own communication cadence with support, engineering, and leadership until resolution. - Command incident response end to end. Own detection, triage, mitigation, customer-facing status communication, and post-incident review. Ensure RCAs are written to a customer-ready standard, preventative actions have owners and target dates, and those actions are driven to closure. - Raise the observability bar. Improve detection coverage so that issues are found by our monitoring rather than by a customer ticket. Own SLI and SLO definition, alert quality and noise reduction, synthetic coverage, APM instrumentation, log hygiene, and dashboard standards. - Support FedRAMP and regulated operations. Grow into supporting our FedRAMP High environment, including change control discipline, evidence collection, boundary awareness, and the operational differences between government and commercial environments. - Reduce toil through automation. Set the expectation that repeat manual work becomes code. Prioritize automation backlog alongside project and reliability work. - Report on operational health. Produce and present incident metrics, trends, and reliability commitments to leadership, and translate them into a concrete improvement plan. We need to keep each as

• . Some sentences are long; we can keep as is. Requirements (What You Will Need) list: - 6+ years in Site Reliability Engineering, DevOps, or Cloud Operations, with demonstrated ownership of production SaaS systems. - 2+ years of direct people leadership, including performance management, hiring, and coaching. - Experience managing contractors or an outsourced delivery team is desired. - Current, hands-on production experience with the Delinea technology stack, including Azure Kubernetes Service, core Azure services (SQL, Redis, Service Bus, Blob Storage), AWS services (SES, EC2, RDS), WAF, Azure DevOps pipelines, Datadog, and Atlassian Jira Service Management. - Hands-on experience across both Azure and AWS is required. You should be able to administer, troubleshoot, and reason about cost and security posture in each. - Deep observability expertise. Demonstrated ownership of an observability framework at scale: metrics, logs, traces, synthetics, SLOs, and alerting strategy. Hands-on proficiency with Datadog or an equivalent platform, including APM trace analysis and log-based troubleshooting. - Proven incident command. You have run major incidents as the incident commander, coordinated multiple responders under pressure, communicated to customers and executives during active impact, and authored the RCA afterward. - Strong cloud networking and security fundamentals: load balancing, DNS, TLS and certificate lifecycle, firewalls, VPN, routing, and identity and access management. - Automation and scripting ability in PowerShell, Python, Bash, or similar, plus practical infrastructure-as-code experience (Terraform, ARM, or Bicep). - Practical experience with multi-region, multi-tenant SaaS architectures, including backup, redundancy, and disaster recovery approaches. - Excellent written communication. You will write and approve customer-facing status updates and incident summaries under time pressure. - Willingness and availability to work across time zones and to participate in an on-call rotation. Skills (We Would Love to See) list: - Direct experience operating in a FedRAMP or other regulated environment (Azure Government, IL4/IL5, SOC 2, ISO 27001). - Experience standing up or maturing an incident management program, including sev definitions, escalation paths, on-call structure, and post-incident review process. - Experience with public status page operations and customer notification practices. - Experience with Atlassian Jira Service Management, Confluence, and Azure DevOps as the operational toolchain. - Track record of reducing customer-detected incidents through improved monitoring coverage. - Cost optimization experience across Azure and AWS on a meaningful scale. Benefits (Why work at Delinea?) list: - Competitive salaries - Meaningful bonus program - Excellent benefits, including healthcare insurance - Pension/retirement matching - Comprehensive life insurance - Employee assistance program - Time off plans - Paid company holidays - Culture of innovation and great career progression - Core values: Spirited, Trust, Respect, Ownership, Nimble, Global (maybe as list) - We take care of our employees. We need to ensure we don't include boilerplate like EEO, etc. The posting includes EEO statement and background check etc. We must remove those. Now construct HTML. We'll start with

  About the role

  then

  company description

  summary

  Then

  Responsibilities