Skip to main content
All Questions

Tell me about a time when you disagreed or conflicted with leadership.

Interview experiences

4 shared
Amazon · 2 months ago
"It's tougher and more in-depth on the technical aspect. Expect complex examples."
Technical Program Manager · Staff / L6
OpenAI · 5 months ago
"They cold-reached out to me, and the process felt unusual right away because there were a bunch of reschedules and the 30-minute recruiter screen was basically a real behavioral interview. The weirdest moment on that first call was hearing that comp was 'beyond competitive' and 'never a concern,' and then being told they usually downlevel people one or two levels. After that I had two PM rounds: a brutal Friday product-sense interview with an under-specified memory-machine prompt and almost no feedback, then a Monday metrics round that was a smash and felt much more normal. I got rejected before the final rounds, which were supposed to include org dynamics and another business-alignment style interview. The whole thing felt extremely interviewer-dependent, with one round feeling dismissive and pedestal-y and the next feeling collaborative and genuinely strong."
Product Manager · Principal / Director / L8+
Netflix · 2 years ago
"I interviewed for a senior full-stack role in Seattle, and the whole process felt way more specialized than most big-company interview loops I’ve been through. By the time I got into the loop, it felt like they'd already assumed I could code, so the real test was whether my background matched the team’s exact domain and whether I aligned with the culture memo. The technical rounds were practical React exercises tied closely to internal tooling, not DS&A problems, and the system design round was surprisingly open-ended and conversational with no architecture diagramming at all. The behavioral side was much heavier than usual, and multiple interviewers repeated the same disagreement or feedback themes to see if I had more than one canned example. Overall, it felt less like a generic company process and more like a team trying to hire someone who had basically already done their job before."
Software Engineer · Senior / L5
Netflix · 2 years ago
"I interviewed for a senior full-stack role in Seattle, and the whole process felt way more specialized than most big-company interview loops I’ve been through. By the time I got into the loop, it felt like they'd already assumed I could code, so the real test was whether my background matched the team’s exact domain and whether I aligned with the culture memo. The technical rounds were practical React exercises tied closely to internal tooling, not DS&A problems, and the system design round was surprisingly open-ended and conversational with no architecture diagramming at all. The behavioral side was much heavier than usual, and multiple interviewers repeated the same disagreement or feedback themes to see if I had more than one canned example. Overall, it felt less like a generic company process and more like a team trying to hire someone who had basically already done their job before."
Software Engineer · Senior / L5

Community answers

No answers contributed by the community yet.

Related courses

Course

Product Management Interview Prep

Land your dream PM role at Anthropic, OpenAI, Meta, Apple, Google, and more. AI product sense rounds, vibe-coding prototypes, metrics questions, and the AI fluency interviewers now expect. Ace product strategy, product sense, analytical & execution, leadership & drive (behavioral), and technical PM interviews.

Course

Product Skills Course

This course covers the fundamentals of product management, helping you understand the basic skills a product manager needs.