Every fresher's CV says the same three things: hardworking, quick learner, knows MS Office. Now half of them also add "knows AI tools." None of it means very much, because anyone can type any of it, and every recruiter reading a stack of CVs knows that. What a hiring manager actually wants is proof — something real you made that they can click, read, and judge for themselves in under a minute. That's a proof-of-work portfolio, and a fresher with no work experience at all can start building one this weekend.
Why "I know AI tools" means nothing on a CV
A claim on a CV is a promise the recruiter has to take entirely on faith, and recruiters have been burned by exactly this kind of promise more times than they can count. "Proficient in Excel," "strong communication skills," "knows AI tools" — these phrases have been on CVs so long, said by so many people who couldn't actually back them up in an interview, that they've stopped carrying any real signal at all. A hiring manager skims past them the way you skim past a cookie-consent banner.
A link to something you actually built is a completely different kind of evidence — it's something they can verify themselves in thirty seconds, without having to trust your self-assessment of your own skill. Evidence beats promises every single time, in every hiring process, because evidence doesn't ask anyone to take your word for it.
You don't need a grand, impressive-sounding project to create this kind of evidence. You need small, real artefacts that show you can point a tool at an actual problem and walk away with a usable result. Three tiny, finished things say far more about you than one big, impressive-sounding claim that nobody in the process will ever get around to checking.
Three tiny projects beat one big claim
Pick the kind of role you actually want, then build the smallest genuinely useful thing someone in that role would be asked to make in their first week on the job. A weekend each is plenty of time — the goal is finished and real, not ambitious and half-done, because a half-finished ambitious project proves nothing except that you started something.
- A one-page report — feed AI a genuinely messy dataset, or a long document nobody wants to read in full, and produce a clean, sourced, one-page summary a busy manager could actually act on. This shows you can turn noise into a decision, which is most of what junior analytical roles actually are.
- A working mini-tool — a simple chatbot that answers questions about a topic you know well, or a small site you shipped by describing it to AI rather than coding it by hand. A live link that someone can click and actually use is worth more than any amount of description of what you "could" build.
- A before/after — take a genuinely boring, repetitive task (a stack of product descriptions, a week's worth of social captions, a pile of customer replies) and show the raw input sitting right next to the AI-assisted output. This one is especially persuasive because it's instantly comparable — the improvement speaks for itself without you having to argue for it.
Package it so a recruiter gets it in 30 seconds
Nobody actually reads a portfolio start to finish; they skim it, decide in the first glance whether it's worth a second look, and move on to the next CV in the pile. Respect that reality instead of fighting it. For each project, write exactly two lines: what problem it solved, and what you specifically decided or did to solve it. Add the link, add one screenshot, and stop there — no jargon, no life story, no three-paragraph justification of why you chose this particular project.
Host it somewhere a single click away — a free personal site, a shared Google Doc, a LinkedIn "Featured" section, whatever's fastest to set up this weekend. The entire portfolio should be scannable on a phone screen in under a minute, because that is exactly the amount of attention and exactly the device it will actually be judged on, whatever a career counsellor might tell you about "proper" portfolio websites.
Resist the urge to add a fourth or fifth project just to look more impressive. Three genuinely good, clearly explained pieces of proof beat six mediocre ones every time — a recruiter's patience is the scarcest resource in this whole exchange, and every extra weak project spends a little more of it for no real gain.
Talk about it like a professional, not a hobbyist
In an interview, don't lead with "I used AI to make this" as if the tool itself were the achievement. Instead, walk through what you decided: why you picked that particular problem, what you tried first that didn't work, how you noticed it wasn't working, and specifically how you checked the final output was actually correct before you called it done. That's the story of judgement, and judgement — not tool familiarity — is genuinely what gets people hired.
The tool was never going to be the impressive part; every candidate in the room has access to roughly the same tools now. The thinking around the tool — the choices, the dead ends, the moment you caught your own mistake — is the part that's actually yours, and the part no other candidate can copy by watching the same YouTube tutorial you watched.
A candidate who can walk an interviewer through three small, honestly-described builds and the reasoning behind each one will consistently beat a topper who can only recite what a course syllabus covered. One of these people has demonstrably done the job already, in miniature; the other has only heard about it. Interviewers can tell the difference within about ninety seconds, and it's the difference that actually decides most close calls.
One more thing worth saying plainly: build the portfolio before you need it, not the week of the interview. The pressure of an actual deadline makes people rush the work and skip the checking step, which produces exactly the kind of shaky, half-verified project that falls apart under a single follow-up question. A portfolio built calmly over a few unhurried weekends holds up; one built in a panic the night before rarely does.
The Sunday Series is built to hand you exactly these portfolio pieces — you leave each session with a real, working thing you made, not just notes to revisit later. Come build your first one with us for ₹99, and free if you need it to be.
Adapted and re-angled for the Institute of Applied AI from LearnPact's career blog. Authored under the LearnPact Faculty byline.
