How to Write a CV for a Technical Role — Engineering, Data, and Development

The technical CV problem

Technical candidates often make one of two mistakes:

Too technical: A wall of programming languages, frameworks, and acronyms with minimal explanation of what was actually built or achieved. This impresses no one and confuses hiring managers who aren't deeply technical.

Too vague: Describing technical work in plain English so general that technical interviewers can't tell what your depth is. "Worked on backend systems" could mean anything from minor bug fixes to architecting distributed infrastructure.

The right balance is specific enough for technical reviewers to evaluate your depth, readable enough for non-technical hiring managers to understand the scope and impact.

The technical CV structure

1. Contact details — standard, at the top

2. Personal profile — 3 sentences: seniority, technology focus, what you're looking for

3. Technical skills — before work experience for technical roles. This is the exception to the usual rule.

4. Work experience — achievement-led, with technical specificity

5. Projects (optional, but valuable for developers and data scientists)

6. Education

7. Certifications

The technical skills section

For technical roles, the skills section moves up. Recruiters and technical screeners scan it first to check for minimum qualification.

Structure:

Languages: Python, JavaScript, TypeScript, SQL
Frameworks / Libraries: React, Node.js, FastAPI, Pandas, NumPy
Cloud & Infrastructure: AWS (EC2, Lambda, S3, RDS), Docker, Kubernetes, Terraform
Databases: PostgreSQL, MongoDB, Redis, DynamoDB
Tools: Git, GitHub Actions, Jira, Datadog, Grafana
Methodologies: Agile, TDD, CI/CD, REST API design

Be specific about your proficiency level for technologies where it matters. Listing Python when you've written 10 scripts vs. 10,000 lines of production code is meaningfully different. Some candidates note "advanced", "intermediate", or the version/scope they've worked with.

Work experience bullet points for technical roles

Technical experience needs to communicate:

What you built or changed
The technical choices you made and why
The scale (traffic, data volume, team size, codebase size)
The outcome

Weak: "Worked on the API layer of the application."

Strong: "Redesigned the REST API layer for the company's core product, migrating from a monolithic structure to microservices in Node.js. Reduced API response times by 60% and enabled independent team deployment across 5 services."

Weak: "Used Python for data analysis tasks."

Strong: "Built an automated data pipeline in Python (Pandas, SQLAlchemy, Airflow) processing 2M+ rows daily, replacing a manual process that took 4 hours weekly. Deployed on AWS Lambda with Terraform-managed infrastructure."

The technical details show what you know. The outcome shows why it mattered.

Projects section (portfolio supplement)

For developers and data scientists, a projects section demonstrates capability that work experience may not cover — either because you're earlier in your career or because your work is proprietary.

For each project:

Project name and brief description (one sentence)
Technologies used
What you built and what it does
GitHub link or demo link (if public)

Keep it to 3–4 projects maximum. Quality over quantity.

How to handle proprietary work

Much technical work can't be shared publicly. Handle this by:

Describing the type of system, not the specific product
Describing scale without confidential specifics ("processed 50M monthly transactions" is fine; "the Barclays payments reconciliation system" may not be)
Linking to any open-source contributions or personal projects as alternatives

What technical hiring managers actually evaluate

Most technical hiring managers scan CVs for:

Have they worked with our stack (or something close)?
What scale have they worked at?
Did they build things independently or as part of a large team?
Do they understand the full stack, or just one part?
Do they mention the things that matter beyond code (testing, deployment, monitoring, documentation)?

Your CV should answer all five.

CVCircuit for technical CVs

CVCircuit builds a clean, ATS-compliant single-column CV — the right structure for technical roles that go through ATS screening. The technical skills section formatting is clear and machine-readable.

Build your technical CV free and export a properly formatted document for every application.