Legacy Migration Case

Problem

This is a consulting-style case used at PwC ETIC for technology consulting and senior engineering hires. A regional bank runs its customer onboarding on a 15-year-old Oracle Forms application. Regulators now require digital onboarding with e-KYC within 12 months, and the bank has asked us for a migration approach. In 25 minutes, structure the problem, ask me clarifying questions, propose an approach, and tell me the top three risks and how you would size the effort. I play the client and I will be vague on purpose.

Examples

Example 1 (good structure), Clarify scope (which journeys, which channels, integration points such as core banking and the credit bureau), then options: rewrite vs. strangler pattern vs. buy an onboarding platform. Recommend strangler: new e-KYC journey as a separate service fronted by an API gateway, old Forms kept for back-office until parity. Phase 1 in four months for the regulatory deadline.

Example 2 (weak), Jump straight to "we should use microservices and React" without asking who the users are, what data must not leave the country, or how the regulator will audit the flow.

Constraints

• You must produce a recommendation, not just options
• Numbers are expected: rough team size, phases, and a timeline that hits the 12-month deadline
• Assume Egyptian data residency rules apply

What they look for

Structure before content, sensible clarifying questions, a defensible recommendation with trade-offs, awareness of non-technical constraints (regulation, change management, vendor lock-in), and a confident close under time pressure.