async def deploy():
# this one actually worked
await ship(build())
log("🚀 live"Arjun
Mehta.
What I believe
and can prove.
Software is communication.
I spent 3 weeks refactoring a working API because the variable names were lying. The tests passed. The code lied. I fixed it anyway.
Shipping beats theorizing.
My first side project had 12 users, 3 of whom were my roommates. It still taught me more than any course I took that semester.
The best engineers read the error messages.
Stack Overflow didn't have my answer once. I read the CPython source. Took four hours. I'll never forget what I found.
Complexity is a choice.
I deleted 400 lines of "clever" code and replaced them with 40 readable ones. The PR review took 8 minutes. First time that had ever happened.
Things I
actually shipped.
VeloFlow
Real-time task orchestration for async teams
Built in 6 weeks during my final semester. WebSocket-first architecture with conflict-free replicated data types (CRDTs) for offline sync. 12ms median latency in prod.
Patchwork
Open source diff tool for non-engineers
A PM at my internship said "I wish I could understand what changed." I built this in a weekend. 200 weekly active users, zero marketing.
Refract
ML-powered code review suggestions
Fine-tuned CodeLlama on 50k reviewed PRs. Catches the things linters miss — naming inconsistency, missing edge cases, architectural drift.
I give back
to what taught me.
Open source is where I learned that code is a conversation. Every merged PR is proof that I can read someone else's codebase, understand their intent, and contribute without breaking the contract.
Fixed a hydration mismatch in server components when using dynamic imports with Suspense boundaries.
Added missing type hints for dependency injection in middleware — caught by a mypy strict run.
Documented an undocumented behavior in nested transactions. Saved 3 hours for future devs.
I shipped a race condition to production. On purpose. Twice.
My internship project had a distributed lock that I was "pretty sure" was fine. It wasn't. Under load, two workers would grab the same job. The fix took 20 minutes once I understood the problem.
Understanding the problem took two weeks of reading about distributed systems, Redis SETNX, and why "pretty sure" is never an acceptable confidence interval for a lock.
I wrote a post-mortem nobody asked for. My manager read it. She said it was the most honest thing she'd seen from an intern. I got a return offer.
"The best engineers I know have all broken production. The difference is what they wrote in the post-mortem."
Capabilities as
stories, not stars.
TypeScript
Converted a 15k-line JS codebase. Found 23 latent bugs. Never went back.
Python
ML pipelines, API backends, glue scripts. The language I think in first.
React / Next.js
Built 4 production apps. I understand the rendering model, not just the hooks.
FastAPI
Favorite backend framework. Type safety end-to-end with Pydantic.
PostgreSQL
Wrote my first EXPLAIN ANALYZE at 2am. Now I write them before noon.
Docker / AWS
Containerized everything. ECS, RDS, CloudFront. Terraform for the brave.
You found me
before everyone else did.
I'm not looking for just any job. I'm looking for a team where the engineering culture matches the ambition — where craft matters and moving fast doesn't mean cutting corners. If that sounds like you, let's talk.
arjun.mehta@dev.io · Available February 2026 · SF Bay Area or Remote