SRE

  • Full-time
  • Hybrid · Gurugram
  • Engineering · DevOps / Infra

About the role

You will make reliability something we measure, not something we hope for. You will set how services are monitored, how incidents are run and how we learn from them.

What you'll do

  • Define SLOs, SLIs and error budgets with each team and track them
  • Build monitoring, logging, tracing and alerting that people trust
  • Lead incident response and run blameless postmortems, then follow through
  • Plan capacity and load test ahead of expected traffic peaks
  • Improve the reliability and cost of Kubernetes on AWS and GCP
  • Remove single points of failure and automate toil
  • Maintain runbooks and share an on-call rotation
  • Review new services for reliability before launch

The kind of person we're looking for

  • 4+ years in SRE, DevOps or production engineering
  • You have been on-call for production systems and led incidents to resolution
  • Strong Kubernetes and Linux experience in production
  • Hands-on with Prometheus, Grafana, ELK, Loki or Datadog
  • You code or script in Go, Python or Bash
  • You prefer fixing the cause over silencing the alert
  • You write postmortems that blame systems, not people

Bonus points

  • Chaos engineering, game days or service meshes

How we work

  • Own it. Teams are small and own their work end to end, from the first sketch to the fix a year later.
  • Ship small. We put a rough version in front of people early and improve it in small steps.
  • Write it down. We write before we meet. Half the time the meeting is no longer needed.
  • Review in the open. Code, designs and decisions are reviewed where everyone can see and learn from them.
  • Kind and direct. We say what we think, early and kindly. Changing your mind is expected.
  • Senior people stay close. The people with the most experience still review code and sit in on the work.

How we hire

  1. A short call. We get to know each other and talk about the role.
  2. A practical task, or a deep dive. A small task close to the real work, or a conversation about something you have already built.
  3. Time with the team. Meet the people you would work with and ask them anything.
  4. An answer. We tell you where you stand after every step, and we move quickly.

About Open Theory Labs

Open Theory Labs is a product engineering studio. Companies come to us with an idea they are not sure of. We find out whether it is right, then build the version that turns out to be true, and we stay to run and improve it.

One team covers the whole path: product strategy, software architecture and development, applied AI, cloud platforms and reliability. We work in three stages, Think, Build and Disrupt, and we hold our own ideas to the same test as our clients'.

We're a small, ambitious team of researchers and engineers in Gurugram, Dubai and Chandigarh, and our studio is at DLF Corporate Greens, Gurugram. We work hybrid with flexible hours, and everyone gets a MacBook Pro and a budget for AI tools and learning. Outside work there are hackathons, movie nights, cricket matches and celebration dinners.