The Special Forces Model
In the Consulting model, SREs form a centralized pool of senior experts who are "loaned out" to product teams for a fixed engagement — typically 3 to 6 months. This model is sometimes called the "SRE as a Service" or "Embedded Consulting" model.
How an engagement works:
A product team requests help: "Our service is unstable, we're getting paged constantly, and we don't know why." Two Consulting SREs join the team temporarily. The engagement follows a structured arc:
- Triage (Week 1-2): Audit the service. Map the failure modes. Identify the top three sources of alert noise.
- Stabilize (Month 1-2): Fix the immediate bleeding. Implement SLOs and Error Budgets. Reduce on-call burden to a manageable level.
- Improve (Month 2-4): Refactor the CI/CD pipeline. Add missing instrumentation. Automate the most painful toil.
- Transfer (Month 4-6): Train the developers to own reliability themselves. Write runbooks. Document the SLOs. Hand off the on-call rotation.
- Exit: The SREs leave. The product team is self-sufficient.
Why the exit matters:
The exit is not optional — it is the whole point. If Consulting SREs never leave, they become Embedded SREs without the organizational clarity. The fixed engagement forces knowledge transfer and prevents dependency.
What makes it succeed or fail:
This model requires very senior SREs who can parachute into an unfamiliar codebase, build trust with a skeptical team, diagnose complex problems quickly, and teach effectively. It fails when the SREs are too junior to be credible, when the product team is resistant to change, or when leadership doesn't enforce the exit timeline.