“I watch recruiters click links first and read almost nothing, so ten projects just becomes noise. Pick the one that proves the exact skill for the role and put it where they look before they scroll: your LinkedIn featured section, your GitHub pinned repo, and a one-line hook on your resume.”
“Ten projects means nothing if the first one doesn't tell me what you built and why it mattered. I spend about six seconds on a resume or portfolio before deciding to scroll or stop, so put the strongest, most relevant work at the top with a one-line outcome: what you shipped, who used it, and what changed. Three well-curated projects that match the role beat ten that make me hunt for the signal.”
“I used to think more projects meant more chances, but recruiters told me they scan the top third in about six seconds and bail if the headline and summary don't scream the role. Pick your two strongest projects that match the job, put them above the fold, and make the rest easy to find but not the main event.”
“I look at dozens of ML and data portfolios a week, and ten seconds is generous if the first project doesn't show the problem, the decision, and the impact in plain language. Most candidates bury the signal under ten similar builds; I'd rather see two projects that explain what you actually changed than ten that look the same.”
“Ten projects is too many. I’ve watched recruiters make a yes-or-no call in six seconds, and a bloated portfolio gives them ten reasons to say no. Pick the three pieces that prove you can do this exact job, put them first, and cut everything else.”
“Ten projects is a lot to scan in ten seconds, so I stopped asking for portfolios and started asking for one thing: the project that solved the hardest problem. If your strongest work is buried at project seven, a recruiter will never see it. Put that one first, with a one-line problem, what you did, and the outcome.”
“Ten projects is noise. Recruiters are looking for the one piece that proves you can do this job, and most portfolios bury it behind broken links, passwords they don't have, or case studies that never say what you actually changed. I've watched hiring managers reject candidates in seconds because the link didn't load or the work looked pretty but said nothing about outcomes.”
“I've screened 600 resumes in 15 minutes and my eyeballs hurt; ten seconds is actually generous if the signal isn't immediate. Your portfolio isn't being studied, it's being triaged, so the project that proves you can do this role needs to be findable in about three seconds. I'd rather see one deeply explained project with the problem, your contribution, and the outcome than ten thumbnails that all look the same.”
“I have spent years looking at CVs and portfolios for tech roles, and ten seconds is generous if the first project does not match the job I am hiring for. At AWS and Maersk I learned that recruiters scan for proof of the specific problem the team needs solved, not breadth of work. Pick the one project closest to the role and put the impact right at the top.”