Product engineer. Product thinking to production.
I help teams shape and ship user-facing products, from early product and interaction decisions through production React and Next.js. My overlap across product thinking, interface design, and frontend engineering reduces clarification cycles and helps small teams move from idea to working software with less rework.
- Sysmind
- Webiosis
- Yetticate
- Adaan Digital
Product engineering across workflows, interaction decisions, frontend architecture, and the supporting systems a feature needs.
- 01
Product Engineering
feature scoping · workflows · prototyping · product decisions
- 02
Design Engineering
interaction design · Figma · design systems · accessibility
- 03
Frontend Engineering
React · Next.js · TypeScript · architecture · performance
- 04
Supporting Systems
Node · Supabase · Postgres · OpenAI · Twilio · automation
How the work helps a team move.
Move from a product idea to a working interface
I can stay with a feature from early discussion through interaction decisions and frontend implementation, reducing the context lost between separate handoffs.
Ship new workflows without rebuilding the same UI
Reusable components, clear states, and consistent interaction patterns give the next feature a foundation instead of another one-off implementation.
Find friction before it becomes frontend rework
Reviewing flows, edge cases, responsive behavior, and accessibility before implementation makes the product easier to use and the build easier to maintain.
Selected product work.
CVLeap AI
A resume product built in eight weeks with Next.js, Supabase, and OpenAI. I worked across onboarding, the AI-assisted editor, authentication and storage, and the PDF export flow.
→ Turned a multi-step resume workflow into one working product, from onboarding through export.
I AM ART
A photography portfolio built around scroll-led image transitions. I used GSAP, Locomotive Scroll, lazy loading, and a preload queue so the motion could support the work without making navigation feel heavy.
→ Balanced a visually dense interaction concept with the loading and rendering work needed to keep it usable on smaller screens.
Last 3 Feet
A React and Tailwind marketing site shipped in five days. Reusable sections kept the build consistent and made follow-on pages easier to assemble.
→ Shipped in five days with a recorded Lighthouse score of 98 and a reusable component foundation.
From the first conversation to a reviewable build.
- 01
30-minute call
We discuss the product problem, the current state, and what needs to change. If I am not a good fit, I will say so.
- 02
Scope the useful slice
I turn the discussion into a written scope with the workflow, deliverables, assumptions, timeline, and price. Larger ideas are split into a first version that can be reviewed or tested.
- 03
Build in visible increments
Work moves through reviewable pull requests and regular walkthroughs. Product and interaction decisions stay visible alongside the code.
- 04
Hand over the reasoning
You receive the code, the reusable patterns, and documentation for decisions that future product or engineering work depends on.
Scope, collaboration, and what happens after you reach out.
Frontend-heavy products where the workflow and interface still need engineering judgment: a new SaaS feature, a complex dashboard, onboarding, a design-system cleanup, or an MVP that needs to move from a product discussion into working software.
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.