How to Write a CV for Tech Jobs

Updated 15 November 2026 · Standard formula, shown below

This guide shows you how to write a CV for a tech job that gets past automated screeners and convinces a hiring manager to interview you. You will learn the exact structure, what to include in each section, and how to phrase your experience using the language recruiters and applicant tracking systems (ATS) look for. Before you start, have your employment history, education, and a list of the technologies you have used ready.

What You’ll Need

Your complete work history with dates, job titles, and company names
A list of programming languages, frameworks, tools, and platforms you have used (even briefly)
Two or three concrete achievements from past roles (e.g., “cut page load time by 40%”)
Your education details, including degrees, certifications, and relevant courses
A plain text editor or a word processor (Google Docs, Word, or a CV builder)

Step-by-Step

Choose the right format. Use a reverse-chronological CV (most recent job first) unless you have large gaps or are changing careers, in which case a skills-based format works better. For tech roles, a clean single-column layout with clear headings is safest for ATS parsing.
Add your name and contact details at the top. Include your phone number, a professional email address, and your city and country. Add links to your LinkedIn profile, GitHub, personal website, or portfolio if they are up to date and relevant. Do not include your full home address, date of birth, or photo.
Write a 2-3 sentence professional summary. State your job title, years of experience, your main tech stack, and one standout achievement. For example: “Backend developer with 5 years of experience building REST APIs in Python and Node.js. Reduced server response times by 30% at a fintech startup. Seeking a senior backend role in a product-focused team.” Tailor this summary to each job posting.
List your technical skills in a dedicated section. Group them into categories like Languages (Python, Java, SQL), Frameworks (React, Django, Spring), Tools (Docker, Git, Jenkins), and Platforms (AWS, Azure). Only list skills you are comfortable discussing in an interview. Put the skills that match the job description first.
Detail your work experience, starting with the most recent. For each role, list the company, your job title, and the dates (month and year). Under each role, write 3-5 bullet points. Start each bullet with a strong action verb (Built, Designed, Led, Optimized) and include metrics where possible. Focus on what you accomplished, not just what you were responsible for. Example: “Built a CI/CD pipeline that reduced deployment time from 2 hours to 15 minutes.”
Add your education. Include your degree(s), the institution, and graduation year. If you have a degree in computer science or a related field, list it prominently. Add relevant certifications (AWS Certified Solutions Architect, Cisco CCNA, Google Data Analytics) in a separate subsection or within education.
Include a projects section if you are early in your career. For each project, give the name, a one-line description, the technologies used, and a link to the code or live demo. Highlight any project that solves a real problem or shows a skill the job requires.
Add optional sections only if they add value. These include publications, conference talks, open-source contributions, or volunteer work. Skip hobbies, references, and “available upon request” — they waste space.
Tailor your CV to each job. Read the job description carefully and mirror its keywords. If the job asks for “Kubernetes” and you have used it, make sure the word appears in your skills and experience sections. Adjust your summary to reflect the role’s focus.
Proofread and save as PDF. Check for typos, inconsistent formatting, and incorrect dates. Save your CV as a PDF with a clear filename like “John-Smith-Backend-Developer.pdf” unless the job specifically asks for a Word document.

Common Mistakes

Using a generic CV for every application. Recruiters can tell when a CV is not tailored. Always adjust the summary and skills to match the job.
Listing skills without context. Saying “Java” is fine, but “Built microservices in Java using Spring Boot” is much stronger. Show how you used the skill.
Including irrelevant work experience. If you worked in retail before becoming a developer, keep it to one line or omit it entirely once you have relevant tech experience.
Using a complex layout with tables, graphics, or multiple columns. ATS software often fails to read these correctly, and your CV may be rejected before a human sees it.
Exaggerating your experience. If you list a technology you only touched once, you risk being caught out in the technical interview. Be honest about your level.
Writing long paragraphs instead of bullet points. Recruiters skim CVs in seconds. Bullet points are easier to scan and more likely to be read.

Tips

Quantify your achievements. Numbers make your impact concrete. Use metrics like “increased test coverage from 60% to 90%” or “supported 10,000 daily active users.”
Keep it to one page if you have less than 10 years of experience. Two pages is acceptable for senior roles, but never go beyond two.
Use the exact job title from the posting somewhere in your CV. If the job is “DevOps Engineer” and your last title was “Systems Administrator,” consider adding a line in your summary like “…seeking a DevOps Engineer role.”
Put your most impressive achievement first in each bullet point. Lead with the result, not the process. “Reduced cloud costs by 25% by migrating to serverless functions” is stronger than “Migrated to serverless functions, which reduced costs.”
Check the job description for specific instructions. Some companies ask for a cover letter, a portfolio link, or a specific file format. Follow them exactly.

Troubleshooting

Your CV is not getting any interview calls. First, check if it is ATS-friendly: copy the text into a plain text file and see if it reads logically. If not, simplify the layout. Second, compare your skills section to the job description — if you are missing key keywords, add them if you genuinely have the experience.
You have gaps in your employment history. Do not try to hide them. Use a functional or skills-based format, and in your summary or a brief note, mention what you did during the gap (e.g., “completed a full-stack bootcamp,” “freelanced for local businesses,” “took time for family”). Be prepared to explain it in the interview.
You are changing careers into tech. Emphasize transferable skills like project management, problem-solving, and analytical thinking. Put your projects and certifications at the top, and keep your old work experience brief, focusing on any tech-related tasks you did.
Your CV is too long. Cut any bullet point that does not relate to the job you are applying for. Remove old jobs (more than 10 years ago) and condense them to one line. Remove hobbies, references, and any section that is not directly relevant.
You are unsure if your CV is good enough. Ask a friend or mentor in tech to review it. Alternatively, use a free online CV checker that screens for ATS compatibility and common mistakes. Do not rely solely on automated feedback — get a human opinion too.

Frequently Asked Questions

How long should a tech CV be?

One page if you have under 10 years of experience, two pages maximum for senior roles. Recruiters spend about 6-7 seconds scanning a CV, so keep it concise and scannable.

Should I include a photo on my CV?

No. In most countries, photos are unnecessary and can lead to unconscious bias. Focus on your skills and experience instead.

How do I handle a lack of professional experience?

Lean on your projects, internships, open-source contributions, and relevant coursework. Create a strong projects section with links to your code and write your summary to highlight your skills and enthusiasm.

Is it okay to use a two-column CV layout?

Generally, no. Two-column layouts often confuse ATS software, causing your information to be read in the wrong order. Stick to a single-column format with clear headings.

Should I list every programming language I have ever used?

No. Only list languages you are comfortable working with professionally. If you list too many, interviewers may ask about ones you are weak in. A focused list of 5-8 core technologies is better than a long list of superficial ones.

How do I explain a job I was fired from?

Do not mention it on the CV. If asked in an interview, be honest but brief, focus on what you learned, and avoid speaking negatively about your previous employer. Your CV should only include roles and dates that you can discuss positively.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.