DevOps Manager, Platform

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. The posting includes description about role, responsibilities, pay, benefits. No explicit "Requirements" or "Qualifications" or "Skills" separate; but we can embed within responsibilities? The instruction: include a section ONLY when posting has real, specific content for it. So we need to parse content: There's an introductory paragraph describing role, then "Starting base pay..." then benefits description. Then "Responsibilities" heading appears in the text: "Responsibilities What this team runs:" etc. So we have a Responsibilities section with detailed bullet-like paragraphs. Also there is mention of "Key responsibilities:" then sub-bullets. We'll need to format as

• for any list of duties/requirements/benefits. The responsibilities are in prose but we can break into list items for each bullet point. The posting includes many paragraphs; we can convert each distinct duty into
• . Also benefits: "This role will be eligible for a bonus as well as competitive medical, dental, and vision benefits, wellness reimbursement, life insurance, and a 401(k) with company match. We offer vacation and sick leave benefits (under a flexible time off policy in most states)." So we can create Benefits section with list items. Pay: Starting base pay range $145,000-$185,000, plus note about dependent factors, bonus eligibility. So Pay section with maybe a

  describing range and note. Schedule: Not mentioned. So omit. About the role: The initial paragraph(s) before responsibilities can be used as About the role. Let's extract: "A great platform team is defined not by how many tickets it closes, but by how little friction stands between an engineer's idea and a running service, because the team built the pipelines, golden paths, and AI-augmented workflows that make delivery self-service. The DevOps Manager, Platform is the people leader and hands-on technical operator who makes that true at Origami Risk. This manager leads the team that builds, runs, and continuously improves the developer platform and delivery automation that Engineering teams depend on to ship every day, spanning CI/CD pipelines and shared templates, service-layer Terraform, the EKS container platform and capabilities golden path, application connectivity and service data stores, environment promotion, and the AI tooling layered on top. Everything runs in AWS, on top of the landing zone the Cloud Infrastructure team owns. This is a hands-on technical leader who coaches Engineers on platform-engineering craft, sets a high bar for delivery reliability and operational discipline, drives AI adoption into daily DevOps workflows, and partners with Engineering, Release, SRE, and Cloud Infrastructure so that the path to production is a source of competitive advantage and not a constraint on what Engineering can deliver. On this team, manual work is a problem to be solved, automation is the default, and every Engineer is expected to use AI to work faster and diagnose more accurately." That's good for About the role. Now Responsibilities: We have many bullet-like items under "Key responsibilities:" with subheadings: People Leadership & Team Development, Developer Platform & Delivery Operations, Pipelines, Build & Release Support, Service IaC & Container Platform, AI-Augmented DevOps Operations, Service Observability & Incident Response, Security, Compliance & Access Management, Cross-Functional Collaboration & Stakeholder Management. We can treat each as a list item with maybe nested list? But instruction: Use

  • for any list of duties/requirements/benefits. So we can create a
    with each top-level responsibility as
    • . Inside each we can have further detail as

      or nested

      ? Probably okay to keep as
      • containing

        and maybe nested

        . But to keep simple, we can make each bullet a
        • with the description as text (maybe line breaks). We'll need to preserve all substantive information; not invent or summarize away detail. So we need to include the details from each subsection. We'll need to extract each subsection's content. Let's parse: People Leadership & Team Development: - Leads, develops, and retains a team of DevOps Engineers building the developer platform, cultivating a high-performance culture defined by technical excellence, an automation mindset, and operational ownership. - Sets clear goals, role expectations, and success criteria for each engineer; conducts regular 1:1s and gives direct, constructive feedback with a visible path for growth. - Conducts structured performance reviews that recognize strong delivery contributions, address quality or reliability gaps specifically, and grow both AI fluency and platform-engineering depth. - Identifies capability gaps across the team, encompassing CI/CD, service-layer Terraform, container orchestration and EKS, API and connectivity patterns, and AI-assisted operations, while building targeted hiring, upskilling, and cross-training plans. - Fosters a culture where every manual process is a temporary state, automation is the permanent solution, and AI tooling is an expected part of how each engineer works. - Supports Engineering hiring across the organization by participating in technical interviews and helping calibrate the platform-engineering bar. Developer Platform & Delivery Operations: - Owns the end-to-end path from “we are building a service” to “it deploys to production on its own pipeline”, repository scaffolding, ECR, Terraform workspace, pipeline, variable groups, secrets paths, hostname, gateway wiring, and alarms, reducing the elapsed time and ownership ambiguity in new-service onboarding. - Leads the team's service-layer infrastructure-as-code practice, ensuring IaC stacks are defined, versioned, peer-reviewed, and deployed through Terraform on S3 and DynamoDB backends, with manual changes treated as exceptions to be immediately codified. - Oversees the shared pipeline templates consumed org-wide, enforcing the additive-only change policy so new parameters carry safe defaults and template changes never break existing consumers. - Sets and enforces the naming and structural standards the delivery path depends on, ECR repositories, variable groups, Kubernetes ServiceAccounts, secret paths, and private hostnames, because they are what make onboarding repeatable. - Drives service-level cost efficiency as a continuous discipline, right-sizing service stacks, OpenSearch Serverless OCU caps, ECR lifecycle policies, and idle-stack cleanup. - Operates within the Cloud Infrastructure team's landing zone, guardrails, and shared platforms rather than owning them, keeping clean boundaries between service delivery and the estate. Pipelines, Build & Release Support: - Owns the per-service Azure DevOps build and deploy pipelines, build, test, scan, containerize, push, deploy, and the environment gates between them, as the team's highest-volume recurring duty. - Holds the team accountable for container image discipline, immutable tags and distinct hotfix tags, ECR repository definitions, and lifecycle policies, so a redeploy can never silently pull a different image. - Owns the environment promotion model, feature branch to main, one pipeline per repository gated per environment, and immutable-tag promotion with roll-forward by default, across the full environment ladder. - Builds the CI/CD pipelines the Release team runs, and trains and supports that team to operate them, how a promotion is gated, how to approve or retry a stage, how to read a failure, and when to escalate back to DevOps versus the service owner. - Coaches Engineers to diagnose and eliminate the root causes of flaky, intermittent delivery failures rather than treating them as acceptable operational noise. Service IaC & Container Platform: - Oversees the EKS platform layer, add-ons, workload identity through Pod Identity and IRSA, namespaces, NetworkPolicies, and the golden-path add-ons, and multi-environment service onboarding. - Owns the golden path, the zero-touch onboarding path for services, the shared token-gateway authorizer, and Helm support, so a new feature/capability needs no bespoke infrastructure work. - Oversees deployment automation for containerized services, Lambda functions, ECS tasks, and EKS workloads, ensuring patterns are consistent, traceable, and recoverable across environments. - Owns application connectivity, API Gateway in REST and HTTP forms and public and private, Lambda authorizers, per-service DNS records and ACM certificates inside delegated zones, and ExternalDNS, along with end-to-end debugging of gateway-path failures. - Provisions the service data stores that belong to a stack, application S3, SSM configuration, Secrets Manager entries, and Aurora/RDS with DDL and Flyway pipelines, handing ongoing database operations to the Database team. AI-Augmented DevOps Operations: - Drives adoption of AI development tools, including Claude Code and Cursor, across the team's daily workflow, establishing norms for AI-assisted IaC authoring, pipeline authoring, automation scripting, and operational documentation. - Builds and operates internal AI tooling across the software development lifecycle, intake, design, implementation, review, CI/CD, and operations, so product and engineering teams can move faster. - Champions AI-assisted operations as a management discipline, integrating AI-powered log analysis, anomaly detection, runbook generation, and LLM-augmented incident analysis into workflows that reduce mean time to diagnosis. - Uses AI to accelerate the team's most demanding work, service onboarding, Terraform scaffolding, pipeline authoring, and operational diagnosis, and shares effective patterns with engineering leadership. - Holds team members accountable for AI tool adoption and proficiency, incorporating AI fluency into performance conversations, development plans, and hiring criteria. Service Observability & Incident Response: - Leads the team's ownership of service observability wiring, CloudWatch log groups, metrics, and traces defined in each service's Terraform, with retention and high-volume log control at the service level, and confirms a new or promoted service emits telemetry before it is handed to SRE. - Keeps clean boundaries with the observability platforms themselves, New Relic, Datadog, Sumo Logic, and Langfuse, which Cloud Infrastructure operates, and with monitor, alert, and dashboard design, which SRE owns, positioning the team as the integration point rather than the on-call owner of those views. - Owns the team's response to delivery-path and service-stack incidents, failed deploys, gateway and connectivity faults, image and task-definition problems, and environment configuration drift, and establishes quickly when an incident is not the team's and hands off with evidence. - Leads blameless post-incident reviews, produces structured root cause analyses, and owns follow-through on corrective actions that prevent recurrence. - Tracks delivery reliability metrics, deployment frequency, change failure rate, lead time, and mean time to recovery for the delivery path, reporting trends and improvement actions to the Director of DevOps. Security, Compliance & Access Management: - Holds the team accountable for the security controls it owns within the delivery path, workload IAM roles scoped to a single service stack, secret paths, container image scanning, and network-policy enforcement, operating within the guardrails, SCPs, and permission boundaries Cloud Infrastructure sets. - Partners with Application Security Engineers to integrate infrastructure-level controls, container scanning, secrets management, and network-policy enforcement, into the automation workflows the team owns. - Ensures pipeline and platform access is timely, least-privilege, regularly reviewed, and audit-ready, service connections, OIDC role mappings, and repository and pipeline permissions. - Supports audit readiness and evidence collection for SOC 2, ISO/IEC 27001, and NIST 800-53, maintaining accurate records of pipeline configurations, access grants, and change history for the systems the team owns. Cross-Functional Collaboration & Stakeholder Management: - Serves as the primary delivery partner to Engineering and capability teams, providing platform consultation during system design and ensuring services are operationally sound and reliably deployable. - Collaborates with the Release and Engineering Systems teams on pipeline governance, release planning, and deployment coordination, ensuring the delivery path is validated and ready before promotion. - Partners with the Cloud Infrastructure team on the shared boundaries between service delivery and the landing zone, the delivery toolchain, EKS placement, IAM roles, and application DNS and secrets, keeping ownership explicit so requests do not stall between (cut off). We'll keep as is. Now Benefits: