Candidates describe a conversational PwC software engineer process: a recruiter or HR screen, one or two technical discussions on projects and fundamentals, and usually a behavioral round. Reported timelines range from a few weeks to about a month.
$147K
Avg. Base Comp
$173K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates describe PwC's software engineer interviews as courteous and conversational rather than a high-pressure coding gauntlet. Reports usually start with a recruiter or HR call about background and logistics, followed by one or two technical conversations and a behavioral interview. One candidate counted two rounds in total, another had three rounds over a few weeks, and a third said the process took about a month.
The technical content is not uniform, so the safest preparation is to explain your own projects and your specific role in them. Candidates were asked about courses, projects and personal contributions. Fundamentals came up in several accounts: database design and SQL retrieval, arrays and linked lists, and basic OOP concepts. One candidate coded on the interviewer's device without AI help. Another described a system design discussion about a ticket booking system, with questions on monolith versus microservices, idempotency and overselling.
Later rounds focus on fit. Candidates describe conversations with a director or partner about experience, teamwork, what they knew about PwC and what they wanted from the role. Salary and benefits came up in some accounts. One candidate also described a short practical case study. Outcomes were mixed: several candidates here did not get an offer, one declined an offer and one accepted. Clear communication mattered throughout, so practice explaining your reasoning out loud as well as your answers.
Synthesized from 10 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.
I was contacted through LinkedIn and the process unfolded over a few weeks. My first conversation was with a recruiter who gave me an overview of the role and what to expect. That call was pretty casual — more of a fit check than anything technical.
The technical round came next, with a senior manager. This was where things got more serious. It wasn't a coding challenge, but rather a discussion around my technical background, problem-solving approach, and how I'd handle real-world scenarios. They asked behavioral questions too, diving into specific projects on my CV and how I'd dealt with challenges. There was also a small practical case study at the end — nothing that felt like a gotcha, but it did require me to think through a problem concretely.
The final round was with a partner at the firm. This was purely behavioral. They wanted to understand my communication style, how I'd fit into their culture, and what I was looking for in a role. The whole interview process was smooth and felt collaborative rather than adversarial. The team was genuinely open and transparent about the position, the expectations, and even the salary upfront.
Turnaround on the offer was decent, though there was a bit of a wait before I heard the final decision. Overall, it felt like they were trying to get to know me as much as I was trying to understand if the role was right for me.
Prep tip from this candidate
Prepare concrete examples from your CV that demonstrate problem-solving and how you handle setbacks — this came up repeatedly in both the technical and behavioral rounds. Also, be ready for a practical case study that tests your thinking process, not just your technical knowledge.
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 | |
| Skyscanner Partner ETL | |
| Real-Time Transaction Streaming | |
| P-value to a Layman | |
| Normalize Grades | |
| Resumable Fact Table Load | |
| Cyclic Detection | |
| Precision and Recall | |
| Duplicate Rows | |
| Find Duplicate Numbers in a List | |
| Real-Time Hashtag Partitioning | |
| Spam Classifier |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an opening call with a recruiter or HR that works as a fit check. Reported topics include current studies or experience, openness to full-time work, and relocation for one internship. One candidate had a second HR call to debrief the first interview. Prepare a concise story about your background and why PwC.
Candidates describe technical conversations with managers, associates or a senior manager. Reported topics include your role in past projects, database design and SQL, arrays and linked lists, and basic OOP concepts. One candidate coded live on the interviewer's device without AI help. The mix differs from candidate to candidate.
Not every candidate reports this step. One described a two-round process whose technical round was a system design discussion on a ticket booking system, covering monolith versus microservices, idempotency and overselling. Another described a small practical case study after a technical conversation. Be ready to explain your reasoning, not just sketch a design.
Candidates describe a behavioral round with a director or partner, sometimes alongside HR. Reported questions cover experience, teamwork, what you know about PwC, communication style and what you want from the role. Salary or benefits came up in some accounts. Prepare specific examples and clear answers on motivation.
