Software Engineer / Team Lead
I find the structure hiding inside ambiguity.
01 — Approach
After 15 years of building software, I've learned that the hard part is rarely the code — it's understanding what the problem actually is before you solve the wrong one elegantly.
Give me something "working" that everyone's afraid to touch and I'll figure out what it's actually trying to be.
I'm drawn to the seams: where design meets engineering, where user needs meet technical constraints, where what someone says they want meets what they actually need. That's where the interesting work lives.
02 — Most recently
Senior Software Engineer / Team Lead · May 2025 → October 2026
Technical owner of a creative tool for footwear designers — an infinite 2D canvas that flowed straight into a full 3D editor, so a rough concept could be refined all the way to a production-ready mesh.
I built the architecture that kept the 2D and 3D workspaces in sync, the rendering pipeline that had to stay responsive on every device, and the state systems that held it all together — then led the rewrite that took design generation from 15 minutes to 90 seconds. Most of the job was translation: between what designers needed and what the technology could do.
03 — Before that
04 — There's more to the story
I volunteer with the Trauma Intervention Program as a "second responder" — sitting with families after a death, offering empathy and emotional first aid.
That work changed how I think about everything else. The same instincts that make me good at engineering — pattern recognition, reading what's not being said, staying calm in ambiguity — translate directly to being present with people in crisis. I've started to see engineering and counseling as the same work at different scales: understanding systems, earning trust, helping people get unstuck.