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. I want to put the forgotten craft back on the page.
DACH means Germany, Austria, and Switzerland. Hiring practices vary across those countries, industries, and employers. This article draws on rebuilding my own CV, with a particular focus on software consulting. My design preferences are recommendations, not measured hiring rules. A salaried application usually needs a compact career summary; a freelance consultant may also need a detailed project profile. Keep that distinction in mind before choosing a template.
Start with the reader. The 2012 TheLadders eye-tracking study reported a six-second initial review in a sample of thirty recruiters. It was a commercial study, not a representative measurement of DACH hiring. Roughly 80% of review time went to name, current and previous title/company, their employment dates, and education. That does not mean 80% went to the top third of page one, as I originally wrote. The useful design lesson is modest: make basic career information easy to find on a quick scan.
A CV may be skimmed before it is read closely. I therefore put the role I am seeking, relevant experience, and clear contact details near the start. I would not spend a separate cover page on a portrait and a job title when that space could show what I can do.
A Lebenslauf is a CV, commonly laid out with dates alongside the corresponding roles and qualifications. Reverse chronology makes recent work easy to find. These conventions are useful defaults, but they do not make an English-language CV or a different readable layout invalid. Match the language and requested format of the employer or client.
A photo is a choice. Germany's Bundesagentur für Arbeit guidance explicitly says it is no longer required. I cannot support the claim that leaving one out signals inexperience across traditional DACH industries. If you include a portrait, use a clear, current image suited to the role. A professional photographer can help, but the photo is not evidence of competence.
Start the contact block with your name, location, phone number, and professional email. Nationality and family details are voluntary in the German guidance cited above; I would not treat date of birth, birthplace, marital status, or a full street address as universal requirements. Include work-authorisation information when it is relevant. Use familiar headings such as Berufserfahrung, Ausbildung, Kenntnisse, and Sprachen in a German CV, or their English equivalents in an English application. Clear headings help readers and software; there is no single compulsory set shared by every parser.
For a conventional salaried application, the German agency recommends one to two A4 pages. An experienced consultant can keep that summary short and attach a longer project list when a client needs the detail. Four to eight pages should not be the default for every senior applicant. Choose length by relevance and the recipient's instructions, rather than by a rule about what seniority must look like.
Typography should make the document easy to read. Matthew Butterick recommends 10–12 point type for print, with line spacing around 120–145% of the point size. Those are useful starting ranges. Twelve-point text is perfectly reasonable; my earlier dismissal of it was too strong. Print a page at actual size before deciding whether your chosen face and spacing work.
Choose a typeface that stays clear at the size you use. X-height means the height of a lowercase x; its proportion to capitals varies, and there is no universal 65–75% rule for a good CV font. Thin strokes and pale text can become hard to read in a small printout. Source Serif and Source Sans, IBM Plex, Charter, and Inter are options I like. Check names, accents, umlauts, and ß in the exported file. One family with a few weights is enough; a restrained serif/sans pairing can also work.
My preferences should not be mistaken for hiring evidence. Calibri, Arial, and Times New Roman can all produce a readable CV. None automatically signals a weak candidate. I avoid delicate display faces for small body text and prefer strong contrast on a white background. The test is whether the reader can comfortably read the document, not whether the font is fashionable.
Cognitive load is the effort needed to process information. Daniel Kahneman's Thinking, Fast and Slow influenced how I think about quick impressions, but it does not establish a rule for CV layout. Nor should a general theory of learning be treated as a precise model of a recruiter. My practical aim is simpler: remove avoidable work from reading the page. Group related information, explain unfamiliar terms, and make the most relevant evidence easy to find.
Grouping helps me make a dense CV readable. I use a few named groups instead of a long, undifferentiated list of technologies. There is no evidence here that every recruiter has exactly four or five active memory slots, or that a group of seven items is a scientific limit. Treat those numbers as layout preferences, then check whether a reader can find the relevant skills quickly.
The familiar skill matrix with thirty equally weighted boxes is a cognitive disaster. Every cell asks for the same attention. The reader cannot decide what matters and begins to process the page as texture. Named chunks of varying weight work better: 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 it into two named groups. This applies to skills, certifications, industries, language proficiencies, and project bullets. The header does the chunking work; the items merely populate it. A minimal layout can still be dense. I use generous outer margins and inter-section gaps, with tight, evidence-packed paragraphs inside each section. A senior CV should feel structured and substantial.
Skill bars are a design choice I would avoid. A self-assigned "90% Python" does not tell a reader what you have built or how the scale works. Some parsers may also lose the information if it exists only in a graphic. Concrete text is more useful: Cloud: AWS used in production at four clients; Azure at two. Only include counts you can substantiate. A short example of actual work tells me more than a coloured bar.
A crowded panel of technologies can make everything seem equally important. I prefer named groups and one restrained accent colour on a black-on-white page. That is a design preference, not a universal hiring rule. Stock imagery rarely helps establish a candidate's experience. Use the space for work samples or evidence when those are relevant.
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.
Some applications pass through an applicant tracking system, or ATS, before a recruiter reviews them. Parsing extracts fields from a document; matching or ranking is a separate step. The exact software and criteria vary by employer. I do not have market-share evidence for the earlier claims about dominant DACH vendors, or evidence that every employer uses a particular mix of keyword and embedding search. Write relevant experience plainly and check the application form's extracted fields when it offers a preview.
Complex layouts can cause extraction errors. Textkernel's column-layout study reported improved rendering from 62% to 90% on its test set of about 700 CVs. That is a result for that system and sample, not a general 10% failure rate for today's best parsers. I also found no support for my earlier 30–60% OCR accuracy claim. Use a PDF with real text when accepted, keep essential details in the main reading flow, and inspect text copied from the export. A date column is different from multiple unrelated reading columns; either still needs checking.
Use one clear date format, such as MM/YYYY–MM/YYYY and MM/YYYY–present, or heute in a German document. Keep section names familiar and expand specialist acronyms on first use: Test-Driven Development (TDD), for example. Describe important skills inside the projects where you used them. This helps a person assess your experience and gives a search system useful context, without pretending that we know its ranking formula.
Do not put hidden instructions or invented keywords into a CV. They do not establish qualifications, and a reader who finds them has a reason to question the application. The earlier claim that ManpowerGroup detects hidden text in 10% of CVs was not adequately sourced and has been removed. There is no reliable basis here for a universal detection rate or a claim about how most ATS products handle prompt injection.
The document changes with the engagement. For a salaried role, follow the vacancy's requested application materials. A concise career history and relevant qualifications usually come first; references, certificates, and a project list can support them where requested. Do not assume that every employer needs exactly two or three Arbeitszeugnisse, or that every project list must fit on one page. For a freelance assignment, a project profile can give more space to comparable client work and outcomes.
A consultant profile serves a particular commercial conversation. Client references and project evidence can help establish whether you can deliver the assignment. Keep an employment CV available as well if the recipient asks for it. The format should make your experience assessable without forcing the reader to reconstruct your career from a long list of unrelated engagements.
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. Make the client and outcome easy to find without reading the whole entry.
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" gives the reader little evidence to evaluate. I prefer concrete project details. "DAX-listed client, 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.
If you choose to use a portrait, a professional photograph may be useful across your CV, LinkedIn profile, and website. Compare local prices and examples of the photographer's work. My earlier ninety-euro figure was not a sourced market price, and paying for a photograph is not a requirement for a good application.
Give the file a useful name, such as Lebenslauf_Surname_Firstname_2026-05.pdf. Follow the recipient's file-format instructions. For PDF, embed the fonts and keep a real text layer. PDF/A is an archival format, not a general ATS requirement. Check that text can be selected and copied in a sensible order. OCR may recover text from an image-only file, but the result adds another source of errors.
The value of this work is making your experience easier to assess. I cannot promise that rebuilding a CV will shorten a job search by months, or infer DACH-wide hiring conditions from my own inbox. Focus on what you can check: relevant evidence, accurate dates, readable text, and a document suited to the role.
The downloadable templates provide English and German versions in Word and OpenDocument formats. They include an optional cover page, a career summary, and space for project examples. Photo, birth details, and nationality are optional. All example roles and figures are placeholders, not claims about my work. Remove sections you do not need and check the exported document before sending it.
You will find the templates in the footer. Use them as a starting point and adapt them to the recipient. They demonstrate grouping and consistent project entries; they cannot enforce a good CV or guarantee that a parser will read it correctly.
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 German section headings preferred by a particular recipient. 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.