Microsoft offers a strong benefits and compensation package, with generous flexibility for remote work and many smart, kind colleagues to learn from.
I was effectively bullied out of a previous org at Microsoft for displaying autistic traits — specifically for questioning the authority of a senior leader, which reflects my neurological wiring rather than insubordination. After switching teams, I was placed under a manager with no neurodiversity training who repeatedly triggered autistic shutdowns.
Despite formally disclosing both my neurodivergence and pregnancy-related health challenges, I was penalized in my performance review for symptoms tied to both — including fatigue, dysregulation, and reduced capacity.
Microsoft publicly promotes disability inclusion, but in practice, accommodations are often ignored, and managers lack the training to support neurodivergent employees. Autistic professionals may struggle with:
Employees can be penalized for displaying traits like direct communication, a preference for predictability, or a need for reduced social overload — even when these needs are disclosed and legitimate.
Work-life balance is another challenge, especially for employees in different time zones who must constantly align with U.S.-based teams. Despite generous remote work policies and smart colleagues, the lack of psychological safety and structural support makes Microsoft a difficult place for many autistic employees to thrive.
If Microsoft truly values diversity and inclusion, it must go beyond surface-level commitments. It’s not enough to celebrate difference in theory — you need to put your money where your mouth is.
That means training managers, implementing real accommodations, and stopping the cycle of penalizing neurodivergent and pregnant employees for challenges the company claims to support.
Until then, the D&I messaging feels hollow and hypocritical.
The typical interview process consisted of four rounds: Leetcode, OOP, and System Design. Most of the interviewers were nice and supportive. During the OOP round, however, I felt the interviewer was disengaged, and it wasn’t clear what the expected
It was a good experience overall. It was a known data structure problem, a low-level design and a high-level design problem. Ask for clarifying questions on what they are expecting. The DSA was medium-level.
Got one assessment. Once you have passed that, there are three interview rounds, each 45 minutes long. For the second round, the interviewer didn't know about Python, but I was able to explain it. I had a little difficulty, but it was a good experien
The typical interview process consisted of four rounds: Leetcode, OOP, and System Design. Most of the interviewers were nice and supportive. During the OOP round, however, I felt the interviewer was disengaged, and it wasn’t clear what the expected
It was a good experience overall. It was a known data structure problem, a low-level design and a high-level design problem. Ask for clarifying questions on what they are expecting. The DSA was medium-level.
Got one assessment. Once you have passed that, there are three interview rounds, each 45 minutes long. For the second round, the interviewer didn't know about Python, but I was able to explain it. I had a little difficulty, but it was a good experien