What German Tech Companies Look For in Your CV

A hiring manager at a Munich SaaS company opens her inbox on Monday morning. There are 147 applications for a senior backend developer position. She will spend six to eight seconds on each CV in the first pass. By the time she finishes her coffee, 120 of those candidates are out.

Most of them were qualified. Many had the right tech stack, the right years of experience, the right education. They still got filtered out, not because their skills were wrong, but because their CV did not communicate those skills in a way that registers in six seconds under German hiring norms.

The advice you find online about German CVs tends to fall into two categories. Generic Lebenslauf guides written for accountants and marketing managers, or US-centric resume tips that actively hurt you in the German market. Neither addresses what German tech companies specifically look for when they screen developer candidates.

This guide covers exactly that: the structure, content, and formatting that German tech hiring managers evaluate, why each element matters, and the mistakes that get otherwise strong candidates rejected before a single line of code is discussed.

The 6-Second Filter: What Happens When Your CV Lands on a Desk🔗

How German Tech Recruiters Actually Screen🔗

The initial CV screening at most German tech companies is not a careful read. It is a pattern-matching exercise. The recruiter or hiring manager scans for a set of signals in a fixed order: current role and seniority level, tech stack overlap with the open position, location or willingness to relocate, and whether the overall career trajectory makes sense for the role.

This happens in six to eight seconds. If those signals align, the CV moves to the “read properly” pile. If they don’t, it goes into the rejection folder. There is no second chance in this round.

German recruiters tend to be more structured in their screening than their US or UK counterparts. Many use standardized evaluation forms (Bewertungsbögen) that assign points to specific criteria. This means your CV isn’t just being “read,” it is being scored. Sections that are missing, misplaced, or formatted in unexpected ways cost you points before anyone evaluates your actual qualifications.

The Mental Checklist🔗

Every recruiter runs a version of this checklist, whether consciously or not:

1. Role fit: Does the candidate’s current or most recent role match the seniority and function of the open position?
2. Tech stack overlap: Do the listed technologies match what the team uses? At least 60-70% overlap is typically required for a callback.
3. Location and work authorization: Is the candidate based in Germany or willing to relocate? Do they have the right to work, or will the company need to sponsor a visa?
4. Career trajectory: Does the progression from junior to mid to senior make sense? Are there unexplained gaps or lateral moves that raise questions?
5. Salary range signal: While not always explicit, the seniority level and company names on your CV create an implicit salary expectation in the recruiter’s mind.

For a deeper look at how recruiters think and what intelligence you can extract from interacting with them, see our guide to recruiter intelligence.

Structure and Format: The German Standard🔗

The Expected Sections (and Their Order)🔗

German tech CVs follow a conventional structure. Deviating from it doesn’t make you look creative. It makes you look like you don’t know the market.

The standard order:

1. Personal details (Persönliche Daten): Name, address (city is enough, full street address is optional), email, phone, LinkedIn. Date of birth is still common in Germany, though not mandatory. Nationality is relevant if you are a non-EU citizen and work authorization is a factor.
2. Professional summary (Kurzprofil): Two to three sentences. Your elevator pitch. This is the single most important section for the 6-second scan.
3. Work experience (Berufserfahrung): Reverse chronological. Most recent position first, with the most detail. Older positions get progressively shorter.
4. Technical skills (Technische Kenntnisse): Grouped by category. Compact and scannable.
5. Education (Ausbildung): Degree, university, year. Keep it brief unless you are a career starter.
6. Certifications (Zertifikate): Only those relevant to the target role. See our guide on what actually proves seniority for when certifications help and when they are just paper.
7. Languages (Sprachkenntnisse): German and English proficiency levels are expected. Other languages are a bonus.

This is different from a US resume in several ways. There is no “objective statement.” Education comes after work experience (unless you are a recent graduate). And the inclusion of personal details like date of birth and a photo, while not legally required, is still the norm in Germany.

For guidance on how many pages your CV should be, our dedicated article on CV length covers the rules by experience level.

Photo: Include It or Leave It Out?🔗

The application photo is one of the most debated topics for international candidates. Here is the straightforward answer: in Germany, a professional photo on your CV is still standard practice. The majority of applications include one.

You are not legally required to include a photo. The Allgemeines Gleichbehandlungsgesetz (AGG) protects against discrimination, and some companies explicitly state that photos are not necessary. But the reality is that most German recruiters expect a photo, and its absence is noticed.

