Engineering Manager, Tooling Interview Experience

Can you walk me through your background and why this role fits?

I walked them through my low-level backend background and my more recent tooling and SRE-heavy experience, which was exactly why this role made sense. I was happy where I was, so I explained the move would have to be about fit and scope, not running away from something. The recruiter also spent a lot of time preparing me for later rounds and making sure I was familiar with the culture memo.

Walk me through your work history, what you're doing now, and the kinds of teams you've managed.

This round was very much about me describing my work history, current role, day-to-day work, and the teams I'd managed. I also talked through some recent projects and why my background was relevant for a tooling team. It did not feel like they were reading off a list of 'tell me about a time' questions. It was more them getting a feel for me and whether my experience matched what they needed.

I used an example of a big cross-team initiative with multiple stakeholders and dependencies. It was a hard cultural, mental, and infrastructural shift, and it was controversial enough that a lot of people were not bought in right away. They kept drilling into the challenges, how I handled the stakeholder side, what the outcome was, and especially what I did differently from others who had tried to push the same change before me and failed.

I started by clarifying requirements, including refresh cadence, scale, and reliability expectations, then walked through the building blocks, caches, CDN, and the different recommendation sources like user-specific versus global. The odd part was that I had to do it all verbally and draw for myself on paper. Where I got a bit stuck was on signals. They clearly wanted things like hover-over time on a title, and I pushed back that if somebody hovers but never clicks, that does not automatically mean real interest.

I got this topic more than once, which made me think the interviewers were not fully coordinating. I answered with real management situations around low performance and, where relevant, what happens when it goes all the way to letting someone go. They wanted the full chain: what the issue was, what I did with the person, whether it improved or ended in exit, and how the rest of the team was affected.

They asked about conflict in a very practical way, both internal to a team and across team boundaries. I answered with actual examples, and then they would keep building follow-ups on top of whatever detail I gave, so one answer could turn into a pretty long discussion. The style was less about hearing a polished framework and more about understanding exactly how I operate when things get difficult.

I answered from my own management practice rather than theory. My overall read in these people rounds was that they wanted proof that I had already dealt with these situations in reality, not that I could give a nice abstract answer.

I talked through how I actually do it in my teams, including balancing tech debt, operational work, and new projects. My sense was that they were much more interested in how I implement this in practice than in hearing some named prioritization framework.

Where do you think you did very well in these interviews, and where could you do better? What would you change?

This came from the hiring manager in the later chat, and it definitely still felt evaluative, not like a casual debrief. I had not seen that question before in an interview. I treated it as a self-awareness check and answered honestly about where I thought my answers were strongest and where I could have done better.

The lunch with the team was loose because we were eating, but it was probably the most probing conversation. Since this was the team I was supposed to manage, they really wanted to understand how I work, what problems I would solve for them, and whether I would actually help. We talked through what they were working on, how they were approaching it, and I suggested a few ways they could tackle some of their current problems.