About
An Associate Product Manager with an engineering superpower.
I started in software engineering and creative delivery. The lesson that stuck: the hardest problems were rarely “can we build it.” They were which problem to solve, for whom, and how we would know it worked.
That pull toward problem framing, prioritization, and cross-functional alignment is why I operate as an Associate Product Manager & Technical Lead. I still read architecture and ship with engineers, but the job is product: discovery, user stories, backlog discipline, and outcomes that show up in cycle time, cost, and revenue.
Technical literacy is leverage, not the destination. It lets me scope trade-offs honestly, speak the engineers’ language, and keep strategy grounded in what can actually ship.
How I work
- Start from user friction, end at the metric. A clear problem statement and a clear measure of success. The work in between is negotiable.
- Write to think. PRDs, user stories, and acceptance criteria before heroic meetings. Written thinking keeps the team aligned.
- Prioritize ruthlessly. Most roadmaps fail at sequencing, not at ambition. The right thing in the wrong order is the wrong thing.
- Translate tech into product bets. Architecture choices are product decisions when they change cost, trust, or time-to-value.
What I'm looking for
Associate Product Manager or Technical Product Manager roles at startups and tech-forward companies where discovery is real, stakeholders stay aligned, and engineering partnership is taken seriously.