DevOps

DevOps Engineers enable our engineering teams by delivering standardized CI/CD pipelines, secure coding frameworks and reference architectures that accelerate development while maintaining high reliability standards. The product is the paved road: the fastest way to ship should also be the safe way, and the development teams who use it are the customers.

The CI/CD platform is production. DevOps Engineers are on call for it, because a broken pipeline is an incident for every team behind it, and the paved road is judged by adoption and developer satisfaction as well as by DORA numbers.

You will own features end to end:the specification, the code, the tests and how it behaves in production. This is an individual contributor role with no direct reports, and you are the engineer who answers for whether what you shipped actually works.

The pull request is the visible part. The job is the machine behind it: turning a loosely worded need into something precise enough to build against, naming what can break before it does, proving the change is correct rather than asserting it, and staying with it once it is live.

How we work

• Business alignment and focus come first. Engineering here exists to move the business, not to be busy. You will know which few things matter most this month and why, say so when the work in front of you is not one of them, and land what you committed to on dates the business can plan around, at a quality that does not come back as an incident or a customer escalation.
• Predictable, reliable delivery of quality software is the output of this job, and everything below is in service of it.
• This job gets more hands-on every quarter, not less. The volume of code goes up while the time you spend typing it goes down, so the value moves to the two ends of it: what you specify, and what you verify. You will stay close to production, run the AI harness daily, read code you did not write, and keep your technical judgment current rather than remembered.
• Whoever ships it owns it, regardless of what wrote it. Most code is AI-generated now, so the judgment moved to either side of it: specifying exactly what to build, and verifying that what came back is correct, secure and operable. An agent wrote it is not a defense. Your name is on the merge.
• You do not need to own the roadmap to know why the work matters. You will not be the Product counterpart at this level and you are not expected to be. You are expected to understand what the customer gets and what the business gains from the thing you are building, and to ask before you build the wrong thing correctly. The engineers who move fastest here are the ones who ask that question early rather than at the review.
• You go on call for what you build, and you take your turn on the rotation. Engineering declares risk and timelines in writing for the business to accept, and that includes yours: when a date is at risk you say so early, with evidence, rather than quietly.

Responsibilities

• Own an enablement domain others come to for answers — the CI/CD platform, secure coding and supply-chain controls, or reference architectures and service templates. This is the rung where you specialize: the domain is yours, and development teams escalate to you inside it.
• Build the AI verification layer for your domain. Review agents in the pull-request path, AI-assisted test generation, gates tuned for AI-generated code, and provenance that records what an agent wrote. Show measurable gains in lead time, change failure rate or escaped defects — not adoption alone.
• Make the paved road agent-ready. Golden-path templates and repos that ship with the context files, skills and MCP connections agents need, and CI that runs agents safely: scoped credentials, sandboxing, defenses against prompt injection.
• Enforce quality on everything you own, including what AI wrote. Pipelines are versioned, tested and observable, and your gates fail the build rather than warn.
• Remove recurring toil for development teams, with the AI contribution measured rather than assumed.
• Be the escalation point for your domain. Mentor engineers on and off your team, run enablement sessions that teach development teams to work specification-first with agents, and hold Tech Lead for an enablement initiative when one needs it.
• Go on call for the CI/CD platform. A broken pipeline is an incident for every team behind it; incidents written up with actions closed on dates, toil removed rather than absorbed.
• Write the specification before the code, and verify with evidence on the pull request — the failure cases exercised, not only the happy path.
• Clear what you need from another team yourself. Find the dependency early, agree it directly with the engineer who owns it, and land it ahead of your work rather than escalating once it is late.

Requirements

• 5+ years in software engineering, with real ownership of developer-facing tooling, CI/CD pipelines, or platform/enablement work after it shipped.
• Hands-on technical fluency in: containerization, deploy automation, PHP, Perl, and GitHub Automation.
• Depth in at least one enablement domain — the CI/CD platform, secure coding and supply-chain controls, or reference architectures and service templates — and the ability to read your way into a part of the pipeline you have never touched. You can read a diff in a language you do not use daily and say what is wrong with it.
• Hands-on AI-assisted engineering, in your daily work rather than a trial. You can specify precisely, review generated pipeline and IaC code critically, and tell us where it fails and what you always check before it merges.
• Tests and evidence as a habit rather than a mandate. You write them as you go, you gate on changed code, and you have caught your own mistakes with them.
• You have operated what you built. A production on-call rotation for a platform or pipeline, an incident you owned, and a write-up that changed something afterwards.
• Clear written communication in a remote, distributed team. Decisions and trade-offs recorded in writing, with colleagues across several time zones.
• Managed hosting, cloud or another high-availability service business is a bonus.

We offer

• Visa support and relocation assistance.
• Daily lunches in the office.
• Work in a team of professionals at an international level.
• Comfortable working conditions.
• Opportunity to practice and improve your English.
• Competitive salary and all necessary equipment.
• Medical insurance.

About Nexcess

Nexcess provides specialty cloud solutions for organizations where performance and compliance have to coexist. We serve businesses worldwide, from agencies scaling client sites to enterprises running mission-critical operations. We've built our reputation on deep technical expertise and genuine partnership with every client we work with. Behind every environment we manage is a team of people who take the craft seriously and keep showing up when it matters.