If you include a photo, invest in a professional headshot. Business casual attire, neutral background, good lighting. No selfies, no vacation crops, no full-body shots. The photo typically sits in the top-right corner of page one.

If you choose not to include a photo, that is fine, especially at international companies and Berlin startups where the practice is fading. Just be aware that at traditional Mittelstand companies, a missing photo may create a small friction point.

The Professional Summary That Works in 6 Seconds🔗

The Kurzprofil sits at the top of your CV, right below your personal details. It is the first text a recruiter reads. In six seconds, this summary needs to answer three questions: Who is this person? What do they do? Why are they relevant for this role?

A strong summary for a developer looks like this:

“Backend developer with 7 years of experience in Java and Kotlin. Most recently led the migration of a monolith to event-driven microservices at [Company], reducing deployment frequency from bi-weekly to daily. Looking for a senior backend role in a product-driven engineering team.”

That is three sentences. It covers seniority, tech stack, a concrete achievement, and intent. The recruiter knows immediately whether to keep reading.

A weak summary looks like this:

“Passionate software engineer with a strong background in various technologies and a proven track record of delivering high-quality solutions in fast-paced environments.”

This says nothing. It could apply to any developer on the planet. It wastes the most valuable real estate on your CV.

The summary is also where your CV’s narrative connects to the role you are applying for. If you are applying to a fintech, mention your fintech experience. If you are applying for a cloud infrastructure role, lead with your cloud stack. This means you will need to adjust the summary for different applications. That takes five minutes per application and significantly improves your callback rate. For a system that makes these per-application adjustments painless, check our guide on separating CV content from design.

Work Experience: Results, Not Responsibilities🔗

The Difference Between Task Lists and Impact Statements🔗

This is where most developer CVs fail, regardless of market. The default mode is listing what you were responsible for: “Developed and maintained microservices,” “Participated in code reviews,” “Collaborated with product team.” These statements tell the recruiter nothing about the quality or scale of your work.

German tech hiring managers care about impact. They want to know what you achieved, not what your job description said. Every bullet point under a position should answer the question: “What changed because I was there?”

Compare:

Before: “Responsible for backend development and performance optimization”

After: “Reduced API response times from 1.4s to 180ms by refactoring database queries and introducing connection pooling, handling 2M daily requests”

The second version is shorter, more specific, and more convincing. It tells the recruiter that you understand what matters: measurable outcomes.

Use numbers wherever you can. Latency improvements, uptime percentages, users served, revenue impact, team sizes you managed or mentored. Concrete figures stand out in a 6-second scan. Vague descriptions blend into the background.

How Many Positions to Include (and How Deep)🔗

For your last two to three positions, include three to four bullet points each, focused on results. For positions older than five to seven years, one line is enough: job title, company, dates. No bullet points.

The exception: if an older position is directly relevant to the role you are applying for, you can add one to two bullet points. But resist the temptation to give equal weight to every job you have ever held. A CV is a marketing document, not a complete employment history.

Our guide on CV page count walks through the “greatest hits” method for compressing 15+ years of experience onto two pages.

If you are actively applying and want a second pair of eyes on how your work experience reads, book a free 15-minute diagnostic call to get initial feedback.

Technical Skills: What to List and How🔗

The Skill Section That Gets You Callbacks🔗

The skills section is the second thing most recruiters look at after the summary. They are scanning for keyword matches against the job posting. If the posting says “Python, Django, PostgreSQL, AWS” and your skills section says “Java, Spring Boot, Oracle, Azure,” the match score is zero.

Structure your skills section by category:

• Languages: Python, Java, TypeScript
• Frameworks: Django, Spring Boot, React
• Databases: PostgreSQL, Redis, MongoDB
• Cloud/DevOps: AWS (EC2, S3, Lambda), Docker, Kubernetes, Terraform
• Tools: Git, Jira, Confluence

Keep it to 10 to 15 technologies total. Only list what you can discuss confidently in an interview. A recruiter who sees 30 listed skills assumes you are exaggerating. A recruiter who sees 12 targeted skills assumes you know what you are doing.

Mirror the language of the job posting. If the posting says “AWS,” don’t write “Amazon Web Services.” If it says “CI/CD,” use that exact term. This matters for both human readers and ATS systems.

What to Leave Off🔗

Remove technologies you used more than five years ago and have no intention of using again. PHP 5, jQuery, SVN, ColdFusion, whatever it is, if it doesn’t match the roles you are targeting, it is taking up space that could go to something relevant.

