Systems thinking. I default to building scalable patterns and component libraries rather than one-off solutions — so the work compounds over time instead of creating more debt.

Complex enterprise workflows that have gotten out of hand — the kind where users have learned to work around the product instead of with it. I've spent 12+ years in cybersecurity, finance, and healthcare, which means I'm comfortable with high-stakes, high-complexity problems where getting it wrong actually matters.

I'm the person teammates come to when something's stuck. Friendly, collaborative, and genuinely dependable — and when something's blocking us, I'll kick down whatever doors are necessary to move forward. People know that when I'm involved, it gets done.

Closely and directly — which is easier when you can speak their language. I've contributed to front-end production code, implemented design systems in Bootstrap, and spent enough time in the codebase to know what's actually feasible.

Teams where design has a real seat at the table and engineers are treated as partners, not executors. I do my best work when there's a hard problem, a collaborative team, and enough trust to move fast and iterate.