Skip to content

Hire me

Open to work, right now. Here is everything you would ask first.

Four years running production on AWS at a services company, which means I did not get one product, I got the whole portfolio. Kubernetes on EKS serving millions of requests a day. ECS microservices behind a platform with 100,000+ users. Terraform for all of it. And the Node.js services on top, because at a services company you write the code too.

Available
Now
Notice
None, served
Based
Ahmedabad, IN
Open to
Remote / hybrid

Titles that fit

  • Senior DevOps Engineer

    the title I have now, and the work I know cold

  • Platform Engineer

    building the thing other engineers ship on

  • Site Reliability Engineer

    if reliability is owned rather than assigned

  • Infrastructure + Backend

    the hybrid role most job boards do not have a name for

What I actually want is the role where the infrastructure and the product are the same job. I have spent four years being the person who owns both ends, and handing one of them away would be a step backwards.

What a first month looks like

Not a promise, a default. If your priorities are different I will do yours instead, but this is where I go if nobody tells me otherwise.

  1. Week 1

    Read everything, change nothing

    Terraform state, the alert list, the last three incidents, and who gets called. I want to know what is load bearing before I touch it.

  2. Week 2

    Fix the thing that wakes people up

    Every team has one alert that fires nightly and never needs action. Muting it correctly is usually a week of small changes, and it buys back everyone's sleep.

  3. Week 3

    Test a restore

    Not the backup. The restore. Almost nobody has timed one, and the number is always worse than the guess.

  4. Week 4

    Write down what only I know

    Whatever I have learned that is not in a repo goes into a runbook. I have been the bus factor. It is not a compliment.

What I am not looking for

Saying this out loud saves us both a call.

  • A role where infrastructure is a ticket queue and nobody talks to the people who write the code.
  • A place that treats being the reason it stays up as overtime rather than the job.
  • Kubernetes because it is on the roadmap, on a product that would be fine on one EC2 box.
  • A team where the on-call rotation is one person and everyone has agreed not to mention it.

The questions I always get

When can you start?
Now. My last day was 31 August, notice fully served.
Notice period?
None. It is already served.
Remote, hybrid or onsite?
All three work. I am in Ahmedabad, so anywhere in Gujarat is onsite if you want it. For remote I have four years of working with clients I never met in person.
Would you relocate?
For the right team, yes. Bangalore, Pune, Hyderabad and NCR are all on the table.
Full time or contract?
Full time preferred. I will take contract if the work is interesting and the scope is real.
Are you on call?
I have been the on-call rotation, alone, for four years. I am not afraid of a pager. I do care whether alerts are tuned, because a pager that cries wolf is how teams burn out.
Timezone overlap?
IST. I have worked across European and US hours on releases and incidents. Four hours of overlap is comfortable, more is better.
Do you write code, or only infrastructure?
Both, and that is the point. At a services company you do not get to hand the backend to someone else. Node.js, Express, NestJS, Next.js and React are all things I have shipped to production, not things I have read about.
What is your salary expectation?
Tell me the band and the scope and I will tell you honestly whether it works. I would rather have that conversation in the first call than the fifth.

Next step

One email is enough to start.

You do not need a formal JD or a scheduled call. Tell me what is broken, or what you are building, and I will tell you honestly whether I am the right person for it.

Prefer to look first? The work · Experience · Project work · Writing