4 ms·
64 here. I do occasionally dream about going elsewhere for beaucoup bucks (not that I'm complaining about my TC), but also, I do really love what I do, who I wo
by mynameisash 5y ago
64 here. I do occasionally dream about going elsewhere for beaucoup bucks (not that I'm complaining about my TC), but also, I do really love what I do, who I work with/for, etc. So I acknowledge the trade-off I'm making -- good W/L balance, very low stress, but not as much money as as my principal engineer friend @ Amazon makes.
- justrudd 5y agoI was a 63 being considered for 64 during my time at Microsoft. I loved it. Great W/L balance. Interesting work. Great coworkers. Was really looking to make that a long term gig. But my org got disbanded, and I got rolled into Mobile (circa 2008/2009 when Ballmer was using the economic conditions as an excuse to shutdown orgs). I was there building the first Windows phone. I hated that org. It was all schedule chicken and politics (you could have an iPhone, but you couldn't use it during meetings in front of GM or higher). I had code reviews rejected for "You aren't going to need that". I'd point them at what was coming in the next cycle and got lectured about "you should be focused on your current tasks not future tasks" in writing. But in person (i.e. no written record), I was told to write the code how the reviewer wanted (a 64 or 65 as I recall) and just keep the changes stashed for when the real work showed up. I hated working that way. So I got blackballed for a shitty attitude (and rightfully so. My attitude was shit). With that said, I'm still friends with some people at Microsoft. And they love it. Just gotta find the right org (just like Amazon, Google, etc.)
- nixgeek 5y agoNot really sure 65 = L7. Probably something closer to 66/67 is a better match for Amazon L7/PE. Apples to oranges comparison of compensation. Source: Done both AWS L8 and MSFT Partner roles. Have hired and led teams with Principal+ in both places.