The engineer behind the work.
Shivam Bhadoriya — AI Engineer at Aaziko Global LLP, based in Navsari. Here is how the work actually runs now, what it used to be, and the road between the two.
I'm Shivam Bhadoriya, an AI Engineer at Aaziko Global LLP, based in Navsari, Gujarat. My job title changed in 2026, and so did the work behind it. I write the specification, direct the coding agents that implement it, and review and test what comes back. The judgement calls — what to build, how it should be shaped, whether the result is actually correct — stayed with me. The typing did not.
The clearest way to describe the shift is with one number. In October 2025, AI wrote 0% of the lines I changed. In August 2026, it wrote 99.77% of them. Nothing about that makes the engineering easier; it moves where the engineering happens. A vague ticket used to produce slow code. Now it produces confident, well-formatted, wrong code — much faster. So the specification stopped being paperwork and became the actual deliverable.
What that looks like day to day: I write down the exact behaviour, the field names, the status values and the acceptance criteria before anything is generated. I keep the work in phases small enough to review properly. I read every diff. I write the tests myself, or I make sure the agent's tests fail for the right reasons before I trust them. When a path is going wrong, I stop and rewind rather than argue the build forward. Most of my value now sits in the review, and in knowing which 0.23% of the lines had to be mine.
I did not start here. Before this I shipped full-stack MERN products end-to-end — production Express and MongoDB backends with JWT auth, rate limiting, realtime sockets and structured logging, behind React front ends built to a performance budget. The habits came from there: 70% faster queries through indexing and aggregation, roughly 60% less bandwidth through caching, 98 Lighthouse. Numbers settle arguments that opinions cannot, and that has not changed just because something else is writing the lines.
I studied B.Sc. Information Technology at Vidhyadeep University, and won a pair of inter-college technical competitions along the way. Outside the day job I run AI-PULSE — a YouTube channel that publishes itself, one video and one Short about a trending AI tool every day, entirely on GitHub Actions with no server and no bill. This site is the other proof: a Next.js front end, a MongoDB-backed API, a self-built analytics pipeline and an admin dashboard, all designed and engineered end-to-end and all inspectable from the outside.

Trajectory
Where I've been.
AI Engineer
Aaziko Global LLPI write the spec, direct the coding agents, and review and test what they build. In August 2026 agents made 99.77% of my line changes; in October 2025 they made none. The hours that used to go into typing now go into specification, architecture, tests and review.
Full-Stack Developer
Freelance & open sourceShipped MERN products end-to-end — Express/MongoDB backends with JWT auth, rate limiting and realtime sockets, behind React front-ends built to a performance budget.
Tech War — Champion
Inter-college competitionWon a high-pressure engineering competition; 2× technical competition winner across the year.
B.Sc. Information Technology
Vidhyadeep UniversityComputer science fundamentals alongside a relentless self-taught build cadence and a long GitHub streak.
Operating principles
What I stand on.
Own the outcome
Not just the ticket — the result. I care whether it actually worked in production.
Measure everything
Opinions are cheap. Numbers — query time, bundle size, Lighthouse — settle arguments.
Simple beats clever
Readable, boring, correct code that the next person can maintain wins every time.
Ship, then iterate
80% live and improving beats 100% that never launches. Momentum compounds.
04 — Approach
What makes it different.
Performance is a feature
70% faster queries, 60% less bandwidth, 98 Lighthouse. I treat speed as a requirement, not a nice-to-have.
Systems, not screens
Auth, rate limiting, validation, realtime, logging — I build the parts reviewers can inspect, not just the surface.
Observable by design
This very site runs a self-built analytics pipeline. If it moves, I want to measure it.
The spec is the work
Agents write most of my lines now. What decides whether the result is any good is the specification they were given, and the review and tests that came after.