UX/UI Designer who turns complex health and genetic data into reports and apps anyone can understand — 4+ years at Geneus Genetics.
Four end-to-end products — landing pages, reporting systems, mobile apps and partner back-offices.
Turning complex genetic data into an experience anyone can understand — a complete digital ecosystem: a landing page that walks people through collecting a saliva sample at home, a report system that turns 500+ results into an easy-to-read spectrum slider with gene and marker references, and a mobile app for tracking health over time.
FIG. 02 A personalized health-care experience designed around trust — a smooth user journey from the health assessment to progress tracking in the mobile app.
FIG. 03 Pairing a bright, playful brand with a powerful ordering system — a fun website plus a partner back-office that is easy for partners to use.
FIG. 04 Where DNA technology meets a love of pets, in a friendly interface — a mobile app and a pet-health report system built on clear visual hierarchy.
FIG. 05 With 4+ years in UX/UI design and a telecommunications engineering background, I work between research, design and code — rewriting expert findings into plain language, and handing developers specs they can build without guessing.
A repeatable process that keeps every project grounded in real user needs — from first goal to final pixel.
Defining project aims and target outcomes to guide design.
Understanding user needs and market trends so every decision rests on evidence.
Translating ideas into rough visuals and structural outlines.
Crafting interactive models to visualize and refine concepts.
Incorporating feedback and polishing design for launch.
I use AI to cut repetitive work in Figma, leaving more time for UX — and to make every handoff to developers complete, clear and smooth from design to code.
AI handles the repetitive, time-consuming tasks, so files stay organized from the start without fixing layer by layer.
Developers get complete, clear information — tokens, component props and every state to support — so less is misread.
File structure mirrors code structure, so the team speaks one language — fewer back-and-forths and less rework later.
