Career & Hiring

Substance over polish: a guide to the DACH Lebenslauf

A practical, evidence-based guide to the Lebenslauf in the DACH market in 2026, written for senior and mid-career professionals who are tired of templates that look like brochures and CV advice that reads like horoscopes. The argument throughout is that what gets measured here is substance, not polish.

Ramazan Yavuz
Ramazan Yavuz ·
Substance over polish: the DACH Lebenslauf

The CV used to be a document about evidence. Then it became a portfolio of visual moves. Templates and CV-builders taught a generation to optimise the page before optimising the work, and a craft that took thirty minutes to learn has been quietly forgotten. I keep opening CVs that look beautiful and say nothing, and I keep watching the people behind them get filtered out by markets that were never going to be impressed by the layout. The 2026 job market in DACH is punishing that bargain harder than I have seen before. This article is, in part, an attempt to give the craft back.

The DACH job market in 2026 is a strange place. Headlines say there is a skills shortage across Germany, Austria, and Switzerland. Inboxes say there is a flood of applicants per role. Both can be true at the same time, and the document that has to thread that contradiction is your Lebenslauf. Most CV advice you find online is written for an Anglo-American audience, decorated with stock photography, and built around the idea that you win by looking polished. This article argues the opposite: in DACH, the CV is judged on substance, and polish that gets in the way of substance actively hurts you. What follows is what I learned while rebuilding my own CV for this market, with the sources, the trade-offs, and a downloadable template at the end. The advice is opinionated. It is also, I hope, useful.


Start with the reader. A recruiter or hiring manager in the DACH market spends, by the most cited eye-tracking studies, somewhere between six and eight seconds on the first pass of your CV. The original TheLadders study from 2012 measured six seconds across thirty recruiters. The widely cited 2018 follow-up bumped it to 7.4, and you should treat the absolute number as folk wisdom and the ordinal finding, that they scan and do not read, as well supported. In that window, the same study found the eye lands on six things only: name, current title, previous title, current employment dates, previous employment dates, education, with roughly eighty percent of the viewing time concentrated in the top third of page one and the bottom of the page often unread.

This is the single most important fact about CV design and almost nobody internalises it. You are not writing a document that gets read. You are writing a document that gets glanced at, parsed by software, glanced at again, and only then, maybe, read. The cover page does triple duty: it sets the verdict, it primes the reading frame for the rest of the document, and it establishes you on the two axes of warmth and competence that decades of social psychology say strangers judge each other on. A cover with a portrait, a name, and a job title fails the test because the reader has nothing to anchor on except your face.


The DACH Lebenslauf is structurally different from the American resume, and pretending otherwise is the most common mistake international candidates make. Germany, Austria, and Switzerland share the same skeleton with small national variations. The differences from an Anglo-American resume are not stylistic preferences. They are conventions that signal whether you understand the local market.

A Lebenslauf includes a professional photo, top right, aligned with the personal-data block. The photo is legally optional under equal-treatment law and culturally expected in practice: in traditional industries (insurance, banking, public sector, manufacturing, semiconductors) its absence is read as inexperience with the market. A passport snap, a phone selfie, or a holiday crop are worse than no photo. Use a professional photographer, neutral background, business attire, slight smile (not broad, not deadpan), eye contact with the camera. A 2020 study by Filkukova and colleagues found that the slight closed-lip smile reads as both warmer than neutral and more competent than a broad smile; the "thinker pose" with chin on hand actively decreases competence ratings. Avoid it.

The personal-data block carries the full legal name, postal address, phone with country code, professional email, date and place of birth, and nationality. Marital status is optional. Religion and political affiliation are omitted unless the role specifically requires them. The body of the document is tabellarisch: two-column, dates on the left, details on the right, reverse-chronological inside each section. The headings are canonical, and changing them is not creative, it is sabotage of the parser that reads you before any human does. The canonical headings are Persönliche Daten, Kurzprofil, Berufliche Laufbahn or Berufserfahrung, Projekthistorie, Technische Kenntnisse or Kenntnisse, Zertifikate, Sprachen. Not "About Me", not "Skills", not "My Journey". A creative heading is a routing failure waiting to happen.

Length is the other place international candidates get caught out. A one-page CV for a senior with fifteen years of experience reads in DACH as either disrespect or a thin career. Senior consultant CVs in the region routinely run four to eight pages including the project history. Do not pack to one page by shrinking the type to eight points; the cognitive disfluency that creates is a worse signal than the longer document.


