Buyers Remorse - Chased the SWE title but job is really devops
Hey guys, I’d love to get your advice and thoughts on my situation. I just started a new job 2 days ago (not this company) and I chose this job due to the SWE title over other offers (even over FAANG) but I’m starting to realize this job is a lot more operational and devops heavy than I expected. I’m expected to maintain a critical legacy system, handle support requests and put out any fires. It’s way different from what I expected. Less coding and more managing manual, infrastructural issues. I wanted to do application and system development. I’m already starting to regret my decision and it hasn’t even been week 1. Can anyone slap some sense into me? Will being in devops slow down my career? How can I make the most of this as I have a 1 yr cliff until I get the rest of my equity? Should I reach out to my old offers and jump ship? I keep thinking I made the wrong decision and now there’s a bunch of hiring freezes everywhere. I’ve only been in one company for 6 years so it’s my first time switching and while the pay is great, I’m worried that my engineering skills will atrophy. TC: 260k (150k base + 110k RSU) YOE: 6 #engineering #software #swe #devops
Can you migrate the legacy system to a modern infrastructure by rewriting the code to the cloud (say aws lambda)? I would propose something like that, and if that doesn't get approved, switch. You can also get to learn about kubernetes as devops. This would be useful for future careers as well.
Switch team, keep up your leet code game. If team switch wouldn't work, hop for another job with your shinny title