PwC · Primly Community

PwC engineering manager interview loop: what they actually evaluate at the manager level

firsttime_mgr · 5 replies

recently went through PwC's interview process for an engineering manager role in their Digital Labs practice, which is their internal product/engineering group rather than client-facing consulting. different from the advisory tracks so worth separating out.

the loop was five conversations total over about four weeks.

conversation 1: HR screen (30 min) baseline fit. comp expectations, location flexibility (this role was hybrid DC/remote), travel appetite (they said 20-30% which in Big 4 language I've been told means 10-15% in reality, ask clarifying questions here).

conversation 2: technical manager screen with a senior director (60 min) not a coding interview. almost entirely about: how I run sprints, how I handle roadmap conflicts, how I've grown engineers, and how I balance technical debt against feature delivery. one question that threw me a bit: 'tell me about a time you had to tell a VP their favorite feature was the wrong thing to build.' they want someone who can push back with data.

conversation 3: people management deep dive (60 min) this was a director from HR-adjacent people team. the whole hour was behavioral, STAR format, focused on: performance conversations (especially underperformers), building psychological safety, handling a high performer who's a jerk to the team, and what I do when someone quits unexpectedly. I've found these conversations separate people who manage from people who lead. they're looking for the latter.

conversation 4: cross-functional panel (90 min, 3 people) three back-to-back 30-minute conversations with a peer EM, a product director, and a finance partner. the finance one surprised me. they asked about budget ownership, headcount forecasting, and how I'd make a case for a new hire. EM roles at this level own real budget, apparently.

conversation 5: partner-level conversation (45 min) more vision and fit. where do you see technology heading in the financial services space, how do you build diverse teams, what's your philosophy on remote vs. in-person for engineering teams. this felt like them deciding if you're someone they'd want in a room with a C-suite client.

a few honest notes: they leveled me as a manager rather than senior manager because I'd been in the role less than 3 years. if you have 4+ YOE as a people manager you might land higher. the process felt more thorough than any startup EM interview I've been through. it's slower but you actually know what you're getting into. the questions around budget and business case were a signal: PwC EMs own more than just people, they own outcomes in a way that's closer to a director at a startup.

still deciding whether to take the offer. the base is below what I'd get at a Series B startup but the stability and the bench of interesting client work is real.

5 replies

ae_andre

the finance partner in the panel is a detail I've never seen called out in Big 4 EM interview writeups and it's genuinely useful to know. by the time you're interviewing for EM roles at established firms, budget ownership is not optional. if you've only managed headcount at a startup you may not have thought through the forecasting side.

for anyone prepping: know how to talk about FTE cost (fully loaded, not just salary), know what a HC requisition process looks like, and have a framing for 'here's how I'd build the case for a new hire' even if you've never actually owned that.

director_dee

the leveling point is real and honestly generous of you to flag. a lot of people walk into Big 4 EM interviews expecting their startup 'head of engineering' title to transfer directly. Big 4 leveling is its own system and it's usually more rigorous than a 20-person startup's.

3 years as a people manager is usually the floor for manager. 5-6 gets you senior manager conversations. principal/director is a different process.

firsttime_mgr

yeah, this was a calibration I had to do mentally. at my last role I was 'Director of Engineering' with a team of 6. PwC mapped that to manager. a little humbling but also fine, the scope at PwC is legitimately bigger.

laidoff_lena

the 'tell a VP their favorite feature is wrong' question is the kind of thing that separates people who've actually been in rooms with executives from people who've just read about it. how did you frame your answer?

firsttime_mgr

I used a real story from my last job. we had a CTO-driven initiative that the data clearly showed wasn't moving any business metric that mattered. I framed it as: I came in with the data, I acknowledged what was exciting about the idea, I proposed an alternative that addressed the underlying goal, and I gave him a way to say no without it feeling like a loss. the key was never making it about who was right.