Deloitte interview questions

Connect your motivation to the role’s software development responsibilities and explain what you would bring.

Summarise relevant experience, your level of ownership, and the technologies or responsibilities involved.

Give a specific example that shows your interests and how you approach problem-solving.

Describe how you adapt the level of detail, check understanding, and agree on next steps.

State your expectations clearly and relate them to the work described in the role.

Give a clear, accurate account of your notice period and any relevant constraints.

Explain the API and data model, validation and error handling, persistence boundaries, and how you would test the service.

Describe how you would inspect the query and execution plan, check indexes and data access patterns, and verify any change.

Cover component structure, loading and error states, semantic markup, keyboard access, and responsive behaviour.

Outline a reproducible image build, automated checks, configuration handling, and a safe way to promote or roll back changes.

Explain how you would trace program and data dependencies, map fields, and test completeness and correctness of transferred data.

Describe how you would use logs and metrics to isolate the failure, assess impact, coordinate remediation, and verify recovery.

Use a clear sequence to explain your ownership, decisions, collaboration, and evidence of the outcome.

Show how you evaluated the technical trade-offs, communicated respectfully, and reached or escalated a decision.

Explain how you would assess impact and urgency, communicate trade-offs, and coordinate an appropriate response.

Give an example of how you clarified interfaces, dependencies, ownership, and progress with the team.

Describe how you would establish impact, validate dependencies, communicate risks, and agree a controlled plan.

Explain the evidence used to find the cause, how you supported recovery, and the preventive improvement.

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

Identify relevant areas and support your choice with concise examples of your contribution.

Describe how you tailor language, explain risk and impact, and make recommendations actionable.

Explain the safeguards and professional judgement you applied, while avoiding disclosure of confidential details.

Name a relevant development goal and describe how it connects to the work and your existing strengths.

Give a clear, accurate account of your notice period and any relevant constraints.

Describe scoping and safe testing, how you would examine common application and API risks, and how you would document evidence and remediation.

Explain how you would assess input handling, access boundaries, retrieved content, and potential information disclosure, with safe validation.

Cover identity and access, network exposure, logging, data protection, and how you would prioritise configuration findings.

Describe a practical automation or analysis task, how you would handle data quality and errors, and how you would validate the output.

Explain how you would establish a timeline, correlate relevant events, assess scope, preserve evidence, and communicate escalation.

Describe how you would evaluate evidence against relevant requirements, rate and communicate risk, assign actions, and monitor closure.

Explain the context, how you assessed impact and likelihood, how you engaged owners, and how progress was followed.

Show how you would explain evidence and risk, discuss mitigation options, and document an agreed decision or escalation.

Describe a risk-based approach that considers exposure, potential impact, exploitability, and available mitigations.

Give a specific example of how you clarified roles, shared relevant information, and supported decisions and recovery.

Explain how you would identify gaps, request verifiable evidence, assess residual uncertainty, and communicate the risk.

Describe how you would account for the environment and constraints, agree ownership, and track implementation and validation.

Connect your motivation to the role’s accounting, tax, audit, or controls responsibilities as relevant to your experience.

Summarise relevant work, your level of responsibility, and the evidence or deliverables you handled.

Explain a practical method for planning, checking work, and raising timing or quality risks early.

Describe how you summarise the issue, its implications, and the action required in accessible language.

State your expectations clearly and relate them to the responsibilities described.

Give a clear, accurate account of your notice period and any relevant constraints.

Explain how you would understand the process, identify risks and control objectives, document the walkthrough, and select controls for evaluation.

Describe the evidence you would request, how you would select and examine items, and how you would document exceptions.

Explain how you would organise source data, apply appropriate comparisons or formulas, investigate discrepancies, and check the results.

Describe how you would compare documents with reported data, record open items, request clarification, and resolve differences.

Explain how you would link evidence to the control objective, distinguish symptoms from causes, and test whether the corrective action addresses the gap.

Describe how you would identify the applicable requirement, support the judgement with evidence, and make the conclusion traceable.

Structure the example around scope, your responsibilities, key judgement or coordination, and the result.

Explain how you would assess deadlines, dependencies, risk, and available capacity, then communicate a realistic plan.

Show how you presented evidence, listened to the stakeholder, agreed next steps, and maintained clear documentation.

Explain how you would identify the evidence gap, give specific feedback, and ensure the conclusion is corrected and reviewed.

Describe how you would make a precise request, assess the effect of the delay, communicate risks, and agree escalation or alternatives.

Cover ownership, due dates, evidence of completion, validation, escalation of delays, and clear status reporting.

Connect your motivation to the role’s infrastructure, automation, cloud, and production-support responsibilities.

Summarise relevant systems, your level of ownership, and the outcomes or operational responsibilities involved.

Describe how you tailor the explanation, clarify impact, and agree on decisions or next steps.

Give a practical example of how you share ownership, clarify interfaces, and help work move forward.

State your expectations clearly and relate them to the role’s listed responsibilities.

Give a clear, accurate account of your notice period and any relevant constraints.

Explain how you would structure configuration, manage state and variables, review plans, and limit unintended changes.

Describe validation, error handling, logging, secure handling of configuration, and how changes would be reviewed and deployed.

Explain how you would check workload health, service and network configuration, logs, and recent changes before verifying a fix.

Cover project structure, networking, IAM, security and governance policies, and how the design supports monitoring and operations.

Describe how you would establish recovery needs, protect and monitor backups, test restoration, and document recovery steps.

Explain compatibility and dependency checks, a staged upgrade approach, workload health monitoring, and recovery planning.

Explain the goal, your ownership, how you managed risk and collaboration, and how you verified the result.

Describe how you would assess impact and risk, explain trade-offs, and agree a delivery plan with stakeholders.

Show how you established impact, assigned or clarified responsibilities, communicated updates, and confirmed recovery.

Explain how you would inspect dependencies and plan output, involve relevant owners, test safely, and communicate the risk.

Describe the evidence you would gather, how you would evaluate trade-offs, and how you would monitor a controlled change.

Give examples of useful documentation, reusable automation, review practices, and feedback from the teams using them.