Engineering Manager, Data Infrastructure Interview Experience

I spent the first 15 to 20 minutes walking through the last seven years on my resume, which was three companies and the main projects at each. They were unusually well prepared and basically went line by line, so I tried to show that the experience on paper really matched an EM role like this. It felt much more thorough than the usual 'tell me about yourself' version.

Why did you move from IC work into management, and why do you want to keep doing management?

They were very interested in my transition from an IC into management. I explained why I chose management, what I get out of it, and why I want to keep growing there. My big takeaway is you cannot assume they will just grant you that story because you have years of management on the resume.

What technologies and design patterns did you use, why was the project done, and what impact did it have?

I answered at a fairly high level on the project tech, design patterns, and choices, but the interviewer cared a lot more about why the work existed and what business or team impact it had. I was probably too long-winded here. The recruiter later told me that directly, which was actually useful feedback because it told me to lead with impact instead of talking too much about the technology.

He wanted a real example, not a hypothetical. I had to talk through a project where priorities shifted after work was already underway and explain how I reset with the team, communicated the reason for the switch, and handled the tradeoffs. The whole round was less about describing a successful project and more about showing what I do when things stop going according to plan.

Again he started with the theme and asked whether I had a real example, and I did. I talked through cases like losing a resource mid-project, having to rework the plan, and then going back to stakeholders and the team with a revised timeline. My prep advice here is to take every major project on your resume and think through resourcing changes, priority conflicts, design disagreements, and every other fire that could have happened.

I came in with a PDF on one recent big project and used the first part of the round to walk through the phases, the technology, the team involved, and how we shipped it. After that, the interviewer picked one or two deep areas and drilled in. In my case, he was especially interested in GDPR data management, so I had to be ready to go much deeper on the parts of the project that looked most critical.

They pulled examples from my resume and asked me to revisit them through an Anthropic lens. It was not a clean behavioral round with one category at a time. They would ask about something I shipped, what went wrong, what I learned, and then how I would handle the same thing here. I would absolutely study their published principles beforehand because that framing was underneath the whole conversation.

They did go into ethics. I said those are not everyday decisions I personally get to make alone, so I would surface the concern, talk through it with leadership, and make sure the decision was aligned at the right level instead of pretending I would unilaterally decide it. The interviewer was pretty poker-faced and open, so it felt more like they wanted to understand how I think than catch me in a right or wrong answer.

How would you set the talent bar, run design reviews, and divide work when two people both want the same feature so they can still grow?

Some of it was the usual EM material around talent bar, design reviews, and making sure stretch opportunities are allocated fairly when two people want the same work. I answered from my own management experience and tried to show how I balance delivery with growth. In hindsight, I think I probably assumed too much and did not spell out enough detail because they seemed to want very explicit examples and mechanics.

This took most of the round. I answered from a more structured, process-heavy background where performance management has documentation, clear timelines, and a real chance to improve, but they kept pushing on why I would not move faster. It felt like they were looking for a much more direct, hands-on style with quicker calls, maybe six weeks instead of a long formal cycle. I had experience here, but I do not think I showed it in the way they wanted.