How to make a CV with AutoCoderCV
A walkthrough from a blank page to a finished PDF, including what to put in each section and the choices that matter most.
Learn
Most CVs are filtered by software before a person sees them, and most advice online ignores that. These guides cover what the machine needs and what the human wants, without the recycled filler.
A walkthrough from a blank page to a finished PDF, including what to put in each section and the choices that matter most.
Most CV advice about ATS is wrong or superstitious. Here is what the software genuinely does, and the formatting choices that matter.
Graduates and career changers have more material than they think. What to include, what order to put it in, and what to leave out.
One page, two pages, or longer — the honest answer depends on your career stage and the country you are applying in.
Twenty minutes per application, done properly, beats a hundred generic submissions. A repeatable method.
Not the obvious ones. These are the mistakes that look fine on screen and cost you the application anyway.
The four lines at the top get read more than anything else, and they are usually the weakest part of the page. A formula that works.
It depends entirely on where you are applying, and getting it wrong costs you the application in both directions.
The same word means different documents in different countries. Sending the wrong one is a quiet, common mistake.
Gaps are common and rarely fatal. What sinks applications is the attempt to hide one. How to present it in a line and move on.
The problem is not your experience — it is that the reader cannot see how it applies. How to restructure so they can.
Your CV is being assessed by someone who screens CVs professionally. What that changes, and the metrics that carry weight in HR hiring.
Sales is the one field where a CV without figures is disqualifying. Which numbers to give, and what to do when you cannot disclose them.
Your CV is not your portfolio, and designing it like one costs you interviews. What belongs on the page and what belongs behind a link.
Where BMDC registration goes, how to present rotations and procedures, and why a doctor's CV follows different rules to everyone else's.
Subject, level and board go in the first two lines. Then results, curriculum work, and the co-curricular record that separates candidates.
How to present project value and scope, which codes to name, and why the software list is doing more work than your job titles.
Why the skills wall hurts you, how to write project bullets that survive a parse, and what to do with a GitHub full of half-finished repos.
Where your ICAB or ICMAB status goes, how to describe compliance work, and why the software you name matters more than you think.
What hospitals here look for, where your BNMC number belongs, and how to describe ward work so it reads as skill rather than routine.