Fresher Resume Without Experience: What Actually Goes On The Page

The question arrives in almost the same words every time: I have never worked anywhere, so what do I actually put on the page? A fresher resume without experience is not a normal resume with one section missing and a hole where it used to be. It is a different document, read on a different axis, and the person reading it knows exactly what they are holding. A campus recruiter working through four thousand applications at Infosys, or a founding engineer at a twelve-person Bengaluru startup, is not scanning for years served. They are scanning for evidence.

The honest answer is that you almost certainly have more raw material than you think, spread across five places most people never look. The rest is ordering it so the strongest thing is seen first, and keeping the file clean enough that a parser does not throw half of it away.

Experience is a proxy, not the requirement

Every hiring decision tries to answer two questions: can this person do the work, and will they still be here in a year. Prior experience is useful because it answers both cheaply. Someone who did the job for eighteen months at Wipro has shown capability and staying power in a single line, and the reader can move on.

Nobody thinks a fresher can produce that line. The entire fresher hiring machine in India is built around its absence — that is what the aptitude test, the coding round and the HR round exist to substitute for. TCS, Cognizant and Accenture between them hire tens of thousands of freshers in a typical year, and not one of those offers turns on prior employment.

So the reframe is this: you are not compensating for missing experience, you are supplying the same two answers by other means. Capability comes from things you built, shipped, taught or fixed. Staying power comes from evidence that you finish what you start and chose this field on purpose. A candidate who ran the same club for two years and shipped one project properly reads far better than one with six half-finished certificates. The wider strategy is in how to get a job as a fresher, but the resume is where it starts.

The section order that works when the experience block is empty

Most templates put Work Experience directly under the header, because most templates are written for people who have some. Copy that layout as a fresher and you place an empty or padded box in the most valuable real estate on the page — the top third, where a recruiter spends the first ten or fifteen seconds. By the time they reach the section that would have helped you, they have already formed a view, and views formed that fast are rarely revised.

The order below puts your strongest evidence where the eye already is. Skills sit high because that is what a recruiter matches against the job description; projects sit immediately after because they are the proof the skills are real.

Section	What goes in it	Lines	Most common mistake
Contact	Name, phone, email, city, LinkedIn URL, GitHub or portfolio if relevant	2	A college email that expires, or a photograph and date of birth
Summary	Two lines naming your discipline, your two strongest skills and the role you want	0–2	Writing it when you have nothing specific to say; a generic objective is worse than no summary
Skills	Comma-separated, grouped by type, only what you can be questioned on	3–5	Listing a language you used once in a lab; rating yourself out of five stars
Projects	Two or three, each with what it does, the stack, your specific part, and one result	9–12	Describing the project and never saying what you did in it
Education	Degree, college, year, CGPA if it helps you; Class 12 and 10 on one line each	3–4	Subject-wise marks, school prize lists, anything below Class 10
Internships / training	Organisation, dates, one line on what you were given to do and what came of it	3–6	Pasting the certificate's description instead of your actual work
Achievements	Ranks, hackathon placements, scholarships, positions of responsibility with numbers	2–4	Participation certificates listed as achievements
Extras	Languages, publications, volunteering — only if the page is not yet full	0–2	"Hobbies: reading, music, travelling"

Two adjustments. If you have done a substantial internship — three months at a real organisation doing real work — promote it above projects, because it is the closest thing you have to the line a recruiter wants. And where the degree is itself the qualifying filter, as in a finance or audit role, education moves up. The layouts in the B.Tech fresher format and the B.Com fresher format differ mainly on this point.

Where the content actually comes from

"I have nothing to write" is almost always a translation problem rather than a supply problem. Things you did that felt like college life were, in fact, work — they just were not paid and did not come with a designation. Here is the same inventory, translated.

