Site Reliability Engineer II

Key Responsibilities

• Own and evolve the multi-stage deployment pipeline using ArgoCD, including approval gates, promotion policies, and rollback mechanisms.
• Maintain trunk-based branching discipline and enforce release governance standards across the engineering organization.
• Build and maintain CI/CD pipelines that enable safe, frequent, and auditable deployments.

Infrastructure as Code & Cloud Operations

• Provision and manage Azure infrastructure using Terraform or OpenTofu, maintaining drift-free state aligned with GitOps principles.
• Own Kubernetes cluster operations including workload scheduling, resource optimization, RBAC, network policy, and cost governance.
• Identify and act on infrastructure cost optimization opportunities (compute rightsizing, storage tier selection, idle resource elimination).
• Support Crossplane or similar operator patterns for Kubernetes-native infrastructure management where applicable.

Reliability & Observability

• Define, instrument, and enforce SLIs and SLOs in partnership with product engineering teams.
• Build and maintain observability infrastructure – metrics, logs, and distributed traces – using Prometheus, Grafana, OpenTelemetry, or equivalent tooling.
• Conduct proactive capacity planning and performance tuning across multi-tenant, distributed environments.
• Establish and maintain runbooks, dashboards, and alerting policies that reduce cognitive overhead during incidents.

Incident Management

• Participate in shared on-call rotation covering core platform and infrastructure services; on-call load is balanced across the team with structured handoff practices.
• Lead mitigation of live production incidents with a focus on minimizing MTTR and clear stakeholder communication under pressure.
• Facilitate blameless post-incident reviews and drive preventative engineering to closure – not just documentation.

Engineering Partnership

• Embed with product engineering teams during design and architecture phases to establish reliability, scalability, and security requirements before code is written.
• Maintain clear, comprehensive documentation for infrastructure architecture, operational procedures, and onboarding guides.
• Push back constructively when proposed designs compromise reliability or operability, proposing alternatives rather than just raising concerns.

Qualifications

• Experience with Crossplane or other Kubernetes-native infrastructure operators.
• Familiarity with feature flag platforms (LaunchDarkly, Flagsmith, or similar) and gradual rollout strategies.
• Background in IoT, physical security, access control, or other latency-sensitive, event-driven domains.
• Comfort with async collaboration across distributed time zones (US + India team structure).
• Experience with AI-assisted development tooling and an appetite to incorporate it into engineering workflows.
• Knowledge of CMMC 2.0, SOC 2, or FedRAMP compliance postures as they apply to infrastructure and access control.