PwC · Primly Community

PwC software engineer interview process, full loop: what actually happened

mobile_mara · 4 replies

Went through the full PwC SWE loop in early 2026 for a senior engineer role in their tech consulting practice. Sharing the breakdown because I couldn't find a current writeup anywhere.

Application to offer: about 6 weeks. Felt slow but every step moved within a week once it started.

Stage 1: recruiter call (30 min) Standard stuff. Role overview, my background, rough salary alignment. They asked about my experience with cloud infrastructure and client-facing delivery. That second part surprised me a little. PwC is a consulting firm at its core even when they're hiring SWEs, and they want engineers who can talk to non-technical stakeholders. Keep that in mind.

Stage 2: online assessment Two coding problems on HackerRank, 90-minute window. Medium-level difficulty, definitely LeetCode-adjacent. One graph problem, one string manipulation problem. Neither was obscure. Then a situational judgment section (about 25 questions) which felt like a personality screen dressed up as business scenarios. You can't really study for that part, just don't overthink it.

Stage 3: technical interview (60 min with a senior engineer) One algorithm problem, similar difficulty to the OA. Then a solid 25-30 minutes talking through a previous project: architecture decisions, how I handled scaling issues, what I'd change. This felt like the real interview. They care about whether you can reason about systems clearly, not just whether you can whiteboard.

Stage 4: behavioral panel (90 min, two interviewers) This is where PwC gets serious. Four to five behavioral questions, STAR format expected, focused on collaboration, handling client expectations, and leading through ambiguity. The phrase "client delivery" came up a lot.

Overall: it's a rigorous process. Not Google-hard on the algorithm side, but the behavioral bar and the expectation that you're also a consultant matters more here than at pure tech companies.

4 replies

ux_uma

Thanks for this. Did they do the behavioral panel before or after the technical? Trying to figure out if I should prep coding or behavioral first.

backend_bekah

Technical came first. So coding/system discussion in round 3, then behavioral panel as round 4. I'd still prep both in parallel since the timing between stages was only a few days.

consultant_cam

The 'client-facing' expectation is real. PwC has been pushing harder on hiring engineers who can go on-site with clients rather than just stay back in delivery centers. If you've ever been staffed on a client project or worked in professional services, lead with that in the behavioral.

market_realist

Six weeks total is actually reasonable by 2026 standards. I've had loops stretch to 12 weeks at companies that definitely should move faster. Did the recruiter keep you updated in between or was it radio silence?