PwC interview questions

Connect your motivation to specific accounting, tax, treasury, or finance-process work and clarify your personal contribution.

Name what draws you to this role and to PwC from your own research (the teams hiring, the work the posting describes), link it to your experience, and say where you want to grow.

Describe how you adapt language, check understanding, and use a clear example.

Name relevant responsibilities and show how they build on your experience and development goals.

Explain how you assess urgency, organise work, communicate risks, and protect review time.

Answer clearly and neutrally, sharing practical constraints and expectations relevant to the opportunity.

Describe matching statement and ledger items, checking timing and errors, documenting evidence, and escalating unresolved discrepancies.

Cover supporting documentation, account and period accuracy, calculations, approvals, and the impact on financial statements.

Explain how you compare balances across periods, investigate unusual movements, validate explanations, and document conclusions.

Discuss matching counterparties and amounts, resolving differences, checking supporting records, and following settlement controls.

Include source-data checks, calculations, relevant tax research, traceable documentation, and review of compliance requirements.

Show how you gather requirements, map current and desired processes, identify controls and gaps, and validate the proposed configuration with users.

Use a clear example, state your individual responsibility, explain how you managed quality and deadlines, and give the outcome.

Describe the evidence gathered, risk assessment, communication, corrective action, and follow-up.

Explain how you assess deadlines and dependencies, assign or sequence work, communicate blockers, and preserve review controls.

Give the problem, evidence behind the proposed change, stakeholder involvement, and how you checked whether it worked.

Explain how you give specific feedback, identify support or training needs, set expectations, and monitor improvement.

Discuss trade-offs, risks, stakeholder decisions, change control, and how you keep delivery and quality visible.

Connect your motivation to relevant development experience and identify the languages, platforms, or responsibilities you can contribute to.

Name what draws you to this role and to PwC from your own research (the teams hiring, the work the posting describes), link it to your experience, and say where you want to grow.

Describe how you adapt terminology, explain impact, and confirm shared understanding.

Use a concrete example relevant to APIs, applications, integrations, data, or AI workflows and explain your role.

Explain how you track dependencies, communicate blockers, and manage commitments.

State practical availability and expectations clearly and neutrally.

Explain resource and request design, validation, appropriate status responses, security considerations, and clear API documentation.

Describe how you inspect the query and data access pattern, use query plans or measurements, and validate improvements.

Cover separation of request handling and business logic, validation, external-service calls, error handling, and testability.

Discuss independent responsibilities, data and interface boundaries, operational complexity, and the costs of service communication.

Describe component or state organisation, API interaction, validation, user feedback, and maintainability.

Explain how you follow the data path, inspect API or middleware behaviour, reproduce the issue, and verify the correction.

Clarify your personal contribution, technical decisions, collaboration, testing, and the result.

Explain what changed, how you confirmed the need, and how you managed the design and stakeholder implications.

Discuss user or business impact, severity, dependencies, communication, and how you preserve safe delivery.

Give a specific example of constructive feedback, shared standards, and the effect on the code or teammate.

Describe ownership, interface agreements, dependency tracking, integration checks, and escalation of blockers.

Explain how you would reproduce and assess the issue, inspect prompts and tools, define evaluations or safeguards, and communicate options.

Connect your motivation to specific modelling, LLM, data, or production work and identify your contribution.

Name what draws you to this role and to PwC from your own research (the teams hiring, the work the posting describes), link it to your experience, and say where you want to grow.

Describe how you make uncertainty and risk understandable, use evidence, and set realistic expectations.

Identify relevant skills such as RAG, evaluation, agent workflows, or production support and give a practical development goal.

Explain how you track hypotheses, results, priorities, and communications while keeping work reproducible.

Share availability and expectations plainly and neutrally.

Cover document preparation, chunking, embeddings and vector search, retrieval quality, context assembly, and evaluation.

Describe a representative test set, measurable criteria, comparisons with a baseline, and checks for regressions or unsafe outputs.

Explain the workflow and state design, tool boundaries, memory selection, error handling, and evaluation of end-to-end behaviour.

Discuss request validation, model and retrieval calls, latency and error handling, observability, and safe output handling.

Include service health, latency and failures, quality or evaluation signals, safety issues, and a process for responding to changes.

Separate retrieval and generation causes, inspect retrieved context and prompt behaviour, test changes, and add evaluation or guardrails.

Explain the problem, your role, technical choices, evaluation approach, collaboration, and outcome.

Give evidence of the issue, the investigation, changes made, and how you verified whether they helped.

Discuss impact and risk, minimum release criteria, stakeholder communication, and options for mitigation or delay.

Describe when you involved them, the requirements addressed, decisions made, and how they affected implementation.

Cover component and end-to-end tests, evaluation cases, observability, failure handling, ownership, and incident response.

Explain how you tailor detail, document key decisions and risks, and confirm that stakeholders understand trade-offs.

Connect your motivation to pipelines, modelling, integration, or platform work and state your contribution.

Name what draws you to this role and to PwC from your own research (the teams hiring, the work the posting describes), link it to your experience, and say where you want to grow.

Describe how you state the evidence, affected data or use, potential impact, and next steps in accessible language.

Name relevant responsibilities and explain how they build on your experience and goals.

Explain how you track dependencies, communicate changes, and manage testing and delivery.

Share availability and expectations clearly and neutrally.

Describe stages, transformation logic, scheduling or orchestration, quality checks, and handling of failures or reruns.

Explain how you inspect joins and keys, trace source records, reproduce the issue, and validate the correction.

Discuss the entities and grain, relationships, definitions, integration rules, and validation with reporting users.

Cover measurements, data volume and partitioning, transformation and join behaviour, resource use, and comparison after changes.

Explain how you organise processing and storage, manage dependencies, validate outputs, and monitor failures and performance.

Trace source-to-target transformations, compare expected and actual results, inspect quality controls, and document the root cause and fix.

Describe requirements, your decisions and responsibilities, quality checks, stakeholder collaboration, and the result.

Explain how you assessed impact, found the cause, coordinated with users or upstream owners, and prevented recurrence.

Discuss business impact, technical risk, dependencies, stakeholder trade-offs, and how you communicate the plan.

Show how you clarified definitions and grain, documented requirements, validated the design, and handled ambiguity.

Describe impact assessment, diagnosis, communication, recovery or safe reruns, and follow-up actions.

Explain how you review designs and code, provide actionable guidance, set standards, and encourage ownership.