About Site Reliability Engineer roles...

I have an interview for a site reliability engineer for a good company. I'm currently an SDE and I enjoy development work, but I'm looking for a role in a new city and this one kind of interests me.

My concern is that I probably won't want to be an SRE for a long time (more than a few years) and they don't seem to do as much development work as an SDE, obviously. This branch of the company is still pretty new, so they say that the role will be more development heavy than usual, but I don't want my ability as a developer to dwindle while working as an SRE and lower my chances of getting a position as a SDE later on.

Has any one had experience with getting work as an SDE after being an SRE? If you were/are and SRE, what is the usual amount of time an SRE spends doing coding, even if it's just scripting in Python/Go/whatever?

Posted Oct 9, 2016, 3:37 AM UTC

12
LM10Site Reliability Engineer•

I'm an SRE and I don't plan to move to an SDE role any time soon, but I can answer the second part of your question.

The bit of a cop out answer is that it depends. Your company's structure and definition of the SRE role is the primary factor in deciding how much development work you get to do. My company (large social network) aims for a 50/50 split between operational and development work for SREs. Another place I'm looking at moving to (famous consumer facing company) wants SREs to be part of the dev team and contribute code. So YMMV, but there's no reason why you can't go back to an SDE role after working as an SRE for a few years.

2
DanteAtWorkOPSoftware Engineer•

Thanks for the response.

Yeah the company said that the role on the team would be more development based, but it would probably transition closer to 50/50 once the office "matured" or whatever. Now to just land an offer.

1