I BUILD
HIGH-PERFORMANCE
WEB STUFF
10+ years of full-stack engineering, architectural therapy, and deleting unnecessary code.
I've spent a decade turning "complex" into "simple." I like clean code, dark mode, and making sure your site doesn't crash on a Friday afternoon.
DESIGN.
BUILD.
SHIP.
Product Engineering
I take your napkin sketch and turn it into something you can actually ship — and be proud of.
- –System architecture (the kind that doesn't fall over)
- –Frontend that humans actually enjoy using
- –Backend APIs that do what they're supposed to
- –Infrastructure that stays up while you sleep
Automation
If you're doing something by hand more than twice, that's a bug — not a workflow.
- –CI/CD pipelines (deploy without sweating)
- –Data ingestion pipelines
- –Web scraping systems
- –Monitoring & alerting (so you know before users do)
Scalable Platforms
Systems that handle growth gracefully — not by duct tape and prayer.
- –Distributed APIs built for real load
- –Search platforms using ElasticSearch
- –Containerized infrastructure
CODING
SINCE
2014
That's over a decade of writing code, breaking things, fixing them, and occasionally doing it right the first time. I've worked across the full stack — from pixel-level UI decisions to infrastructure that runs quietly in the background (which is exactly how infrastructure should run).
- ⚡Turning vague ideas into actual products
- 🎨Frontend that doesn't make designers cry
- 🔧Backend services that handle real traffic
- 🔍Search infrastructure (ElasticSearch deep-dives included)
- 🤖Automating the things everyone else does manually
- ☁️Cloud deployments that aren't terrifying at 3am
THE
WORK,
UNFILTERED
Real projects. Real constraints. Real outcomes. No vague claims — just what the problem was, what I built, and what actually happened.
Rebuilding Search From Scratch
The platform had grown to over 800,000 SKUs across 60+ categories. The existing search was built on PostgreSQL full-text indexes — a perfectly fine solution at 10,000 products, but a slow, expensive disaster at 800K. Average search latency had crept above 4 seconds. Mobile users were abandoning search entirely. Support tickets about "can't find what I'm looking for" were filling up. The business knew this was a revenue problem. They just didn't know how big.
The new system went live in a phased rollout over 3 weeks. A/B test ran for 4 weeks before full cutover. Old system stayed warm as a fallback. Zero downtime migration.
💡Lesson: Users will always misspell the one product that actually makes you money.
Automating the Ops Team Away
The operations team at this SaaS company had a problem that felt normal to them because it had always been that way: six people spending 30–40 hours a week pulling data from five different vendor APIs, reformatting it into spreadsheets, sending reports, flagging anomalies, and hunting down mismatched records. It was skilled work being done by skilled people — but it was entirely automatable. The real cost wasn't the salary hours. It was the errors. Manual processes at scale mean manual errors at scale.
Delivered in 11 weeks across 4 phases. Each workflow went live independently with a 2-week parallel run where both the manual process and the automated one ran simultaneously — output was compared daily before the team signed off on the automation.
💡Lesson: If someone says "I just have a quick 5-minute manual task," they are lying. It takes 4 hours and breaks on weekends.
Zero to Shipped in 10 Weeks
A two-person founding team — one clinician, one business person — had raised a pre-seed round and needed to ship an MVP in 10 weeks before a major healthcare conference. The product: a scheduling and patient intake platform for independent physiotherapy clinics. The constraints: tight timeline, strict regulatory considerations around patient data, and a budget that couldn't afford mistakes. They'd gone through two freelancers who'd built nothing usable.
Shipped to private beta on day 68. The founders demoed it live at the conference. Three clinics signed up as paying customers in the first two weeks after the demo.
💡Lesson: Every "MVP" request secretly includes 40 features they definitely don't need until year three.
HOW WE
CAN WORK
TOGETHER
I don't do hourly rates. I solve specific problems. Here is what that usually looks like.
The Quick Fix
"Why is this broken?"
Code audits & architectural sanity checks.
- +Performance profiling
- +Security & debt audits
- +Architecture review
- +Post-mortem diagnostics
The Build
"Let's make it real."
From Zero to MVP in record time.
- +Full-stack development
- +System architecture
- +Database design
- +Initial CI/CD setup
- +Launch preparation
The Long Haul
"I'm basically your co-founder now."
Fractional CTO & Lead Engineering.
- +Technical leadership
- +Hiring & team building
- +Scaling infrastructure
- +Long-term roadmap planning
ACTUAL
HUMAN
FEEDBACK
Since corporate testimonials are universally fake, here are some real things people have said about working with me.
"He wrote code so clean I actually understood it."
"Darshan is 10% caffeine and 90% 'I told you so' (he was right)."
THINGS
I WRITE
ABOUT
Lessons from the trenches. Stuff I wish someone had told me earlier. Occasionally a rant disguised as a tutorial.
GOT AN
IDEA?
LET'S BUILD.
Whether you have a half-baked idea or a fully-specced system ready to build, I'm happy to have a real conversation about it. No sales call. No deck. Just talk.
- –Building your product from scratch
- –Fixing the mess someone else left behind
- –Automating workflows that are eating your team's time
- –Scaling a system before it becomes a crisis