Senior SAP Solution Architect

Why This Role Exists

Klario is our decision intelligence and change management platform for SAP, built on SAP BTP. It exists because most SAP change goes wrong for reasons that have nothing to do with transports. The intent behind a change gets lost somewhere between the business case and the build, the effect on people and process is understood too late, and afterwards nobody can reconstruct why a particular decision was taken or whether it delivered anything.

Klario captures that chain, from the original business signal through to the verified outcome, and uses AI to help organisations understand what a change will really cost them before they commit to it.

Our architecture team sets the patterns and guardrails that our product is built on. Klario reasons about SAP change, which means our product decisions and our AI outputs are only as good as our understanding of how SAP actually behaves in a live business.

This role is the functional authority in that picture. You will work alongside product to make sure what we build reflects real SAP practice, and alongside our AI team to validate and curate the reference data that our models are judged against. When a generated answer is textbook correct but operationally naive, you are the person who spots it.

• Act as the functional reference point for the architecture team across the core SAP process spine, from order to cash through to the financial close.

• Review and validate the reference datasets used to evaluate our AI outputs, judging not only whether an answer is technically correct but whether it reflects how the process really runs.

• Work with product to pressure test features against real SAP change scenarios, identifying where a design assumes an idealised landscape.

• Translate SAP nuance for colleagues who do not have an SAP background, including our data science team, and explain why a given detail matters.

• Contribute to the architecture team's patterns, standards, and decision records where SAP domain knowledge is the deciding factor.

• Bring the customer reality into internal discussion, drawing on your own experience of what breaks, what gets worked around, and what people quietly stop doing after a change.

• Hands‑on experience with SAP Signavio and SAP LeanIX. These are where our customers describe their processes and their landscape, and they are central to how we think about the problem. We need someone who has used them on real work, understands what they capture well, and knows how quickly the content in them goes stale or drifts from what the system actually does.

• Functional grounding in the SAP core, and the ability to reason beyond it. You should know at least one process area properly, and be able to look at an unfamiliar one and form a sensible view of what good looks like and why. We are testing how you think about SAP as a system, not the list of modules on your CV.

• A career that began in functional delivery or support and grew into architecture. We are looking for someone who has configured systems, not only designed them.

• Substantial exposure to SAP change under real conditions. That might be new country or plant rollouts, absorbing an acquisition, a carve out, a pricing model overhaul, or a major process redesign. Time spent inside one organisation that never stopped changing counts for as much as a series of implementations.

• The judgement to tell the difference between how the system is configured and why it ended up that way. You should be able to look at an unusual setup and form a sensible view about the history and politics behind it.

• The ability to explain SAP clearly to people who do not know SAP, without either oversimplifying or retreating into jargon.

• Comfort with not knowing an answer immediately. We do not need instant recall. We need someone who knows where to look, who can validate what they find, and who comes back the following day with an answer they are willing to stand behind.

• Awareness of the wider SAP portfolio beyond the core, for example Success Factors, Sales Cloud, Ariba, or Concur. We are not looking for depth in these. What matters is…