What you did	What it becomes on the resume	Where it goes
Attended a 36-hour hackathon, did not win	Built a working prototype in 36 hours with a team of four; name the stack and the problem it solved	Projects
Took school tuitions for two years	Ran a private tutoring practice for 12 students across two years; retention and results are the metric	Freelance / work
Handled a stall at the college fest	Managed a stall over three days with a ₹40,000 budget and a team of six; footfall and revenue are the numbers	Positions of responsibility
Made posters for the cultural committee	Designed 20+ event creatives in Canva and Illustrator used across campus and Instagram	Projects or skills
Was on the placement committee	Coordinated with 30+ recruiters across a placement season for a batch of 400	Positions of responsibility
Did a six-week summer training at a PSU	Industrial training with dates, department, and the one thing you were actually shown or measured	Internships / training
Finished a long self-study course and built something with it	The certification on one line, and the thing you built with it as a project	Certifications + projects
Two years in NSS or NCC	A sustained commitment with hours, camps attended and any leadership rank	Extras or achievements

Academic and personal projects

Projects carry the most weight here, and they are where most people write the least useful thing. The failure mode is describing the software instead of describing yourself. "A machine learning model to predict crop yield" gives a reader nothing to interview you on. Write what the problem was, what you specifically built, what you chose and why, and what came out of it: dataset size, accuracy, users, load time, whether it is deployed.

Two or three projects is the right number, and one should be something you built outside a syllabus — a personal project is the clearest signal that you would work on this without being made to. If it is on GitHub, link it, and make sure the README can be read in a minute.

Internships and industrial training

A four or six-week industrial training stint is still worth a line. Write it plainly — organisation, dates, department, what you were given — and do not inflate it into a quarter of leadership. Recruiters know exactly what a summer training programme at a public sector unit involves; what they are checking is that you turned up somewhere and produced something. An honest short entry costs you nothing, while an inflated one invites a question you cannot answer. If you are weighing an unpaid internship against holding out for a full-time role, the comparison between an internship and a full-time job lays out both sides.

Freelance and paid work

This is the most under-reported category in the country. Tuition, content writing, running a small business's Instagram, editing videos, designing logos, helping at a family shop — all of it is work, and it belongs on the page under Freelance Work or Work Experience. Money changing hands is the strongest available proof that someone valued your output. Write it like a job: what you did, for how long, for how many clients, and the outcome. "Wrote 60+ SEO articles for three D2C brands over eight months" is a real line of experience.

College positions and responsibility

Positions of responsibility fail when they are listed as titles. "Event Coordinator, Techfest 2025" is a designation, not a claim. What makes it land is scale: budget in ₹, team size, footfall, sponsorship raised, number of events run. A fest coordinator who managed a ₹2,00,000 budget, a team of fourteen and 3,000 attendees over two days has demonstrated project management under a deadline, and that is a transferable thing an interviewer will happily spend five minutes on.

Certifications and self-study

The honest test for a certification is whether you could answer three questions about it under pressure, or whether it produced something you can show. An eighty-hour course ending in a graded project passes. A three-hour video course finished at 1.5x does not, and listing eleven of them signals that you collect certificates rather than skills. Keep the two or three that map to the role, one line each with issuing body and year, and let the projects carry the proof. If you are still deciding what to learn, this piece on upskilling as a fresher beats a course catalogue.

What to leave off

The most damaging thing on a fresher resume is a fabricated internship. It feels low-risk because the company is small and the dates are vague, but background verification at large employers is routine and outsourced — offer letters at TCS, Capgemini and Accenture are conditional on it, and the check happens after you have accepted and often after you have joined. A stint that cannot be verified does not produce an awkward conversation; it produces a withdrawn offer or a termination, and it can follow you, because these checks are logged. There is no version of this that is worth the risk.

The rest of the cut list costs you space rather than a career. Take off the photograph, date of birth, marital status, father's name and full address — none of it is asked for in a private-sector role here, and it is the fastest way to look like a template from 2009. Take off marks below Class 10, subject-wise breakdowns and school prizes. Take off "Hobbies: reading, music, travelling", which now reads as filler. And take off every course you have ever signed up for. These recur so predictably that they are worth reading in full in the resume mistakes freshers make, alongside the structural reasons behind why a resume gets rejected.

The CGPA and percentage question

