Hivemind Division
Senior Engineer, Platform Infrastructure (R5516)
- Location
- Dallas, Texas, United States
- Work type
- On-site · Full-time
- Salary
- USD 120,000 – 180,000 / year
- Posted
- (2 months ago)
About the role
Why This Role Exists:
We build and operate the platform that our engineers and our customers rely on.
The platform isn't a product that's ever "finished." It's something we improve continuously. Every deployment, outage, bug, and annoying manual task is an opportunity to make the system better.
An L3 Platform Engineer is a fully contributing member of that effort.
This isn't a ticket factory. We expect engineers to think critically, collaborate closely, and continuously improve both the platform and the way we build it.
How We Work:
Our engineering culture is built on Extreme Programming and Continuous Delivery.
That means:
Pair programming is our default way of developing software. We work in small batches. We integrate continuously. We automate repetitive work. We test first whenever practical. We optimize for learning and feedback instead of individual velocity. The team owns the outcome.If you're looking for a role where you're handed tickets, disappear for a week, and come back with a pull request, this isn't it.
What You'll Do:
What We Expect:
You Build for Change
Software is never finished.
Your goal isn't simply to make today's feature work.
Your goal is to leave the code, infrastructure, and deployment process easier to change tomorrow.
You Prefer Automation
If humans perform the same task repeatedly, the system probably needs improvement.
Manual processes are temporary.
Automation is the destination.
You Think in Small Batches
Large changes hide mistakes.
Small changes expose them.
We value engineers who can decompose large problems into safe, incremental improvements.
You Work as Part of the Team
Platform engineering is a collaborative discipline.
You bring potential solutions to the team, clearly explain your reasoning and tradeoffs, and help the team build a shared understanding of the code or design not merely produce it. You are responsible for understanding, validating, and clearly communicating the work you contribute.
You Improve the System
When something goes wrong, we don't stop at fixing it.
We ask:
Why did this happen? Why wasn't it detected sooner? How do we make this impossible or at least unlikely next time?Incidents should improve the platform.
Technical Expectations:
You should be comfortable working across most of these areas:
Kubernetes Linux Networking fundamentals Git and trunk-based development GitLab CI Infrastructure as Code Ansible Terraform Helm Zarf Containers PKI and certificate management Secrets management Observability Infrastructure testing Troubleshooting distributed systemsNo one is expected to know everything.
We do expect you to learn quickly and become productive in unfamiliar systems.
How Success Is Measured:
Successful L3 engineers consistently help the team:
Deploy more frequently. Deploy more safely. Recover from failures faster. Remove manual work. Reduce operational complexity. Improve documentation. Increase confidence through testing. Deliver changes in small, reversible increments. Make the platform easier to operate and easier to evolve.