The handoff is the bug.
Most design-to-engineering friction isn't a communication problem — it's a missing source of truth. I co-lead Labcorp's enterprise design system and personally build the Angular and React component libraries underneath it, so the design and the code are the same artifact instead of two guesses.
Same component. Two truths.
This is the whole job in one control. Drag the seam: on one side the component as a designer inspects it, on the other the exact production source a developer ships. Code Connect is what keeps them honest.
import { Component, input } from '@angular/core';
@Component({
selector: 'lib-button',
changeDetection: ChangeDetectionStrategy.OnPush,
template: `<button [class]="classes()">
<ng-content />
</button>`
})
export class ButtonComponent {
variant = input<Variant>('primary');
size = input<Size>('md');
// tokens, not hard-coded hex
}Design and code are the same component, described twice — 13+ of them, in Angular and React.
designers & researchers on the system I co-lead
components personally designed and built, Angular + React
recurring research analysis, after I shipped UnifyUXR
NPM packages published from one NX monorepo
Four things that shipped
The professional work is internal to Labcorp, so every artifact on this page is recreated in live code rather than screenshotted. What you see is what I can actually build.
Enterprise Component Library
Product teams kept rebuilding the same button. I initiated and now co-lead dual Angular and React libraries, wired Figma Code Connect so developers see real production code on inspect, and documented all of it in Storybook. Angular is the source of truth; React holds functional parity.
AI-Powered Live Prototyping
Stakeholders can't give useful feedback on a written requirement. So I open Replit in the meeting and build a working UI from the brief in real time with Claude and Cursor. Alignment happens in the room, not in a follow-up two weeks later.
Internal Healthcare Product UX
End-to-end UX for 2–3 internal applications: requirements and stakeholder feedback turned into flows, information architecture, and high-fidelity prototypes. Includes the three-column test-compendium redesign that clarified source records against Labcorp destinations and AI suggestions — and got approved to move forward.
UnifyUXR — Research Data Automation
I noticed researchers hand-merging UserZoom exports in Excel and nobody had claimed the problem. So I designed and built the fix alone: an Angular app that normalizes and combines multiple exports with weighted calculations. Hours or days of analysis, now seconds — deployed on Kubernetes and still in regular use.
How I actually work with AI
Not a buzzword on this page — a working method. AI collapses the distance between a requirement and something people can react to. I'm the go-to AI resource in my UX organization and lead biweekly Learning Labs to get other designers and PMs using it too.
Read for the interaction
Requirements land as a written spec, a meeting, or a Figma comment thread. I read past the feature list for the core interaction — what is the person actually trying to get done, and what's in their way.
Build it in the room
I open Replit in the meeting and build working UI with Claude and Cursor while stakeholders watch. Feedback lands on something real while the context is still fresh, and "I didn't picture it like that" stops happening.
Land it in production
The aligned prototype becomes a Figma file, then Angular or React code — with the component library keeping design and code the same thing. Design-system updates that used to take months now take days.
I came to design through infrastructure
Before I owned UX for healthcare applications, I was root-causing enterprise systems for customers who were down. That's why I care whether a design survives contact with production.
UX Designer
- Co-lead the enterprise design system across Figma and a Bootstrap-based SCSS framework used by roughly 30 designers and researchers and most internal product teams — shared patterns, documentation, and WCAG AA-compliant components.
- Own end-to-end UX for 2–3 internal healthcare web applications, translating requirements and stakeholder feedback into flows, IA, layouts, interactions, and high-fidelity prototypes alongside product and engineering.
- Designed and independently developed UnifyUXR after spotting a recurring manual Excel bottleneck — cutting a repeated analysis from hours or days to seconds for five UX researchers; deployed with Docker, Kubernetes, and Jenkins CI/CD, and still in regular use.
- Initiated and co-lead the standardized Angular and React component-library program after identifying repeated component recreation across product teams.
- Serve as the go-to AI resource in the UX organization and lead biweekly Learning Labs, helping designers and PMs adopt AI-assisted workflows through reusable skills and agents.
Systems Reliability Engineer
- Diagnosed complex infrastructure, software, and hardware issues for enterprise customers across Nutanix AOS and AHV, meeting SLA commitments through systematic troubleshooting and root-cause analysis.
- Managed a high-volume Jira support queue and partnered with engineering to reproduce defects, document findings, and reduce recurring incidents.
- Acted as technical contact for enterprise clients, validating multi-vendor configurations with VMware, Cisco, and Lenovo.
Systems Reliability Engineer, Intern
- Supported enterprise customers and validated hardware and software configurations in internal labs across AOS/AHV, storage, and virtual-machine environments.
Information Technology Intern
- Developed Java and Spring REST services integrated with FHIR APIs for clinical data exchange; deployed Nutanix and VMware test infrastructure and supported enterprise end users.
- Nutanix Support Specialist
- CompTIA A+
The designer who builds it too
I design in Figma and build in Angular and React. That puts me on both sides of the handoff, which is the only reason I have strong opinions about it.
My work spans the whole lifecycle: requirements and research, prototyping, building and publishing component libraries, and writing the production code that consumes them. AI runs through all of it — live prototyping sessions where a stakeholder requirement becomes interactive UI in real time, and agent workflows that take design-system updates from months to days.
The pattern in everything on this page is the same. I notice the gap nobody has claimed — a manual Excel process, three teams rebuilding the same button, a rushed workflow that hides the source record — and then I go build the fix instead of filing a ticket about it.
I'm looking for UX Designer, Product Designer, and Design Technologist roles where design and engineering are one conversation rather than two.
workflow design · information architecture
design-system governance · WCAG AA
Storybook documentation
HTML/SCSS · Bootstrap · NX monorepo
NPM publishing · Figma Code Connect
Docker · Kubernetes · Helm · Jenkins
Figma Make · agent workflows
AI-assisted prototyping & team enablement
Let's build something that ships.
Open to UX Designer, Product Designer, and Design Technologist roles. I bring the design craft and the engineering depth to ship it — usually replies same day.