Π‘Π°Π΄Π° доступноiOS Β· Android

Π”ΠΎΠ±ΠΈΡ‚ΠΈ Stat Sniper Π°ΠΏΠΏ

Пикови са Π²Π΅ΡˆΡ‚Π°Ρ‡ΠΊΠΎΠΌ ΠΈΠ½Ρ‚Π΅Π»ΠΈΠ³Π΅Π½Ρ†ΠΈΡ˜ΠΎΠΌ, ΠΏΡ€Π°Ρ›Π΅ΡšΠ΅ Ρ€Π΅ΠΊΠ²ΠΈΠ·ΠΈΡ‚Π° ΡƒΠΆΠΈΠ²ΠΎ ΠΈ Π·Π°Ρ˜Π΅Π΄Π½ΠΈΡ†Π° створСна Π·Π° ΠΎΡˆΡ‚Ρ€Π΅ ΠΊΠ»Π°Π΄ΠΈΠΎΡ†Π΅. БСсплатно ΠΏΡ€Π΅ΡƒΠ·ΠΈΠΌΠ°ΡšΠ΅.

← All open roles

Senior DevOps Engineer

InfrastructureRemote (worldwide)Full time

Own the platform everything else runs on. We are genuinely multi-cloud: Kubernetes, Cloud Run, Cloud SQL, and Pub/Sub on GCP, alongside ECS Fargate, DynamoDB, and S3 on AWS β€” serving a mobile app, a web app, and a content site that cannot afford to be slow or down during a live slate. You'll make deploys boring, make failures visible, and keep the bill proportionate to the traffic.

What you'll do

  • Run and tune Kubernetes (GKE and EKS) plus serverless container workloads on Cloud Run and ECS Fargate.
  • Own the data layer's operations: Cloud SQL and Postgres tuning, backups and failover, DynamoDB capacity and cost.
  • Manage S3 and Cloud Storage lifecycle, encryption, and IAM so storage stays cheap and correctly locked down.
  • Own CI/CD end to end so a merge reaches production safely without a human in the loop.
  • Build the observability layer β€” metrics, logs, traces, alerts that fire on user impact, not on noise.
  • Manage infrastructure as code across both clouds, and treat cloud spend as an engineering metric.

What we're looking for

  • Senior experience operating production workloads on both AWS and GCP, or deep expertise in one and real fluency in the other.
  • Real Kubernetes operations experience β€” autoscaling, resource limits, rollouts, and debugging a wedged node β€” not just authoring manifests.
  • Hands-on with Fargate, S3, and DynamoDB on AWS, and Cloud Run, Cloud SQL, and Pub/Sub on GCP.
  • Infrastructure as code (Terraform or similar) and container build pipelines you have owned.
  • Security fundamentals: secret management, least-privilege IAM, and a credential that never reaches a client bundle.

Nice to have

  • You have cut a cloud bill substantially without degrading the product, and can say exactly how.
  • Experience with a traffic pattern that spikes on a schedule someone else sets β€” like a kickoff time.
  • Incident-response practice: you write the postmortem and the fix lands.

What you'll work with

KubernetesTerraformCloud RunECS FargateCloud SQLDynamoDBS3

How hiring works

1. ApplyEmail careers@statsniper.com with the role in the subject line, your resume or GitHub, and a short note on what you'd want to own.
2. Intro callA 30-minute conversation about your background, what you're looking for, and what the role actually involves day to day.
3. Working conversationA working session on a real problem from our domain. No algorithm trivia and no unpaid take-home project.
4. OfferA final conversation with the founding team, then a decision. We aim to go from first email to offer in under two weeks.

Interested?

Email us with Senior DevOps Engineer in the subject line, your resume or GitHub, and a short note on what you'd want to own. We reply to everyone.

Apply for this role

Other open roles

Π‘ΠΏΡ€Π΅ΠΌΠ½ΠΈ Π΄Π° Π·Π°ΠΏΠΎΡ‡Π½Π΅Ρ‚Π΅?

ΠŸΡ€Π΅ΡƒΠ·ΠΌΠΈ Stat Sniper ΠΈ ΠΏΠΎΡ‡Π½ΠΈΡ‚Π΅ Π΄Π° ΠΏΠΎΠ±Π΅Ρ’ΡƒΡ˜Π΅Ρ‚Π΅ данас.

Ова страница јС аутоматски ΠΏΡ€Π΅Π²Π΅Π΄Π΅Π½Π° ΠΈ ΠΌΠΎΠΆΠ΄Π° садрТи Π³Ρ€Π΅ΡˆΠΊΠ΅ ΠΈΠ»ΠΈ Π³Ρ€Π΅ΡˆΠΊΠ΅ Ρƒ ΠΊΡƒΡ†Π°ΡšΡƒ.