The best tech CV tips come down to one idea: make it easy for a busy reader to see, quickly, that you can do the job. Recruiters and hiring managers often skim CVs fast, and many companies use applicant tracking systems that filter applications before a human reads them. A clear, focused, honest CV gets through both.
For beginners and career switchers, the challenge is that you don't have years of tech experience to list. That's fine. A strong entry-level tech CV leads with skills and projects, shows how your past work transfers, and drops anything that doesn't help.
Here is how to write one.
What should a tech CV include?
Keep the structure simple and predictable. A good order for most entry-level candidates:
- Name and contact details: phone, email, city, LinkedIn and GitHub or portfolio link.
- Short profile: two or three lines saying who you are and the role you want.
- Skills: grouped and relevant to the job.
- Projects: your strongest evidence if you're new to tech.
- Experience: previous jobs, framed around transferable skills.
- Education and certifications.
You don't need a photo, date of birth, marital status, state of origin or religion on a tech CV. Many international employers expect these to be left off, and they take up space better used for skills.
How long should a tech CV be?
One page is ideal for most beginners. Two pages is acceptable if you have a longer work history, for example if you're switching from banking or teaching after several years. Anything longer usually means you're including things the reader doesn't need.
Writing a profile that actually says something
Avoid empty phrases like "hardworking, result-oriented team player". They tell the reader nothing. Instead, state your target role, your main skills and what you bring. For example:
Junior data analyst with hands-on experience in SQL, Excel and Power BI, built through three published analysis projects. Former bank operations officer with a strong eye for reconciliation and reporting accuracy.
That's two sentences, and it tells the reader exactly where you fit.
How to list technical skills
Group your skills so they're easy to scan:
- Languages: Python, SQL, JavaScript
- Tools: Git, Excel, Power BI, Docker
- Concepts: REST APIs, data cleaning, responsive design
A few rules help:
- Only list what you can discuss in an interview. If you followed one tutorial on a tool, it doesn't belong on the CV yet.
- Match the job advert. If the advert asks for SQL and you know SQL, make sure the word "SQL" appears clearly. Applicant tracking systems often look for these keywords.
- Skip rating bars and percentages. "Python: 80%" means nothing to a reader. Let your projects show your level.
Why projects matter so much on a beginner CV
If you don't have tech job experience, your projects section does the heavy lifting. Treat each project like a job entry:
- Project name and link
- One line on what it is
- Two or three bullet points on what you built, the tools you used and a result
For example:
Sales Dashboard (link)
- Cleaned and analysed two years of sales data for a small retail business using SQL and Excel.
- Built a Power BI dashboard tracking monthly revenue, top products and stock levels.
- The owner now uses it to plan monthly restocking.
Only claim results that are true. If you don't have a measurable outcome, describe what the project does clearly instead. Our guide on building a tech portfolio with no experience covers which projects to build.
How to describe non-tech experience
Career switchers often undersell their past. Your previous job taught you things employers value. The trick is to describe it in terms that connect to the role you want.
- Banking: reconciliation, attention to detail, working with sensitive data, regulatory processes.
- Teaching: explaining complex ideas clearly, planning, managing groups, creating learning materials.
- Customer service: troubleshooting, handling difficult conversations, documenting issues, working under pressure.
- Accounting: Excel, reporting, data accuracy, spotting anomalies.
Write bullet points that start with action verbs and focus on what you did, not just your job title. "Resolved customer account issues by phone and email, escalating technical faults with clear written reports" is much stronger than "Handled customer complaints."
Formatting tips that help you pass screening
- Use a simple layout. One column, standard headings, plain fonts. Fancy templates with graphics, tables and icons can confuse applicant tracking systems.
- Save as PDF unless the employer asks for Word.
- Name the file clearly, for example "Firstname-Lastname-Data-Analyst-CV.pdf".
- Use consistent dates and formatting throughout.
- Make your links clickable and check that they work.
- Proofread carefully. Spelling mistakes suggest carelessness, which matters in jobs where attention to detail counts.
Tailor your CV for every application
Sending the same CV everywhere is one of the most common reasons beginners get few replies. You don't need to rewrite it each time. Keep a master CV, then for each application:
- Read the job advert and highlight the key skills and tools.
- Adjust your profile to mention the role and the most relevant skills.
- Reorder your skills and projects so the most relevant ones come first.
- Make sure important keywords appear, but only where they're true.
If you're unsure which role your CV should target in the first place, that's worth settling before you apply anywhere. You can take the free TechDNA assessment to see which of nine tech roles fit your strengths.
Common CV mistakes to avoid
- Listing every tool you've ever touched. It dilutes your real strengths.
- Writing paragraphs instead of bullet points. Readers skim.
- Exaggerating. Interviewers will ask about anything on your CV. Being caught out costs you the job.
- Leaving gaps unexplained. If you took time out to study, say so: "Career break: full-time study in web development."
- No links. For a tech CV, a GitHub or portfolio link is often what gets you shortlisted.
Once your CV is getting responses, the next step is preparation. Our guide on how to prepare for a technical interview picks up from there, and getting your first tech job in Nigeria with no experience covers the wider job search.
Frequently asked questions
Should I include a photo on my tech CV?
Generally, no. Most tech employers, especially international ones, don't expect a photo, and leaving it off avoids any risk of bias. Use the space for skills and projects instead.
Do I need a cover letter for tech jobs?
It depends on the employer. Some ask for one, many don't. If you write one, keep it short: say which role you're applying for, why you're interested in this company and what you bring, in three or four short paragraphs.
Should I list online courses and certificates?
Yes, in a short certifications or education section, but don't let them dominate. Courses show you're learning; projects show you can apply it. Prioritise the projects.
How do I handle having no tech experience at all?
Lead with a strong profile, skills and projects, then present your previous experience in terms of transferable skills. Volunteer work, freelance gigs and open-source contributions can also go under experience if you describe them clearly.
A good CV opens the door; your skills take you through it. If you want to aim your CV at the role you're most likely to thrive in, take the free TechDNA assessment. It takes about seven minutes.