Open to senior product / UX roles · US, EU, Remote
UX/UI & product designer for software where ambiguity has a price — expert tools, enterprise platforms, and the states real products can’t skip.
Selected work GIA Hamilton RKS Design Freddie Mac NomadNest
5+ years designing across regulated, technical, and high-context product environments — platforms used by experts, internal teams, and global institutions.
01One token ladder drives both themes — no per-theme overrides survived review.
02State parity: hover, focus, disabled, and error verified across both renders.
03Density held at instrument scale — the same 8-px rhythm both sides of the split.
What I actually do
Eight states, every component: default · hover · focus · active · disabled · loading · error · empty.
Four engagements, each proving a different muscle — in-house expert systems, enterprise UI at scale, agency end-to-end, and founder-led product. The range is the thesis, not an accident of who was hiring.
Sole UX/UI Specialist; interim PM · 2.5+ years · 2023–2026
Sole UX/UI specialist for the institution behind the 4Cs — the app, the verification service, the printed reports, and the client- and student-facing web.
Visual designer, design system · Multi-sprint engagement
Extending a coherent visual system across 60+ enterprise screens with WPF rendering constraints.
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.
Founder · product & design · 2025 — ongoing
A community-first travel platform, built from category thesis to interactive iOS prototype — founder-led, pre-launch on purpose.
Five years, five operating contexts. The question a portfolio this varied has to answer is whether the range is a thesis or a drift. Two views — the arc it followed, and the ground it covered — answer it.
Eight engagements, one continuous line — founding team to agency to in-house to a venture of my own. The trajectory is deliberate: each context was chosen to learn what the last one couldn’t teach.
Every operating context, covered at least once. Four engagements documented end-to-end as full case studies. Range you can audit — not just claim.
Five positions I’ve defended in rooms where agreeing would have been easier. Not taste — conclusions, 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.
The same path on every engagement — an unclear problem resolved into a built, documented interface. Not handed between people; carried as one continuous process.
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 — 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.
Ambiguous product spaces
NomadNest — built the V1 structure before there was data to lean on.
Expert & enterprise workflows
GIA — sole UX/UI specialist across an institution’s product portfolio, verification to education.
Research-backed IA
RKS — restructured the IA around visitor intent after discovery inverted the brief.
Interface systems
Hamilton — one token system holding 60+ screens across three rendering contexts.
Engineering-aware handoff
GIA — ran sprint ceremonies while designing; watched what every vague annotation became.
If you need a designer who turns ambiguity into shipped interface, this is the fastest way to start. No form — just an email, answered within 24 hours.
