Do projects count without a job title?

Yes. A project counts when your CV shows what you did, in enough detail for a recruiter to judge it against the job. A recruiter is not checking whether the work came with a job title. They are checking whether the work matches what the posting asks for, and a project described well shows that more clearly than a job title described badly.

The rest of this piece covers why the title is the wrong test, what makes a project count, where a project falls short, and how to describe yours.

Why the job title is the wrong test

A job title is a label. It tells a recruiter roughly what kind of role someone held, and nothing about what they did in it. Two people with the same title can have done very different work, and a recruiter knows that.

When a CV has no relevant title, the recruiter has to read the work itself. That takes more effort from them, which is the reason a project needs to be described more carefully than a job, not less.

What makes a project count

Three things turn a project from a line on a CV into evidence.

What you did

A recruiter can only credit you with work the CV attributes to you. For a group project or a hackathon, that means saying which part was yours. "Built a route planner" could mean anything from the whole system to a button. "Wrote the backend" tells the recruiter exactly what you can be asked about.

What you decided

A project counts for more when it shows a choice. Picking one approach over another, dealing with data that did not fit, cutting a feature to finish on time: each is a sign of judgement, which a tool name cannot show. This is the same idea the Interview Score is built on, a skill shown in context counts for more than the same skill named once. How the Interview Score works sets out the method.

What happened

A result, however small. It ran on real data, someone used it, it was faster than doing the task by hand, it held up against a test set. A result does not need scale to be useful. If there is no result yet, say what the project does and stop there. An invented result is worse than none, because it is the one claim that can undo the rest of the CV.

Where a project falls short

A project is strong evidence of skill, and weaker evidence of some other things. Three limits are worth knowing before you rely on one.

• A project shows what you can build. It shows less about working with a team on a live system, so if a posting asks for that, describe honestly what your project does show rather than stretching it.
• A project does not replace a genuine requirement, such as a licence, a work permit or a required degree. Which job requirements are genuinely mandatory explains how to tell those apart from a wish list.
• A project described only by its name and tools counts for very little. "Weather app, Python, React" is a tool list with a title attached.

The same project, described two ways

Here is an invented CV entry, written for this article and not taken from any real CV.

Before: "Hackathon project: cycling route app. Python."

After: "Wrote the backend for a cycling route app at a weekend hackathon, using a public elevation data source to rank routes by how much climbing they involved, and demonstrated it to the judges."

The tool has not changed. The second version says which part was the candidate's own, one decision that shaped the result, and what happened at the end. Nothing in it needed a job title, and nothing in it is more than the project actually was.

Where a project goes on the CV

A recruiter looks first for the most relevant work, so a project belongs where it is easy to find. Give it its own heading, and place it above older, unrelated jobs when the posting asks for exactly what the project shows. A relevant project buried under unrelated history is easy to miss. How a recruiter evaluates your CV covers what gets read first.

A five minute self check

Take one project from your own CV and ask three questions of it.

• Does it say which part was yours?
• Does it show a choice you made or a problem you dealt with?
• Does it say what happened, without claiming more than did?

A project that answers all three is evidence. A project that answers none is a title.

To see how a project reads against a specific posting, use the checker for your role: AI engineer, machine learning engineer, data analyst, data scientist or software engineer. MyRecruiterCheck treats projects, internships and coursework as evidence, does not penalise a lack of paid employment, and only works from what your CV already says.