Design a data platform enablement

Quick Overview

This question evaluates a candidate's competence in designing a compliant cloud data platform, covering architecture (ingestion, storage, governance, transformation, consumption), data contracts and lineage, operational considerations like SLAs/SLOs, partitioning, backfill/late-arrival handling, cost guardrails, and phased rollout planning.

Design a data platform enablement

Company: EY

Role: Data Scientist

Category: Data Manipulation (SQL/Python)

Difficulty: medium

Interview Round: Technical Screen

Design a pragmatic data‑platform enablement for a mid‑tier retail bank migrating to cloud under PII and data‑residency constraints. Describe the target architecture (ingestion, storage, governance, transformation, consumption), data contracts, lineage, and access patterns. Specify SLAs/SLOs, partitioning strategy, backfill/late‑arrival handling, cost guardrails, and a 3‑wave rollout plan with success metrics. Include the one thing you would deliberately postpone and why.

Overview: This question evaluates a candidate's competence in designing a compliant cloud data platform, covering architecture (ingestion, storage, governance, transformation, consumption), data contracts and lineage, operational considerations like SLAs/SLOs, partitioning, backfill/late-arrival handling, cost guardrails, and phased rollout planning.

|Home/Data Manipulation (SQL/Python)/EY
EY logo
EY
Oct 13, 2025
mediumData ScientistTechnical ScreenData Manipulation (SQL/Python)
10
0

Design a pragmatic data‑platform enablement for a mid‑tier retail bank migrating to cloud under PII and data‑residency constraints. Describe the target architecture (ingestion, storage, governance, transformation, consumption), data contracts, lineage, and access patterns. Specify SLAs/SLOs, partitioning strategy, backfill/late‑arrival handling, cost guardrails, and a 3‑wave rollout plan with success metrics. Include the one thing you would deliberately postpone and why.

Loading comments...