Product engineer for user-facing software
I work across product decisions, interaction design, and frontend engineering, with React and Next.js as my strongest implementation layer. That lets me carry a feature from an early discussion into working software while keeping the user flow, interface states, and component architecture connected.
- Turn a broad request into a focused, testable first release
- Map workflows, edge cases, and interface states before implementation
- Prototype interaction decisions when the brief is still uncertain
- Build production React and Next.js interfaces in TypeScript
- Create reusable components instead of screen-specific solutions
- Add APIs, authentication, data, or AI services when the workflow needs them
Where this capability shows up in the work.
- 2025CVLeap AI: product workflow built in eight weeksWorked across onboarding, the AI-assisted editor, authentication and storage, and PDF export to turn a multi-step resume task into one product flow.Next.jsTypeScriptSupabaseOpenAI
- 2023NextDoor: local-news concept redesignReorganized navigation around locality and reader intent, moved source cues onto story cards, and expressed the proposed behavior through reusable Figma components.FigmaUXDesign SystemIA
- 2026Phone Assistant: measured voice-support demoBuilt a voice-support workflow for FAQ resolution, call routing, ticket creation, and human handoff, with a Next.js operations interface around the calls.Next.jsOpenAI RealtimeTwilioPostgres
The useful overlap is continuity, not replacing a team.
I do not replace a product manager, designer, and backend engineer. I can work across their boundaries well enough to keep a frontend-heavy feature moving when decisions are still close to the implementation.
In practice, that means questioning an unclear workflow before it becomes code, identifying missing states in a design, and shaping components around the next related feature rather than the current screen alone. Small teams get fewer clarification cycles and a product surface that is easier to extend.
Scope, evidence, and how I apply this work.
What do you mean by product engineer?
An engineer who participates in deciding how a product workflow should work, then owns its implementation. My strongest contribution is on frontend-heavy features where product, interaction, and component decisions affect one another.
Are you a product manager or product designer?
No. I am an engineer with product and design-engineering strengths. I can contribute to scoping, flows, prototypes, and interaction decisions while collaborating with dedicated product and design peers when the team has them.
What business problem does that overlap solve?
It reduces the back-and-forth required to turn a product decision into a working interface. It also catches missing states and reusable patterns earlier, which can reduce rework as the feature grows.
What is your strongest technical layer?
Frontend engineering with React, Next.js, and TypeScript. I also implement supporting APIs, authentication, data, and AI integrations when they are part of the product workflow.
Tell me where the workflow is stuck.
Share the product, the people using it, and what needs to become easier or faster. I will tell you whether my product and frontend experience fits the problem.