Taro Logo
0

Help me choose: Senior SWE vs Reliability Engineer

Profile picture
Mid-Level Software Engineer at Taro Community3 hours ago

I have been doing incident management work for product (not infra) all throughoutmy career, and I'm up against two offers I have at hand.

I wanted your insights on the Problem Management role if anyone has some idea about this role

Option A: Senior SWE : Regular backend development/Java, Spring Boot, microservices, APIs. Building features customers use.

Option B: : Basically you dig through system outages and failures to spot patterns that keep happening. Then you have to convince different engineering teams to actually fix the root causes and put those improvements on their roadmaps. Lots of post-incident reviews and working with service owners to make sure problems get properly addressed. It's more about influencing people and being the technical voice pushing for stability improvements rather than writing code yourself. High visibility role since executives care about platform reliability, but you're mostly coordinating and advocating rather than building things.

What do you think of the problem management role?
Does it have long-term career sustainability as opposed to dev roles where I could earn hard skills in development?

I am in a dilemma because the Option B pays significantly more than A, while option B is progression from what I am currently doing in the similar line of work, Option A will equip me with new set of skills in dev world that I see transferrable (hoping AI will not automate them away down the line?)

9
0

There are no comments on this discussion yet.

Give it an upvote, and you'll be notified when the community chimes in!