Skip to main content
All Questions

Tell me about a time when you provided important feedback.

Unlock detailed company stats for this questionUpgrade

Interview experiences

3 shared
Meta · 5 months ago
"I interviewed for an M1 Engineering Manager role, and the process included a screening round first, followed by the main loop. The screening consisted of one broad behavioral interview and one system design interview, in which I could choose between machine learning systems, software systems, and products; I chose machine learning. In the main loop, I had another ML system design round, a project deep dive, a team management interview, another behavioral round, and an AI-assisted coding interview. The AI-assisted coding piece was the newest part of the process for me, but the bigger surprise was how behaviorally heavy the EM loop was. My main takeaway is that they expect you to provide depth on your own, even if the interviewer isn't especially good at eliciting it."
Engineering Manager
Netflix · 9 months ago
"My Netflix intern process was four rounds total if I count the OA: two CodeSignal assessments first, then a live coding round, then system design, and then a hiring manager round. I was nervous at every step because Netflix has such a high bar, but the people I met were really free and welcoming, so it felt less like an interview and more like working through things with engineers. The most unusual part to me was the AI-assisted assessment early on and then the longer team-matching wait before the hiring manager round. The earlier rounds usually took about a week to hear back from, but I waited around three weeks for the manager step. Once I got to the manager round, it honestly felt almost definite that I was very close, and I ended up getting the offer."
Software Engineer · Intern
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

Engineering Management Interview Prep

Land your dream engineering manager role at Meta, Google, Amazon, Microsoft, Stripe, and other top companies. Learn from mock interviews, frameworks, and advice from senior candidates. Explore system design, people management, project retros, behavioral interviews, and more.

Course

System Design Interviews

Learn how to answer the latest system design questions across product, infrastructure, and AI domains. Features in-depth video examples, written breakdowns, and helpful reference patterns. Watch senior engineers and managers answer these questions in mock interview videos.