The SAP CV: what actually gets read

An SAP CV is not read first — it is scanned, by a person looking for four facts: role, SAP areas, projects, years. Everything else is read only after those four pass. Structure the document around that reality and strong experience stops getting buried.

The four facts, stated in seconds

The top third of page one should answer: what role are you, which SAP areas (with the classic module names — screeners search for "FI", "EWM", "SuccessFactors"), since when, and where. These are the same four facts the market searches everywhere — the logic behind a profile that gets found.

Why does a project list beat prose?

Because a screener goes straight to it. The SAP-specific convention that surprises career changers: experienced CVs carry a project list — client (or industry if confidential), your role, the areas, the project shape (greenfield, rollout, AMS…), and what you personally owned. One line per project, newest first, no adjectives.

Write ownership, not attendance

"Participated in a global S/4 implementation" says nothing. "Owned pricing and billing configuration in SD for two country rollouts; ran the integration test wave with FI" says everything — it is also exactly what the interview will probe, so the CV should promise only what you can walk through out loud.

How should a career changer write an SAP CV?

Lead with the domain, because it is the half of the job you already have. An accountant moving toward FI should open with the processes they ran — the close, payables, fixed assets — in SAP vocabulary, then state the one area they have learned and how (a course, a sandbox scenario, a test seat), and only then list the non-SAP employment history. The mistake is the reverse order: an IT-sounding summary, a row of module names, and the real evidence buried on page two. Sandbox and course work belong on the CV, clearly labelled as what they are; a screener who finds "implementation" and discovers it meant a trial system stops reading. One area, one process story, one honest line on how you learned it — that is a career changer's CV, and it is what the interview will ask about (what transfers from other backgrounds).

The classic mistakes

• Area soup — listing nine modules reads as depth in none; the market hires depth (how it's measured).
• Tool lists without context — transactions and tools belong inside project lines, not in a keyword cloud.
• Hiding the years — screeners will compute your start year anyway; state it.
• One CV for two tracks — a functional and a technical story mixed together reads as unclear; lead with one.
• Certificates above projects — supporting evidence, not the headline (where they help).

Consistency across surfaces

Recruiters cross-check: CV, LinkedIn, and wherever else you're findable. The same four facts should read identically everywhere — discrepancies cost credibility before the first call.