CAREERS

The portfolio projects that actually get interviews

Three kinds of project that make hiring managers keep reading, the ones they skim past, and how to write a project up so it does its job.

Ashwood Education · 4 min read · Sept 2026

A person sketching a flowchart on a large whiteboard

A portfolio has one job: to make a stranger believe you can do the work before they have met you. Most portfolios fall short of that, not because the projects are bad but because they look like everyone else’s and do not explain themselves.

Here is what tends to work, what tends not to, and how to present it.

What gets skimmed past

Hiring managers for junior data, AI and security roles see the same projects again and again. These rarely hurt you, but they rarely help:

  • The famous tutorial datasets. Predicting survival on the Titanic, classifying iris flowers, estimating house prices. Almost everyone has done them, often by following the same tutorial.
  • A course assignment that looks like a course assignment. It shows you finished a course, which your CV already says.
  • Twenty half-finished notebooks. Quantity reads as a lack of focus. Three finished projects beat twenty starts.
  • A chatbot with no evaluation. For AI roles, a demo that only works on the questions you happened to try is not much evidence of anything.

What gets interviews

1. A messy real dataset, cleaned in the open

Pick public data that nobody has tidied up for you. In the UK, data.gov.uk, local council open data and the Office for National Statistics are good places to start. Document your cleaning decisions as you go: what was missing, what was wrong, what you assumed and why. Then use the clean data to answer one or two real questions.

This works because it mirrors the actual job. Most of the work in data roles is getting from messy data to something trustworthy, and very few candidates show that part.

2. A small tool someone actually uses

A dashboard your current team checks every week. A script that saves a colleague an hour a month. A small app for a club or a charity. The scale does not matter. What matters is that a real person relies on it.

This works because it proves something tutorials cannot: that you can understand someone else’s problem, build something for it, and keep it working.

3. Work aimed at the kind of company you are applying to

Take something the company or its sector does, and try your own version using public information. An analysis of their market using open data. A prototype of a feature their product might have. For security roles, an investigation in a lab you set up to resemble their kind of environment. Be clear that it is your own exercise, not a claim about their internal systems.

This works because the interviewer is now discussing their own world with you, which is the most persuasive conversation an interview can be.

For security roles

A few things carry particular weight in cyber security portfolios: write-ups of lab exercises or capture-the-flag challenges that explain your reasoning, a home lab with logging you configured and then attacked yourself, and detection rules you wrote and tested. Only ever test systems you own or have explicit permission to test.

A laptop with code on screen, a phone and an open notebook on a white desk

How to write a project up

The write-up matters as much as the work. A hiring manager may give your project two minutes, so make those minutes count with a short page that answers, in this order:

  1. The question or problem, in one or two sentences
  2. The result, before any detail
  3. The data and its problems, briefly
  4. What you did, with the key decisions and why you made them
  5. What did not work, and what you would do next

Put a chart or screenshot near the top. Keep the code tidy enough that someone who opens it is not put off. Link to each project from your CV and LinkedIn profile, next to the skills it proves.

How many projects?

Two or three finished, well-explained projects are enough for most junior roles. Choose them to cover different skills: for example, one that shows data cleaning and analysis, one that shows a model or some automation, and one that shows you working for a real user. Then stop adding projects and start applying.

Be ready to talk about every one

Every project on your CV is an invitation to ask questions. Expect “why did you do it that way?”, “what would you change?” and “what was the hardest part?” If you cannot answer those comfortably, the project is not ready to show yet.

At Ashwood, every course includes a project in each module and finishes with a capstone that you shape around an industry you choose, assessed by two practitioners. The aim is that you finish with portfolio work that passes the tests above. For the next step, read how UK employers read a career-change CV.

Want to work at Ashwood?

We hire practitioners to teach and mentor each cohort.

See open roles