Taro Logo

Great place to coast with linear growth

Software Engineer II
Current Employee
Has worked at Microsoft for less than 1 year
January 13, 2022
3.0
RecommendsPositive OutlookApproves of CEO
Pros
  • Great work-life balance (usually never expected to check work-related messages after 5 p.m.)
  • Nice people across the company
  • Linear growth is easy to predict and work toward
  • Chance to work on a team whose product/service impacts millions
Cons
  • Linear growth stagnates high-potential employees, preventing them from growing at the same pace as less ambitious colleagues.

  • Way too many PMs and not enough Engineers. This leads to multiple verticals introduced in the same product but no consistency or connection between these verticals.

  • Prioritization of tasks is a joke. There could be an issue impacting 1M+ users, but they'll put priority on fixing an issue or creating a feature that the PMs or leadership team want to pivot towards because they think it will have impact (it literally never does). They don't use user studies correctly or even acknowledge customer feedback, which leads to important customer-requested features being in massive backlogs.

  • Engineering quality isn't impressive at all and is easily noticeable in product performance, product bugs, service outages, and even internal tools.

  • Engineering teams are underfunded, so there is always work to do and not enough time, which leads to scope creep and delays in shipping features or bug fixes.

  • Build systems are a constant work in progress, and policies are continually being added, which brings down development velocity.

  • The hiring bar has definitely dropped, and some of the new grad hires are questionable.

  • Pay is less than the industry standard, and engineering is underfunded. So, it makes a lot of sense when they report earnings every quarter because they're understaffed on the engineering front and still underpaying engineers.

Advice to Management
  • Promote high-potential employees faster to show your investment in them.
  • Hire more engineers and fewer PMs. If engineers are the ones creating, fixing, and supporting the product/service, there doesn't need to be six-plus PMs in one team just to triage bugs and make specs for features no one has bandwidth to commit to.
  • Prevent organizational leadership from having less federal control over the product's vision and encourage teams to push their own agendas, which promotes better growth in each vertical.
  • Invest in engineering systems so engineers can ship faster.

Additional Ratings

Work/Life Balance
5.0
Culture and Values
4.0
Diversity, Equity, and Inclusion
4.0
Career Opportunities
3.0
Compensation and Benefits
3.0
Senior Management
3.0

Was this helpful?

Microsoft Interview Experiences