Most platforms don't fail because of bad code or bad design. They fail because no one held both at once.
I'm a UX designer, engineering lead, and technical project manager with 13 years of experience building web platforms where those things can't be separated. I do my best work on problems that don't fit neatly into one lane.
I work across design, engineering, and delivery because the problems I'm drawn to don't stay in one lane. My best work happens when those things have to talk to each other.
Diagnose first. Build second. Make sure it holds.
I don't close tickets. I solve problems. Thirteen years of figuring out what's actually broken, and building the thing that fixes it.
A note on source code: I don't share it publicly out of respect for client and organizational IP. I'm glad to walk through architecture, technical decisions, and implementation details in a conversation.
The existing onboarding experience for admitted students was fragmented, confusing, and generating unnecessary support load. I redesigned the process end to end, simplifying how new users enter the University's ecosystem and reducing support inquiries in the process.
Built a tool to solve a problem I was living in, comparing resumes to job descriptions the way ATS systems actually do it. Uses semantic analysis and scoring to surface the roles worth pursuing and flag where a resume needs to close the gap.
Prospective students were struggling to compare degree programs in a way that mapped to how they actually made decisions. I conceptualized, designed, and built a browsing experience that reduced friction and gave users clearer paths to a choice.