How Many Pages Should Your Tech CV Have?

A recruiter at a German Mittelstand company receives 200 applications for a single senior developer position. For each one, they have between six and eight seconds in the first pass. Six seconds. In that time, nobody scrolls to page three. Nobody reads the paragraph about your internship in 2009. And nobody sees the AWS certification you buried on page four.

Yet developers regularly submit CVs with four, five, or even seven pages. The thinking behind it is understandable: if you have 15 years of experience, you want to show everything you’ve done. The problem is that a longer CV doesn’t show more. It shows less, because the important things get lost in the noise.

This guide explains how many pages your CV for the German tech market should actually have, what belongs on which page, how to compress 15+ years of experience into two pages without losing anything essential, and why the page count itself is a signal to the recruiter.

The gold standard: one to two pages🔗

What the German market expects🔗

In Germany, one to two pages is the standard for tech CVs. This applies across industries, but it’s taken especially seriously in tech because recruiters here handle a higher volume of applications than in most other fields.

The rule of thumb is simple: one page for career starters and juniors, two pages for anyone with more than three to five years of experience. Even for seniors with 15+ years of experience, two pages is the upper limit. Anyone who submits three or more pages is unintentionally sending a signal: this person can’t prioritize.

This isn’t just a German quirk. It reflects how recruiting processes work. The first screening step is a visual scan. Name, current position, relevant skills, education. Anything that isn’t visible in the first six to eight seconds doesn’t exist for the recruiter. If your most relevant achievements are on page three, they won’t be read. They aren’t poorly placed, they’re invisible.

Why more pages don’t mean more information🔗

The instinct to list everything comes from an understandable logic: more information gives the recruiter more reasons to invite me. In practice, the opposite happens. A long CV dilutes the strong points. If your experience as a tech lead at a scale-up sits alongside your student job as a working student in help desk support, both formatted the same way and equally prominent, the recruiter in a quick scan rates everything as “average.” The help desk entry drags the tech lead entry down, not the other way around.

Two pages force you to make an editorial decision: what matters most? That decision itself is a signal. It shows you know what counts. In a profession where prioritization is a core competency, a precise CV is a work sample.

What belongs on which page🔗

Page 1: Your strongest material🔗

The first page is the only one guaranteed to be read. This is where everything goes that makes a recruiter keep reading or pick up the phone right away.

Top third: Name, contact details, optionally a professional photo (still common in Germany, though not mandatory), and a brief summary of two to three sentences. This summary is your elevator pitch. It answers the question “Who is this person and why should I keep reading?” No quotes, no self-congratulation. A concrete profile: “Backend developer with 8 years of experience in Java and Kotlin, most recently responsible for migrating a monolith architecture to microservices at [company].”

Middle section: Your most recent and relevant work experience, ideally the last two to three positions. Each position with three to four bullet points describing concrete results, not task lists. “Reduced payment service latency from 800ms to 120ms by introducing Redis caching” is better than “Responsible for maintaining the payment service.”

Bottom third: Technical skills as a compact list (programming languages, frameworks, tools, cloud platforms). No prose, no lengthy descriptions. A quickly scannable list that the recruiter can match against the job posting.

Page 2: Context and depth🔗

The second page is for everything that completes the story but didn’t fit on page one.

Older work experience: Positions from more than five to seven years ago get just one line: job title, company, time period. No bullet points. If the role is truly relevant (e.g., you’re applying to a FinTech position and worked at a bank ten years ago), then two bullet points maximum.

Education: Degree, university, year. No listing of individual courses or modules, unless you’re a career starter and have nothing else to show.

Certifications: Only those relevant to the target position. An AWS Solutions Architect is relevant if you’re applying for a cloud role. A Scrum Master certificate is relevant if you want a role with project responsibility. Everything else is filler. Our article on certifications and paper tigers goes into detail about which credentials actually signal seniority and which are just paper.

Languages and other: Language skills belong in the CV, especially if you cover both German and English. Hobbies and personal interests are optional. In Germany, they don’t hurt if they’re brief (one line), but they won’t save a weak CV either.

Page count by experience level🔗

Not every CV needs two pages. And not every CV can fit on one page. The right length depends on your career stage.

Note that even for staff-level developers, two pages remains the limit. The temptation is strong to add a third page “because there’s so much more.” Resist it. What doesn’t fit on the first two pages belongs in the conversation, not in the CV.

15 years of experience on two pages: here’s how🔗

Step 1: Ask the relevance question🔗

Go through every position in your CV and ask yourself one question: is this relevant to the job I’m applying for? If the answer is no, condense the position to one line or remove it entirely.

This means: yes, you’re allowed to omit positions. A CV is not an Arbeitszeugnis (a formal German employment reference). It’s a marketing document. Nobody expects a gap-free chronological listing of every job since university. What matters is the narrative: where does this person come from, what can they do, and why are they a fit for this role?

Step 2: Results instead of tasks🔗

The biggest space hog in CVs is task descriptions. “Responsible for developing and maintaining microservices” says nothing, because it applies to every developer in a microservice architecture. Replace every task description with a concrete result:

• Task: “Responsible for performance optimization”
• Result: “Reduced API response time from 1.2s to 200ms through query optimization and introduction of connection pooling”

