Real, anonymous reports from people who interviewed for Software Engineer at PwC, newest first and distilled into what to expect across the loop.
My process started with recruiter outreach and then two back-to-back interviews in English, each about half an hour, with HR as one of the sessions. The recruiter call and HR portion focused on the usual motivation and fit themes, and I noticed the rounds were fairly light on difficulty—sometimes the interviewers even seemed to decide how deep to go based on what they wanted to learn.
The experience I had with PwC’s process was mostly defined by poor communication. I had to confirm the technical interview timing by email multiple times, and after my office visit there wasn’t a clear timeline for what came next. I kept waiting and got radio silence for weeks, and I didn’t get any real status update.
The interview process typically begins with an HR call followed by a technical interview, often structured into multiple rounds including behavioral and technical assessments. Candidates noted varying timelines and communication issues, with some experiencing long waits for feedback or unclear next steps.
Technical interviews focus on core programming skills, particularly in Java, JavaScript, and frameworks like Spring and Angular, with an emphasis on problem-solving and real-world applications. Candidates reported a mix of coding challenges and scenario-based questions that required deep understanding rather than surface-level knowledge.
Behavioral rounds often utilize STAR-style questions to assess candidates' past experiences and how they handle various situations, focusing on teamwork, project involvement, and personal motivations. The atmosphere in these rounds is generally low-pressure and conversational.
Overall, candidates rated the difficulty of interviews as average, with a focus on understanding fundamentals and practical applications rather than trick questions. However, some candidates felt unprepared due to mismatches between their expectations and the actual interview content.
Several candidates experienced poor communication regarding interview scheduling and feedback, leading to frustration and uncertainty about their application status. Clearer timelines and follow-ups were highlighted as areas for improvement in the process.
Interviews often included discussions about past projects and real-world scenarios, emphasizing how candidates approach problem-solving and design decisions in practical contexts. This approach aimed to assess candidates' ability to apply their knowledge effectively.