Careers
We have no open roles at the moment — and we'd rather tell you that on the page than run a permanent "always hiring" board that quietly collects applications nobody reads. If you're a senior infrastructure engineer, the rest of this page is still worth two minutes: we would rather hear from the right person before we need them than after.
What the work actually is
Not one company's stack for five years. Several at once, each with a different problem on a different week.
Breadth, by design
A Kubernetes upgrade one month, Postgres replication the next, a compliance push after that, and a migration that pulls in the network. It is the opposite of owning one service for years — if that variety sounds exhausting rather than interesting, this will not suit you.
Never alone on an engagement
Every piece of client work has at least two of us on it, with specialists rotating in for the parts that need them. Nobody is the single point of failure for a client's production, which is as much a protection for you as it is for them.
Reviewed before it ships
We use AI where it genuinely speeds delivery and not where it doesn't, and every change it produces is read by a senior engineer before it reaches anyone's infrastructure. You would be doing that reading as often as you'd be writing.
Based in the EU, working both ways
DevOps Team is operated from Romania and works with clients across EMEA and the United States, so the day has an early half and a late half. Remote by default; we care where you overlap, not where you sit.
Who we'd want to hear from
Written as specifically as we can manage, so you can rule yourself out in thirty seconds rather than after an interview.
- Genuinely deep in at least one of these — production Kubernetes, AWS or GCP at architecture level, PostgreSQL replication and failover, networking and load balancing (F5 or NGINX), security and compliance work, CI/CD, or observability. Deep in one and competent in two more beats shallow in all of them.
- You've been on the other end of an incident, not just read about one. The interesting part of your experience to us is what broke and what you changed afterwards.
- You can write. Runbooks, postmortems, handover documents, an explanation a client's CTO can follow. A large part of what we deliver is written down, and work that lives only in someone's head is the thing we are hired to undo.
- You're comfortable talking to the client directly. There is no account manager between you and the person whose infrastructure it is.
- You'd rather say "I don't know this one, get the specialist in" than learn it live on someone's production system.
How to reach us
Email [email protected]. Tell us what you have run in production, what broke, and what you would want to be doing more of. A CV is fine but it is the least interesting attachment — a paragraph about a system you fixed tells us far more.
No tracking system, no automated acknowledgement, and no form with eleven required fields. The flip side of that honesty: with no role open, we cannot promise a reply by any particular date, and we would rather admit it than send you an auto-responder that implies otherwise. When something does open up, the people who wrote to us are the first list we look at.
Looking for us to run your infrastructure instead?
That's the other half of the site — and that one we can start on this week.
Book a Free Audit