SAP Fiori interview questions for developers and administrators

An SAP® Fiori interview starts with a question you should answer before anyone asks it: which Fiori role are you interviewing for? "Fiori" covers two quite different jobs. The application developer builds the apps — SAPUI5 code, Fiori elements floorplans, the services behind them. The system administrator makes those apps reachable — the landscape, SAP Gateway, app activation, launchpad content, security and day-to-day operations. The questions barely overlap, and preparing for the wrong set is a common way to lose an offer. For how certification fits into a wider plan, start with whether SAP certification is worth it.

This guide is a job-interview question bank, organised by role. It is not a certification comparison — if you are still choosing between the two Fiori exams, read Fiori certifications: developer vs administrator first. And it is not career-path advice; that lives in the best SAP certification for a Fiori / UX career. If you would rather practise reasoning through a task than read about it, a free performance-based sample is useful rehearsal for explaining decisions out loud.

Key takeaways

• Two roles, two question banks. Developers are probed on SAPUI5, OData and Fiori elements; administrators on landscape, activation, roles, security and troubleshooting.
• Both share a foundation. Launchpad concepts, app types and the front-end / back-end split come up in either interview.
• Reasoning beats vocabulary. Say why you would pick an approach and what goes wrong if you pick badly.
• Troubleshooting is the tell. The "missing tile" or "app will not load" scenario shows whether you have done the job.
• These are job-interview questions, not exam questions. A different genre, though performance-based certification builds the same applied fluency.

What do developer and administrator Fiori interviews have in common?

Both roles share a starting course in SAP's learning journeys — the basics of Fiori from the end user's view, the technology underneath, the architecture and how launchpad content is managed — so expect a few warm-up questions either way. The most common is "what is the Fiori launchpad?" A good answer goes beyond "the home page": SAP describes the launchpad as a shell that hosts Fiori apps and supplies shared services such as navigation and personalisation, and its design guidance notes that what a user sees depends on their role. That one sentence — content follows the role — is the bridge to everything an administrator does, and it explains to a developer why their app is invisible until someone configures it.

The other shared warm-up is app types. Be ready to explain the difference between transactional apps, analytical apps and fact sheets, and where classic user interfaces fit when they are launched from the launchpad. You do not need a lecture; you need to show you know which kind of app answers which kind of business need.

What do SAP Fiori developer interviews ask?

The developer interview usually moves from SAPUI5 fundamentals to Fiori elements and then to how you work in a team. Fiori apps are built on SAPUI5, so the toolkit is where most interviews begin.

How is a SAPUI5 application structured?

Expect "explain model-view-controller in SAPUI5" and "what is a component?" A strong answer describes the component as the unit that bundles an app so the launchpad can load it, the app descriptor as the place where models, routes and dependencies are declared rather than hard-coded, and views, controllers and fragments as the way you keep layout, logic and reusable dialog pieces apart. Follow-ups often probe bootstrapping and modularisation — how the library is loaded and why code is split into modules that load on demand. Add one sentence on why it matters: a well-declared descriptor is what lets the app run inside the launchpad without special handling.

How do models, data binding and OData V2 vs V4 come up?

Data binding is the core of almost every SAPUI5 technical interview. Be ready to explain the binding types (a single property, a list or aggregation, and a context or element binding), the difference between one-way and two-way binding, and how formatters and expression binding keep presentation logic out of the controller. Localisation usually rides along: texts belong in resource bundles, never in the view.

Then the OData question. Interviewers want to hear that the V2 and V4 models are not drop-in replacements — they differ in how they batch requests, handle changes and expose the API — and that the choice is usually made by the service you are consuming, not by preference. If you have only used one, say so and explain what you would check before switching. That honesty reads better than a vague claim to know both.

How do Fiori elements questions differ for CAP and RAP?

SAP describes Fiori elements as generating apps from metadata annotations and predefined templates. The interview question is rarely "what is it?" and more often "when would you use it, and how far can you push it?" Know the floorplans — list report, object page, worklist, overview page and the analytical list page — and SAP's guidance that a list report suits working across many items while an object page suits a single object.

The stack question follows. On a CAP service, annotations typically sit in the service layer and you lean on the Fiori tools for generation and previews; on a RAP service, annotations live in ABAP CDS in the back end. Either way, show you know the escalation path when a floorplan does not quite fit: adjust annotations first, then use the flexible programming model to add custom sections, columns or actions, and only drop to a freestyle app when the requirement genuinely sits outside the templates. If the team is RAP-heavy, the ABAP interview guide covers the back-end half; if it is CAP on SAP BTP, see SAP BTP interview questions.

What about routing, quality and team practices?

Routing questions test whether you understand that navigation is declared, not scripted: routes and targets map a URL pattern to a view, which is what makes deep links and the browser back button behave. Expect a scenario such as "the detail page breaks on refresh" — the answer is usually about loading data from the route parameters rather than relying on state from the previous screen.

