Senior SAP Fiori / UI5 Consultant — SAP S/4HANA
Enterprise UX and front-end engineering · SAP domain
Adoption is the part of an S/4HANA migration no steering committee can fake. This mandate is for the Fiori engineer who decides whether users can actually work in the new system.
- Discipline
- Enterprise ERP
- Seniority
- Senior · 10+ years (5+ in Fiori/UI5)
- Languages
- Dutch & English
- Work mode
- Hybrid — Netherlands
- Employment
- Full-time · Contract or permanent
- Listed
- 16 Aug 2026
How to approach this mandate
No application form. No CV portal. Read the position brief, then speak with Harald directly, under confidence.
The client is not named here. On an engaged mandate the client's hiring intent is commercially sensitive, so the organisation is identified to you under confidence in the first partner conversation — not published to their competitors.
The remit
Why this role exists now. And what it carries.
S/4HANA migration has moved user experience from cosmetic to consequential. Organisations deploying intuitive, role-based Fiori apps see higher adoption, fewer support tickets and faster execution across finance, procurement, sales and operations. Those that ship SAP GUI with a new label absorb the cost quietly, for years.
The profile that delivers this is unusual: deep SAPUI5 engineering, OData and CDS fluency, Launchpad and Gateway configuration, and the presence to run a UX discovery workshop with business process owners. Most candidates hold one half of that pair.
The client is running an active S/4HANA programme and needs the person who owns the front end end-to-end — from service design through Launchpad configuration to production adoption.
What the role carries
- Design, develop and deploy custom SAPUI5 and Fiori applications using SAP BAS — from list-report apps to freestyle UI5 with custom controls.
- Activate and configure standard Fiori apps: Launchpad catalogues, groups, role mapping, semantic objects and cross-app navigation.
- Design and implement OData services (SEGW, CDS views, RAP) and tune service performance with ABAP developers.
- Configure SAP Gateway — service registration, maintenance and association handling — and manage authentication via SAML 2.0 and OAuth 2.0.
- Lead UX discovery workshops with business users and process owners, translating requirements into wireframes and Fiori designs.
- Deliver responsive experiences across desktop, tablet and mobile, including offline-enabled and field or warehouse scenarios.
- Lead integration testing across OData services, backend connectivity and cross-app navigation, through to production and hypercare.
The brief
The challenge, the mandate, and the impact.
The challenge
The client's S/4HANA landscape is being built behind a front end nobody owns. Standard Fiori is partially activated, custom UI5 work is queued against backend availability, and Launchpad, Gateway and role mapping decisions are drifting. Without a single front-end authority, adoption becomes the programme's unmeasured risk.
The mandate
Reports into the lead SAP architect. Ownership of the Fiori and UI5 scope end-to-end: app development, standard activation, Launchpad and Gateway configuration, OData and CDS service design with ABAP counterparts, and UX discovery with business process owners. Authority to set front-end standards for the programme.
The impact
- 6 months
- Assigned Fiori and UI5 scope live in production, reusable UX components documented, and the seat established as the front-end authority for team and business users.
- 12 months
- Adoption measurable — role-based apps in daily use, support-ticket volume down against the GUI baseline, and next-phase front-end scope planned from usage evidence.
35
Median days to shortlist
Category norm: 84–120 days
8 in 10
12-month retention
Category norm: ~60% at 18 months
90 days
Replacement guarantee
With backfill
1
Partner, start to close
Never delegated
Index reading
The market reading behind the brief.
This mandate is not written from a job description. It is written from our own quarterly reading of how these roles are being eliminated, redefined and created in this corridor.
Where this mandate sits in the market
Current Q3 displacement intensity in the sectors that frame this search. Higher intensity means more leadership turnover and sharper talent scarcity.
- Tech ConsultingDisplaced · 9/9
- SaaS & CloudDisplaced · 9/9
- AI EngineeringDisplaced · 9/9
Read the full Displacement Index — 7 sectors across APAC, EMEA and the GCC.
The profile
Who closes this. And on what terms.
Critical
UI5 engineering depth
Custom controls, component architecture and clean maintainable code — built for users, not for a requirement list.
Full-stack SAP reach
OData design, CDS views, ABAP RAP and Fiori consumption; you debug across the chain, not just your layer.
Launchpad and Gateway ownership
Catalogues, groups, semantic objects, cross-app navigation, SAML 2.0 and OAuth 2.0.
UX advocacy in a technical room
You can run a discovery workshop, sketch a wireframe and defend the user journey.
Differentiators
- SAP BTP deployment on Cloud Foundry or Kyma, with destination and connectivity services.
- Mobile and offline scenarios: SAP Mobile Cards, PWA patterns for field and warehouse.
- S/4HANA Cloud extension patterns via SAP Build.
- Design-system thinking across a portfolio of apps rather than app-by-app delivery.
What the client offers
- End-to-end ownership of the Fiori front end on a live S/4HANA programme — visible work with measurable adoption outcomes.
- Day rate or salary benchmarked to Netherlands market standards for senior Fiori/UI5 consultants.
- Contract or permanent engagement, agreed before commitment.
- Direct access to business process owners rather than requirements filtered through three layers.
- Hybrid working from the Netherlands.
- Stack
- SAPUI5 · Fiori Elements · OData · CDS · RAP · SAP BAS
- Platform
- S/4HANA · Fiori Launchpad · SAP BTP (Cloud Foundry / Kyma)
- Engagement
- Contract or permanent · EUR day rate or salary
- Reports to
- Lead SAP Architect / delivery lead
The approach
How this mandate runs. Partner-led, end to end.
01 · Day 0–1
Approach
You reach out — through this page, the partner's direct line, or a confidential booking. No application form, no CV upload to a portal. The first conversation is about fit, not paperwork.
02 · Days 2–7
Partner conversation
Harald Agterhuis, the partner who signed this mandate, speaks with you directly. The conversation establishes whether the role and your delivery record genuinely align before anyone invests further.
03 · Days 8–21
Client introduction
If the fit holds, Harald introduces you to the hiring client under confidence. The client sees a short, serious shortlist — not a pile of CVs. You meet the decision-makers and test the role against what you need.
04 · Days 22–35
Decision
The client decides. If it's a yes, Harald works the offer with you and the client to land it — including counter-offer defence. If it's a no, you get a direct debrief, not silence.
Your partner on this mandate

Founder · Amsterdam · Dubai
Works across all corridors. Thirty years placing technology executives across APAC and EMEA, personally, mandate by mandate.
Where this mandate connects
Research behind the brief
The discipline this sits in
Other mandates on the register
SRX-2601 · Enterprise ERP · Netherlands (EMEA)
Accounts & Sales Executive — SAP S/4HANA & Cloud ERP
Enterprise ERP sales leadership · SAP domain
SRX-2602 · Enterprise ERP · Netherlands (EMEA)
ERP Account & Sales Executive — SAP Domain
Career-building entry into the SAP ecosystem
SRX-2603 · Enterprise ERP · Netherlands (EMEA)
Senior SAP MM Consultant — SAP S/4HANA
Procure-to-pay architecture · SAP domain