Design Engineer
I build interfaces where every decision is intentional. Typography, motion, color, and interaction states working together to create experiences that feel inevitable.
View selected workSelected Work
Fintech Platform
A payment orchestration dashboard for a Series C fintech company. Reduced onboarding friction by restructuring the information architecture around progressive disclosure: merchants see critical metrics immediately, configuration details only when they engage.
Developer Tools
A visual database schema designer. Built a 12-state interaction system for every node: default, hover, active, focused, selected, dragging, drop-target, and more. The interface feels alive because every state has distinct visual expression and spring-based motion.
Healthcare
A patient portal for a regional healthcare network. Designed a dual-theme system with 10-step tonal palettes, elevation-through-tone surfaces, and high-contrast mode for accessibility compliance. The dark mode isn't an inversion — it's a complete recalculation with desaturated accents to avoid the "neon glow" effect common in AI-generated dark themes.
How I Work
Every project starts with the same question: what does this interface need to make inevitable? Not beautiful — inevitable. The kind of design where removing any element would make the experience worse, not better.
Define purpose in one sentence. Identify the audience. Choose an aesthetic direction that is specific, not "clean and modern." Document anti-directions: what you are not doing, and why. This is the layer most designers skip, and it is the layer that makes every subsequent decision defensible.
Map content as a story with rising action, not a flat list. Assign disclosure levels: what is visible immediately, what requires a scroll, what requires engagement. Design section-to-section tonal shifts so the page breathes and accelerates. Replace generic data with specific, credible metrics.
Create a type scale with dramatic ratios (minimum 2:1 display-to-body). Generate a 10-step tonal palette from a mood-driven hue. Establish an 8px spatial grid where type and space are mathematically aligned. Design elevation through tonal surface shifts, not drop shadows.
Map 12-state machines for every interactive element. Specify asymmetric transition timing (entries slower than exits for positive states). Apply spring physics instead of generic easing. Use stagger cascades for grouped elements. Respect reduced-motion preferences with instant fallbacks.
Get in Touch
I work with teams who believe design is a system of decisions, not a coat of paint. If that sounds like you, let us talk.