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 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, technically deep, and willing to lead when a system needs an owner. 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 a stack of projects, postmortems, and side experiments. I run a homelab to break and rebuild things safely, contribute to internal wikis and public portfolio repos, and study ML operations because it’s the next layer of “how do we trust what runs in production?”

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 ticket queue

When I’m not automating something, I’m usually still tinkering: homelab infrastructure, portfolio projects, game development experiments, or tooling that might graduate from “personal” to “someone else could use this.”