There are perks and benefits. Some engineers are fun to work with.
Microsoft Security Copilot has a deeply unhealthy culture. Management completely micromanages employees. Performance ratings are heavily dependent on individual manager discretion. Actual accomplishments matter far less than maintaining a favorable relationship with leadership.
The environment rewards politics over results. Employees have little visibility into how ratings are determined, and there is no clear connection between performance and outcomes. This creates a culture where people focus on managing perceptions rather than delivering impact.
The org is disorganized, priorities frequently change, and there is little alignment around long-term goals. Leadership does a poor job of communicating direction, making it difficult to understand what the team is trying to achieve.
Concerns brought to HR and upper management about poor management practices are not addressed in a way that led to any noticeable improvement, accountability, or resolution.
Work-life balance is also poor. Tight deadlines, shifting priorities, and management expectations frequently created pressure to work beyond normal hours. Sustained workloads and constant urgency made it difficult to maintain a healthy balance over time.
Despite being part of a high-profile product, the organization operates largely in maintenance mode. There are limited opportunities to learn new technologies, take ownership of meaningful initiatives, or grow professionally. I would not recommend Security Copilot as an org to anyone.
Applying for a role at Microsoft was both an exciting and nerve-wracking journey. Application Timeline Oct 30: Submitted my application through the portal without a referral. Nov 1: Received a technical assessment on Codility. Nov 19: Got an email to
On-campus interview: I waited about two weeks before hearing back. They were very nice and flew me out to Seattle. There, I had a chance to interview with four different teams inside of Cloud and Enterprise (one of the organizations within Microsoft
The first interviewer had not even glanced at my resume and was dismayed when I turned out to be an experienced professional, not fresh out of college. I was never asked about my professional experience, nor were there any technology-specific questio
Applying for a role at Microsoft was both an exciting and nerve-wracking journey. Application Timeline Oct 30: Submitted my application through the portal without a referral. Nov 1: Received a technical assessment on Codility. Nov 19: Got an email to
On-campus interview: I waited about two weeks before hearing back. They were very nice and flew me out to Seattle. There, I had a chance to interview with four different teams inside of Cloud and Enterprise (one of the organizations within Microsoft
The first interviewer had not even glanced at my resume and was dismayed when I turned out to be an experienced professional, not fresh out of college. I was never asked about my professional experience, nor were there any technology-specific questio