The typography decisions are where most templates fall apart, and they are also where the smallest tweaks make the biggest difference. Body text on A4 should sit between ten and eleven points, with line height around 1.35 to 1.45 of the point size. Twelve points is a typewriter convention; under nine points is unreadable when your CV gets photocopied in an HR department that still photocopies, and many do. Matthew Butterick's Practical Typography remains the canonical reference and is worth an evening of your time.

The typeface matters more than designers admit. Use a face engineered for text, not a display face borrowed from a magazine. The marker is the x-height: the height of lowercase letters relative to capitals. Body text faces sit between sixty-five and seventy-five percent. Display faces, the Didone serifs like Bodoni, Didot, and Playfair, have thin hairlines that disappear at ten points and look luxurious in editorial design and painful in a CV. Geometric sans like Futura, Avenir Light, and Brandon Grotesque at light weights have the same problem. Safe choices that handle the full DACH character set (umlauts, the German eszett, the Swiss "ss" convention), render well on a laser printer, and read calmly at small sizes: Source Serif and Source Sans, IBM Plex Serif and Sans, Charter, Whitney, Mallory, Inter. Pair one serif with one sans, or two cuts of one super-family. Never two unrelated serifs. Never two unrelated sans faces. Body text in true black or near-black on white. Grey body text is a fashion choice that fails on photocopiers and fails on screens at low brightness.

The traps to avoid: Calibri, the Microsoft Office default, signals zero design effort. Arial is a tired Helvetica knock-off without personality. Times New Roman reads as 1995. Helvetica Neue at body weights has poor legibility at small print sizes. Any face with "Pro Display" in the name is, by definition, drawn for headlines and not for ten-point body. The fact that a typeface exists in your operating system is not an argument for using it on a CV that has to survive print.


Cognitive load is the technical term for how much effort the reader has to spend just to process what you have presented. I first ran into the underlying dual-process idea, the System 1 / System 2 split that explains why the cover page is judged before it is read, in Daniel Kahneman's Thinking, Fast and Slow. It is the rare popular-science book whose claims have held up well enough to influence how I write almost every document I now produce. John Sweller's framework sits adjacent to Kahneman and splits the cost into three: the intrinsic load of the material itself, the extraneous load created by bad presentation, and the germane load that goes into actually understanding and remembering. The first you cannot change. The second is what design controls. The third is what you want.


Working memory is small. Older estimates put the magic number at seven plus or minus two; modern revisions at roughly four plus or minus one fully compressed chunks. A chunk is whatever the reader recognises as a unit, so chunk size scales with expertise. For our use case: a senior CV reader has at most four or five active slots while scanning. Thirty atomic facts arranged in a uniform grid will not chunk; they will parse as "lots of stuff", which is a verdict, not a memory. The same thirty facts arranged in four named groups of six or seven will collapse on first glance.

This is why the skill matrix, the corporate template with thirty equally weighted boxes that almost everyone has seen and many people still use, is a cognitive disaster. Every cell asks for the same attention. The reader cannot decide what matters. The brain disengages and processes the page as texture, not content. The fix is not fewer cells. The fix is named chunks of varying weight in a clear vertical sequence: a heading that primes the reader, four to six items per chunk, white space marking the boundary, and a clear next chunk below.

The discipline I now apply: any visually bounded list holds no more than seven items, ideally four to six. If I have more, I split into two named groups. This applies to skills, certifications, industries, language proficiencies, and project bullets per project. The header does the chunking work; the items merely populate it. Minimal is not the same as sparse. Generous outer margins, generous inter-section gaps, but tight, evidence-packed paragraphs inside each section. A senior CV should feel structured and dense, not airy and thin.


The anti-patterns that most consistently disqualify a CV in the DACH market are unambiguous, and most CV-builder tools push you into them by default. Skill bars and percentages are the worst offender. Hiring managers describe them as filler, unhelpful, more focused on design than substance. They are subjective, unreliable, and self-undermining: a 90% bar invites the question "why not 100%", a 60% bar tells the reader the candidate is publicly admitting weakness. They are illegible to applicant tracking systems. They are also juvenile, which is fatal in DACH consulting where the buyer wants to see calm seniority. Replace them with structured text: Cloud: AWS (production at four clients), Azure (production at two), GCP (one engagement). Or grouped tag lists with optional subtle weight differentiation, regular versus bold for "core" versus "familiar". Never a quantified bar.

