pierce moore

$ git log --all --oneline --since="2007-01-01"

Certified

• certified curling instructor
• PADI advanced open water diver
• AWS cloud practitioner (lapsed; re-test pending)

Volunteering

Director of Communications · DFW Curling Club

2022 — 2023

Led communications, member engagement, event coordination, and public messaging for a volunteer sports club. Less glamorous than production infrastructure, but the same core skill shows up fast: make the system understandable, keep people informed, and reduce chaos before it turns into work for everyone else.

Elsewhere

woodworking · 3d printing · esp32 / arduino · home automation · curling · scuba · homelab infrastructure · built environments.

What are you looking for?

A senior DevOps or Platform Engineering role. Remote or Dallas-based. I'm most interested in teams running production infrastructure at real scale, multi-region, multi-tenant, or multi-venue, where reliability and developer experience both matter. I'm less interested in pure cloud-native greenfield work and more interested in the messy reality of production systems that have to serve humans in physical spaces.

Why are you leaving your current role?

I'm not in a rush. I've built something I'm proud of at Drive Shack / Puttery: a multi-venue Kubernetes platform, company-wide Ansible, major cost reductions, and a long list of incidents handled well. I'm looking for the next tier of problem. More scale, more peers who push me, and a team where platform engineering is funded as a first-class function instead of an afterthought.

What's your strongest skill?

Diagnosing production problems under pressure and writing up what happened afterwards. I'm good at the forensics, narrowing down what actually went wrong versus what looked wrong, and I'm a stickler about postmortems that tell the truth, including the uncomfortable parts.

What about software development? You were a developer for a long time.

Twelve years before the DevOps pivot. Full-stack, with real UI and UX experience. I don't bill myself as a developer anymore. DevOps is the title and the work. But that background is why I care obsessively about developer experience in the platforms I build, and I can still write production Python, Node, or Bash without needing to look it up (but I usually still do anyway).

Why haven't you told me about your cat yet?

You didn't ask. This is Linus, orange American shorthair, b. 2014, official CTO. He's been the constant through twelve years of career changes, so he gets to be on every important thing I make. Why the lambda? Because Half-Life 2 is one of the greatest games of all time. And it looks kickass.

What's your stack, in one line?

Kubernetes (Rancher / RKE2) · Terraform · Ansible · AWS · Prometheus / Grafana · Python · Jenkins / GitHub Actions · Helm · VMware / Proxmox. Macbook primary, Linux in production, Windows where needed.

Are you open to relocating?

Remote-first is the strong preference. I'm open to hybrid if the role is in the Dallas / Fort Worth metroplex. Not relocating.

Contract vs. full-time?

Full-time primary. Open to senior contract work on the side where it makes sense and doesn't conflict.

What does "human-centric infrastructure" mean?

Engineers shipping code, operators running it, guests using what we built. They're all users of the platform, and they all deserve to be designed for. Elegance is a means; the end is people.

Biggest mistake you made in the last year?

Trusting that a cloud provider's default pod storage would be fine for a low-traffic Postgres. It wasn't. We lost data on a controller-manager failure and spent a long night rebuilding. The postmortem is honest about that. emptyDir for stateful workloads is indefensible and I should have caught it before production.

What do you not want to work on?

Adtech, gambling, crypto-as-the-product, surveillance, weapons. Not how I want to spend the next decade.

How should I reach out?

Email is best. See the contact section at the bottom of the page. GitHub is /rex. LinkedIn is /in/piercemoore. I respond to all of them within a day or two. No phone number on the website for now; happy to share it once we're in a conversation.

email

email

github

/rex

linkedin

/in/piercemoore

resume

piercemoore.com/cv