Preparing for Manager Interviews When You’ve Only Been an Individual Contributor

Manager interviews feel different from coding rounds. Nobody cares that you can reverse a linked list if you cannot describe how you unblocked two teammates who disagreed. If you have only been an IC, you are not automatically disqualified—but you cannot bluff a performance-review philosophy you never practiced.

What they are trying to learn

Panels usually probe: how you prioritise, how you give feedback, how you hire or ramp people, how you handle underperformance, how you communicate with product and stakeholders, and whether you still respect the craft enough to support ICs rather than micromanage. Titles on your resume matter less than concrete moments.

Stories you already have (even without direct reports)

• Mentoring an intern or junior through their first production change.
• Driving a project where you coordinated across design, QA, or support.
• A conflict about technical approach that you helped resolve without escalating into a week of Slack drama.
• A time you raised quality or reliability concerns and changed the team’s default.

Write these as situations with stakes, your actions, and outcomes—same discipline as strong behavioral answers in HR and behavioral rounds, but with more emphasis on other people’s growth, not only your heroics.

Topics to study without pretending

Read how your company (or target company) thinks about leveling, on-call, and planning—if that information is public or shared in the process. Be ready to discuss how you would run a 1:1, what you would do in the first 90 days as a new manager, and how you would protect focus time for the team. Borrow frameworks lightly; interviewers notice cargo-culted TED-talk language.

If the role still includes technical screens, do not abandon IC prep. Many EM loops keep a design or code-adjacent conversation. Balance matters.

What not to fake

Do not invent direct reports. Do not claim “I hired ten people” if you only sat in one panel. Do not trash your current manager to sound senior. If you want the path but are early, targeting tech lead / player-coach roles can be a more honest bridge than skipping straight to a large org chart.

Questions you should ask them

Ask how success is measured for this manager role in the first two quarters, how much hiring vs delivery vs firefighting exists, and how the team handles underperformance. Good questions signal seriousness—pair with habits from what to ask at the end of an interview, tuned toward people and systems rather than only tech stack trivia.

Translate influence you already had into clear stories, study the people problems managers actually face, and stay honest about what you have not done yet. That combination interviews better than borrowed jargon.