Resume, CV and profile, and the four gates a resume decides

Before you can write a good resume, you need to be sure you are writing the right document, and you need to know what that document decides. Both sound obvious. Both are where a lot of applications go wrong.

The first half of this lesson separates three documents that people treat as one. The second half follows your resume through the four gates it controls, from the software that stores it to the interviewer who reads it minutes before your loop.

Resume, CV, and profile: three different documents

These three words get used interchangeably, and they should not be. They are different documents with different jobs, and sending the wrong one marks you as unfamiliar with the process.

Resume

A resume is a short, targeted summary of your relevant experience — usually one page, two if you have a decade or more behind you.

This is what almost every software engineering application wants, in the United States, Canada, India, and most of Asia.

CV

CV stands for curriculum vitae, Latin for "course of life". A CV is comprehensive rather than selective: every position, every publication, every grant, every talk. Academic CVs commonly run past ten pages, and that is correct for what they are.

Use a CV when:

• You are applying for an academic or research position.
• You are applying in a country where "CV" is the ordinary word for what Americans call a resume — much of Europe, the UK, Australia, and parts of Africa and the Middle East. In those markets, an advert asking for a "CV" usually wants a two-page resume, not a ten-page academic document.

That second case causes real confusion. If a UK job advert asks for your CV, send a two-page resume. If a university research post asks for your CV, send the long one.

Profile

A profile is your LinkedIn page, your personal site, or your GitHub. It differs from a resume in three ways: it is written in the first person, it is longer, and it is found rather than sent.

Because recruiters search profiles, a profile should contain the breadth a resume leaves out. This is the one place where listing more technologies genuinely helps — it is how you turn up in searches.

Section 10 (Beyond the Resume) covers profiles properly. For now, the rule is that a profile and a resume must never contradict each other on facts: same job titles, same dates, same companies. A mismatch is a red flag that costs you more than either document gains.

What the resume actually decides

With the right document in hand, look at what it is for. The resume does not decide whether you get hired. It decides four smaller things, and each one is a gate you cannot pass any other way.

Gate 1: whether a human sees your application

Most medium and large companies run applications through an applicant tracking system.

The important consequence is not that a robot "scores" your resume. It is that if the parser cannot read your document, your application becomes close to invisible in searches. The lesson on ATS parsing covers what this actually means; Section 4 (Tech Resume Basics) covers the formatting that keeps you parseable.

Gate 2: the recruiter screen

A recruiter looks at your resume and decides, quickly, whether you are worth a call. They are checking a small number of things: are you roughly the right level, do you have the technologies the role needs, is your work history coherent, are you in a workable location.

This is the fastest and least forgiving read your resume gets.

Gate 3: the hiring manager's review

If the recruiter passes you on, an engineer or engineering manager reads more slowly — maybe a minute. They are asking a different question: does this person operate at the level we are hiring for?

They are reading for scope and ownership. What did you actually decide? What broke if you got it wrong? How big was the thing you were responsible for?

This is where most resumes fail, and they fail quietly, because "not clearly senior enough" does not feel like a rejection reason worth writing down.

Gate 4: the interview itself

Your interviewers read your resume before the loop, often minutes before. Many will pick their questions from it.

That means the resume partly writes your interview. If you list a distributed queue you built, expect to design one. If you list Kubernetes, expect a question about it. This is an opportunity if what you listed is what you are strongest at, and a trap otherwise.