Open to senior product and UX roles: US, EU, remote · as of August 2026
Senior product designer and design engineer, computer science and sociology by training. Five years across enterprise SaaS, expert tools, and design systems. In-house, at an agency, on contract, and as a founder.
Selected work GIA Hamilton RKS Design Freddie Mac · DPA One NomadNest
Where the work has been
Life sciences: Hamilton’s lab-automation design system, shipping on thousands of instruments. Financial services: Freddie Mac’s DPA One, the national down-payment-assistance platform. Luxury and verification: the GIA App, Inscription Matching, and the reports the trade relies on. Medical devices and e-commerce, under NDA. Travel, with a platform of my own. And education: now on contract with a confidential EdTech client, on a K–2 core-curriculum platform.
aOne token ladder drives both themes; no per-theme overrides survived review.
bState parity: hover, focus, disabled, and error verified across both renders.
cDensity held at instrument scale: the same 8-px rhythm on both sides of the split.
Scope, 2021–2026Select a line for its source
How I work, in six lines
Eight states, every component: default · hover · focus · active · disabled · loading · error · empty.
Selected work
Each one asked for something different: in-house product work at an institution, enterprise UI under platform constraints, a design firm’s own site from research to build, and a founder’s first product. Together they are the range I would bring to a team.
In-house UX/UI designer; interim PM · 2023–2026
In-house designer at the institution behind the 4Cs. The GIA App, the Inscription Matching service, the B2B e-commerce and checkout flows, the printed reports and certification materials, and the client-, manufacturer-, and student-facing web.
Problem. An institution’s entire client-, trade-, and student-facing surface area, a small design function, and a vocabulary the industry will not let you redefine.
Constraint. Institutional and under NDA; the deepest engagement, Facetware, stays off the page entirely.
Move. Carried design across those surfaces while running the product team’s sprints as interim PM.
Proof. The App and the Inscription Matching redesign shipped; retail verification errors and processing times came down. Specifics in conversation.
Visual designer, design system · Multi-sprint engagement
Extending a coherent visual system across 60+ enterprise screens with WPF rendering constraints.
Problem. Extend an approved design direction across 60+ enterprise screens.
Constraint. WPF rendering limitations across three distinct rendering contexts.
Move. Simplified the visual system so one set of decisions held across all three.
Proof. One token set rendering both themes across web, WPF, and embedded, shipped to engineering and running on instruments in labs worldwide.
Sole UX/UI designer & developer · Multi-sprint engagement
Research-led IA and visual-system execution for a 45-year-old design firm, owned end to end.
Problem. A 45-year-old design firm whose site didn’t read with the authority of its own work.
Constraint. Design and development in the same pair of hands, research through build.
Move. Restructured the IA around visitor intent after discovery inverted the brief.
Proof. Full rebuild: researched, designed, built, and shipped.
Founder · product & design · 2025–ongoing
A community-first travel platform, built from category thesis to interactive iOS prototype. Founder-led, pre-launch.
Problem. A community-first travel product where booking is solved but belonging isn’t.
Constraint. Pre-launch: a thesis to structure, with no usage data yet to lean on.
Move. Built the V1 product structure and experience language from the thesis up.
Proof. Three V1 surfaces at prototype fidelity; concept-validation interviews scoped and running.
Evidence
Whether that range is a plan or a drift, two views answer it: the path it took, and the ground it covered.
Eight engagements on one line — an agency and its enterprise clients, an institution, ventures of my own, and a current contract in education. Each step was chosen to learn something the last one couldn’t teach.
| In-house | Agency | Founder | |
|---|---|---|---|
| NomadNest | Not covered | Not covered | Full case study |
| GIA | Full case study | Not covered | Not covered |
| Wildr | Not covered | Covered | Covered |
| RKS Design | Not covered | Full case study | Not covered |
| Hamilton | Not covered | Full case study | Not covered |
| Freddie Mac | Not covered | NDA, concurrent | Not covered |
| Synaptic Medical | Not covered | NDA, concurrent | Not covered |
| Confidential Client (EdTech) | Not covered | NDA, concurrent | Not covered |
Every context covered at least once; four engagements documented as full case studies. The rest is under NDA and shareable in conversation.
Positions
Five positions, each with the project that taught it. Open any one for the reasoning.
RKS: discovery inverted the brief; I restructured the IA around visitor intent.
I’ve thrown away a month of design work because one interview revealed I was solving the wrong thing. Research that only confirms what you already believe isn’t research — it’s decoration. The reversal never happens if it’s scoped as a validation step.
Unreleased product: iterated a reply affordance until zero test participants missed it.
When a participant pauses before acting, that pause is a defect. My first treatment was visually minimal because I’d optimized for hierarchy; one in four people missed it. The version that tested clean was not the one I’d have shipped on intuition.
Hamilton: two treatments I argued for were cut once the render cost was measured.
I’ve set aside work I was proud of because the data was unambiguous. It never gets easier and it’s always the right call. Preference has no standing in a decision once there is evidence pointing the other way.
Hamilton: a WPF rendering limit became the filter the visual system was built through.
A constraint met in sprint one produced a more disciplined system than a blank canvas would have. Treated as a late-stage blocker, a constraint forces compromise. Treated as a first-order input, it produces the design you wouldn’t otherwise have reached.
GIA: ran sprint ceremonies while designing; watched what every vague annotation became.
Engineering fills whatever the handoff leaves open. A missing edge case becomes a bug; an undocumented loading state gets invented by someone who didn’t design the component. A handoff should leave no decision the designer would have made differently than the person building it.
Method
The same path on every engagement: an unclear problem, worked into a built and documented interface, without changing hands along the way.
Name what the team can’t yet answer.
Interviews and testing aimed at the riskiest assumptions.
Information architecture and flow before any surface.
Layout, hierarchy, and the system that holds them.
Empty, loading, error, and edge cases: designed, not assumed.
Annotated specs that leave no decision to guess.
Built result checked against the design intent.
Competitive landscapes read for the decisions behind them, not the features. Interviews that listen for what people don’t say. Usability testing aimed at the work I’m most attached to, because that’s where the useful surprises are.
Tokens, states, and edge cases decided before the showcase view. Flows that hold under real data, not demo data. The work is done when an engineer could build it without asking a question the design should have answered.
I’ve run sprint ceremonies while designing, so I scope for what production actually does with a spec. The handoff is annotated, walked through, and treated as the last design decision, because it is one.
Capabilities
Ambiguous product spaces
NomadNest: built the V1 structure before there was data to lean on.
Expert and enterprise workflows
GIA and Freddie Mac’s DPA One: verification services, dense tabular data, and B2B e-commerce for professionals.
Research-backed information architecture
RKS: restructured the IA around visitor intent after discovery inverted the brief. DPA One: interviews and task-based usability testing that reordered the roadmap.
Design systems and tokens across platforms
Hamilton: one semantic token set holding 60+ screens across web, WPF, and embedded touchscreens.
Accessibility built in, not audited in
GIA and this site: WCAG AA as a first-artifact requirement, from contrast to focus management.
Engineering-aware handoff
GIA: ran sprint ceremonies while designing. This site is hand-built in HTML, CSS, and JavaScript.
Correspondence
If this is the kind of designer your team needs, a conversation is the fastest next step. No form. Just an email, answered within a day.
