Technical interviews feel like a lottery until you've sat through enough of them to see the pattern. They aren't random. The same handful of question shapes recur across nearly every Oracle HCM technical panel, dressed in slightly different words. Learn the shapes and you walk in prepared instead of hoping.
They're rarely checking whether you've memorised every function name. They're testing whether you understand how the pieces fit together and can reason calmly under pressure. Structure your preparation around understanding, not recall.
The ten shapes
- The data model question. Person versus assignment versus work relationship — the foundation everything else sits on.
- The HDL question. File structure, metadata and merge lines, source keys versus GUIDs, and load order.
- The extracts question. Designing HCM Extracts, delivery options, and when an extract beats a report.
- The Fast Formula question. Formula types, database items, and a small scenario to reason through aloud.
- The security question. Roles, duties, data security and areas of responsibility — who can see and do what.
- The integration question. REST versus SOAP, when to use which, and where Atom feeds fit.
- The reporting question. OTBI versus BI Publisher — the same decision we covered in its own article.
- The personalization question. Sandboxes, page configuration, and increasingly the Redwood and Visual Builder story.
- The troubleshooting scenario. "A load failed" or "a report is slow" — walk me through how you'd diagnose it.
- The project question. "Tell me about something you built" — answered with structure and real decisions, not a job description.
For each pattern, prepare one concrete example from your own hands-on work. "I once had a load fail because the organisations weren't loaded before the assignments…" beats a textbook definition every single time, because it proves you've actually done it.
The fastest way to lose a panel is a confident wrong answer. "I haven't used Atom feeds in production, but here's how I understand they work…" earns far more trust than pretending. Interviewers are testing judgement as much as knowledge.
Understand how the pieces connect, and most questions answer themselves.
Key takeaways
- Ten question shapes cover most HCM technical panels — prepare each one deliberately.
- Anchor every answer in a concrete example from your own work.
- Understand how components connect, not just isolated definitions.
- Honesty about gaps beats confident bluffing every time.
None of this replaces real hands-on experience — it organises it. Do the configuration work, then map your stories onto these ten shapes, and the interview becomes a conversation you're ready to lead.