Journey
An unconventional resume. Less about titles, more about the work and what it taught me.
I've always been drawn to the edges of disciplines — the places where product meets design meets engineering. My best work has happened when I've been trusted to work across those lines, to ask "why are we building this?" and "how should it feel?" in the same breath.
I believe that good products come from deep understanding of users, clear thinking about tradeoffs, and the patience to get the details right. I'm most energized when I'm solving genuinely hard problems with small, high-trust teams.
I care about craft. Not perfectionism — craft. There's a difference. Perfectionism is fear dressed up as standards. Craft is the discipline to keep improving even after something is "good enough."
Senior Product Manager
Leading product for [core product area], working closely with a cross-functional team of engineers, designers, and data scientists. Rebuilt the [feature] from scratch after discovering that our original assumptions about user behavior were fundamentally wrong. Learned more from that failure than from most of my successes.
Product Manager
Joined early as the second PM. Owned the onboarding experience end-to-end and reduced time-to-value from 14 days to 3. Collaborated with design on a full UI overhaul that meaningfully improved retention. The hardest part wasn't the work — it was learning how to influence without authority at an early-stage company where everyone had opinions.
Associate Product Manager
My first PM role. Came in with strong opinions, got appropriately humbled, and emerged with a much clearer understanding of what the job actually is. Built two features from spec to launch, learned how to write a PRD that engineers actually want to read, and discovered that the best product decisions are usually the ones you don't make.
Software Engineer
Started as an engineer, which is where I learned to have genuine respect for the craft of building software. Shipped features, wrote bad code, rewrote it, and slowly developed an intuition for what "well-designed" meant from the inside of a codebase. The engineering background shapes how I think about product to this day.
B.Tech, Computer Science
Built small side projects, led the college tech fest, and spent more time reading about startups than studying for exams. The curriculum gave me fundamentals; the extracurriculars gave me the drive to do something with them.
Technical
- Product Strategy & Roadmapping
- Data Analysis & SQL
- A/B Testing & Experimentation
- API Design & Documentation
- Front-end Development (React, JS)
- Python (scripting, data work)
- Figma & Prototyping
Product & Design
- User Research & Interviews
- Jobs-to-be-Done Framework
- Metrics Definition & OKRs
- Go-to-Market Strategy
- Competitive Analysis
- Information Architecture
- Design Systems
Ways of Working
- Cross-functional Collaboration
- Async-first Communication
- Writing & Documentation
- Stakeholder Management
- Structured Decision-making
- First-principles Thinking
- Iterative Shipping