Show the number when it helps you and leave it out when it does not — but understand what leaving it out does and does not achieve. Roughly speaking, a CGPA of 7.5 and above, or 75% and above, is worth printing. Between 7.0 and 7.5 it is neutral; print it if the rest of the page is thin, since a missing number invites a worse assumption than a modest one. Below 7.0, the number is usually better left off the resume so that the reader's attention stays on your projects.

At 6.2, leaving it off is right for the resume — but it does not get you past the application form. Most large service companies have historically gated at 60% or its CGPA equivalent throughout, across Class 10, Class 12 and the degree, with no active backlogs, and their portal asks for each number separately. Omitting it from a PDF changes nothing there. Above 60% you are eligible for most mass recruiters and your resume simply should not lead with academics. Below 60% in any of the three, that route is largely closed, and the honest plan is to stop optimising for it: target product companies, startups and mid-size firms that screen on a portfolio and a technical round, apply off-campus through Naukri and LinkedIn rather than waiting on the placement cell, and push skills and projects so far forward that education is read last. Placement from a tier-3 college and campus placement preparation cover that route in more detail.

Making a thin resume survive the ATS

Parsing errors hurt a fresher more than anyone else, and the reason is arithmetic. A candidate with six years of history can lose a section and still have enough left to be read sensibly. If your projects block fails to parse, there is nothing underneath it. The whole document was three things, and one of them just vanished.

So keep the file boring on purpose. One page, single column, no text boxes, no tables used for layout, nothing in the header or footer, and a text-based PDF rather than a scan. Use the literal headings a parser is built to recognise — Work Experience, Education, Skills, Projects, Certifications — not Journey So Far or My Toolkit. Put skills in a comma-separated block rather than a grid of icons, because a comma-separated list survives extraction almost perfectly while a two-column grid often interleaves into nonsense; the case against two-column resumes covers why. Mirror the posting's vocabulary — if it says SQL and Power BI, say SQL and Power BI, not "database querying and dashboards", which is where resume keywords for freshers earns its keep. The mechanics are in how ATS software works, the layout rules in the ATS resume format.

Before you send anything, run the file through the free ATS resume checker. It reads the document in your browser and shows you what a parser extracts, which is the only way to find out that your project titles were being read as body text. Freshers regularly discover an entire section missing.

One page, and why two is worse

For a fresher the one-page rule is real, not a stylistic preference. A second page with nothing on it is not neutral — it actively signals that you could not tell what mattered, and it moves your best material further from the top. Two pages of thin content read worse than one page of dense content, every time.

Running short, the fix is depth rather than padding: another line on your best project, a number attached to a position you already listed, a result added to an internship. Running long, cut the oldest and weakest first — school achievements, the third certification, the second-best project. The guide to ideal resume length in India sets out the conventions by level; the short version is that one page holds until roughly your third or fourth year of working.

Getting a real line of experience in sixty days

The fastest way to stop having a resume without experience is to acquire some, and sixty days is genuinely enough for one solid entry. Three routes work reliably.

• A scoped free project for a small local business. Walk into a clinic, coaching centre or restaurant near you and offer one specific deliverable with a deadline — a booking page, a two-month Instagram calendar, an inventory sheet that replaces their register. Finish it, then ask for a two-line written testimonial and permission to name them. That is a client engagement, and it is written as one.
• One merged open-source contribution. Pick a mid-sized project whose tooling you already use, filter for issues labelled good-first-issue, and spend the first fortnight reading the codebase rather than writing. A merged pull request with a public link is verifiable in a way almost nothing else on a fresher resume is.
• A published data study. Take a public dataset — a government open data portal, scraped listings from a job site — ask one narrow question of it, and publish the analysis with code and charts on GitHub. It demonstrates the whole pipeline, which is what an analytics interviewer wants to test.

All three produce something with a date, an outcome and a link, which is what turns a claim into evidence. Do one properly rather than three badly. Meanwhile keep the pairing tight: a resume that gets past the parser, a short and specific cover letter for freshers where the application allows one, and a LinkedIn profile whose headline matches the roles you are chasing. The document you send is not the whole game, but for a fresher it is the part you fully control.