How to Write a CV for an Internship (Students & Recent Grads)

An internship CV follows different rules from a full-time-job CV, and the candidates who understand that immediately outperform the large share of the pool who just shrink a graduate template and hope. The reader is different — usually a junior recruiter or a hiring manager who already knows the applicants are mostly students with little or no professional experience. And the question they're asking is different: not "is this person already good at this job?" but "will this person be capable, motivated and reasonably independent within three months?" Optimise for that actual question and your CV jumps ahead of the rest. This guide shows how: why education leads, how to build the Projects / Coursework / Activities sections that internship reviewers actually read, how to turn a part-time or campus job into real signal, how to write a skills section that differentiates you from identical-looking classmates, how to prove initiative beyond the curriculum, how to write the short forward-looking summary, why one page is non-negotiable, why the cover letter does extra work here, and how to tailor the CV to the type of internship you're chasing.

Why internship CVs follow different rules

Before formatting, internalise who reads an internship CV and what they're actually deciding. The reader knows you don't have a career yet — so the CV that wins isn't the one pretending to, it's the one that answers their real question:

The reader is usually a junior recruiter or a hiring manager who expects a pool of students with little professional experience — so a thin work-history section is normal, not disqualifying
Their question isn't 'is this person already good at the job?' — it's 'will they be capable, motivated and reasonably independent within three months?'
That reframes what counts as evidence: projects, initiative, learning speed and reliability matter more than a polished job history you couldn't possibly have yet
Most of the applicant pool submits a shrunk full-time-CV template — leading with sparse experience and burying the things that actually signal potential
Optimise for the real question and a clean, well-aimed internship CV outperforms the large majority of that pool

Everything below builds the CV around the reader's genuine question. You're not hiding the lack of experience — you're showing capability, motivation and independence through the evidence a student actually has: education, projects, initiative and the way you describe even small jobs.

Lead with education, not experience

On an internship CV, education sits at the top — right under the summary — because it's both your strongest credential and where the reader expects to start. Present it with the detail that's relevant to the role:

Put education directly under the summary: university, degree (in progress), and expected graduation year
Add one line of relevant coursework when it maps to the role: 'Relevant coursework: distributed systems, algorithms, databases'
Include GPA or grade only if it's strong by your system's standard; otherwise leave it off rather than draw attention to a weak one
Example: 'BSc Computer Science (expected 2027), University of Bucharest. Relevant coursework: distributed systems, algorithms, databases.'
Add academic honours, scholarships or a notable thesis/capstone topic if you have them — they're cheap, credible signals of ability

Leading with education acknowledges honestly where you are in your career and aligns the CV with what the reader expects to see first. It's the foundation the rest of the document builds on — so make it precise and role-relevant rather than a single bare line.

The sections that replace work experience

Swap the heavy Work Experience section for the ones internship reviewers actually read: Projects (or Coursework), Activities, and — if you have it — Part-time / Summer Work. These carry the evidence of capability when a job history can't:

Projects: anything where you produced an output — a final-year project, a Kaggle entry, an open-source contribution, a freelance gig, a hackathon entry, a side product
Coursework: substantial graded projects can sit here when you don't have independent ones — frame them by what you built, not the module name
Activities: society leadership, volunteering, competitions, organising events — evidence of initiative, teamwork and reliability
Part-time / Summer Work: any paid job, reframed for transferable signal (covered below)
Order these by what best fits the role — for a technical internship lead with Projects; for a business or operations one, Activities and work may lead

These sections are not filler standing in for 'real' experience — for a student they ARE the experience. Built well, a strong Projects-and-Activities block tells the reader far more about your potential than an empty Work Experience heading ever could.

The full playbook for a CV when you have little or no formal experience

How to write a project entry

Treat each project like a job entry — that's what makes it read as real evidence rather than a hobby. Give it structure, specifics and an outcome:

