Allowed R6 · Within policy
{
"slug": "functional-consultant-modules-round",
"title": "Functional Consultant Modules Round",
"difficulty": "medium",
"tags": [
"technical",
"fundamentals",
"business",
"general"
],
"is_free": true,
"locked": false,
"frequency": 1,
"last_reported_at": "2025-01-23T16:38:41.536626Z",
"url": "https://www.mokabla.com/en/c/oracle/functional-consultant-modules-round",
"agent": {
"page": "https://www.mokabla.com/agent/en/c/oracle/functional-consultant-modules-round",
"question": "https://www.mokabla.com/agent/_call/get_question?company=oracle&question=functional-consultant-modules-round"
},
"company": {
"slug": "oracle",
"name_en": "Oracle"
},
"body_md": "## What they ask\nThe local office's biggest hiring stream is applications consulting: EBS and Fusion functional or technical consultants for HCM, Financials and EPM, placed on customer projects. The reported shape is short: an HR conversation about your experience and exactly which modules you have implemented, then a technical interview with a technical manager or a senior consultant from the practice. For some openings the contract runs through a third party payroll company rather than as a direct position, and candidates say that only came up at the technical stage, so ask early.\n\nThe technical round is a module deep dive. Questions reported, grouped by practice:\n\n**HCM (Fusion or EBS)**\n- Which modules have you configured end to end, and which did you only support: Core HR, Payroll, Absence, Talent?\n- What are the challenges you face in your current project and how do you deal with them?\n\n**Financials**\n- Walk me through the lease accounting process and the accounting entries it generates at inception, each period, and termination.\n- How does a payables invoice reach the general ledger, and where can it get stuck?\n\n**EPM**\n- In a block storage application, which operations create blocks, and what happens to a calculation when the block it needs does not exist?\n- How do you decide between a dense and a sparse dimension?\n\n## What they look for\n- Depth on the two or three modules you actually implemented, not breadth across the suite. They pick one and keep going.\n- Business process first, then configuration: the accounting entries behind a transaction, the policy behind an absence plan, not screen names.\n- Project war stories: a data migration that went wrong, a go live under pressure, a customer who changed requirements after UAT.\n- Clear communication, since the role is customer facing. One candidate reported an interviewer who was abrupt and off topic; stay calm and steer back to your experience.\n\nTimelines are uneven: some candidates got a decision within a week, others waited two months.",
"follow_ups_md": "- The customer wants a localisation the module does not support out of the box. Customise, extend, or push back?\n- Your lead consultant leaves mid project. What do you do in the first week?",
"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."
}