5 CV myths developers should stop believing

There is no shortage of CV advice online. Some of it is helpful. Some of it belongs next to dial-up internet. If you work in software, data or DevOps, you have probably heard a few "rules" that sound absolute but do very little to help you get hired.

Below are five common myths that tend to hold people back rather than move them forward.

Myth 1: Your CV must fit on exactly one page

This is one of the most persistent myths in tech. A single page can work if you are early in your career, but once you have several years of experience, shipped products and real impact to show, forcing everything into one page usually cuts out the most important details.

Two pages are completely normal in 2025. Three pages should only be used if you have extensive experience, such as long consulting work or a senior leadership background. Clear, concise content always matters more than strict length rules.

Myth 2: Fancy design templates impress recruiters

Developers appreciate clean interfaces, and recruiters feel the same. What they do not appreciate is a CV that looks like a design experiment. Overly visual templates, icons, tables and timelines can break ATS parsing or hide essential information.

You do not need a visually loud CV to stand out. You need one that is easy to scan, predictable and readable by both humans and software. A simple single-column layout consistently performs better.

Myth 3: Listing every tool you have ever used makes your CV stronger

A long, crowded skills section rarely adds value. Instead, it often raises questions about what you actually specialise in. Hiring managers look for clarity, not volume. They want to understand which technologies you use regularly, how they connect to real outcomes and where you applied them.

A strong skills section groups your tools logically, but the real clarity comes from your experience section. For each role, explain which tools, languages or frameworks you used and how you used them. This helps hiring teams and ATS systems understand your skill depth and context, rather than treating your skills as a disconnected list.

Myth 4: You only need to list big achievements on your CV

A lot of advice focuses on adding huge, impressive metrics to your CV, but not every project results in dramatic percentage gains or headline‑worthy outcomes. What matters is showing impact at a realistic scale. Smaller results still demonstrate initiative, problem solving and awareness of business value.

If you improved build times by 12%, reduced error rates in a service, automated a repetitive task or helped unblock a team, those outcomes count. They show how you think and where you add value.

A CV filled only with massive wins can look exaggerated or incomplete, while a mix of meaningful, well-explained results presents a far more accurate picture of your contribution.

Myth 5: Soft skills do not belong on a tech CV

Soft skills still matter, especially at mid to senior levels. The key is to show them rather than simply listing them. Instead of writing generic qualities like "team player," demonstrate how you collaborated, presented, mentored or led. These examples bring credibility and help hiring teams understand how you work with others.

They also make behavioural interviews much easier, because you already have clear, concrete stories that show how you communicate, collaborate and solve problems under real conditions.

What actually helps your CV

A strong CV is clear, structured and focused on real outcomes. Highlight measurable results, keep formatting clean, group your skills logically and show where you used the technologies in your experience. Add relevant projects or continuous learning that reflects where you want your career to go.

Are you looking for your next tech role? Create your free profile on hackajob and let companies apply to you. Once your CV is uploaded, we highlight your skills, experience and preferences so hiring teams can see exactly why you are a match. No keyword games, no guesswork.

FAQ: Tech CV myths and best practices

What length should a tech CV be?

Most developers with mid to senior experience will naturally end up with a two-page CV. This is completely normal. One page works for early-career roles, while three pages should be reserved for people with extensive experience. Clarity always matters more than strict page limits.

Do design-heavy CV templates help me stand out?

Not usually. Creative templates often confuse ATS systems and make it harder for recruiters to scan key information. A clean, single-column layout with consistent formatting works far better.

Should I list every technology I have ever used?

No. Hiring managers care more about relevance and depth than volume. Focus on the tools you use regularly and show where you applied them inside your experience section.

Do my achievements need big numbers to matter?

Not at all. Smaller improvements such as reducing error rates, improving performance, automating tasks or unblocking teams still show valuable impact. What matters is demonstrating how your work made a difference.

Can soft skills help me when applying for engineering roles?

Yes. They are especially important from mid-level upwards. Instead of listing soft skills, demonstrate them through examples such as mentoring, presenting, collaborating or leading initiatives.

How can I make my CV more discoverable to hiring teams?

Use clear section titles, clean formatting and measurable results. You can also upload your CV to hackajob, where your skills are extracted and mapped to relevant roles so employers see why you are a match, not just the keywords on the page.