Quality questions close the developer interview. Be ready to describe how you would unit-test controller logic, write integration tests that drive the app the way a user would, follow the Fiori design guidelines so the app feels like the rest of the launchpad, and work with version control in a team — branches, reviews and keeping generated files out of the noise. A developer who mentions testing unprompted stands out.

What do SAP Fiori system administrator interviews ask?

The administrator interview is about making apps reachable, secure and reliable. It tends to follow the life of a landscape: plan it, connect it, activate content, secure it, then keep it running.

How do you explain the landscape and SAP Gateway?

A classic opener is "why do we need SAP Gateway?" Explain that Fiori apps talk to the back end through OData services, and Gateway is what exposes and manages those services. Then cover deployment choices: Gateway can run embedded in the back-end system or on a separate front-end hub, and each choice has consequences for upgrades, sizing and how many back ends one launchpad can serve. You do not need to declare one option right — say what you would weigh.

Planning questions often mention the tooling SAP's administration course covers: using Maintenance Planner to work out what an app needs before you activate it, and the rapid activation approach for switching on standard content in bulk. Describe the intent — plan dependencies first, then activate in a controlled way — rather than reciting steps you are unsure of.

How do launchpad content, roles and security come up?

Expect "how does a user end up seeing an app?" The answer is a chain: the app is reachable through a catalog, the catalog is assigned through a role, the role is assigned to the user, and the layout the user sees — spaces and pages, or groups on older setups — arranges what the role allows. Add the back-end half: the user also needs authorisation for the underlying service and data. Interviewers like candidates who say both halves without prompting.

Security questions follow naturally. Be ready to explain why the connection between browser, front end and back end runs over SSL, what single sign-on buys users and support teams, and why you would never grant a broad role just to make a missing app appear. Optional features such as enterprise search, notifications and in-app help also come up — usually as "what would you need to configure for this to work?", which is another dependency question in disguise.

How do you answer troubleshooting and operations questions?

This is where administrator interviews are won. The scenario is usually a tile that does not appear, or an app that opens to an error. Walk through it in order: role and catalog assignment, the target mapping behind the tile, whether the OData service is active and reachable, back-end authorisation, then caches and whether the latest configuration actually arrived through transports. Mention that you would reproduce the issue with the user's role rather than your own administrator access, which hides most of these problems.

Operations questions round it off: how you move launchpad and service configuration through a transport landscape, what you monitor, and how you would handle a regression after an upgrade. A calm, ordered method impresses more than any single fact.

How should you structure a Fiori interview answer?

Whichever role you are interviewing for, a three-part shape works. First, name the mechanism — the component, the binding type, the catalog-to-role chain. Second, give the reason it exists — what problem it solves for the user or the team. Third, say what goes wrong if it is handled badly — the app that cannot be launched, the binding that floods the back end with requests, the user who sees an empty launchpad. Interviewers rephrase constantly; this shape survives rephrasing because you are explaining, not recalling.

When you reach the edge of what you know, say so and reason forward. "I have not configured that myself, but I would expect it to depend on the role and the service being active, so I would check those first" is a strong answer. A confident invented detail is a weak one.

What mistakes cost Fiori candidates the offer?

• Answering the other role's questions. A developer who only talks about activation, or an administrator who only talks about controllers, signals a mismatch.
• Treating Fiori as a skin. Fiori is an architecture — front end, Gateway, services, roles. Describing it as "the new look" ends the technical part of the interview early.
• Skipping the back-end half. Most launchpad problems involve a service or an authorisation, not just the tile.
• Over-building. Reaching for a freestyle app or a broad role when annotations or a targeted role assignment would do.
• Inventing specifics. A made-up setting name or menu path does more damage than describing the concept honestly.

Which Fiori certification supports the interview?

Certification will not answer interview questions for you, but it gives you a shared vocabulary with the interviewer. The details below come from each exam's page on learning.sap.com; SAP updates exams, so confirm before you book.

SAP does not publish topic-area weightings for either exam, so treat any resource quoting a precise split with caution. For what the two formats feel like, see what a Scenario-Based Assessment is and what a System-Based Assessment is. For the broader interview approach across SAP roles, the guide to preparing for an SAP consultant interview is the hub.

How should you practise for a Fiori interview?

There is a reason this guide gives themes instead of a script. A memorised answer key is the same failure mode as chasing dumps: it collapses as soon as the question is rephrased. What holds up is having built, activated or debugged enough that explaining it is simply narration. Pick the role you are interviewing for, take each question above, and answer it aloud in the mechanism-reason-consequence shape. Where you have a gap, close it with hands-on work rather than reading.

SAP's 2026 performance-based formats reward the same habit, which is why practising the real task helps with both the exam and the interview. When you are ready to rehearse with a hands-on scenario, try a free sample and explain every decision as you make it.