Received an offer but worried I'll be out of my depth
I've been working as an SRE for coming up to 4 years now. I started my tech career in support, then DevOps, and now SRE. My official job title is SRE but in practice the lines at my company are a bit blurred between SRE, cloud engineering, DevSecOps, cloud security and so on, as my company doesn't have a mature SRE practice and the SRE team have to wear multiple hats due to being spread thin (I appreciate this is somewhat common within the industry).
I've been offered an SRE role at a much larger company with a more established SRE culture. They have an embedded model and I'd be working directly with one of the product teams, up to and including helping write application code to help optimise availability and reliability (although this wouldn't be on customer-facing services for the time being).
I'm really excited by the offer but part of me is apprehensive. I'm comfortable working with all the traditional SRE/DevOps-y things (cloud, IaC, alerting and monitoring, incident response, automation and so on), but my current role is somewhat silo-ed, as although we do interact with the product team it's not in a capacity that could really be described as embedded. I'm comfortable with Go and Python for scripting and custom tooling but I understand application engineering is a different kettle of fish, and I haven't had to wear that "hat" in my career before.
I am also a bit apprehensive about how well my SLI and SLO knowledge and experience will translate, as at my current company availability is by far and away the one we track and optimise for the most, to the neglect of the others (n.b. I recognise I'm at fault here for not pushing my company's SRE practice to think harder about these things); I was honest about this, although did my best to put a positive spin on it during the interviewing process (I was also very candid with them about never having been embedded in a team before).
I'm at a bit of a crossroads. I'm fairly content, although stagnant, at my current company, as I feel like I have "maxed out" there for the time being in terms of learning and experience; and as we all know, this industry tends to punish you if you stay in your comfort zone for too long. I've been eyeing a way out into something better for some time now ,and am genuinely excited by this offer, but I wonder if I'm really a good fit for the role and am trying really hard not to let the impostor syndrome creep in.
For those who've moved from a siloed SRE role into an embedded one, how steep was the adjustment (particularly if you found yourself writing application code coming from an ops background)? How did you navigate it and are you happy you took the leap in hindsight? If it felt awkward at first, how long did it take for that feeling to go away? Thanks.
(P.S. I have a fairly long notice period and it's pretty quiet in my company at the moment, so I'd have a bit of time to upskill/brush up on patches in my knowledge if I decided to take it.)