A DevOps Engineer's Part-Time Consulting Journey: Rs 4,500 Per Hour

An 11:20 pm message landed on LinkedIn: "Hey, you're into DevOps right? Our CI/CD pipeline is down, production release is stuck. Can you help?"

It was a former colleague who'd moved to a different company. I figured I'd just help for free, we were friends after all. He said, "No no, we'll pay, this is official, we just need it fast."

Hopped on a screen share at nearly midnight, half annoyed, half curious what had actually gone wrong. Found a simple YAML syntax error buried deep in the pipeline config, the kind of thing that's obvious once you spot it and invisible until then. Fixed in 50 minutes flat. Rs 4,500 showed up via UPI the next morning, no invoice, no negotiation, just a straightforward transfer.

---

The first realization: my regular skill was someone else's emergency

After that 50-minute job, I remember thinking, this is just a normal Tuesday for me, what's so special about it. But for their team, with nobody specifically skilled in DevOps, it was a genuine emergency.

Honestly, I'd assumed consulting was reserved for senior people with 10-plus years behind them. What actually happens is companies look for help on small problems too, anywhere their own team happens to be missing specific expertise.

That one incident got me thinking this could become something repeatable rather than a one-off.

---

The second client, where I learned to actually scope the work

The second client was a startup that needed Kubernetes set up from scratch. I jumped straight into the work without discussing scope properly, figuring I'd just "do whatever it takes."

Two weeks in, it hit me I'd already put in 30-plus hours, and the client was expecting me to manage their entire infrastructure on an ongoing basis, with no additional payment attached.

An awkward conversation followed where I had to clarify that the initial setup was one scope, and ongoing management was an entirely separate one, with its own separate rate attached. The client was a bit surprised, pushed back mildly for a day or two, but ultimately accepted it once I laid out exactly what ongoing support would involve. Since that day, I send a written scope before starting anything, even small jobs.

---

Raising my rate, which took longer than it should have

The first job paid Rs 4,500 (an emergency rate). The second regular project went for Rs 2,400 an hour, because I didn't yet have confidence in pricing myself higher.

With the third client, I tried Rs 3,100. They accepted without any negotiation at all. That moment made it obvious, almost embarrassingly so, that I'd been underpricing myself the entire time without ever actually testing it.

Seven months in now, my regular rate sits at Rs 3,800 an hour, and urgent or emergency work goes up to Rs 7,200. I test the rate a little with each new client, watching where resistance actually shows up.

---

Balancing this with a full-time job

Time management is genuinely the hardest part. Office work runs 9 to 6, and consulting happens entirely on evenings and weekends.

In the first two months, I overcommitted badly, four active clients at once. Burnout crept in, and quality at the day job started slipping too. Now I cap it at 2 active clients at any given time.

One more thing I made clear to my employer, without going into specifics: I do some freelance work on the side, but it never compromises the day job. Staying transparent about that has kept the trust intact.

---

The real income numbers, seven months in

Months 1 to 2: Rs 4,500 (just the one emergency call) Months 3 to 4: Rs 33,400 (two regular clients came on board) Months 5 to 7: Rs 61,600 to 71,200 average per month (three clients, a mix of ongoing and project-based work)

Total across 7 months: roughly Rs 2,54,300 in extra income, separate from the regular salary.

---

What I learned from other tech consultants

I connected with other people starting out in Docker and Kubernetes consulting through an online community. Turns out the pricing and scoping mistakes I made early on are shared almost universally among people starting out, I wasn't the exception.

Finding freelance projects after AWS certification follows a strikingly similar path too, except the certification itself becomes a trust signal for clients, one that sometimes lands before actual experience even gets discussed. Ethical hacking and bug bounty work falls into this same tech-skill-as-side-income category too, just with a completely different skill set underneath it.

---

The mistake that cost the most

I did one project on a verbal agreement with a client, never sent a written scope over email. Once the work was done, they started delaying payment, saying, "We assumed that was included in the scope too."

I had nothing in writing to point back to. Waited 3 full weeks for payment, and the final amount that came through was lower than what we'd originally agreed, after some genuinely uncomfortable back-and-forth negotiating over email.

Since that day, no matter how much I trust a client, I send a short email thread laying out scope, deliverables, and payment terms before starting anything. It takes two minutes, and it's saved me more than once since.

---

Thinking now about structuring this side income a bit more formally, maybe setting up something like a small LLC purely for tax purposes...