Working4 min read
The career roadmap I never followed
Students keep asking me what they should learn. I never had an answer at 19, and I'm not sure I have one now. What I do have is a different question.
Hey there ๐ I'm
I build products and teams, and write about what I learn along the way.
Building technology, leading engineers, navigating careers, and figuring out what changes when AI enters the room.
CTO @ Metafic ยท Founder, Leadnics ยท Writing about technology, products & careers
Working on something interesting? [email protected]
Building
Leading
Speaking
CommunityWriting
Essays from someone who builds things. Mostly about how technology changes the way we build and work.
Working4 min read
Students keep asking me what they should learn. I never had an answer at 19, and I'm not sure I have one now. What I do have is a different question.
Thinking5 min read
Try creating something with your hands, without distractions. It might unblock you and show you a completely different side of things.
Working8 min read
Every essay your school assigns tonight will be written by a machine in eleven seconds. We can keep pretending otherwise, or we can rebuild education for the world that actually exists.
Building
A product, and the open-source tools I build when nobody is paying me to.
Author2026
Connecting N agents to M MCP servers turns into an NรM mess of auth, limits and failures. One secure, observable endpoint in front of all of them: auth, RBAC, rate limiting, caching, OpenTelemetry and circuit breakers.
Author2026
Prompts are code, so why don't we test them like code? Unit tests for prompts: deterministic and LLM-as-judge graders, snapshot baselines, cost tracking, and a CI gate that fails the build on drift.
Speaking
23 developer events organized and taught in 2018โ19, with 3,600+ attendees, then talks at DevFest, Google Cloud Community Day and universities. These days I talk about building careers, AI in production, and leading engineers.

Students & early-career engineers
Why "what should I learn?" is the wrong question, and what to build instead.
Engineering teams
Evals, gateways, and the boring distributed-systems engineering AI products still need.
Engineers moving into leadership
What changes when your job stops being writing the code.
Organizers & DevRel
Lessons from starting codeIndore() and co-organizing GDG Indore.
About

I've been on both sides of the room. At 19 I was the student asking what I should learn, organizing hackathons, porting operating systems to phones that didn't need them, and teaching Git to anyone who'd sit still. Now I'm the one students ask.
In between: a GitHub Campus Expert badge, co-organizing GDG Indore, becoming CTO at Metafic in 2020, building Leadnics, and somehow ending up in ISB Hyderabad's IVI venture program.
I didn't follow a roadmap. I built things, and the roadmap appeared afterwards.
When I'm not in the code, I'm mixing beats, documenting my cold brew obsession, or reading whatever my book club picked this month.
Way back
Where it started
A kid, a desktop computer, and a chair much too big for me.

2016
Ported Sailfish OS to a Redmi 2
Android kernels, device trees and vendor blobs, before I knew what any of it was for.
2018
Organized my first hackathon at 19, became a GitHub Campus Expert, and taught Git to anyone who'd sit still.

2019
DevFest'19 for 400 developers, plus hackathons, study jams and meetups across the city.

2020
September 2020. I lead engineering at Metafic, which builds production software for other companies.
2023
Helped scale Metafic past 300 people
Three years in, Metafic had grown past 300 people, with engineering scaling alongside it.

2024
A CRM for people who close deals with a handshake. Built from time on trade-show floors like Canton Fair.

2025
A six-month venture program from October 2025. Went back to school to learn the business side of what I build.

2025
Joined the board at Thinqzo
A seat at the table where company decisions get made, not just engineering ones.
Now
Open-source developer tools, essays here, and back in rooms full of students.

Off the clock








Contact
The fastest way to reach me is email. I read everything, and reply to most of it.
[email protected]Newsletter
Occasional essays about software, AI, products, teams, and the strange things I've learned while building them. No schedule I can't keep, no spam.