Résumé

It started early

My dad was an IT guy, and I grew up sharing his love of technology. I was making things in Kid Pix at seven, playing around in system preferences and exploring the filesystem. By fourteen I was installing Opera because I wanted to try something other than Internet Explorer. Technology was just always part of how I engaged with the world.

But I didn't go straight into IT. After college I became a kindergarten teacher—and I loved it. The patience and empathy I built in the classroom turned out to be one of my biggest assets in support.

Stumbling into it

I stumbled into my first desktop support job at a nonprofit in Cambridge. My manager didn't understand why I knew what I knew—but I'd been doing this my whole life. That role was where I first got hands-on with Active Directory, Jamf Pro, and all things enterprise IT.

I was new to working in an office. I followed what I was told, watched how things ran, and started filling in the gaps. I got involved with the Mac Admins community and began learning from people who'd been doing this at scale.

Finding my voice

I spent eight years at a financial services firm in New York. Early on I was learning how to operate in a corporate environment—observing, adapting, figuring out how things worked. Over time I developed stronger opinions about what good IT looks like: structured triage, self-service documentation, proactive maintenance instead of constant firefighting.

I started pushing for those changes—building a knowledgebase, running training sessions, making the case for better tooling. I learned how to advocate for the right approach and back it up with evidence.

Becoming a leader

Over eight years I built the Mac endpoint platform from scratch, stood up security monitoring, and mentored a junior hire. I hosted training sessions on macOS skills—someone learned keyboard shortcuts for copy and paste, others discovered Spotlight. I wrote monthly cybersecurity education newsletters for seven years straight. I stayed because I kept finding things to build, and left when I'd done everything I could.

What I'm looking for

I'm in Austin now, building things with Claude Code and looking for my next role. I want to work somewhere that treats IT as a partner—where the goal is to enable people to do their work faster.