skip to content
Vishnuvardhan Reddy
bangalore · ist

/about

Hi, I'm Vishnu.

I'm a software engineer at FactSet, where I work on data-intensive systems that financial professionals lean on to do their actual jobs. The work pays the rent. The obsession is the part that doesn't — building things, breaking them on purpose, and figuring out what's really load-bearing about a design.

I think a lot about judgment— the unglamorous part of engineering that doesn't fit on a resume. Most decisions in software have a defensible version and a careless version. The career is the practice of choosing the first one when nobody's looking.

Outside of code: long walks, slow reading, the kind of coffee that takes too long to make. In another life, I would have taught — and I think the best engineers secretly do.

§01 · what i believe

The short version of
how I read code.

the tradeoff is the work
shipping == done
boring tech where it counts
framework-of-the-month
type the system, not the code
ts as decoration
small interfaces, deep modules
wide apis, fragile boundaries
name what you don't know
confident-sounding ignorance
the prod incident is the curriculum
blameless without learning

§02 · the practice

The obsession,
in numbers.

Daily reps. For a year. Unbroken. Algorithms aren't the work — but a year of uninterrupted daily practice is the kind of evidence I can't fake, and it shows up in the work that is.

365
days of consecutive practice
guardian
top 1% · 2150+ contest rating
1,200+
problems solved across difficulties
last verified · apr 2026verify on leetcode →

§03 · the path

Three years, four titles,
one practice.

2023
intern → engineer i

Joined FactSet as an intern. Found that I cared less about being right than about being honest about what I didn't know yet. Converted to full-time within six months.

2024
engineer i → engineer ii

Took ownership of a critical pipeline. Cut a recurring on-call page by chasing the actual root cause instead of papering it over. Learned that the boring fix is usually the right one.

2025
ships side projects

Built Chat with PDF and VoiceFlow on weekends — both shipped to real users. Side projects are where I test the version of myself I want at work.

2026
engineer ii → engineer iii

Promoted to SWE III. Started leading architecture conversations rather than just executing on them. Mentoring engineers who joined after me.

The best way to learn is to build, break, and rebuild.
— the only career advice that aged well

§04 · the bar

What I'm looking for.
And what I'm not.

open to

  • software engineering roles at product based companies
  • senior IC roles at AI-first companies
  • infra / devtools companies
  • early-stage startups (series A–B) building real systems
  • remote-first or bay area teams

Cleared the bar?

Short emails get short replies. Use the form for context, or copy the address and write me directly.

contact form →