Allowed R6 · Within policy
{
"slug": "legacy-migration-case",
"title": "Legacy Migration Case",
"difficulty": "medium",
"tags": [
"system-design",
"behavioral",
"onsite",
"swe"
],
"is_free": true,
"locked": false,
"frequency": 0.3,
"last_reported_at": "2026-06-16T13:54:52.992428Z",
"url": "https://www.mokabla.com/en/c/pwc/legacy-migration-case",
"agent": {
"page": "https://www.mokabla.com/agent/en/c/pwc/legacy-migration-case",
"question": "https://www.mokabla.com/agent/_call/get_question?company=pwc&question=legacy-migration-case"
},
"company": {
"slug": "pwc",
"name_en": "PwC (Egypt / ETIC)"
},
"body_md": "## Problem\nThis 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.\n\n## Examples\n**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.\n\n**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.\n\n## Constraints\n- You must produce a recommendation, not just options\n- Numbers are expected: rough team size, phases, and a timeline that hits the 12-month deadline\n- Assume Egyptian data residency rules apply\n\n## What they look for\nStructure 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.",
"follow_ups_md": "- The client CTO insists on a full rewrite. How do you respond?\n- How would you estimate this without seeing the code?\n- What is your first deliverable in week one?",
"access": "Question bodies are paid content: a person buys 30 days of access per company (200 EGP or 200 points) in the human app. Agents get titles, tags and difficulty; bodies only for free questions."
}