Word-cloud or tag-soup skill panels, with fifty tags floating in a single block, leave the reader nowhere to anchor and nothing to take away. Replace with named groups of four to six. Excessive colour is the next trap. Consensus from Indeed and Resume Genius: one accent colour, used sparingly, on a black-on-white base, two complementary tones maximum. Bright and neon are universally read as unprofessional. The safe DACH palette is black plus one restrained accent: deep navy, oxblood, forest green, or charcoal. Body text always black or near-black. Stock photography of people pointing at laptops, glass office buildings, world maps with connection arcs: all signal "we did not have anything real to show". Show the candidate's actual photo or show nothing. No exceptions.

Decorative icon ribbons, the tiny phone and email and pin glyphs next to every contact line, are individually harmless and collectively form a pixel-noise band that competes with content. At most one restrained icon per top-level section heading, or none. Always pair the icon with a word: a phone glyph alone is invisible to parsers, "Telefon: +49 ..." is not. Centred multi-line body text breaks the F-scan and forces the eye to start in a different place on every line. Left-align body text, always. Headings can be centred; paragraphs cannot. Hobbies can stay on the Lebenslauf, but keep them brief and professionally adjacent: running, choir, association board. "I love beer and cats" is fine on Tinder, not on a CV.


Before any human sees your CV, it usually passes through software. In the DACH freelance and contractor market, the dominant parsers are Textkernel (which absorbed Sovren in 2022), Daxtra (commonly bundled with Bullhorn ATS for Anglo-rooted staffing firms like Hays and Progressive Recruitment), and RChilli. The receiving ATS at large DACH corporates is overwhelmingly SAP SuccessFactors. GULP runs an internal product called GULP Direkt with automatic matching. Etengo has publicly stated they use semantic, embedding-based skill matching. Hays has announced AI-augmented matching at the corporate level. The defensible assumption in 2026 is hybrid: classical parsing for ingestion, embedding-based search for ranking. You optimise for both.

What parsers reliably fail on is well documented. Multi-column layouts scramble in about ten percent of cases even on the best parser, by Textkernel's own admission. Tables used for layout, as opposed to data, process in unpredictable order and produce interleaved nonsense. Headers and footers are stored in a separate stream and frequently end up disconnected from the candidate's name. Photos and graphics are ignored, which is fine, but image-only PDFs (Canva exports, "design as PNG then wrap as PDF") force OCR at thirty to sixty percent accuracy and quietly destroy your candidacy. Skill bars and progress bars render as nothing.

Dates parse most reliably as numeric ranges. Pick MM/YYYY - MM/YYYY and MM/YYYY - present (or heute if the document is in German) and use it everywhere. Mixing formats is the worst case. Section labels need to be the canonical DACH Lebenslauf headings, listed above. Every load-bearing skill should appear in expansion form once and as acronym at least once across the document: Test-Driven Development (TDD) on first occurrence, TDD thereafter. Both forms must exist somewhere so a parser indexing either token finds you. And every skill in your Technische Kenntnisse block should also appear inside at least one project entry's context. Embedding matchers reward rich context; classical parsers index the dedicated block. Do both.

On hidden text and prompt injection: do not. White-on-white instructions for an LLM screener are detected at scale. ManpowerGroup detects hidden text in roughly ten percent of CVs and excludes those candidates. Greenhouse alerts recruiters when format manipulation is detected. The reputational damage is real and growing. Most ATS-side screeners in 2026 are still rule-based pattern matchers, not LLM-prompt-injectable in the first place, so the technique is also mostly theatre.


A clarification before the next part. Most of what follows in this section applies to freelancers and independent contractors pitching projects, not to salaried applicants pursuing a Festanstellung. The German HR literature draws a sharp line between the two. A salaried application is a Bewerbungsmappe: an Anschreiben (cover letter), a two-page tabellarischer Lebenslauf organised by employer and role rather than by project, and separate attachments for Arbeitszeugnisse, certificates, and Referenzen. The Bundesagentur für Arbeit, Karrierebibel, and Stepstone all describe this format as the conservative default. What carries the document there is an unbroken career arc, named employers, degrees with final grade, role progression, and the qualified Arbeitszeugnisse behind it. Recruiters expect current Arbeitszeugnisse with the application, conventionally the most recent two or three. A Projektliste is treated as an optional supplement, capped at one A4 page, mostly relevant for architects, consultants, engineers, project managers and developers (per Robert Half).

The freelance and contractor world flips this. Industry usage replaces the Lebenslauf with a Profil, in which the Projektliste is the centerpiece and the employer chronology fades to a few lines (Freelance.de, FreelancerMap, Aristo Group). Freelancers have no legal entitlement to Arbeitszeugnisse, so client references substitute for them. The document is a sales asset for a specific engagement, not a hiring prerequisite for a permanent role. The "credibility artifact" framing, the named clients, the anonymised client tiers, the compressed STAR project entries, all of that is freelance/consulting convention, not Festanstellung convention. If you are applying for a permanent role through a corporate HR funnel, this section is interesting context, but the structural advice for your document is in the sections above.

