I build
like it matters.
I’m Aakash Dhanyamraju — a software engineer who treats every product like it’s the only one. I obsess over the edges, ship with intent, and stay until it’s right.
Idon'tshipcode.Ishipoutcomes.Itreateverylinelikeit'llbereadat3a.m.bysomeonetiredandtryingtofixsomethingImissed.Iwriteless.Ichecktwice.Istayuntilitworks,andthenIstayalittlelongertomakesureitstaysthatway.
The work, in numbers that survived production.
Uptime maintained across production deployments
People served by systems I’ve built and kept running
Latency cut on the workflows that mattered most
Database records orchestrated, day in and day out
Numbers don’t make a craftsman, but craftsmen tend to leave numbers behind. These are mine, earned across products real people use.
Stories, not stacks.
What I built, why it mattered, and what was different the day after I shipped it. The tools are on the resume.
An autonomous agent platform that doesn't lose its mind in production.
A multi-tenant control plane for deploying AI agents that reason, act, and stay observable. Built so a non-engineer can launch one in minutes, and an engineer can debug one at 2 a.m. without crying.
Architecture, end-to-end build, the late-night fixes nobody sees.
- Scaled to 50K+ daily interactions without paging anyone
- Cut end-to-end latency by 60% on the hot paths
- 99.9% uptime, and the boring kind of operations
Pick-A-Pad AI — turning a slow, painful review into a 60% faster decision.
A tenant screening platform managing thousands of property units. The bet: let an LLM read the messy documents so humans can make the actual call. The hard part was making something operators trust enough to use every day.
From a blank Figma to a system property managers depend on.
- Managing 2.9K+ property units in active use
- Cut manual document review by ~60%
- Quietly removed the part of the job nobody liked
A social platform that grew to 500K users — without ever feeling slow.
Joined as an intern. Left having co-built the recommendation engine, the moderation system, and most of the surface area people actually touched. The win wasn't being clever; it was making a fast app stay fast.
Owned the hard performance work, mentored two engineers along the way.
- Supported 500K+ users, 2M+ records, zero downtime weeks
- Cut API response times by 35%
- Engagement up 25% after the recommendation rewrite
How I show up every day.
Not values on a wall. The actual operating system behind the work.
Ownership without a ticket.
If I see it, it's mine. The bug, the doc gap, the awkward UX. Waiting for someone to assign it is how things rot.
Boring on the outside.
Software should feel like a good appliance. Predictable, quiet, durable. The cleverness lives inside, where it earns its keep.
Read it twice. Ship once.
Reviews aren’t a formality. They are the last place the future-me will thank the present-me. I show up to them.
Speed is a side-effect of clarity.
I don’t go fast by skipping steps. I go fast by knowing exactly which steps I’m skipping, and which ones I’m not.
Learn out loud.
If I figured something out, somebody on the team should be able to figure it out in half the time tomorrow. Notes, PRs, docs, voice.
Care is a feature.
Loading states. Empty states. Error copy that doesn’t condescend. The 1% that decides whether people stay.
A repeatable five-move game.
I read first. Listen second. Type third.
Before any code, I want to know what hurts, who it hurts, and what 'done' actually feels like. That conversation is the project.
I draw the smallest thing that could be wrong.
A diagram on paper, a Loom, a doc. Fast and disposable. I'd rather find the flaw in 20 minutes than three sprints.
I ship something ugly within a week.
Real shape only emerges when something actually runs. Polish lies. Behavior tells the truth.
I sit with the people using it.
I watch where they pause. Where they squint. Where they alt-tab. That's where the next version begins.
I clean up after myself, always.
Dashboards, alerts, runbooks, deprecations. I treat the project as alive after launch — because it is.
Hi,
I’m writing this because a resume can tell you what I’ve built, but not why I’ll be a good person to build with.
The thing I’m most proud of isn’t a project. It’s a habit: I don’t leave things half-done. Not the PRs, not the alerts, not the documentation, not the awkward conversations.
Nearly three years in, I still approach every standup with the curiosity and energy of day one—because if the project doesn’t feel interesting, what’s the point?
If you’re looking for someone who will quietly raise the floor of your team — who will write the doc nobody asked for and own the bug nobody saw coming — we should talk.
— Aakash