I've been managing people, projects, and processes for most of my career, starting with
running a print shop before moving into software. Once I moved into tech, I led the
engineering team at Hippo Manager Software and spent five years at Kalamazoo Valley
Community College building and shipping internal tools alongside designers, back-end
developers, and a rotating cast of institutional stakeholders.
I've spent enough time in the code to know what's genuinely hard and what just sounds
hard. I've built full-stack applications, managed cloud infrastructure, untangled legacy
systems, and made architectural decisions my team and I had to live with. That experience shapes how
I lead. It's a lot easier to earn a team's trust when you understand what you're asking
of them.
I studied visual communications before moving into tech, and having that background
alongside the ability to actually build what I'm evaluating is a combination that doesn't
come up often. Most people end up on one side or the other. Understanding hierarchy,
contrast, and user flow changes the conversations you're able to have, and being able to
implement those decisions means they rarely stop at the design stage. Outside of work, I
build small tools for myself, because I value privacy; I don't want my data harvested;
and most of the existing options are more app than I need.