Fractional DevOps and SRE
A fractional hire does not give the work an owner.
Deploys, access, cloud accounts, and the on-call week have no owner. People cover the gaps by hand. A part-time hire can hide that. It does not make the products and the processes agree.
What the search is buying
Keep the platforms up. Cut the bill. Be the one who is called. Three jobs. Under them: shared production access, a change with no record, a calendar of updates.
The post says fractional because a full-time hire feels like too much. The picture is the same. Products and processes do not agree. People bridge them.
What this practice does
We do not add a person to the roster. We trace the platform work, name what is split, and align it. Your team runs it. Identity, network, platforms, onboarding, offboarding, access review, and the week's cadence.
AI only on a step people already do, after we review exposure and cost. A tool or a hire that needs its own team is out.
The infrastructure assessment crosses the systems. Cloud cost and reliability starts from the bill and the outage. Both hand the work back. Neither is a standing fraction of an engineer.
When a fractional engineer is second
After a named owner exists. One person owns the path. Access is not a shared login. The work exceeds the week. Then a specialist can sit in a real cadence. A hire first builds another bridge.
The seams remain when the contract ends, unless we wrote them down and named an owner. That writing is the engagement. A specialist, if still needed, is a later decision. You will have the record.
Before a hire
We write these before anyone posts the job. Empty lines pause the hire.
- Which systems stop revenue or delivery if they fail.
- Who can change them today. A shared account is the fact.
- Whether access review has a date.
- What we would hand someone on day one, other than the cloud.
- Which promise is slipping because nobody owns the handoff.
Empty lines mean an assessment, not a fraction of a person. The name step is this: one owner on each duty that can stop the path. Two owners, or none, is the finding.
How an engagement ends
We scope the first visit in writing before it is scheduled. You receive what is sound, what is split, and the sequence to join it. The record stays with you. We leave when your team can run the next week.
If the note is “we are down and we need someone on the keyboard tonight,” say so. We will say if that is not this engagement. Readiness your team can run is on incident response readiness. Not a retainer.
Contact
Task us with the gap.
Task us with the system that stops the week, who can change it, and where a hire was about to cover it. We reply with a scoped visit, or we say you need a specialist we are not.