Senior DevOps Engineer
Were looking for a Senior DevOps Engineer to own how our platform is built, deployed and run. Our feature teams own their modules end to end, and this role owns the ground they all stand on: cloud architecture, pipelines, environments, observability and release safety. It also comes with real influence over how the whole team works, and room to grow that influence over time.
We build with AI. Agents are part of how the team works day to day, not an experiment on the side, and we use them to make the team better at what it already does. You own what you ship whether you typed it or generated it, and if you cant explain it, it isnt ready.
We change how we work fairly often. Not every change lands, and when one doesnt we say so and try something else. The process you join wont be the process youre working in six months from now, so were looking for people who help push those changes along rather than wait them out.
What Youll Do
- Own the path from merge to production and make it the thing we trust. Pipelines, automated checks, builds and the release tooling the teams ship through every day, fast enough that nobody routes around it. Every change is scanned and checked the same way, whoever or whatever wrote it, and the pipeline is what gives us confidence the code is good.
- Own the environments. Dev, staging and production, the infrastructure as code behind them, the cost of running them, and the state theyre in on a Monday morning.
- Own observability. Decide what we measure and what wakes someone up, and make sure a developer can tell whether their change is healthy without coming to find you.
- Review the platform and infrastructure work, and the areas that bite us: document query and index design, heavy data processing, anything touching performance or security. Fix root causes rather than kicking problems down the road.
- Use agents daily on real infrastructure and platform work, and bring back what you learn. Try new tooling and process, judge it honestly, and help the team adopt what works.
- Work in the open. Linear issues before the work, a spec for anything feature-sized, and a weekly update people can read instead of asking.
Who You Are
- Youve designed cloud architecture thats still running and carried the pager for it, so you weigh cost, reliability and security together rather than trading one off quietly.
- Youve built the pipeline, not just used it, and you can stand up an environment from code rather than from memory.
- You can read and write application code, so you understand what the teams you support are building and can meet them in their own codebase.
- You use agents daily and have opinions from real use, not from headlines. You own what you ship whether you typed it or generated it, and you can explain and defend it.
- Youre forward thinking. You read ahead of where the team is, form a view, and bring people with you rather than pushing tools at them. People come to you for a second opinion and leave better at their own work.
- You own your failures and stop them recurring, and you adapt quickly when things change. Priorities move, tools move and the way we work moves, and you get on with it rather than waiting for things to settle.
Qualifications
- 5+ years designing and running cloud architecture in production, with clear ownership of something real.
- Strong CI/CD and release process design, including infrastructure as code, and a clear view of the automated gates that hold the line on security, architecture and code standards, whoever or whatever wrote the change.
- Observability and quality tooling (e.g. Sentry, PostHog, SonarQube), and a view on what should page someone.
- Software security principles and practices, applied to a running platform.
- Running a document database in production: indexes, query performance, backup and recovery.
- Strong automation and scripting, plus enough application development to work inside the product when you need to. Were a JavaScript and TypeScript shop.
- Daily hands-on use of agentic coding tools, with a clear view of where they help and where they dont. We use Claude Code.
Bonus Points For
- Docker and container orchestration.
- Azure. Its our primary cloud.
- Building the test, preview and staging environments teams rely on.
- Helping a team work out its own rules for AI-assisted development, rather than inheriting someone elses.
- Multi-tenant SaaS architecture.
- Cost management at a scale where it starts to matter.
Why Enaimco?
- Work on a platform offshore operators run their integrity work through, alongside the engineers who use it.
- Build for subsea assets and the people responsible for them, where a bad release costs an operator real time.
- A role with reach. What you build here is used by every team, every day, and the way you work sets the pattern others follow.
- A team growing fast enough that theres room to go deeper on the craft or wider on leading people, depending on which you want.
- A written SOP for how we work, including how we use agents, built by the team and still changing as we learn.
- Nobody is ranked by pull request counts or lines shipped.
- Competitive salary and benefits, including health and dental coverage.
- Flexible working hours and location.
