Collaborate, Learn, and Ship Work That Matters

Why I do this work

Technology is most satisfying when it solves a real problem with people who care about the outcome. I’m motivated by genuine curiosity (why did that fail? what would catch it earlier?) and by proactive work that prevents the next page, not just the current incident. Collaborative environments where sharp engineers push each other, where ideas turn into working systems quickly, and where you can see the impact of a change: fewer pages, faster recovery, a workflow that used to take an hour and now takes none.

How I like to work

I enjoy pairing on hard problems, writing documentation that helps the next person, and mentoring when I can offer something useful. Peers have described me as calm under pressure and willing to take ownership of systems and projects. I try to earn that by showing up prepared, communicating clearly during incidents, and leaving things better documented than I found them.

Learning as a habit

Growth isn’t a one-time certification. It’s projects, postmortems, side experiments, and failure. I may not have all of the answers, who does? But I am willing to find the best solutions available. I try my best, learn from mistakes, and leave notes for the next person.

My homelab is where I break things on purpose. If something’s going to implode, better there than in production. That’s what dev environments are for, am I right?

When I’m curious about how something works under the hood, I dig through internal wikis and repos. I’m studying Machine Learning Operations (MLOps) for the same reason: how do we trust what runs in production? is the question I keep coming back to.

What I’m seeking

A team where I can focus on work I enjoy (reliability, automation, and increasingly ML-adjacent systems) while validating my understanding against real constraints and continuing to level up. I’m looking for high-impact projects, honest feedback, and room to innovate without sacrificing operational discipline.

Outside the Backlog & Ticket Queue

When I’m not automating something, I’m usually still tinkering: homelab rebuilds, private repos, chaos and monitoring drills, or a small tool that might become useful to someone else. Sometimes it’s just a deep dive down a rabbit hole for something I’m curious about at the time.

But I strongly believe that balance is important. I also like to enjoy life away from my desk.