Tech recruiter CV: vocabulary, examples and mistakes to avoid (dev, data, IT)
Hiring developers, data engineers or cloud engineers has little in common with generalist recruiting. Candidates are heavily approached, engineering managers quickly spot a recruiter who confuses back-end with DevOps, and the process often includes technical stages you need to know how to run. Your CV therefore has to show two things at once: that you recruit well, and that you understand what you recruit. Here is how to build it, with the vocabulary to master, before/after experience lines and the mistakes that give away a "tech" profile that is only skin-deep. Examples are drawn from the French market.
What a Head of Talent or CTO looks for on your CV
When a tech recruiting lead reads your CV, they ask four questions:
- Which technical roles have you hired for? "IT profiles" is not enough. Front-end developers, systems engineers, data scientists, product managers: these are different markets.
- At what seniority? Hiring junior developers fresh out of school and hiring staff engineers or engineering managers call for different methods.
- How did you find candidates? For these roles, inbound applications often aren't enough. Direct sourcing is expected.
- How did you work with engineering teams? Scoping the need, designing assessment stages, structured feedback.
Every line of your CV should answer at least one of these questions.
Vocabulary to master (and use correctly)
You don't need to code. But the job titles on your CV and your examples must be accurate. Here are the distinctions most often misunderstood.
Software development
| Term | What it covers | |---|---| | Front-end | User interface: JavaScript, TypeScript, frameworks such as React, Vue or Angular | | Back-end | Server logic, APIs, databases: Java, Python, Go, PHP, Node.js, C#… | | Full-stack | Front and back, usually with one dominant side | | Mobile | iOS (Swift), Android (Kotlin) or cross-platform apps (React Native, Flutter) | | Embedded | Software on hardware: C, C++, Rust, real-time constraints |
Infrastructure and operations
| Term | What it covers | |---|---| | DevOps | Automating deployment and continuous integration (CI/CD), tools such as Docker, Kubernetes, Terraform | | SRE (Site Reliability Engineering) | Reliability and availability of production services, monitoring, incident management | | Cloud engineer | Architecture and operations on AWS, Google Cloud or Azure | | Systems and network engineer | Internal infrastructure and networks, often in IT departments and consultancies | | Cybersecurity | A wide range of roles: SOC analyst, pentester, security architect, GRC (governance, risk, compliance) |
Data
| Term | What it covers | |---|---| | Data analyst | Analysis and reporting: SQL, BI tools such as Power BI, Tableau or Looker | | Data engineer | Building data pipelines and platforms: Python, Spark, Airflow, dbt, data warehouses | | Data scientist | Statistical modelling and machine learning | | ML engineer / MLOps | Deploying and maintaining models in production | | Analytics engineer | Transforming and modelling data for analysis, often with dbt |
Confusing a data engineer with a data scientist, or DevOps with a systems administrator, is exactly the kind of mistake that costs you credibility with an engineering manager on the very first call. Use these titles precisely on your CV.
The structure of a tech recruiter CV
Job title and summary
Your title should state the specialism: "Tech Recruiter", "Talent Acquisition Partner, Tech & Product", "IT Recruiter". The summary specifies job families, company type and one achievement.
Before: "Recruiter passionate about tech, with a strong appetite for innovation."
After: "Tech Recruiter, 5 years' experience at scale-ups and IT consultancies. Hiring back-end developers, data engineers and SREs, from mid-level to lead. Direct sourcing beyond LinkedIn and assessment process design with engineering managers."
Experience: roles, seniority, method, result
Before: "Recruited IT profiles for technical teams."
After: "22 hires in 12 months for the data platform (data engineers, analytics engineers, 1 head of data), 14 of them through direct sourcing."
Before: "Organised technical interviews."
After: "Redesigned the developer process with engineering managers: replaced the take-home test with a pair programming interview and a shared scorecard by level; process cut from 5 to 3 stages."
Before: "Took part in tech events."
After: "Hosted 4 technical meetups on site with the backend team (Go, Kubernetes); 6 hires over the year from among attendees."
Take a fictional profile: a recruiter with 3 years' experience at an IT consultancy in Lyon. Her line "Recruited IT consultants" becomes:
"40 consultant hires a year (Java/Spring developers, testers, systems administrators) for client assignments; first-level technical screening agreed with technical directors, improving the conversion of client interviews over the year."
Skills: technical vocabulary in its proper place
"Roles hired: development (back-end Java, Python, Go; front-end React), data (engineering, analytics), infrastructure (DevOps, SRE, AWS/GCP cloud), cybersecurity · Sourcing: Boolean strings, X-ray, GitHub, tech communities · ATS: Greenhouse, Teamtailor · Assessment: structured scorecards, organising technical tests and system design interviews"
To expand on sourcing, the article on Boolean sourcing on your CV offers phrasings and sample search strings suited to technical profiles.
Tech market specifics worth showing
The technical assessment process
Tech companies use several formats, and knowing how to run them is a skill in its own right:
- Take-home test: an exercise completed independently.
- Live coding or pair programming: an exercise done in real time with an engineer.
- System design interview: for experienced profiles, an architecture discussion.
- Code review: the candidate comments on existing code.
On your CV, show your role: did you design or improve these stages? Train engineers to run structured interviews? Reduce candidate drop-off during the process?
Employment statuses and ways of working
Tech hiring in France often mixes several statuses: permanent contracts (CDI), freelancers, portage salarial (an umbrella employment arrangement for independent workers) and consultancy staff placed on client sites. It also involves decisions about remote work and, sometimes, international hiring with work permit procedures. If you have handled these situations, say so:
"Hired 8 engineers from outside the EU, working with the legal team on work permits; supported candidates through to arrival."
Technical employer branding
Engineering blog, open source contributions, conferences, meetups, a careers page that shows the real stack: for these roles, employer branding runs through the engineers themselves. If you coordinated this kind of work, it makes a strong line.
Mistakes to avoid
- Piling up programming languages without linking them to hires. A skills list reading "Java, Python, React, Kubernetes, Kafka, Rust, Scala" proves nothing if your experience never mentions those roles.
- Using approximate job titles: "back-end data science engineer", "network DevOps". An engineering manager spots the inconsistency immediately.
- Claiming to assess technical skills. Your role is to assess fit, motivation and behavioural skills, and to orchestrate the technical assessment. Write "technical pre-screening" rather than "assessed coding level".
- Highlighting InMail volume rather than replies and hires. With heavily approached profiles, targeting matters more than quantity.
- Forgetting the candidate relationship. Developers talk to each other about their hiring experiences. A respectful process (timelines, feedback, pay transparency) is part of what is expected of you.
Preparing for interview questions
A tech recruiter role often comes with scenario questions: explain the difference between two roles, build a search for an SRE position, persuade an employed candidate to take a first call. The article on interview questions for recruiters helps you prepare.
And if you are wondering how to present the tracking tools you use (Greenhouse, Lever, Teamtailor or others), the article on ATS used in France gives you a simple method.
Build your tech recruiter CV
The pre-filled talent acquisition CV gives you a proven structure; just swap in the roles and methods from your tech scope. You can also start from scratch in the CV editor. Open the pre-filled Talent Acquisition CV.
Frequently asked questions
Do I need a technical background to become a tech recruiter?
No, many tech recruiters come from generalist recruiting, sales or the humanities. You do need to learn the vocabulary, understand the main job families and know how to ask managers the right questions. A short course in development or data can help and deserves a place on your CV.
Should I list programming languages in my skills?
Yes, but grouped by the roles you hire for and consistent with your experience. Present them as recruiting scope ("hiring Python and Go developers"), not as personal skills, unless you actually code.
How do I move from generalist to tech recruiting on my CV?
Highlight the technical hires you have already made, even if there were few, along with your direct sourcing methods. Add what you did to build your knowledge: courses, industry watch, attending meetups. Your summary can state the direction you are aiming for.
Consultancy, software vendor, scale-up: should I specify the company type?
Yes. Hiring consultants for client assignments at an IT consultancy and hiring product engineers at a software company or scale-up call for different skills. Giving the context helps the reader map your experience onto their own need.
Which metrics should I highlight for a tech recruiter role?
Share of hires from direct sourcing, time-to-fill by job family, offer acceptance rate and engineering manager satisfaction are the easiest to read. Always specify the roles and seniority behind each number.