"Tell me about a time you had to deliberately maintain or rebuild your technical credibility as an engineering manager. What was the context, what did you do day to day, and how did it change your effectiveness with engineers and cross-functional partners? If helpful, you can use a Meta-relevant example like a backend, ranking, or Instagram/Feed infrastructure team."
This question tests whether you can lead engineers without becoming detached from the technical work. At Meta, engineering managers are expected to make strong people and execution decisions while still being credible in technical discussions, trade-off conversations, and reviews with senior ICs. Interviewers want to understand how you balance depth with leverage: staying close enough to architecture, code health, and operational reality without micromanaging or acting like the tech lead.
They are also looking for judgment. Strong managers know when to go deep, how to create mechanisms to stay current, and how to use technical context to unblock teams, coach engineers, and influence decisions across functions.
A strong answer is a specific story, not a philosophy statement. It should show concrete habits or interventions, a clear before-and-after, and measurable impact on team execution, decision quality, or trust. The best answers also show self-awareness about where the manager chose not to be hands-on and what they learned from that boundary.