Updated by Meta candidates
Engineering Manager Interview Experience
I was really confident of getting an offer, but they told me I scored higher on the management side and failed coding and product design. What surprised me most was hearing the product design feedback was structured so the recruiter couldn't really challenge it.
Interview process
I had a first product design screening round, then went into the full loop, which included coding, another product design, a project retro, and a people management round. The process felt very self-led, especially in the technical rounds, where they gave me a board or editor and expected me to drive the discussion without much prompting. I was told that many engineering manager candidates tend to score higher on the technical side and lower on the management side, but in my case, it was the opposite. I failed the coding round and the full-loop product design round, which really surprised me, since I felt I had answered the product design interview more comprehensively than the screening one. I actually came out of the interviews feeling quite confident I would get an offer, but did not.
- Phone interview
- Technical interview
- Other
- Final round
Interview rounds
8 questions across 5 roundsPhone interview
1 questionOverview
I had a 45-minute screening round on a shared board where I drove a Twitter-like design end to end, and the interviewer mostly jumped in to ask why I made certain choices and how it would scale.
Question types asked
Specific questions asked
Why did you make those design choices?
How would your system function if it had to scale to hundreds of millions or potentially a billion users?
I started by asking a few clarifying questions, then I talked through the design on the board. I laid out the main components and explained my tradeoffs as I went. When they pushed on why I had chosen certain pieces, I defended those choices, and near the end I walked through how I would think about scaling it to hundreds of millions or even a billion users.
Technical interview (1)
2 questionsOverview
The coding round was in a shared editor with two mid-level engineers, with some boilerplate already there, and it was very self-led because they did not prompt much at all.
Question types asked
Specific questions asked
I talked through my approach, wrote code in the shared editor, and added some test cases, but I slightly struggled on this one and could not really get a working output. With about 20 minutes left, we moved on to the second question.
I did a lot better on this one. I kept narrating the choices I was making and why I was writing the code a certain way, then I wrote the solution and test cases and was able to get the output. The interviewers stayed pretty quiet, so I had to drive the round myself.
Technical interview (2)
1 questionOverview
The second product design round was a one-hour shared-board discussion where I used my usual framework, and the interviewer mostly let me run with it rather than steering much.
Question types asked
Specific questions asked
How would you keep track of how many times a user has seen particular genres of ads?
How would you capture whether they interacted with an ad or marked it as 'do not show again'?
I used my usual structure for these. I wrote down the requirements first, defined the non-functionals, talked through the numbers depending on scale, and then broke the system into key blocks and added detail into each one. The scope was not the whole global ad system. It was really about tracking genre views, interactions, and 'do not show again' signals and then using that data to influence what gets surfaced.
Other
1 questionOverview
The project retro was a 45-minute round that started with me drawing the architecture from a recent project and then turned into a conversational drill-down on my decisions and stakeholder handling.
Question types asked
Specific questions asked
Why did you use those components and design choices?
If you had to do it again, would you do it the same way?
Who were the key stakeholders, and how did the project address their requirements?
I started by describing the project and drawing the key blocks. After that, it became conversational. I explained why I had used certain components, what pushed those design choices, whether I would make the same calls again, and who the key stakeholders were. I tied the architecture back to how it addressed their requirements and shared some hindsight on the design decisions.
Final round
3 questionsOverview
The people management round was a 45-minute STAR-based interview focused on how I handle performance, motivation, and stakeholder pressure, and this was the part where I felt strongest.
Question types asked
Specific questions asked
I answered it in STAR format. I framed the situation, the task, my assessment of the problem with the individual, and then the results or outcomes I would want at the end.
I answered this one in the same STAR style and focused on how I would think through the situation and what outcome I was trying to drive with that person over time.
I answered these management questions using the same structure, laying out the situation, the task at hand, my assessment of where the stakeholder or team tension was, and the outcome I would be aiming for.
Interview tips
I would treat it as a one-shot process and give it a real prep block of 20 to 30 days. I would absolutely do mock interviews, especially for coding and product design, because for me, the technical bar was real, and the product design piece was also about how I communicated, not just whether I had the right blocks or scale numbers. I would get direct feedback on how I structure and articulate my answers. I would also try to build rapport on the day because I came away feeling that if the interviewer is on your side, they read your answers more positively instead of constantly trying to poke holes in them.
Company culture
My read is that they still expect engineering managers, even product generalists, to clear a pretty serious technical bar. The interviewers were very hands-off and seemed to expect me to lead the room, which felt deliberate for the level. I was told that a lot of EM candidates do better on technical than management, so they are clearly looking for both and not letting strong people management make up for misses in coding or product design. The product design scoring also felt subjective to me, and once the interviewer wrote the feedback up, the recruiter more or less could not push back on it. I also came away thinking that soft things like rapport matter more than people admit in this process.
Get full access with a membership, or share your experience to try it free.
More Meta interview experiences
“Not all interviewers may be able to adequately ask the right questions to go in depth, but they are absolutely looking for you to provide that depth by yourself. Your examples should not be surface level, but show you actually lived through the situation.”
“I was a little complacent because I’m already ex-Meta, and the surprising feedback was that my project retrospective was only leaning toward hire because I answered a constructive feedback question like they were asking for praise. I cleared the loop, discussed numbers and joining date, and then the offer got put on hold because of the hiring freeze.”
