A common request
Organisations often look for a DevOps engineer when releases are slow, environments drift apart or the people running the service are stretched. That is a sensible request. The engineer's impact depends largely on where they sit, because an engineer placed between developers and operations as one more hand-off can automate that hand-off without shortening the path a change has to travel.
Agree the mandate
Before the engagement starts, agree what the engineer is expected to change, for example the release path for one named service. Set out which decisions they can make themselves, such as changes to pipeline configuration or infrastructure code, which need approval and from whom, and who they report to. A clear mandate saves weeks of polite uncertainty.
Arrange access before the first day
An engineer who spends three weeks waiting for repository, pipeline and non-production account access has spent three weeks of the budget on waiting. Prepare an onboarding plan, agree production access in proportion to the role, and use the same identity and approval routes as permanent staff, so that access can be reviewed and removed cleanly at the end.
Keep ownership with the team
The engineer builds and improves, while the client team owns what is produced. Give every pipeline, module and runbook a named owner in the team, have the team review the engineer's changes, and avoid any arrangement in which one external person becomes the only person who understands how releases work.
Work with operations from the start
Bring the people who run the service into the design of alerts, dashboards and runbooks, and have the engineer join incident reviews. Where a supplier operates the service, invite them to the same reviews. Where a change board approves releases, show it the evidence the pipeline already produces, so that the improved process is also easier to govern.
Measure progress as DORA recommends
DORA describes software delivery with five measures. Throughput covers change lead time, deployment frequency and failed deployment recovery time. Instability covers the change fail rate and the deployment rework rate, meaning the proportion of deployments that are unplanned fixes for problems in production.
DORA's guidance is to apply these to a particular service, use several together, and track a team's own improvement over time. It advises against turning them into targets or using them to compare teams, because a measure that becomes a target soon stops describing reality. Record a baseline in the first fortnight and review it at the end.
Working document: responsibilities and acceptance objectives
A one-page agreement, written before the engineer starts, gives the team and the engineer the same understanding of success.
| Field | What to record |
|---|---|
| Role and reporting | Title, reporting line and the team the engineer joins. |
| Mandate | Decisions the engineer may take, and those requiring approval, with the approver. |
| Access | Systems and accounts required by the end of the first week, and production access arrangements. |
| Objectives | Two or three outcomes, for example removing manual steps from the release of a named service, with baseline measures. |
| Ownership | The team member who owns each pipeline, module or runbook the engineer produces. |
| Knowledge transfer | Pairing arrangements, documentation expected and a handover plan. |
| Acceptance | How completion is shown, for example a team engineer releasing and rolling back the service unaided. |
| Review | The review date and the basis for ending or extending the engagement. |
See how engagements work or discuss specialist capacity.
Further reading
DORA: software delivery performance metrics
DORA: 2025 State of AI-assisted Software Development report