Do not use skill bars, percentage ratings, or star ratings. They are meaningless (what does “Python: 80%” even mean?) and they are a red flag for most hiring managers. List the skill or don’t. The interview is where you demonstrate proficiency.

ATS Compatibility: Getting Past the Machine🔗

How German ATS Systems Parse Your CV🔗

Most German companies from the Mittelstand upward use Applicant Tracking Systems that automatically extract data from your CV. Popular systems in Germany include Personio, SAP SuccessFactors, Softgarden, and Greenhouse. These systems parse your CV into structured fields: name, contact details, work history, skills, education.

The parsing works best with simple, clean formatting:

• Single-column layout. Two-column designs confuse many ATS parsers, causing data to appear in the wrong fields or get lost entirely.
• Standard section headings. Use “Work Experience,” “Education,” “Skills,” not creative alternatives like “My Journey” or “Toolbox.”
• PDF format with selectable text. Not a scanned image, not a Word document. PDF is the safest format for German ATS systems.
• No tables, text boxes, or graphics within the main content areas. These elements are frequently ignored or misread by parsers.

For tools that help you create ATS-compatible CVs with clean, professional layouts, see our guides on JSON Resume and flexible CV design and Reactive Resume as a visual CV editor.

Keywords That Matter🔗

ATS systems use keyword matching to score candidates. If the job posting mentions “Kubernetes” five times and your CV never uses the word, your match score drops significantly, even if you have extensive container orchestration experience listed under a different label.

Go through the job posting line by line and identify the key technologies, methodologies, and qualifications mentioned. Make sure those exact terms appear in your CV. This is not keyword stuffing. It is speaking the same language as the company.

One German-market-specific consideration: many job postings in Germany are bilingual or use a mix of German and English technical terms. “Softwareentwickler” and “Software Developer” mean the same thing, but the ATS may treat them as different keywords. If the posting is in German, use the German terms. If it is in English, use English. When in doubt, include both in your skills section.

Common Mistakes That Get German Tech CVs Rejected🔗

The US-Style Resume in a German Process🔗

International developers, especially those coming from the US or UK, often submit a one-page resume with no photo, no date of birth, and a generic objective statement. In the German market, this creates immediate friction. The recruiter sees an unfamiliar format and has to work harder to find the information they need. In a 6-second scan, “has to work harder” means “gets skipped.”

The most common format mismatches:

The Everything-CV🔗

Four or more pages. Twenty-five listed technologies. Every position since the university internship described in full detail. This CV signals one thing: the candidate cannot prioritize.

In tech, the ability to identify what matters and cut what doesn’t is a core competency. Your CV is a demonstration of that skill. If you cannot fit your career onto two pages, a hiring manager will wonder whether you can scope a project, write a concise design document, or focus a presentation.

Design Over Substance🔗

Infographic CVs, timeline layouts, and heavily designed templates look impressive on Dribbble. They perform poorly in German tech hiring processes. They break ATS parsers, they waste space on visual elements that carry no information, and they distract from the content.

The best-performing CV design for the German tech market is boring: single-column, clear section headings, consistent formatting, readable font, enough white space. The design should be invisible. The content should do the work.

How CodingCareer Optimizes Your CV for the German Tech Market🔗

Knowing these rules is the first step. Applying them to your own career story, deciding what to cut, which achievements to highlight, how to phrase results, and whether your layout passes both the ATS check and the 6-second human scan, is where most developers get stuck.

CodingCareer’s CV optimization works as a structured review conducted by a developer who has been through the German tech hiring process firsthand. The review covers section order and completeness, whether your professional summary works in six seconds, whether your work experience communicates impact or just lists tasks, ATS compatibility of your layout and formatting, and alignment with the specific roles you are targeting. You receive back a revised CV, not just a list of feedback notes.

For career starters and junior developers, the Junior Kickstart package combines CV optimization with an application strategy workshop and technical interview preparation. International developers entering the German market for the first time benefit from the Germany Market Entry package, which adds an online presence review and a mock behavioral interview to the CV work. Senior developers targeting high-compensation roles will find senior CV optimization, personal branding, two mock interviews, and advanced salary negotiation coaching in the High-Pay Tech Strategy package.

All packages are available with a pay-on-success pricing model: you pay a reduced rate upfront and the remainder only after you land a job. CodingCareer only earns when you get hired.

Book your free 15-minute diagnostic session and get an honest assessment of where your CV stands and what to improve.