EY interview questions

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

Summarise your experience clearly and cite examples of responsibilities or skills relevant to the role.

Describe how you tailor language, organise the explanation, and check the other person’s understanding.

Identify a relevant development goal and explain how it builds on your experience and the role’s work.

Give a clear, neutral account of your notice period, availability, and any practical constraints.

State realistic expectations and connect them to the accounting, tax, reporting, or audit work you are seeking.

Explain a logical workflow for cleaning, structuring, summarising, and validating the data, with relevant functions or pivot-table uses.

Describe how you would compare sources, investigate mismatches, document adjustments, and prepare reliable supporting data.

Give practical validation checks, explain how you would investigate exceptions, and describe how results would be documented.

Cover the organisation of source data, traceability of calculations, supporting evidence, and clear presentation of the analysis.

Describe how you would check balances, supporting schedules, applicable accounting treatment, disclosures, and review points.

Explain how you would sequence tasks, check completeness and accuracy, track outstanding items, and meet close deadlines.

Use a clear account of the issue, your analysis and communication, and the outcome or control improvement.

Explain how you assess deadlines, dependencies, risk, and available resources, and how you communicate trade-offs.

Give an example of your review approach, how you gave actionable feedback, and how you confirmed corrections.

Show how you clarify the missing information, communicate deadlines and risks, document follow-ups, and escalate appropriately.

Describe your role, how you aligned on evidence and responsibilities, and how the issue was brought to resolution.

Explain how you would investigate root causes, involve the right people, strengthen checks, and monitor whether the solution works.

Give a specific motivation linked to the engineering work described and a clear reason for applying to EY.

Summarise relevant experience and cite examples involving development, delivery, or maintenance of applications.

Explain how you adjust detail, use clear language, and confirm shared understanding.

Name a relevant direction and connect it to your existing skills and the responsibilities in this role.

State your notice period, earliest availability, and any practical constraints clearly and neutrally.

Set realistic expectations and relate them to the development, collaboration, and delivery work you are seeking.

Discuss service boundaries, API design, separation of concerns, validation, error handling, and appropriate testing.

Describe how you would trace the request path, inspect available logs and metrics, isolate dependencies, and verify a fix.

Cover repeatable builds, automated checks and tests, artifact handling, deployment stages, and safe handling of failures.

Explain component structure, typed data, request handling, state updates, and testing of the key paths.

Describe input validation, clear separation of logic, suitable error responses, and tests for expected and invalid input.

Explain how you clarify user workflows, document functional needs and constraints, and validate the specification with stakeholders.

Describe the trade-offs, how you protected essential quality, and how you communicated risks and outcomes.

Explain how you assess impact, urgency, dependencies, and effort, then align the decision with stakeholders.

Give a specific example of constructive review or mentoring, the developer’s response, and the resulting improvement.

Show how you clarify the underlying need, explain technical implications, explore options, and agree on next steps.

Explain the problem and evidence, how you presented the benefits and risks, and how you assessed the result.

Describe how you would assess impact, involve decision-makers, communicate clearly, and choose a controlled response.

Connect your motivation to the cybersecurity work described and give a specific reason for applying to EY.

Summarise relevant experience and give concise examples of security, compliance, testing, or advisory work.

Describe how you communicate impact and uncertainty in plain language and make the implications actionable.

Name a relevant development area and explain how it builds on your experience and the role’s responsibilities.

Give a clear, neutral account of your notice period, availability, and any practical constraints.

State realistic expectations and connect them to the security engineering, advisory, or risk work you are seeking.

Explain how you identify communication needs, apply least-privilege access, and validate policy behaviour.

Describe alert validation, evidence gathering, containment considerations, escalation, and recording the response.

Cover scope and authorisation, suitable testing methods, validation of findings, and risk-based remediation priorities.

Explain a methodical testing approach, how you validate issues, and how you present impact and remediation clearly.

Describe how you establish scope, gather evidence, compare current controls with the selected framework, and record gaps.

Explain how you identify applicable obligations, review relevant cloud controls and data handling, and document gaps and actions.

Describe how you adapted the message, agreed on practical actions, and followed up on progress.

Explain how you assess severity, exposure, business impact, dependencies, and response capacity, then communicate priorities.

Give an example of how you clarified ownership, managed evidence and communication, and resolved delays or disagreements.

Show how you elicit requirements, compare options against risks and constraints, and explain trade-offs and next steps.

Explain the risks, stakeholders involved, options considered, and how you reached and documented a proportionate decision.

Describe how you would validate evidence, assess business implications, communicate priorities, and develop practical recommendations.

Link your motivation to the planning, delivery, or consulting work described and give a specific reason for applying to EY.

Summarise relevant engagements and cite examples of delivery, stakeholder coordination, or control of scope and budget.

Explain how you tailor detail, make risks and decisions clear, and keep reporting consistent.

Identify a relevant area and connect it to your experience and the responsibilities in this role.

State your notice period, availability, and any practical constraints clearly and neutrally.

Give realistic expectations and relate them to the delivery, stakeholder, and governance work you are seeking.

Explain how you define deliverables, owners, dependencies, milestones, and reporting fields, and keep the plan current.

Describe how you identify dependent activities, estimate schedule impact, consider recovery options, and report changes.

Cover baseline control, actuals and forecasts, resource needs, change evaluation, and approval records.

Explain the measures and comparisons you would use, investigate causes, and present implications and corrective actions.

Describe how you organise evidence, assess significance, connect findings to causes and impacts, and make recommendations actionable.

Explain how you would define programme objectives, track startup progress and mentor coordination, and compare relevant ecosystem evidence.

Describe the warning signs, your assessment and escalation, the action taken, and the effect on delivery.

Explain how you assess criticality, dependencies, impact, recovery options, and stakeholder decisions.

Show how you assessed implications, consulted stakeholders, obtained appropriate decisions, and updated plans.

Give a concise approach that explains status, cause, impact, options, and any decision needed.

Describe how you surfaced differences, clarified shared objectives, agreed responsibilities, and maintained progress.

Explain how you would clarify deliverables and decision rights, establish a workable tracker, and escalate unresolved dependencies.