Important things to know
Tech hiring is brutal. A single role at a well-known company can attract hundreds, sometimes thousands of applications. Your CV has seconds to make an impression before a recruiter moves on or an algorithm filters it out.
The good news? Most tech CVs are mediocre. They list tools and job titles without telling a coherent story about what the candidate actually built, fixed, or delivered. If yours does something different, if it leads with impact, speaks clearly to the role, and passes both ATS and human review you're already ahead of the majority.
Here's how to build a tech CV that works in 2026.
Understand the Two Audiences You're Writing For
Before you write a single word, know who's reading your CV because in 2026, there are two audiences, and they have very different needs.
The ATS (Applicant Tracking System) scans your CV for keywords before any human sees it. Most large tech companies use them. If your CV doesn't contain the right terms from the job description, it gets filtered out regardless of how strong you are. The ATS doesn't care about your narrative, it's counting keyword matches.
The human recruiter or hiring manager cares about impact, clarity, and proof. They're scanning fast, often under ten seconds on first pass, for signals that you can do the job and have actually done it before. Vague claims and dense paragraphs lose them immediately.
The winning CV satisfies both. It's keyword-rich enough to pass the filter and compelling enough to make a human want to call you. These goals aren't in conflict clean, well-structured writing that's specific about tools and outcomes achieves both at once.
Format: Simplicity Always Wins
Tech CVs are not the place for creative layouts, infographic sections, icons, or colour-coded skill bars. These look impressive in design tools and break down entirely in ATS software which reads your CV as raw text and gets confused by anything non-standard.
The format that works:
- Clean, single-column layout with consistent fonts (Calibri, Arial, or similar at 10–12pt body, 14–16pt headings)
- Black text on white background
- Clear section headings: Profile, Skills, Experience, Projects, Education
- Bullet points, not paragraphs, for job descriptions
- No photos, no graphics, no tables
- Saved as PDF or .docx both pass ATS reliably
Length: For most tech professionals, two pages is the standard. One page can work for early-career candidates. Don't pad to fill space, but don't compress so aggressively that you strip out the evidence that makes you credible.
Section 1: The Profile — Write It Last, Make It Count
Your profile (also called a summary) sits at the top and is the first thing both ATS and humans read. It's your two-to-three sentence elevator pitch.
Write it last. Once the rest of your CV is complete, you'll have all your best material fresh in your mind. Writing it first almost always produces something generic and vague. Writing it last produces something specific and confident.
What your profile needs to answer:
- What kind of tech professional are you and what's your seniority level?
- What do you specialise in, and what's your most relevant proof point?
- What are you looking for or offering next?
Weak profile:
"Experienced software engineer with a long history of working in the technology sector and a passion for innovation."
This says nothing. Any of the other 400 applicants could have written it.
Strong profile:
"Backend engineer with six years building high-traffic APIs in Python and Node.js. Led the migration of a monolithic system to microservices at [Company], reducing latency by 40% and cutting infrastructure costs by £120k annually. Looking for senior engineering roles in fintech or SaaS."
This is specific, credible, and immediately tells the reader something they can act on.
Section 2: Skills — Be Specific and Group Logically
Your skills section needs to do two jobs: give the ATS the keyword matches it's looking for, and give the human reader a fast, scannable picture of your technical stack.
Group your skills logically rather than dumping them in one undifferentiated list:
- Languages: Python, JavaScript/TypeScript, SQL, Go
- Frameworks & Libraries: React, Django, FastAPI, Node.js
- Cloud & Infrastructure: AWS (EC2, S3, Lambda), Docker, Kubernetes, Terraform
- Data & Analytics: PostgreSQL, MongoDB, Spark, Power BI
- Tools & Practices: Git, CI/CD, Agile, REST APIs, GraphQL
Only include skills you can actually speak to in an interview. If it's on your CV, you should be ready to answer detailed questions about it.
A common mistake: listing every technology you've ever heard of. This reads as untrustworthy and dilutes the skills that actually matter. Depth beats breadth. Curate rather than accumulate.
Section 3: Work Experience — Show What You Built, Not Just Where You Worked
This is the section most tech CVs get wrong. The majority read like job descriptions: a list of responsibilities that tells the employer what the role involved, not what you contributed.
The formula that works for every bullet point is:
Action + Technology + Impact + Scope
Start with a strong verb: Built, Optimised, Migrated, Automated, Reduced, Designed, Deployed, Led, Delivered.
Then name the technical details: the language, platform, framework, or system involved.
Then give the outcome: what changed, what improved, what was saved, what was enabled.
Weak bullet:
"Responsible for maintaining backend services and fixing bugs."
Strong bullet:
"Refactored legacy payment processing service in Java, reducing average transaction time from 800ms to 120ms and eliminating a class of timeout errors affecting 3,000 daily users."
Both describe broadly the same work. Only one of them tells the employer what hiring you is worth.
Where you don't have a hard number, use scope signals: team size, user count, transaction volume, system scale. These give context that raw metrics sometimes can't.
Section 4: Projects — Your Secret Weapon
For early-career candidates, career switchers into tech, or anyone with gaps in their employment history, a projects section can be more valuable than anything else on the CV.
Side projects, open source contributions, bootcamp builds, freelance work, and personal tools all count provided you can speak to the technical decisions you made and the outcomes you achieved. GitHub links, deployed URLs, or brief technical explanations make these credible and give interviewers something to dig into.
What to include per project:
- Project name and one-line description
- Technologies used
- Your specific role and contribution
- Outcome or what it demonstrated technically
Make sure your GitHub is clean and up to date. Recruiters will check it. Pinned repositories, clear README files, and recent commits all signal an active, engaged engineer.
Section 5: Education — Less Space Than You Think
Unless you're a recent graduate, education belongs near the bottom and takes up minimal space. Your degree and institution, graduation year, and any relevant modules or dissertation are enough.
Certifications matter more than degree name in most tech hiring. AWS certifications, Google Cloud credentials, Microsoft Azure qualifications, professional Scrum certifications — these signal current, demonstrable capability and should be listed clearly, with the issuing body and date.
Tailor Every Application — Yes, Every One
The biggest mistake in tech job applications is sending the same CV to every role.
Read the job description carefully. Note which technologies are mentioned repeatedly — those are the keywords the ATS is scanning for and the hiring manager is prioritising. Adjust your profile to reflect the specific role. Reorder or emphasise the skills that are most relevant. Swap in project examples that align with the company's tech stack or problem space.
This doesn't mean rewriting your CV from scratch every time. It means making targeted adjustments that take 15 minutes and meaningfully improve your match rate. In a market where the ATS is the first filter, those 15 minutes may be the most valuable you spend.
Common Tech CV Mistakes to Drop
The skills-bar graphic. Representing your Python proficiency as "80%" on a colour bar tells the reader nothing and confuses ATS scanners.
"Responsible for..." You are documenting achievements, not a job description. Cut this phrase everywhere.
Buzzword density without substance. "Passionate, results-driven, innovative team player" without a single concrete outcome is noise.
Outdated tech with no context. Listing languages or frameworks from ten years ago without explaining relevance makes your stack look stale.
One CV for every role. Not tailoring is the equivalent of showing up to an interview without researching the company.
The Bigger Picture
A winning tech CV doesn't try to impress — it tries to inform. It makes it easy for a busy recruiter to understand quickly what you build, how you build it, and why that matters.
The formula isn't complicated: specific technologies, measurable outcomes, clean formatting, and language tailored to the role. What it requires is honesty about what you've actually delivered and the discipline to translate that work into terms that land clearly on paper.
Do that, and you won't need to send hundreds of applications. The right ones will start converting.
