How CAPM interviews changed
CAPM interviews in 2026 aren't "what does CDS stand for" quizzes anymore. Interviewers probe architecture judgment — Node.js vs Java, service security, CAP-to-Fiori wiring — plus a brand-new category: AI and Joule.
Here are the questions that come up most often, with the answers interviewers want to hear.
CAP fundamentals
1. What is CAPM, and when would you choose it over RAP?
CAP is SAP's framework for cloud-native business apps on BTP (Node.js or Java). Choose CAP for side-by-side extensions and new cloud apps; RAP for on-stack S/4HANA development. Real landscapes often use both, with CAP consuming S/4HANA via destinations.
2. Explain the core CDS artifacts.
Entities = data model. Services = OData/REST exposure with projections. Annotations = semantics (UI annotations drive Fiori Elements, validation annotations drive behavior).
One CDS model feeds the database schema, the service API, and the UI.
3. Node.js or Java for CAP?
Both are first-class. Node.js: faster prototyping, lighter services, JS/TS teams. Java: heavy enterprise integration, Spring expertise, long-running transactions. Know one deeply, read the other.
Services, protocols, and data
4. How does a CAP service become an OData API?
Define the service in CDS with projected entities — protocol adapters expose OData V4 automatically ($metadata, query options, draft where modeled). Custom logic lives in event handlers (before/on/after).
5. How do you handle auth in CAP?
XSUAA for authentication (JWT, cds.requires.auth). Layers for authorization: @requires for role checks, @restrict for instance-based rules. Mention role collections in the BTP cockpit — interviewers want the deployment side too.
6. Where does the data live?
SAP HANA Cloud via HDI containers — isolated schemas per deployment, cds deploy manages deltas. Know managed (CAP owns tables) vs unmanaged (your DDL), and when unmanaged is justified.
Fiori and integration
7. How does your CAP backend connect to a Fiori Elements UI?
CAP OData V4 + UI annotations = list report / object page with zero UI code. Custom logic via actions and functions. Bonus: draft modeled in CDS flows straight through to the UI.
8. How do you call S/4HANA from CAP?
Destinations in the BTP cockpit, consumed via cds.connect.to, with principal propagation carrying the end user's identity. The standard side-by-side pattern — know it cold.
9. How do you deploy a CAP app to BTP?
cds build → cds deploy to Cloud Foundry (or Kyma); mta.yaml orchestrates HANA, XSUAA, approuter. Mention blue-green deployment — and that the HDI deployer always complains about something the first time.
The new 2026 category: AI and Joule
10. How would you expose a CAP service to a Joule agent?
CAP OData actions and functions become Joule skills: single-purpose actions with clear descriptions (Joule matches intent on descriptions), attached as tools in Joule Studio. Full pattern in my Joule Studio agent tutorial on this blog.
11. How do you ground an AI agent in enterprise data?
Document grounding for policy/context, structured tool access (OData/REST/MCP) for live data. Never rely on the model's training data for business facts.
Scenario questions (these decide offers)
12. "Design a side-by-side approval app for purchase requisitions."
They're testing architecture, not syntax: CAP service on BTP, destination with principal propagation, draft-enabled Fiori Elements UI, XSUAA roles for requester/approver, Build Process Automation for multi-step approvals. Talk trade-offs out loud — that's the actual test.
How to prepare
Don't memorize — build. One deployed CAP app with auth, one Fiori Elements UI on top, one destination to a backend. You'll answer 80% from experience instead of memory.
For the AI questions: build one Joule Studio agent against your own CAP service. A weekend project that makes you stand out immediately.
Got asked something not on this list? Share it in the comments — I'll keep it current.