Title, dates, and a one-line description of what it is and who it was for (even if 'for' is a course or yourself)
Two or three bullets on what you built, the tools you used, and what it produced or achieved
Quantify or concretise the outcome where you can: 'deployed to 200+ weekly users', 'placed top 8% in the Kaggle competition', 'cut the script's runtime from 40s to 3s'
Link it where possible — a GitHub repo or a live URL turns a claim into verifiable proof
Name your specific role on group projects: what you owned versus what the team delivered
Weak: 'Did a database project for class.' Strong: 'Built a normalised PostgreSQL inventory system with a Python CLI for a 4-person course project; designed the schema and wrote the query layer.'

A project written as a proper entry — what, with what, to what effect — is the single most persuasive thing on most internship CVs. It directly answers the reader's question about whether you can build and finish things, which is exactly what they're screening for.

Reframing part-time and campus jobs

Any paid job — retail, food service, tutoring, a campus role — belongs on the CV under Part-time / Summer Work. Don't apologise for it; reframe the bullets around the transferable signal it actually carries:

Lead with the verb and the result, not the duty. 'Cashier, Coffee Shop, Summer 2024' → 'Trained 4 new staff on the POS workflow during peak summer, cutting onboarding from 5 days to 3.'
The same role can signal communication, training, ownership, reliability and results — surface those, not 'operated the till'
Quantify the everyday: customers served per shift, money handled accurately, hours balanced around full-time study (which itself signals time management)
Tutoring, society treasurer, event organiser, sports captain — all carry real, namable skills; treat them as seriously as a 'proper' job
Show progression or trust where it exists: 'promoted to shift lead after three months', 'trusted to open and cash up independently'

A part-time job, reframed, proves you've held responsibility in the real world and delivered — a signal of reliability that pure students can't show. The job is the same; the framing is what turns 'I worked in a shop' into evidence the reader values.

Strong action verbs to turn everyday duties into achievement bullets

The skills section — your differentiator

A strong skills section matters more on an internship CV than on a senior one. When recruiters scan hundreds of near-identical education backgrounds, the skills section is what separates you — so make it specific, verifiable and honest:

List concrete, relevant skills: programming languages, tools, frameworks, software, methodologies, languages spoken — not vague traits
Be honest about level, and signal it: 'Python: proficient, 3 years', 'React: learning, 6 months'. It reads as self-aware and survives the interview
Don't overclaim — an inflated skill is exposed fast in a technical screen or task, and it costs you credibility on everything else
Group by category (languages, tools, frameworks, spoken languages) so the reader parses it in seconds
Match the role's stated tools — if the posting names specific software or languages, make sure the ones you genuinely have appear

Among a stack of students with the same degree, the honest, specific skills section is often the deciding differentiator. Calibrate it to the role and keep every claim defensible — overclaiming on an internship CV backfires the moment the technical conversation starts.

How to build a skills section that reads as a credible, specific competency map

Proving initiative beyond the curriculum

The signal internship recruiters weigh most heavily — because it separates candidates with identical formal qualifications — is evidence that you do things beyond what's required. One or two genuine examples are enough:

A GitHub with two or three real projects (not just forked tutorials) — recent commits and a written README each
A blog or technical writing with a handful of well-made posts, showing you can explain as well as build
A side product with real users, however small — it proves you can ship something end to end
A meaningful competition result: a Kaggle ranking, a hackathon placement, a case-competition finish
Community involvement: a talk you gave, a society you ran, an open-source issue you fixed
Link the evidence and keep it current — a stale or empty link is worse than no link

Initiative is the trait that predicts whether a student will become 'capable and independent within three months', so recruiters lean on it hard. You don't need many examples — one or two real ones, clearly linked, do more to differentiate you than another line of coursework.

The internship summary

The summary at the top of an internship CV is short and forward-looking — three sentences that orient the reader before they reach the detail. It frames who you are, what you're about, and what you want:

