Design decisions that survive implementation
Design engineering is a supporting strength within my product-engineering work. I use flows, prototypes, and design systems to make an interface clear before and during implementation, then carry those decisions into React so important states and interactions are not lost in handoff.
- Map user flows and information before polishing screens
- Prototype uncertain interactions before committing them to code
- Identify loading, empty, error, permission, and responsive states
- Create reusable Figma and React component patterns
- Build keyboard, focus, semantic, contrast, and reduced-motion behavior
- Collaborate with product and design peers without claiming their roles
Where this capability shows up in the work.
- 2023Wanderlust Woof: dog-friendly travel conceptMapped four travel journeys and prototyped how policy and verification information could appear before a booking decision.FigmaResearchIAPrototyping
- 2023NextDoor: local-news concept redesignReworked navigation, locality and source cues, and the component structure for editorial and community content.FigmaUXDesign SystemMobile
- 2025CVLeap AI: flow to working productConnected onboarding, AI-assisted editing, account state, storage, and export in a single product flow implemented with Next.js.Next.jsTypeScriptSupabase
Design work is most valuable when it removes implementation uncertainty.
I use design artifacts to answer questions the frontend will otherwise answer accidentally: what the user sees before data arrives, how a failed action recovers, which information matters first on a small screen, and which patterns should repeat.
That is different from positioning myself as a dedicated product designer. My value is carrying product and interaction reasoning into a well-structured implementation, while working closely with specialist designers when the project has one.
Scope, evidence, and how I apply this work.
Are you a UX designer?
No. I am a product engineer with design-engineering strengths. I can work on flows, prototypes, interaction decisions, and systems, but I do not present myself as a replacement for a dedicated product or research designer.
What does design engineering change for a product team?
It reduces the gap between the intended interaction and the shipped interface. Missing states, component behavior, accessibility, and responsive decisions are handled closer to implementation instead of becoming late rework.
Can you work from an existing design system?
Yes. I can implement and extend an existing system, identify where the Figma and code representations disagree, and document new patterns so future features do not create another fork.
Do you include accessibility?
Yes. I consider semantics, keyboard access, focus behavior, contrast, and reduced motion during component and interaction decisions, then verify them in the frontend implementation.
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.