u/Specialist-Address98

Moved from embedded dev to platform engineering, became the cyber champion on our team, and have been loving the work. The most fulfilling thing I've done so far is building a pipeline that automatically rectifies CVEs across our microservices, and runs tests to validate that nothing regressed.

The only issue is the 24/7 on-call rotations. I know the quality of on-call depends on the company or team, but from what I've heard, it seems like platform and sre teams typically have an especially high load.

I'm trying to figure out a good role to pivot to that overlaps with platform engineering, but with less chance of having 24/7 on-call, and devsecops seems like it might be the one.

Transitioned from embedded (5 yoe), to platform engineering 2 months ago.

Recently, the principal engineer on our team was showing me our cloud cost dashboards, and complaining about how much of a headache it is to justify the huge o11y costs to Finance every month. I said that I'd like to take on that responsibility, and that it sounds like something finops would do.

He said great, and gave me the first official "finops champion" title of the team. I realize this may be a huge mistake given how little professional experience I have with cloud, but I feel it's worth a shot and will be a good learning experience regardless of what happens. Also the principal engineer said he will still be at the meetings to help out if I'm really floundering.

My first meeting with finance will be in 6 weeks. I know I won't be expected to contribute much if anything, but would like to get started.

Any general advice? Or recommended resources or certs (like from FinOps Foundation) worth starting over the next few weeks?

Spent 5 years working in embedded/FPGA before recently moving into a platform engineering role.

I enjoy the work, but one thing I don't think I can do long-term is the 24/7 on-call rotations.

If I spend 2-4 years here, would it be difficult to transition back into embedded roles?

I do have a homelab and plan to keep building embedded projects on the side, so I'm hoping that I won't be completely disconnected.

Moved from embedded to platform and love the nature of work. But the only issue is the 24/7 on-call rotations.

From what I know (which isn't a lot) it seems that my company actually does on-call pretty well. Senior team members said they try their best to follow the guidelines in the Google SRE book. So it’s not bad, but can't see myself doing these 24/7 rotations for more than 2 years.

Trying to figure out if I should focus on trying to find a platform role with no on-call (or at least follow-the-sun), or just transition back to embedded where on-call is rare in a couple years.

I have no regrets taking this platform job either way though because I've always been interested in learning how large company platforms are built and operated.

Made a transition from embedded (5 yoe) to Platform engineer last month. Was asked about areas where I think the team could improve, and I pointed out automated testing as one of them. Manager said great, because they were looking for somebody to lead the automated testing initiative for our o11y infra and REST services, and my background building automated test pipelines from my previous role would transfer nicely.

I agree, but coworkers said that most start working on tests initially, then move onto other things like service development, or operating infra. So I was thinking there must be a reason people decide to move on from improving tests, maybe not a lot of room for growth.

Also, the reason I took this role was to move more towards SDE/Devops instead of SDET, because I was basically that in my previous team, and I pretty much had to find a new job to relieve myself of being the "test guy" since nobody else wanted to do it.

Made a transition from embedded (5 yoe) to Platform engineer last month. Was asked about areas where I think the team could improve, and I pointed out automated testing as one of them. Manager said great, because they were looking for somebody to lead the automated testing initiative for our o11y infra and REST services, and my background building automated test pipelines from my previous role would transfer nicely.

I agree, but coworkers said that most start working on tests initially, then move onto other things like service development, or operating infra. So I was thinking there must be a reason people decide to move on from improving tests, maybe not a lot of room for growth.

Also, the reason I took this role was to move more towards SDE/Devops instead of SDET, because I was basically that in my previous team, and I pretty much had to find a new job to relieve myself of being the "test guy" since nobody else wanted to do it.