Sentence one — who you are: degree, year, university. 'Final-year computer science student at the University of Bucharest.'
Sentence two — what you're known for or focused on, with a proof point: 'Focused on distributed systems and backend; built and deployed three SQL/Go side projects on GitHub.'
Sentence three — what you want next: 'Looking for a summer backend engineering internship where I can learn from a senior team and contribute on real production work.'
Keep it concrete and forward-looking — no 'hardworking, passionate team player', which says nothing and wastes the best space on the page
Tailor the 'what you want' line to the specific internship — it signals you're applying deliberately, not blasting a template

A good internship summary tells the reader, in three sentences, where you are, what you can already do, and what you're aiming for. Concrete and tailored, it sets up everything below; generic and adjective-laden, it wastes the most valuable lines on the CV.

The summary-writing playbook, applied to early-career and student CVs

Keep it to one page

An internship CV is one page. Always. At this stage, length is a signal in itself, and going over works against you:

One and a half pages signals padding; two pages signals you don't yet know what matters — both hurt at the screening stage
Use generous whitespace and clean section dividers so a short CV looks intentional and confident, not thin
Cut the filler that tempts students: high-school grades (once you're at university), one-day-course certificates, and every club you've ever joined
Keep only what serves the reader's question — capability, initiative, reliability — and let the rest go
If you're struggling to fill a page, add a real project rather than inflating what's there; depth on one page beats padding across two

Treat the one-page limit as a forcing function for judgment — deciding what matters is itself the skill the reader is screening for. A confident, well-spaced single page reads as someone who knows what's important; a cluttered overflow reads as someone still guessing.

The cover letter does extra work here

For internships, the cover letter carries more weight than it does for experienced hires. With less on the CV, the letter is where the human story lives — and it measurably lifts your odds:

Use it to tell what the CV can't: why this field, why this company, and what you've learned that didn't fit on the page
Show genuine, specific interest in the company — a sentence that proves you actually researched them beats any amount of enthusiasm
Connect a project or a course to what the team does, so the reader sees the link between your potential and their work
Keep it short — three or four tight paragraphs; an internship cover letter shouldn't run a full page either
Don't skip it: internship applications with a strong cover letter convert at roughly 2–3x the rate of CV-only applications

For a student, the cover letter is leverage the CV alone can't provide — the place to turn thin credentials into a motivated, specific candidacy. Given how much it moves the odds, writing a real one per application is one of the highest-return things you can do.

How to write a cover letter that adds the story your CV can't

Tailoring to the type of internship

Different internships weigh the same CV differently, and the strongest applicants tune theirs to the field. Read the posting and lead with what that internship is really screening for:

Tech / engineering: lead with Projects and a specific skills section; a live GitHub matters a lot, and shipped code beats listed coursework
Finance / consulting: lead with academics (grades, target-school signal), quantitative coursework, case-competition results, and evidence of analytical rigour
Marketing / creative: lead with a portfolio or samples, campaigns or content you've made, and any audience or engagement numbers
Research / academic: lead with relevant coursework, a thesis or lab experience, technical methods and any publication or poster
Operations / business: lead with leadership and reliability signals — society roles, organising, part-time work where you held responsibility

The same underlying material, reordered for the field, reads as a targeted application rather than a generic blast. Decide what the specific internship values most, and make sure that's the first thing the reader meets.

Common internship-CV mistakes

Most weak internship CVs fail in a handful of avoidable ways. Each is quick to fix:

Using a shrunk full-time-CV template that leads with sparse experience instead of education and projects
Listing projects as one-liners with no tools, role or outcome — so they read as hobbies, not evidence
Apologising for or omitting part-time jobs instead of reframing them for transferable signal
A vague skills section ('hardworking, good communicator') instead of specific, honest, verifiable skills
Overclaiming skills you can't defend in a technical conversation
Going over one page, or padding with high-school grades and one-day certificates
Skipping the cover letter — the single biggest lift available on an internship application

Run the reader's test: in a few seconds, can a recruiter see your degree, one or two real projects, the skills that fit the role, and a sign you take initiative? If yes, you're already ahead of most of the pool. If not, the fixes above are about leading with education, turning projects and jobs into evidence, and cutting the filler.