Azure Networking - Bad decision?
Work life balance in Azure Networking (Bay area). Is it as bad as blind shows it to be? Too much ops load? Any inputs would be appreciated ! #microsoft #azure #networking #opsload #wlb #worklifebalance #bayarea TC : 200k Exp : 4.5 years
Avoid it if you can
A friend of mine went to Azure Networking in Redmond. I tried to talk him out of it. I've seen first hand a giant amount of churn, reorgs, passing around projects, and general disorganization. He still went anyway and he's loving it. Learning a lot every day, work life balance seems to not be so bad when not on call (and mostly rerouting when on call), and he's found a great team where he's able to make a big impact. So moral of the story is... Uh... I don't know. Maybe it won't be terrible.
Avoid
If you are in Cisco, I think you should jump to Microsoft unless you have better offers. Cisco is a sinking ship with onprem only technologies. Moving to Microsoft will give you an opportunity to work on cloud side of things. If you don’t like azure networking, you can always move internally within Microsoft to other teams.
Avoid
Gets worse, promos are based on how close you are with your mgr, how loud you can bark on calls, it’s easy to get to principle in azure networking without doing any coding. Recent principle promos are a good example. Promos are based on upper managements desperation to jump to say 67 -> 68 aka give an easy promo to undeserving direct reports so that your in a position to move to the next level
I 100% agree with this.
Tc or gtfo
Updated