A small, independent team that cares more about building good software than looking busy. We build and run distributed systems — device management, building automation, private cloud, data, identity, and operations — the kind of unglamorous infrastructure other businesses quietly depend on every day.
We sweat the details, tell the truth, treat people right, and keep learning.
We don't care where you went to school, whether you finished, or where you worked before. We care about who you are now and what you can do today. If you're a self-directed manager of one who can be handed a fuzzy problem and turn it into a system people can rely on, you'll feel at home.
You'll own the platform our products and our customers run on. This is distributed systems at the infrastructure layer — clusters, event streaming, identity, data, secrets, and observability — built so everyone above you can ship without thinking about what's underneath.
The goal is boring infrastructure in the best sense: reliable, automated, and understandable. When something does break, it should be recoverable and explainable, not a mystery. You'll design it, run it, harden it, and quietly make whole categories of problems disappear.
The Red Hat ecosystem is home turf: OpenShift, Ansible, Keycloak, and the rest of it. You've run event streaming in production (Apache Kafka and Redpanda), managed secrets properly (HashiCorp Vault), operated PostgreSQL as a first-class citizen, and lived inside the ELK stack when things got interesting. GitOps, infrastructure-as-code, and automation are reflexes, not chores.
A Red Hat Certified Engineer (RHCE) or Architect (RHCA) certification is a genuine plus.
The stack matters more here than in most roles — but judgment under pressure matters more still. You can learn, reason, debug, and stay calm.
Platform and automation
Data and messaging
Identity and security
We work in small, independent teams on six-week cycles, with far fewer meetings and interruptions than you're probably used to.
We're AI-first and AI-native. We expect you to reach for frontier AI models and get everything you can out of them — that's how we build now.
We'd rather read a clear paragraph than sit through a status meeting, and ship a small finished improvement than babysit a half-built one. We value judgment and ownership — no blaming, no "not my job."
You like making infrastructure boring in the best way — automating the toil, killing the 3am pages before they happen, and taking responsibility when they do. You want the why before the how, and you're senior enough to say "not yet" or "this is simpler than we're making it."
You like throwing config over the wall, treating on-call as someone else's problem, or building clever systems nobody else can operate.
Keep the platform reliable, understandable, and automated, so everyone building on it can move fast without fear. Not perfect. Just solid, quiet, and trustworthy.
Interested? Tell us about a system you built or rescued — what was failing, what you decided, and how you'd do it differently now. That tells us more than a résumé.