DevOps Engineer

As Senior SRE / DevOps 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 first phase your job is to measure and document what we are inheriting; after that, your job is to operate it reliably while we transfer ownership from the client's team to ours.

First 90 days

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

Ongoing

• Own CI/CD across all services
• Own AWS infrastructure (with Terraform / Pulumi where 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 token spend, AWS rightsizing)
• Implement security baselines (least-privilege IAM, secrets rotation, dependency scanning)

Must-have skills

• 5+ years SRE / DevOps / Platform Engineering in production
• AWS at depth — ECS or EKS, IAM (assume-role patterns, scoped policies), VPC, RDS, ElastiCache, S3, CloudWatch
• Infrastructure-as-code — Terraform (preferred) or Pulumi
• GitHub Actions — building reusable workflows, secret handling, reproducible builds
• Container fundamentals — Dockerfile authoring, multi-stage builds, image hardening
• Linux operations
• 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

Nice-to-haves

• Cost-optimisation discipline (FinOps, 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, TestFlight / Google Play internal tracks
• On-call playbook authoring