When should a startup hire its first DevOps engineer?
Later than most founders think, and earlier than most engineers want. The common advice is a ratio. A better answer comes from counting the hours infrastructure already takes from your team.
Pay data checked: 19 Oct 2026
Why "one DevOps engineer per five developers" doesn't help.
You'll often read that you should hire once you have three or more developers, keeping a ratio of one DevOps engineer to every three to five. Taken literally, that tells a four-person seed startup to spend 20% of its engineering payroll on infrastructure. Very few should.
A more honest test: for the last eight weeks, how many hours did your developers spend on deploys, cloud access, incidents, CI and the AWS bill? Write the number down. That number, not headcount, tells you what to buy.
The signals, by team size.
| Team | Usually true | What tends to work |
|---|---|---|
| 2 to 5 engineers | A few hours of infra a week, mostly by the CTO. One production environment. | Managed services, a checklist, an occasional outside review. |
| 6 to 10 engineers | Deploys need coordinating. Someone senior loses a day a week to infrastructure. First compliance asks arrive. | Fractional help, 20 to 40 hours a month. |
| 11 to 15 engineers | Several environments, on-call, a SOC 2 audit, costs a board member asks about. | Fractional at 40 to 80 hours, while you recruit. |
| 15+ engineers, or infra-heavy product | Infrastructure is a full-time job every week. | Hire. Keep outside help for peaks and second opinions. |
Our rule of thumb, not a survey. Data and ML-heavy products move up a row.
What the first DevOps hire actually does.
Not Kubernetes, usually. In the first six months a good first hire:
- Moves everyone to single sign-on and removes the keys nobody remembers creating
- Puts the infrastructure into Terraform so it can be reviewed and rebuilt
- Makes deploys boring: from CI, with a rollback that's been tested
- Builds monitoring that pages for real problems and stays quiet otherwise
- Owns the AWS bill and the first SOC 2 controls
Most of that is a project with an end, which is why fractional help often covers the first year. Our production readiness checklist is roughly the first hire's to-do list.
DevOps engineer salaries and rates in 2026, US and UK.
| Role and market | Figure | Source |
|---|---|---|
| UK permanent, median salary | £70,000 | ITJobsWatch, 6 months to 18 Oct 2026 |
| London permanent, median | £83,750 | ITJobsWatch, same period |
| UK range, 10th to 90th percentile | £49,377 to £100,000 | ITJobsWatch |
| UK contractor, median day rate | £525 | ITJobsWatch contracts |
| US base salary, job-posting median | $153,000 | Jobspipe, 814 postings |
| US base salary, survey average | about $139,000 | Underdog.io |
| Fractional senior DevOps, hourly | $100 to $153 | GoFractional, 25th to 75th percentile |
Our assumption: employer taxes, benefits, equipment and tools add 20 to 30% to base pay, plus a one-off recruiter fee of about 20%. Adjust for your own payroll.
What a hire costs against the alternatives, year one.
| Option (US figures) | Year one | Notes |
|---|---|---|
| Full-time hire at $140k base | about $196k to $210k | Base plus 20 to 30% overheads, plus a $28k recruiter fee. 2 to 4 months to fill. |
| Contractor, 3 days a week at $120/hr | about $150k | No cover for holidays; context leaves with them. |
| Fractional, Growth plan | $4,900 x 12 = $58,800 | Up to 40 hours a month, a small team behind it. |
| Fractional, Scale plan | $7,900 x 12 = $94,800 | Up to 80 hours a month, 1-hour response for outages. |
The comparison only holds while the work is part-time. At 160 hours a month of real infrastructure work, a hire is cheaper and better. That's the honest crossover.
Questions worth asking your first DevOps candidate.
- Walk me through the last production incident you handled. What did you change afterwards?
- We have one engineer, an AWS account and no Terraform. What do you do in your first two weeks?
- When would you choose ECS over Kubernetes, and when the opposite? (Our answer is in ECS vs EKS for startups.)
- How would you tell me, as a founder, whether our AWS bill is reasonable?
- What would you refuse to build for a team our size?
The last one is the best filter. A good first hire says no to complexity more often than yes.
When fractional is the wrong answer.
Hire instead of buying fractional help if infrastructure is your product (a developer platform, a data pipeline you sell), if you need someone in the office every day, or if the work has filled a full week for three months straight. We'd tell you the same on a call.
If it's not there yet, fractional DevOps covers the gap, and our pricing is on the page.