2011
“First real job. Database admin. I didn't even know what an API was.”
I've been writing code since smartphones were still just phones.
Chapter Three
Not a list of tools. A way of thinking.
01 /
Laravel, Node.js, Express, Fastify. REST APIs, GraphQL, WebSockets. Database design that scales. Queue systems that never drop a message.
02 /
React, Next.js, TypeScript. Component systems, state management, performance obsession. Pixel-perfect doesn't mean rigid it means intentional.
03 /
Docker, AWS, GitHub Actions. CI/CD pipelines, monitoring, zero-downtime deploys. The code doesn't matter if it can't ship.
04 /
12 years taught me that the best code serves the business, not the ego. Architecture decisions. Team mentorship. Async leadership across time zones.
areas of expertise
tools of the trade
Chapter Four
Not just projects. Each one taught me something I couldn't learn any other way.
API observability you can actually use
My first real product. I built this because every time I was debugging a production issue, I was flying blind no visibility into what APIs were actually doing. Zero dependencies in the npm package. Real-time monitoring in the dashboard. Real users.
This one taught me that building the product is 20%. Marketing is 80%.
589 AI tools. 12 platforms. One monorepo.
589 AI tools across 12 CMS platforms. Open source. One Turborepo monorepo. Built because the AI tooling ecosystem for CMS platforms was fragmented and incomplete.
The WordPress blog post about this is still pending review.
SMS drip campaigns that actually deliver
Sole backend engineer. Thousands of businesses. Millions of messages. The queue system was the hardest thing I've ever built getting it to be reliable at scale without dropping a single message.
The queue system was the hardest thing I've ever built.
Paste a GitHub URL. Get a security audit.
Still in progress. Powered by Claude. The prototype already caught real bugs in real codebases. Paste a GitHub URL, get back a structured security audit in seconds.
Still in progress. But the prototype already caught real bugs.
Chapter Five
Numbers don't tell the whole story. But they're a good start.
Writing production code since 2011. PHP → Laravel → Node.js → React → building my own SaaS.
Still learning. Still building.
SaaS platforms, marketplaces, e-commerce, healthcare, education, booking systems, blockchain apps.
Across 5+ industries.
Sprint planning, code reviews, architecture decisions.
APILens · CMS MCP Hub · CodePulse AI
From startups to established businesses.
Async-first · Jira · Slack · GitHub
PM skills →
Project ManagementDelivered 50+ projects on time from kickoff to production.
Lead skills →
Tech LeadershipLed 7–10 engineers. Set the architecture. Raised the bar.
Technology stack evolution: 2011–2013 PHP and MySQL; 2013–2016 PHP, CodeIgniter, jQuery; 2016–2018 WordPress, Laravel, Angular, Node.js; 2018–2022 React, Node.js, MongoDB, AWS, Web3, Solidity; 2022–2026 React, Next.js, TypeScript, Docker, GSAP, Web3.
Certified →
HackerRank
Open Source Contributor
@rahhuul on GitHub
from the notebook
The story behind auto-api-observe a zero-dependency Express/Fastify observability middleware. Architecture decisio…
8 min readEverything you need to know about AsyncLocalStorage from basic context tracking to building a full request-scoped …
12 min readA step-by-step guide to building a Model Context Protocol server that lets Claude manage WordPress content. Zod sch…
15 min readChapter Six
Senior engineering roles, architecture consulting, or a product you need shipped I'll reply within a day.
Full-time · Contract · Freelance
Ahmedabad, India · Remote worldwide
Thanks for reading.
Rahul, 2026