Changing careers to become a developer means entering the market with a background that looks nothing like that of a young computer science graduate. Ten years in sales, teaching or accounting take up a lot of space on the page, and it is tempting to reduce them to one line so as not to "look old". It is often a mistake. Rewritten well, a first career becomes an argument: knowledge of a sector, experience with clients, the rigour of a regulated profession. This article explains how to organise a career-change resume, then shows three annotated rewrites.
What recruiters look for in a career changer
Faced with a candidate who is changing careers, a tech recruiter asks three questions, in this order.
- Can they really code? This is the decisive question. They settle it by looking at the training completed, the projects built and, often, the GitHub profile.
- Why this change, and will it last? The recruiter wants to be sure it is not a passing experiment. A long programme, a project continued after the training or a first concrete assignment reassures them.
- What does their former job bring? This is where the career changer can stand out from classic juniors: professional maturity, knowledge of a domain, ease with clients or teams.
The resume must answer these three questions in the same order: at the top of the page for the first, in the summary for the second, in the experience section for the third.
You also need to own the level you are targeting. Despite your professional experience, you are applying for a junior developer role. Claiming an experienced level because you have a ten-year career confuses recruiters and closes doors.
Put training and projects at the top of the page
In a career-change resume, the usual order (experience first, education second) is reversed. The recruiter must find proof of your technical skills before reading about your former career.
An effective order:
- Summary: your new job, your stack, your former career in a few words.
- Development training: the provider, the title, the real duration, the qualification obtained if there is one, and what you practised there.
- Projects: two or three projects, at least one built after the training, with a link to the code.
- Development experience, if you have any: end-of-programme internship, freelance assignment, work-study.
- Previous experience: your former job, rewritten.
- Skills, languages, interests.
If you funded your training through a scheme such as the French personal training account 🔗 (CPF) or the professional transition project 🔗, there is no need to mention it on the resume. The recruiter is interested in what you learned, not in how you paid for it.
For presenting the training itself, our article on the resume after a bootcamp details the mistakes to avoid, notably presenting the programme as a job.
Rewrite your former job as useful skills
The former job is rewritten along three lines, which match what a development team values.
Knowledge of a domain. Software serves professions: healthcare, logistics, education, banking, industry. A developer who understands an end user’s constraints asks better questions and proposes better solutions. Highlight the processes, tools and rules you know from the inside.
Transferable professional skills. Managing clients or service users, writing, prioritising, running a project, leading a team, presenting to an audience. They count in a product team, provided they are described through facts rather than adjectives.
First contacts with technology. A macro written to automate a report, a complex spreadsheet, taking part in choosing a software package, writing specifications for a supplier. These show that your interest in technology did not start with the training.
Keep two to four bullets per job, no more: the former job supports the resume, it should not take it over.
Three annotated rewrites
A former salesperson
Before: "Key account sales representative (8 years). Developed client portfolio, prospecting, negotiation, targets achieved."
After: "Sales engineer at a vendor of management software for SMEs (8 years): sold and demonstrated the solution to finance departments; gathered client requirements and passed them on to the product team; configured demos in the test environment, which sparked my interest in development."
Comment: the second version removes empty phrases ("targets achieved") and highlights three elements the technical team values: knowledge of a software product, the relationship with product, and a first concrete contact with a technical environment. This profile naturally targets a B2B software vendor.
A former primary school teacher
Before: "Primary school teacher (6 years). Taught Year 5 and Year 6 classes, prepared lessons, relations with parents."
After: "Primary school teacher (6 years): designed teaching sequences for classes of twenty-five pupils; the school’s digital lead (rolled out tablets, supported colleagues on the digital learning environment); created interactive exercises, a first contact with HTML and JavaScript."
Comment: the rewrite brings out the ability to explain, group management and a digital lead role that shows a long-standing appetite for technology. This profile is particularly relevant for an education software vendor, or for a team looking for someone comfortable with documentation and user support.
A former accountant
Before: "Accountant at a firm (5 years). Bookkeeping, tax returns, year-end accounts."
After: "Accountant at a chartered accountancy firm (5 years): kept the books for a portfolio of very small business clients, VAT returns, prepared year-end accounts; automated bank reconciliations with VBA macros, then in Python; advanced user of two accounting software packages on the market."
Comment: rigour and knowledge of accounting rules are real assets for a fintech, a management software vendor or a team building invoicing tools. Mentioning VBA macros then Python tells a story of progression towards code, which makes the career change coherent.
In all three cases, the rewrite also guides targeting: each former job opens doors more naturally at certain employers. Our article on the first developer job explains how to target these employers and approach them directly.
The summary that explains the change in one sentence
The summary of a career-change resume has a precise mission: to say in one or two sentences who you are today, what you can do and what you bring from your background. It does not tell your story; it sums it up to make the reader want to continue.
Three rules:
- start with the new job, not the old one: "Junior web developer" before "former salesperson";
- give technical proof: the stack, the training, a project;
- link the former job to value for the employer, in a few words.
Examples:
- "Junior web developer (JavaScript, React, Node.js), trained in 2026 after eight years selling management software: I understand business users’ needs and know how to turn them into features."
- "Junior full-stack developer (TypeScript, PostgreSQL), former primary school teacher; comfortable documenting, explaining and supporting a product’s users."
- "Junior Python developer, former accountant at a firm; two projects automating accounting tasks published on GitHub."
Avoid phrases that justify or apologise ("despite my unusual background") and those that promise without proving ("passionate about code for as long as I can remember"). The junior developer resume template gives a first-job summary that you can adapt by adding a mention of your former career.
For this unusual background to be read properly, the form must stay classic: one page, clear sections, text that screening software can extract. The TechCV editor spares you from wrestling with the layout while you reorder your sections. You can create your resume and try several section orders in a few clicks. Finally, take care of the profile you will link to: our article on GitHub on a resume explains what a lead looks at there.
Frequently asked questions
Should I keep all my previous jobs?
Keep the most recent and most useful ones, rewritten in two to four bullets each. Older or unrelated jobs can be grouped in one line ("Previously: six years in retail, department manager then assistant store manager") to avoid a gap without cluttering the page.
Can my age be an obstacle?
Some employers favour young profiles; others value the professional maturity of a career changer. Do not mention your age on the resume, focus on technical proof and target employers for whom your former job is an asset.
Should I explain my career change in the resume or in the cover message?
The resume summary sums it up in one sentence; the full explanation belongs in an accompanying message or in the interview. Prepare a two-minute spoken version, focused on what brought you to code and what you have built since.
Is an internship essential after a career-change programme?
It is not mandatory, but a first team experience, even a short one, greatly strengthens a career-change resume. If your programme does not include an internship, a supervised freelance assignment or regular contributions to an open source project can play a comparable role.