Skip to main content
All Questions

Tell me about a time you had a conflict with your manager.

Unlock detailed company stats for this questionUpgrade

Interview experiences

4 shared
Microsoft · 5 months ago
"I went through a pretty long Microsoft process for an SDE II role compared with other companies. It started with a HackerRank, then a one-hour recruiter screen that was very focused on motivation and culture fit, and then a loop of three back-to-back interviews on coding, system design, and low-level design. What stood out to me was how vague several prompts were, because I had to keep asking questions to uncover the requirements instead of just jumping into a textbook answer. In the coding round, they seemed to care more about how I reasoned through the binary tree problem than whether I used the exact BFS or DFS terminology. Overall, it felt about the same difficulty as Google or Amazon, but a little more focused on logical thinking and culture."
Software Engineer · Mid Level / L4
Meta · 7 months ago
"The process was first a phone screen followed by a virtual loop with four rounds. The phone screen was a single tree traversal coding problem, and the onsite had two coding rounds, one system design round, and one behavioral round. The most interesting part was a new AI coding section that I hadn't seen before. It sounded new enough that even the format felt a little flexible, but the expectation was still that I do the actual coding myself and only use AI in a limited way. Overall it was pretty challenging, and if I did it again I would spend more time on behavioral prep because that was my weakest part."
Software Engineer · Senior / L5
Meta · 8 months ago
"A recruiter cold-reached out to me for an E5 software engineer role, and the whole process felt very standard Meta. I had a short recruiter call, then a coding screen with two common problems in one session, and I actually did poorly on the easy one but still barely made it through. After that I got the full loop spread across multiple days, and they gave me a few weeks to prepare. The final coding rounds were mostly standard too, but I felt weak in behavioral because I did not have the right work stories ready, especially for conflict, and I think I mishandled system design by not controlling time and not setting scale assumptions myself. I got the rejection after the final round."
Software Engineer · Senior / L5
Meta · 10 months ago
"I got into the process through a referral and started with a recruiter call that was actually very informative. The process was five rounds for me: recruiter, a 60-minute technical screen with 30 minutes SQL and 30 minutes Python, a 30-minute behavioral, and then three loop rounds. The loop was a little different from other data engineer interviews I have done because each round combined product sense, data modeling, SQL, and Python rather than testing them in isolation. The interviewers were super helpful if I spoke out loud and asked clarifying questions, and the recruiters gave me a lot of prep material up front."
Data Engineer · Mid Level / L4

Community answers

No answers contributed by the community yet.

Related courses

Course

Data Engineering Interview Prep

Land your dream data engineering role at Meta, Google, Amazon, Microsoft, Walmart, DoorDash, and other top companies. Learn from mock interviews, frameworks, and advice from senior candidates. Practice data modeling, pipeline design, SQL, coding, behavioral interviews, and more.

Course

Software Engineering Interview Prep

Land your dream software engineering role at Google, Amazon, Microsoft, Meta, Apple, and other top companies. Learn from mock interviews, frameworks, and advice from senior candidates—practice data structures, algorithms, system design, people management, behavioral interviews, and more.