Cons:
I've been here for 8 years. When I started, the company was pushing new products and reacting to the harsh realities of real-life politics and market conditions. Everyone felt connected and guided towards the mission.
Ever since MSFT management came in, they started turning the eng culture into more numbers-driven rather than product/innovation-driven. A key part of this is mandating diff counts as well as tying performance mainly to that rather than genuine impact or work.
Over time, I have seen this culture drive multiple good engineers away and continue to degrade the mental health of employees who feel like they have to continuously put up meaningless code reviews just to hit a monthly quota.
This isn't how engineers should work or how a company should incentivize engineers. In a world where engineers are worried about being replaced by AI, this kind of culture not only incentivizes it but also rewards those who use it to do absolutely nothing.
I have lost count of the amount of diffs where people ask for stamps with just 1 or 2 lines of changes. Not only is this requirement awful, but it's incredibly inconsistent and seems to play into politics.
I'm seriously considering leaving and would suggest that people who are looking to join consider if this is the culture for them.
For those who are still here and read this review, bring this up with as many upper managers as possible.
The recruiter was nice and reached out to me. I scheduled a technical phone interview, and the interviewer asked me to code online, where I could submit the code and run test cases. I had a few issues with the syntax. I completed one of the coding q
Very pleasant interviewers, but my software skills didn't cut it. I came away thinking that the people at Uber were very smart yet humble. There was a one-hour phone screen. After the usual chit-chat about my resume, I was asked a programming questi
Phone interview: Previous projects, then two standard technical questions. Onsite interview: Somewhat of a joke. The whole process felt quite disorganized, and two of the interviewers on the loop quite plainly didn't know what they were talking ab
The recruiter was nice and reached out to me. I scheduled a technical phone interview, and the interviewer asked me to code online, where I could submit the code and run test cases. I had a few issues with the syntax. I completed one of the coding q
Very pleasant interviewers, but my software skills didn't cut it. I came away thinking that the people at Uber were very smart yet humble. There was a one-hour phone screen. After the usual chit-chat about my resume, I was asked a programming questi
Phone interview: Previous projects, then two standard technical questions. Onsite interview: Somewhat of a joke. The whole process felt quite disorganized, and two of the interviewers on the loop quite plainly didn't know what they were talking ab