DevOps Engineer

As Senior SRE / Dev Ops Engineer you own everything from CI to production: build pipelines, infrastructure-as-code, deploy automation, observability, on-call response, cost control,secrets management, and security baselines. In the firstphaseyour job is to measure and document what we are inheriting; after that, your job is tooperateit reliably while we transfer ownership from the client's team to ours.

• Audit the existing CI/CD on Git Hub Actions.
• Audit AWS infrastructure: ECS or EKS topology, IAM posture, VPC layout, RDS,Elasti Cache, S3
• Audit Datadog: which dashboards exist,what'stracked, where the gaps are, SLO/SLI definitions
• Audit incident history past 12 months — count, severity, MTTR, root-cause patterns
• Build the vendor inventory (Auth0, One Signal, Eleven Labs, OpenAI, Branch, Amplitude, Terra, Strava, Crashlytics) — owners, billing, MFA, recovery plans

• Own CI/CD across all services
• Own AWS infrastructure (with Terraform /Pulumiwhere it makes sense)
• Set up the on-call rotation when we take production ownership
• Lead incident response and post-mortems
• Build cost-control discipline (especially OpenAI tokenspend, AWS rightsizing)
• Implement security baselines (least-privilege IAM, secrets rotation, dependency scanning)

• 5+ years SRE / Dev Ops / Platform Engineering in production
• AWS at depth — ECS or EKS, IAM (assume-role patterns, scoped policies), VPC, RDS,Elasti Cache, S3, Cloud Watch
• Infrastructure-as-code — Terraform (preferred) or Pulumi
• Git Hub Actions — building reusable workflows, secret handling, reproducible builds
• Container fundamentals —Dockerfileauthoring, multi-stage builds, image hardening
• Linuxoperations
• Datadog in production — logs, APM, metrics, dashboards, monitors, SLO/SLI definition
• Incident response — leading or co-leading real production incidents, writing post-mortems
• Observability for both Node.js and Python services
• Secrets management — AWS Secrets Manager, SOPS, or comparable
• Working English

• Cost-optimisationdiscipline (Fin Ops, AWS Cost Explorer, Reserved Instance planning)
• LLM cost monitoring (per-route OpenAI token spend dashboards)
• Kubernetes specifically (we may or may not be on EKS)
• Security baseline experience — CIS benchmarks, dependency scanning (Snyk,Dependabot), SAST tools
• GDPR / data-residency considerations for cross-border data flows (US PL)
• Mobile CI considerations — Fastlane, app-signing automation, Test Flight / Google Play internal tracks
• On-callplaybookauthoring