I’m a senior generalist product designer. I move easily between research, design, systems work, and stakeholder conversations, and I’m just as comfortable working closely with engineering as I am with support, product, or leadership. On several projects, I was the only UX person involved, which meant taking real ownership of the work end-to-end: not formal project management, but genuine responsibility for keeping research, design, and delivery moving together, and for making sure the right people were looped in at the right time.
Most of my career has been as the sole UX person on a project, though I’ve also worked embedded on a larger design team, and I genuinely enjoy both. What I like most is coordinating closely with teammates: aligning with engineering and PM, and mentoring newer designers as they come up. That collaborative instinct doesn’t go away just because a given project happens to be solo.
That range shows up most clearly on complex, B2B problems: the kind where the real difficulty isn’t the interface, it’s the system underneath it. Reconciliation logic, rule-building engines, time tracking tied to invoicing. These aren’t projects where you can start from a blank page. They’re projects where you’re navigating existing architecture, legacy data models, and real engineering constraints, and where the job is often figuring out what the actual problem is before you can design anything credible.
That’s the thread across most of my work: research deep enough to find the real problem (not just the stated one), and design that survives contact with how the business and the technology actually function.
A few things shape how I get there:
Engineering and front-end development. I understand not just how something should look, but how it needs to be built, and that changes what I design. It’s shaped my design systems work in particular, since I know what actually holds up in code versus what just looks good in Figma.
A Master’s in Information Architecture. Most of my strongest project insights come from IA thinking: recognizing that tracked time isn’t the same as billed time, or that a reconciliation problem was really a transaction problem underneath. I design with an understanding of what the underlying data can and can’t do, not just what the screen shows.
An MBA. This shows up in how I navigate stakeholder conversations and business tradeoffs, and in judgment calls like designing something flexible enough that a feature could be pulled from a release and added back later without a rebuild.
A background in Psychology. This is where my interviewing skill comes from. Getting honest signal from people takes more than asking the right questions; it takes knowing how to ask them. That shows up directly in techniques like asking people to describe their ideal experience rather than critique their current one.
That solo experience has made me comfortable owning research, design, testing, and documentation end-to-end, and comfortable advocating hard for a fix when I see one that isn’t on anyone’s roadmap yet.
More recently, I’ve brought AI tools directly into my process, for brainstorming, for prototyping, and for testing early concepts faster. I’m genuinely excited about where this is heading, but I treat it carefully: it’s a tool that rewards people who already know what they’re doing, and can encourage laziness or a disjointed result if you let it lead instead of you.
How I Work
- Comfortable in ambiguous, constraint-heavy B2B environments
- Generalist range: research, design, systems, and stakeholder work, not siloed to one part of the process
- Senior level, with experience both embedded on a design team and as the sole UX person on a project
- Enjoy coordinating closely with teammates and mentoring newer designers
- Run my own research: interviews, competitive analysis, synchronous and asynchronous studies
- Collaborate closely with engineering, PM, and information architects, not just at handoff
- Take real ownership of delivery when needed, keeping work moving and the right people looped in, without needing a formal project manager
- Work in Agile environments
- Build design systems that go beyond components: patterns, documentation, and usage guidance
- Use AI tools deliberately, with testing and verification, not as a shortcut around judgment