Allowed R6 · Within policy
{
"slug": "cloud-solution-map-case",
"title": "Cloud Solution Map Case",
"difficulty": "medium",
"tags": [
"system-design",
"take-home",
"business"
],
"is_free": true,
"locked": false,
"frequency": 0.333,
"last_reported_at": "2018-10-02T15:13:42.834068Z",
"url": "https://www.mokabla.com/en/c/oracle/cloud-solution-map-case",
"agent": {
"page": "https://www.mokabla.com/agent/en/c/oracle/cloud-solution-map-case",
"question": "https://www.mokabla.com/agent/_call/get_question?company=oracle&question=cloud-solution-map-case"
},
"company": {
"slug": "oracle",
"name_en": "Oracle"
},
"body_md": "## What they ask\nFor pre-sales engineering roles in Cairo (Cloud Solution Engineer and similar), the process has three parts. A first interview checks your technical background. You are then given a discovery case to work on at home: a customer scenario for which you build a solution map and prepare a presentation. The second interview is you presenting that solution and defending it.\n\nA representative case:\n\n> A mid-sized Egyptian retailer runs an ageing on-premise ERP and a separate e-commerce site. They want to move to the cloud within a year, keep the finance module stable, and cut infrastructure spend. Map their needs to a cloud solution, propose a migration path, and present it to their CIO.\n\nYour solution map is expected to cover: the current-state pain points you discovered from the brief, which workloads move to IaaS versus SaaS, integration between ERP and e-commerce, security and data residency, a phased timeline, and a rough cost story.\n\n## What they look for\n- Discovery before design: what questions would you have asked the customer, and which assumptions did you have to make.\n- Correct mapping of business needs to product categories (compute, database, integration, identity), not just a list of services.\n- A phased plan with a low-risk first step, since \"lift and shift everything in month one\" is a red flag.\n- Presentation craft: a clear storyline for a CIO audience, few slides, and the ability to handle objections on cost and lock-in.\n- Honesty about what you do not know. They probe technical depth on one or two components you picked.\n\nBring the deck as a file and be ready to present without it if the room setup fails.",
"follow_ups_md": "- The CIO says a competitor quoted 30% cheaper. What do you do?\n- Which single workload would you move first, and why?",
"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."
}