For freelancers and consultants specifically, then. The framing shift from employee CV to consultant profile is fundamental. An employee CV is an application document: "please consider me for this open role". A consultant profile is a credibility artifact: "here is the body of work that justifies my rate". Melisa Liberman puts it well: clients choose consultants based on reputation, referrals, demonstrated expertise, and confidence in outcomes. The profile's job is to do the work of a referral when no referral is available.

Some practical reframings: responsible for X becomes engaged to deliver X for client. Worked on Y team becomes embedded as role in client's Y programme. Skilled in Z becomes Z deployed in production at three named clients. Job titles by company become project titles by outcome. The strongest single credibility signal a consultant has is the named client. If your NDA permits, name them. If it forbids, anonymise as top-three German motor insurer or DAX-listed semiconductor manufacturer; the structure of the anonymisation itself signals tier.

For project entries, compressed STAR (Situation, Task, Action, Result) is the workhorse. Structure each entry as: client/industry, role, period; one line of business context (situation); one line of what they engaged you to deliver (task); two or three bullets of what you actually did with named tools and methods (action); one line of quantified outcome (result); inline tag list of technologies. Same template every project. Predictability is part of the design. The reader's eye should be able to land on client and outcome in the same fixation, without reading anything in between.

The DACH voice is factual and restrained in both archetypes. Numbers and named systems do the bragging. Adjectives stay out of the way. "I am a results-driven, dynamic, world-class change leader" lands in this market the way American sales copy always does: with skepticism. "DAX-30, eighteen months, on time, EUR 4.2M programme volume" reads as a senior practitioner who knows what business they are in. Strong action verbs (architected, delivered, migrated, restructured, automated, mediated) carry far more weight than soft ones (supported, assisted, involved in). The latter sound like a sub-contractor describing the work; the former sound like the person who owned it.


A few opinions that fall outside the research literature but that I have earned the hard way. Photos taken in front of a wall in your apartment look like photos taken in front of a wall in your apartment, no matter how good your phone camera is. Pay a professional photographer once. The same headshot serves your CV, your LinkedIn, your profile on FreelancerMap and Freelance.de, and your personal site. It is the single piece of design investment that compounds the most. Ninety euros once, used for years.

Your CV file lives a long life inside email systems and recruiter CRMs. Name it like a senior person would: Lebenslauf_Surname_Firstname_2026-05.pdf. Not CV_neu_final_v3.docx. Not Resume.pdf. The filename is part of the document, and recruiters who handle hundreds of files a week notice the discipline. Use PDF/A-1b export with embedded fonts and a true text layer. Verify you can select the text in the exported PDF. If you cannot, the parser cannot either.

The job market in 2026 is harder than the LinkedIn posts suggest. There are still roles. There are also more applicants per role than there were two years ago, more candidates from outside the region than ever, and more automated screening between you and any human reader. None of this is a reason to give up. It is a reason to take the document seriously. The CV is one of the cheapest pieces of leverage you have. A morning rebuilding it can save you months of being filtered out before your work is ever seen.


A template, not a copy of mine. I have prepared a Word and an OpenDocument template you can adapt, derived from the principles above but with a design language different from my own CV. It carries no personal information. It uses IBM Plex Sans, Plex Serif, and Plex Mono (all libre, all render the full DACH character set correctly), a tabellarisch skeleton, the canonical German section headings, the compressed STAR project entries, and a profile-evidence strip at the top in place of a cover page. There is no skill bar in it. There is no stock photography. There are no decorative icon ribbons.

You will find the templates linked from the article footer below. Take them as a starting point, not a destination. Your CV should look like your own document, not like mine and not like a template you downloaded. The point of the template is to enforce the rules in this article so you can spend your editing energy on the content, which is where the real difference is made.

One last reminder. Almost every recommendation here has an exception. A creative-industry client may welcome the design moves that a Mittelstand banking client would penalise. A Berlin startup hiring in English may not care about the canonical German section headings that a Zurich bank or a Munich insurer absolutely requires. The discipline is to know which document you are writing and which reader you are writing for, and to make the choices on purpose. Templates exist to make the right choice the easy choice. Knowing when to break them is the senior move. The reason it works in DACH is the same as the spine of this article: substance over polish.