PwC Software Engineer interviews reported here combine experience-focused conversations with practical technical discussion, including SQL, coding, core data structures, and, in one account, ticket-booking system design.
$126K
Avg. Base Comp
$158K
Avg. Total Comp
2 rounds
Typical Rounds
4 weeks
Process Length
PwC Software Engineer candidates describe a process that emphasizes how clearly they explain real work alongside practical technical reasoning. Prepare a crisp account of your individual contribution to each project: one candidate was asked to distinguish their own role from the broader project, while other accounts focused on background, courses, education, motivation, and teamwork.
Technical coverage varies by interview. One candidate discussed database design and retrieving information with SQL; another encountered basic arrays, linked lists, and object-oriented programming; a further account required live coding on the interviewer’s device without AI assistance. Build explanations around the decisions you made, then practice writing and narrating straightforward code unaided.
System design may also appear. In one two-round account, the technical discussion was a ticket-booking design: monolith versus microservices, modular-monolith trade-offs, scaling, idempotency, and preventing overselling. Be ready to defend choices under load and failure conditions rather than stopping at a component diagram.
Several accounts describe interviews as conversational and fit-focused, even when technical material is included. Use that tone to your advantage: connect your technical choices to the team problem, ask thoughtful questions, and communicate trade-offs plainly. The sample is limited, so the precise technical emphasis may differ by team.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Pwc process.
The process was a lot longer than I expected, and the most memorable part was how many different formats they packed in before the final decision. I started by submitting my CV and a cover letter explaining my motivation, then moved through an initial one-way interview, some IQ-style games, a Workday roleplay scenario, a group activity, a personal presentation, and finally a last interview. The first round was mostly about fit and motivation, especially how I connected to the company values, so it felt less technical and more about whether I could speak clearly about why PwC and why the role. After that, the process got more interactive and a bit more stressful because each stage seemed designed to test a different side of you rather than just your coding or technical knowledge.
The group interview was especially unusual because there were 12 people in the room, and one part turned into a debate where two teams had to argue a topic after only a few minutes of prep. That made it feel more like a communication and teamwork assessment than a traditional software engineer interview. 5-hour personal fit interview followed by an intense case study in the second round, which lines up with the overall style of the process: lots of emphasis on presentation, judgment, and how you handle structured scenarios. I made it to the final stage and didn’t get the offer, and honestly the length of the process felt hard to justify for a graduate-level role. If you’re preparing, I’d focus on being able to talk naturally about PwC’s values, defend your motivation clearly, and stay composed in group debate or roleplay settings, because those seemed to matter as much as anything technical.
Prep tip from this candidate
Prepare to speak directly about PwC’s values and your motivation, since that came up early. Also practice a timed group debate or roleplay format, because the process included short prep followed by live discussion rather than just standard technical questions.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Pwc
Write a query to return the two students with the closest test scores and the score difference
| Question | |
|---|---|
| Size of Joins | |
| Sort Strings | |
| Hurdles In Data Projects | |
| RAG Strict Source Control | |
| Slow SQL Query | |
| Data Pipelines and Aggregation | |
| Electricity Supply | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Raining in Seattle | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Longest Streak Users | |
| Real-Time Transaction Streaming | |
| P-value to a Layman | |
| Normalize Grades | |
| Cyclic Detection | |
| Resumable Fact Table Load | |
| Duplicate Rows | |
| Find Duplicate Numbers in a List | |
| Skyscanner Partner ETL | |
| Real-Time Hashtag Partitioning | |
| Spam Classifier | |
| Portfolio Platform Architecture |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an introductory HR or online conversation focused on background, experience, courses, projects, motivation, and fit. Prepare concise examples that identify your own contribution rather than describing a team project only at a high level.
Reported technical formats include database design with SQL retrieval, basic data structures and OOP, and live coding on an interviewer-provided device without AI assistance. The exact format varies, so practice both explaining solutions and coding straightforwardly.
Candidates report a later director or onsite conversation that may combine behavioral and technical questions. One account used a ticket-booking system-design discussion covering architecture trade-offs, idempotency, scalability, and overselling prevention.
