EY·Data Scientist·Onsite - Behavioral / Leadership·Senior

SeniorPrefer not to say

Jul 2026

Summary

EY data scientist interview that went deep on program ownership across the full lifecycle. One question, but it had a lot of layers and I wasn't fully prepared for how specific they wanted me to get.

Questions Asked (1)

Walk me through a program you fully owned from start to finish, covering strategy, planning, requirements, design, development, testing, and rollout. For each phase, what artifact did you produce, what was the riskiest assumption you had to validate, how did you know the phase was done, and what happened when a dependency slipped on the critical path?

Stakeholder ManagementCross-functional AlignmentAdaptability & Ambiguity

Author's notes

This question is brutal if you haven't actually owned something end to end.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a data science project where you led end-to-end delivery, and narrate it as a phased story that maps to the question's structure. For each phase, explicitly state the artifact, riskiest assumption, completion criteria, and how you handled a critical-path dependency slip. Emphasize stakeholder alignment, cross-functional collaboration, and adaptive problem-solving to showcase EY-relevant consulting skills.

Pro tip: Frame the dependency slip as a leadership opportunity: describe how you re-planned, communicated transparently, and still delivered value—this shows maturity and adaptability. Also, quantify business impact (e.g., 'reduced churn by 15%') to demonstrate commercial awareness.

1. Set the Scene and Strategy

Briefly introduce the project's business goal, your role, and the high-level strategy. State the key artifact (e.g., project charter or strategy deck) and the riskiest assumption (e.g., data availability or stakeholder buy-in).

2. Planning and Requirements

Describe how you translated business needs into technical requirements. Mention the artifact (e.g., requirements doc or user stories), the riskiest assumption (e.g., data quality or scope), and how you validated it with stakeholders.

3. Design and Development

Explain your design choices (e.g., model selection, pipeline architecture) and the artifact (e.g., design doc or prototype). Highlight the riskiest assumption (e.g., model performance or integration) and how you tested it early.

4. Testing and Rollout

Cover your testing approach (e.g., validation, A/B test) and the artifact (e.g., test plan or deployment guide). Discuss the riskiest assumption (e.g., user adoption) and how you measured success.

5. Dependency Slip and Adaptability

Describe a critical-path dependency that slipped (e.g., delayed data access or API). Explain how you detected it, communicated, re-planned, and mitigated impact, and what you learned.

Key Points to Mention

Clear phase-by-phase artifacts (e.g., charter, requirements doc, design doc, test plan, rollout plan)
Riskiest assumptions per phase and how you validated them (e.g., data profiling, stakeholder interviews, pilot tests)
Definition of done for each phase (e.g., sign-off, acceptance criteria, KPI thresholds)
Specific example of a dependency slip on the critical path and your mitigation actions
Stakeholder management and cross-functional alignment techniques (e.g., regular syncs, RACI, escalation)
Quantified business impact and lessons learned

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.