Results are shorter than task lists and simultaneously more informative. They show not just what you did, but how well you did it. This saves space and improves quality at the same time.

Step 3: Cut outdated technologies🔗

If you worked with PHP 5.2 and jQuery ten years ago and aren’t looking for a position that requires those skills today, they don’t belong in your CV. Every technology you list tells the recruiter: “I can do this and I want to do this.” If you don’t want to write PHP anymore, take it out.

This also applies to skills sections that have turned into technology museums. CVS, SVN, Ant, ColdFusion, all of it goes if it doesn’t match the target position. These entries cost space and distract from what you’re actually offering.

Step 4: The “greatest hits” method🔗

For positions older than seven to ten years, apply the greatest hits method: one line with job title, company, and time period. Not a single bullet point. If there was a genuine highlight in that role (you built a product from scratch, introduced a technology the company still uses today), then one bullet point maximum.

This is how you fit a 15-year career onto two pages without it feeling like a summary. The last five to seven years tell the story. The rest provides context.

What doesn’t belong in a CV🔗

Testimonials and reference quotes🔗

In Germany, quotes from former colleagues or managers are not included in CVs. It comes across as an American-style application and can create the impression that you’re trying too hard to sell yourself. The German market relies instead on Arbeitszeugnisse (formal employment references with a standardized, coded language), which are attached separately.

Personally, I’ve included testimonials anyway and gotten callbacks. But the effect is neutral at best. If you have space issues (and with a two-page maximum, you will), testimonials are the first thing to cut.

Photo: yes or no?🔗

In many countries, application photos are taboo. In Germany, they’re still standard, though not mandatory. The majority of German CVs include a professional photo. If you use one, invest in a professional picture. No selfie, no vacation photo with your partner cropped out. If you don’t want to use one, leave it out, it rarely leads to a rejection.

The photo takes up space: typically the upper right corner of the first page. If you use a photo, plan the layout accordingly so the first page doesn’t look cluttered.

Overlong skills lists🔗

A skills section that lists 30 technologies isn’t a strength. It’s a red flag. Recruiters then wonder: does this person really know all 30 technologies at a usable level? Or are they listing everything they’ve ever seen in a tutorial?

Limit yourself to 10 to 15 skills, grouped by category (languages, frameworks, cloud/DevOps, databases). Only list what you can talk about in an interview without breaking a sweat. Everything else hurts more than it helps.

ATS systems and page count🔗

How automated systems process your CV🔗

Many German companies, especially from Mittelstand (mid-sized companies) upward, use Applicant Tracking Systems (ATS) that automatically parse CVs. These systems don’t read your CV like a human. They extract data fields: name, contact details, work experience, skills, education.

For page count, this means: ATS doesn’t care about page count. The system doesn’t see pages, it sees text. But the human reviewing the parsed output absolutely notices how much text there is. A CV that ATS summarizes as “7 positions, 45 skills, 3 pages” still ends up on the “too long, too unspecific” pile.

Your CV’s ATS compatibility has less to do with page count than with format. Single-column layouts are parsed better than two-column ones. Standard headings (Work Experience, Education, Skills) are recognized more reliably than creative alternatives. PDF is safer than Word, as long as the text is selectable and not embedded as an image.

Format beats length🔗

If you’re choosing between a pretty three-page CV with a creative layout and a clean two-page CV with standard structure, take the two-page one. For tools that help you build a clean, ATS-compatible layout, check out our guides on JSON Resume and flexible CV design and Reactive Resume as a visual CV editor.

The CV as part of the overall strategy🔗

Your CV is the door opener. Nothing more and nothing less. It gets you the first conversation, but it alone doesn’t get you the job. Still, many application processes fail at the CV stage, long before it ever comes to the HR interview or the technical interview.

The 642 applications case study shows how an international developer navigated the German market. One of the levers that significantly improved his callback rate was optimizing his CV to the German standard: two pages, clear structure, results instead of tasks, and a summary that works in six seconds.

If you’re actively job hunting right now, it’s also worth thinking beyond just page count. Salary negotiation doesn’t start when the offer comes, it starts with your positioning in the CV. A CV that demonstrates senior-level impact shifts the company’s salary expectations upward before you’ve named a single number.

How CodingCareer optimizes your CV🔗

Writing a two-page CV that works is harder than it sounds. Most developers know their CV is too long. But deciding what stays and what goes requires an understanding of how recruiters in the German tech market actually read and filter.

CodingCareer’s CV optimization starts with a structured analysis of your existing CV. A coach who has personally gone through the German recruiting process as a developer reviews every section: is the order right? Are the results concrete and measurable? Does the layout meet ATS requirements? Does the summary work in six seconds? You get back a revised CV, not just feedback notes.

In the Junior Kickstart package, CV optimization is combined with an application strategy and technical interview preparation. For international developers who are new to the German market, the Germany Market Entry package additionally covers an online presence review and a mock behavioral interview. Those applying for senior-level positions with higher compensation will find senior CV optimization, personal branding, mock interviews, and salary negotiation coaching in the High-Pay Tech Strategy package.

The pay-on-success model means you pay a reduced amount upfront and the rest only when you land a job. CodingCareer only earns when you get hired. This completely changes the dynamic compared to services that charge regardless of the outcome.

Book your free 15-minute diagnostic call and get an initial assessment of where your CV stands and what can be improved.