How to build a strong resume with no internships (yet)

If you're a student staring at a blank resume thinking "I haven't done a hackathon or an internship — what do I even put?", the good news is this: the problem is almost never that you have no achievements. It's that you haven't learned to see and phrase the ones you already have.

Recruiters hiring for internships know you're early. They're not looking for a decade of experience — they're scanning for evidence that you can build something and finish it. That evidence is hiding in places you're probably discounting.

Where your achievements are hiding

Course projects. The semester assignment where you built an app, trained a model, or implemented a data structure from scratch is real, describable work. Treat it like a job: what you built, the stack, and the outcome.
Personal or self-taught projects. Even a small project on GitHub beats an empty section. Pin it, write a real README, and it becomes a talking point.
Open-source contributions. A couple of merged pull requests to a library you actually use are genuine, verifiable signals — a link a recruiter can click.
Competitions and practice. Kaggle notebooks, competitive-programming ratings, a sustained LeetCode streak — all quantifiable and relevant.
Non-technical work. Tutoring, a part-time job, a club you helped run. "Tutored 15 first-years in intro algorithms" shows ownership and communication — things every team wants.

None of these require a hackathon. They just require you to count them.

The formula that turns a task into an achievement

Every strong bullet follows the same shape:

Action verb + what you did + a number or outcome.

Watch what it does to a weak line:

❌ "Worked on a team project for my databases class."
✅ "Built the query layer for a 4-person class project, indexing 10k rows and cutting lookup time from seconds to under 50ms."

Same fact. Ten times stronger — because it names your contribution, the scale, and the result. If you can't attach a hard number, use a concrete outcome instead: "shipped on time," "used by the whole class," "caught a bug the starter code missed."

This is the same discipline behind good interview answers, too — if you haven't seen it, the STAR method is the spoken-word version of this exact formula.

Common mistakes

Saying "we" the whole time. The recruiter is assessing you. Own your specific piece: "I built…", "I owned…", not "the team did…".
Listing responsibilities instead of results. "Responsible for the frontend" is a job description. "Built the frontend that let 200 test users sign up" is an achievement.
No numbers, ever. "Fast", "better", "a lot" are invisible. Rows, users, percentages, and hours are what stick.
Waiting for the 'perfect' experience. Don't. Draft the resume with what you have now, then strengthen one bullet at a time as you do more.

Start with what you have

Make a list of everything you've built or done this year — every project, assignment, side thing, and job. Then run each one through the formula above. You'll almost always finish with more than you expected.

If you want a second opinion on the draft, JobLane's free Resume Checker scores your resume and flags the weak, generic bullets — the "worked on a team project" lines — with concrete rewrites, so you can see exactly which ones to sharpen before you hit send.