software
engineer.
I'm Vishnuvardhan Reddy—a software engineer at FactSet, three years in. I build systems where every decision can be defended. The work is RAG, voice AI, and the unglamorous backbone underneath.
§01 · how i work
Engineering is the art
of defending choices.
Most code can be written two ways. Most architectures have a shadow architecture beneath them. The job isn't to ship — it's to ship the version of the system that you can still defend a year later, when the constraints have changed and the alternative looks tempting.
§02 · the stack
11 tools.
Each one, a defensible opinion.
Recruiters read fast. Engineers read carefully. This section is for both.
languages
2 tools
- TypeScriptdaily
Strict mode from day one. `any` is a smell, not an escape hatch.
used in:→chat with pdf - Pythonshipped-with
When the problem is data-shaped, not request-shaped.
frontend
3 tools
- Reactdaily
Components as functions. State as the last resort, not the first.
used in:→chat with pdf - Next.jsdaily
Server components by default. Client ones earn their keep.
used in:→chat with pdf - Tailwinddaily
Utility-first. Extract a component the second the classes repeat.
used in:→chat with pdf
backend
2 tools
- Node.jsdaily
The runtime, not the framework. Bun and Deno when it earns it.
used in:→voiceflow - Expressshipped-with
Thin router, fat services. Middleware is a contract.
data & ai
2 tools
- Postgresshipped-with
The default. NoSQL earns its place; it doesn't assume it.
- LangChainshipped-with
Chains for glue, not for thinking. Prompts are still code.
infra
2 tools
- Dockershipped-with
For parity with prod, not for kubernetes cosplay.
- Gitdaily
Small commits. Honest messages. Rebase before review, merge after.
§03 · selected work
Two systems.
Both shipped. Both defensible.
“Simple is harder than complex.
But it's worth it.”
— guiding principle
§04 · the path
Intern to swe iii.
Three years. Each rung earned.
Leading architecture for data-intensive systems. Mentoring across the team. Owning the long-term shape of the platform.
Owned and scaled critical pipeline components. Made the system-design calls that improved throughput and cut on-call pages.
Shipped production features across the core platform. Developed deep expertise in financial-data systems and API design.
Rapid ramp on enterprise systems. Delivered production-ready features within the first month and converted to a full-time offer.
§05 · let's talk
The bar to reach out is lower than you think.
If you're building something where judgment matters, I'd like to hear about it. Direct messages are read, signals are noticed, and short emails get short replies fast.