Can you move from delivery platform work into SRE or infrastructure?

November 19, 2026 5 answers
Asked by _w65+plivaro.9

My platform work is mostly CI/CD, runners, policy gates, and artifact tooling rather than production infrastructure. Does that experience transfer well to runtime-heavy SRE roles?

Also, as organizations grow, is it normal for platform engineers to spend less time debugging infrastructure because product teams own their services?

Answers

5x!canvasgauge_682

Yes, but read the responsibilities rather than the title. Platform engineering, DevEx, and SRE can overlap a lot, or be separate jobs with very different expectations. One SRE team might own much of the infrastructure while another focuses on a narrower reliability remit.

Ask who owns clusters, deployments, incidents, and service debugging. That will tell you more about the role than the label.

Reply to this answer
Rovdeli-9c

Delivery work gives you useful experience with automation, deployment systems, policy, and the software supply chain. It does not automatically demonstrate the Linux, networking, Kubernetes, scaling, and incident response skills a runtime-heavy role may require.

The distinction is especially relevant if your work has mostly been templates and managed tools. Running the compute underneath your tooling gives you a different set of debugging problems. Look for opportunities to investigate runner failures, resource exhaustion, or networking issues, and be clear about what you have and have not owned.

_w65+plivaro.9:

That distinction helps. Owning runners sounds like a useful place to build more runtime experience without pretending it is the same as owning production clusters.

Reply to this answer
Tavqunex.4m

A good bridge is to own more of the delivery feedback loop. Runner reliability, deployment failure rates, rollback time, and service-level signals connect your platform work to production outcomes.

That won't replace on-call or cluster experience, but it makes the reliability side of your existing work easier to show.

Reply to this answer
_m74!drivnelo.3

It can be normal for a platform team to build abstractions while product teams debug their own services, especially when responsibilities are split across teams. That doesn't necessarily mean nobody on the platform side debugs infrastructure. Check the actual ownership boundaries and escalation path for each role.

_p84!zunmari.3:

It's also worth asking whether platform engineers own the underlying tooling or just provide templates for it. Those can be pretty different jobs.

Reply to this answer
_c57!tovrani.2

DevEx is a bit harder to pin down. Work on pipeline templates and policy gates could fit there, but employers may look for different skills depending on how they define the role. Don't assume every DevEx opening is interchangeable with an infrastructure job.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions