Ethos - Senior/Staff DevOps Engineer

• Design & Operate the Platform: Architect, implement, and run secure, scalable, multi-tenant infrastructure (infra as code, immutable artifacts, GitOps). • AI-Augmented Operations & Platform Work: Use AI coding and agentic tools (Claude Code, Cursor, Copilot, MCP-based ops agents) for IaC authoring, pipeline development, log/trace analysis, postmortem drafting, and toil reduction; build and improve agentic workflows for the team. • CI/CD & Release Engineering: Build and harden pipelines (build, test, scan, sign, promote, deploy) for multi-environment delivery—including disconnected/air-gapped workflows. • Observability & Reliability: Establish SLOs; instrument systems for metrics/logs/traces; drive incident response and postmortems; reduce MTTR and change failure rate. • Security & Compliance by Design: Integrate supply-chain security (SBOMs, signing, provenance), secrets management, and baseline hardening (CIS/STIG-aligned). • Cost & Performance: Optimize infrastructure spend and performance (capacity planning, autoscaling, right-sizing, storage/egress strategies). • Technical Leadership: Lead design reviews, author RFCs, mentor engineers, and raise the quality bar for platform changes. • Gov/Constrained Deployments: Support IL-4/IL-5-aligned patterns, RMF documentation support, and offline artifact promotion processes where needed. • (Staff) Strategy & Standards: Define platform roadmaps, establish consistent deployment and infrastructure patterns, and guide cross-team adoption of best practices. • Measures of Success (First 6–12 Months) • Availability & Reliability: Meet or exceed service SLOs; reduce MTTR by ≥30%. • Delivery Velocity: Increase deployment frequency by ≥2× while keeping change failure rate ≤15%. • Pipeline Efficiency: Cut CI pipeline duration by ≥25% and reduce flaky tests significantly. • Security Posture: Achieve ≥95% pass rate for supply-chain/security gates (image signing, SBOM scans, vulnerability thresholds); reduce MTTR for CVEs to ≤14 days for high severity. • Cost & Drift: Deliver ≥15% infra cost savings without performance regressions; keep infra drift near zero via GitOps and policy as code. • Gov/Offline Readiness: Stand up an artifact promotion flow (build → scan → sign → export) suitable for disconnected deployments with documented runbooks. • 30/60/90 Day Plan • First 30 Days — Map & Baseline • Deep-dive on current cloud topology, CI/CD, observability, security controls, and on-call. • Inventory build and runtime artifacts; document deployment environments and promotion paths. • Baseline reliability and delivery metrics (SLOs, MTTR, deploy frequency, CFR, pipeline timing). • Establish and prove the effectiveness of your personal workflow with AI tooling. • 60 Days — Design & Deliver • Harden CI/CD: add SBOM generation, signing (e.g., Cosign/Sigstore), and policy gates. • Implement or refine infrastructure modules (Terraform) and Helm/Kustomize charts with GitOps flows. • Establish service SLOs and golden signals; wire alerts and dashboards for top services. • Pilot artifact export/import flow for air-gapped/disconnected deployments; write runbooks. • 90 Days — Scale & Standardize • Standardize CI/CD pipelines and infrastructure modules across existing services. • Migrate priority services to hardened delivery paths; deprecate legacy workflows. • Land cost/performance wins (e.g., autoscaling policies, instance/storage class right-sizing).