Resume for Freshers With No Experience (Campus Placement Edition)
A fresher resume has to do the one thing a "no experience" candidate fears it cannot: prove you are worth an interview slot before anyone has worked with you. This is the campus-placement version of that answer — how placement cells actually shortlist, exactly where your CGPA and 10th/12th marks belong, what to do about a sub-7 CGPA, why a projects section beats an objective statement every time, and a copy-paste resume skeleton you can fill in tonight.
What is a "fresher resume," and how is it different?
A fresher resume is a one-page document built for someone whose strongest evidence is academic and project work rather than a job history — the format leads with Education and Projects instead of Work Experience, because that is where a student's real proof of ability actually lives. It is not a weaker version of a professional's resume; it is a different template optimized for a different kind of evidence.
That distinction matters because most general resume advice online is written for someone with three years of job titles to list, and it quietly assumes a structure that does not fit a student. Following it literally produces the two most common fresher-resume failures: an Experience section left embarrassingly blank, and a long Objective paragraph written to fill the silence where work history should be. Neither helps you. The fix is not to apologize for having no job history — it is to use a structure built for what you do have: coursework, projects, internships of any length, certifications, and campus achievements.
This guide is written specifically for campus placements in India — the mechanics of how your college's placement cell and visiting recruiters actually screen resumes, which differ in a few important ways from the general global job market. If you also want the semester-by-semester roadmap this resume fits into, read our campus placement preparation guide; if you are earlier in the pipeline and still hunting for something to put on the resume in the first place, see our guide on getting your first internship with no experience.
How placement cells actually shortlist resumes
Most Indian campus drives run through your college's Training and Placement Officer (TPO) / placement cell, and understanding its two-stage process changes how you should think about your resume. The first stage is almost entirely about numbers, not prose.
- Eligibility filter (structured data, not your resume document). Before a company's drive is announced, the placement cell typically collects your CGPA, 10th and 12th percentages, branch, batch, and active-backlog count into a spreadsheet or portal. When a company visits, this data is checked mechanically against the drive's published criteria. A resume with beautiful formatting does not fix a CGPA below the cutoff at this stage — the fields decide it, not the document.
- Resume shortlisting within the eligible pool. Once eligibility narrows the list, the placement cell (and sometimes the recruiter directly) skims the eligible students' resumes to decide who actually gets an interview slot — this step exists because the number of eligible students is often larger than the number of interview slots a company can run in a day. This is where your resume as a document, and specifically your Projects and Skills sections, earns its keep.
- Off-campus and direct applications skip stage one entirely. If you apply to a company's careers page directly rather than through your placement cell, there is no TPO pre-filter — your resume document is usually the very first thing evaluated, often by the company's own applicant tracking software before a human ever opens it.
The practical takeaway: your CGPA and marks fields get you through the campus gate, but your resume's prose — projects, skills, achievements — decides whether you get called in when there are more eligible students than seats. And because you cannot always predict whether a given opportunity will come through campus or a direct application, it pays to format for the stricter case (software-readable) by default. If you want to check yourself against a specific drive's published numbers before you even open your resume, the free placement eligibility calculator does that pass instantly. The next few sections work through both halves.
| Screening path | What decides the first cut | Where your resume document matters |
|---|---|---|
| On-campus (via TPO) | CGPA, 10th/12th %, branch, backlogs — checked as structured data | Shortlisting within the eligible pool, then interviews |
| Off-campus / direct application | Your resume document, often parsed by applicant tracking software first | The very first filter — format and keywords matter immediately |
| Referral | A person forwards your resume, sometimes bypassing the software filter | Still matters at the human-review and interview stage |
Format and length: the non-negotiables
Keep it to one page. As a fresher you simply do not have enough high-value content to fill two pages without diluting it with filler, and recruiters skimming dozens of resumes will not read a second page from a student. If your draft is running long, the fix is almost always to cut weaker lines — a vague club membership, an unnecessary Objective, a fourth adjective in a bullet — not to add a page.
Use a single-column, reverse-chronological layout, with your most recent and most relevant items first within each section. For freshers specifically, put Education before Experience — it is your strongest section, and burying it below a thin or empty Experience section undersells it. A sensible section order for most fresher resumes is: Header (contact info) → short Summary (optional) → Education → Skills → Projects → Internships/Experience (if any) → Certifications → Achievements/Extracurriculars.
Whatever order you choose, put your strongest section — usually Projects for most fresher engineering resumes — as close to the top third of the page as your structure allows. Recruiters and placement-cell staff spend seconds on a first pass; the top third gets read even when the rest is skimmed.
Where CGPA, 10th, and 12th marks actually go
All three belong in the Education section, not scattered elsewhere on the page, and not omitted. Because so many mass-recruiter drives specifically check 10th and 12th percentages alongside your degree CGPA (see our CGPA cutoffs for placements guide for which employer tiers typically look at school marks), leaving them off your resume does not hide anything from the placement cell's eligibility check — that check already has the data from your registration form — it only makes your resume look incomplete to a human reader.
| Item | Where it goes | Why it matters |
|---|---|---|
| Current degree + institute | Top of Education, with expected graduation year | First thing a recruiter confirms — your programme and timeline |
| CGPA | Same line or directly below the degree, e.g. "CGPA: 7.6/10 (up to Sem VI)" | A primary eligibility field for most drives — never omit it |
| Class XII % | Below the degree, with board name and year | Checked by many mass recruiters as a legacy eligibility criterion |
| Class X % | Below Class XII, with board name and year | Same as above; cannot be changed, so state it plainly and move on |
| Diploma (if applicable) | In place of, or alongside, Class XII depending on your path | Some drives treat diploma marks as equivalent to 12th for eligibility |
One formatting note worth repeating from the ATS section below: present this as plain text lines, not as a visually elaborate table with borders, shading, or merged cells — a simple layout survives both a human skim and a software parse.
If your CGPA is below 7: a decision tree
A CGPA below roughly 7 does not disqualify you from a resume-worthy application — it changes what you should do next, and the right move depends on how much of your degree is still ahead of you and what else you can already show. The flowchart below walks through the four most common situations.
Whichever branch fits you, the resume-level guidance is the same: report your CGPA truthfully, keep it visually understated, and shift the reader's attention to Projects and Skills — the sections a below-average CGPA cannot touch. For the underlying math on how much a CGPA can realistically move with your remaining credits, see our SGPA to CGPA guide or run your own numbers with the CGPA calculator, and for the full policy picture on backlogs, see our backlogs in engineering guide.
Do you disclose backlogs on the resume?
Not usually as a dedicated resume line — there is no standard "Backlogs" heading on a fresher resume the way there is an Education or Skills section. Backlog status is instead collected as structured data, typically in your placement cell's eligibility form or in a company's own application form, and it is checked against your official transcript or marksheet. Treat every one of those forms as a verification document, not a marketing document: understating or omitting an active backlog where a form explicitly asks for it is a factual misstatement, not a resume-writing choice, and it can surface at document verification after an offer.
Where backlogs indirectly touch your resume is the same place CGPA does: if an active backlog is currently narrowing your eligible drives, the practical response is to clear it at the next supplementary opportunity, not to try to manage how it reads on paper. Our backlogs in engineering guide covers the distinction between active and cleared backlogs and how each is typically treated by recruiters.
Why projects beat an objective statement
An objective statement tells a recruiter what you want; a project tells them what you can do. For a fresher with no job history, that trade is not close — space on a one-page resume is the scarcest resource you have, and a generic objective line spends it on the one thing every candidate already technically wants (a job), while a project bullet spends it on the one thing that actually differentiates you.
If you want a summary line at all, keep it short, specific, and skill-forward — degree, one standout skill or domain, and (if you have one) a measurable result — rather than a paragraph about your career aspirations. Most fresher resumes are better off skipping the section entirely and using that space for a fourth project bullet.
The same principle applies inside the Projects section itself: a bullet built around a real outcome reads as evidence, while a bullet built around a duty ("worked on," "was responsible for") reads as an unverified claim.
"Seeking a challenging and dynamic entry-level position in a reputed organization where I can utilize my skills and grow professionally."
"Built a Flutter + Firebase attendance app with offline-first sync, cutting perceived load time from ~2s to under 300ms; piloted with 50+ classmates over one semester."
Notice what the second version does that the first cannot: it names a technology stack a recruiter can match to a job description, states a measurable improvement, and gives an interviewer three follow-up questions to ask — exactly the conversation you want to be having.
Skills and certifications: keep them honest and specific
List skills you can actually defend in an interview, grouped into clear categories — Languages, Frameworks/Tools, and Core Subjects (Data Structures, DBMS, Operating Systems, and so on) are the standard groupings for an engineering fresher. Resist the urge to pad this list with every technology you have briefly touched; an interviewer who spots a skill on your resume will usually ask about it, and a shallow answer costs you more credibility than a shorter, honest list would have.
Certifications — NPTEL, SWAYAM, Coursera, and similar — are worth including in a short dedicated section when they are relevant to your target role or fill a gap your coursework does not cover. List the platform, the exact course title, and the year; if a certification came with a graded or proctored exam (as NPTEL courses typically do), that is worth signaling since it distinguishes it from an audit-only course completion. Two or three well-chosen certificates read as focus; ten generic ones read as padding, and they can crowd out the Projects section that is doing more of the real persuasive work.
ATS basics: formatting that survives software, not just eyes
An Applicant Tracking System (ATS) is the software many companies use to collect and, in some cases, automatically parse resumes before a person opens them — most relevant the moment you apply directly through a company's careers portal instead of through your placement cell. The safest default is a resume that is boring to a machine and clear to a human: single column, standard section headings, and no elements that exist purely for visual flair.
| Element | Do this | Avoid this |
|---|---|---|
| Layout | Single column, top-to-bottom flow | Multi-column layouts, text boxes, tables used for layout |
| File format | Text-based PDF (or .docx if the portal asks) | A scanned image saved as a PDF |
| Section headings | Standard words: Education, Skills, Projects, Experience | Creative renamed headings like "My Journey" or "What I Bring" |
| Contact info | Plain text in the body of the page | Inside a header/footer or an image, where parsers may miss it |
| Photo | Omit unless your placement cell's template requires it | An embedded photo on a resume you might submit off-campus |
| Keywords | Mirror the exact skill/role words used in the job description | Only generic buzzwords ("hardworking," "team player") |
| Fonts | Standard sans-serif (Arial, Calibri, or similar) | Decorative or script fonts that some parsers cannot read |
One more habit worth building now: before you submit any resume through an unfamiliar portal, copy-select the text out of your exported PDF and paste it into a plain text editor. If the words come out in the right order and nothing is missing, your formatting is parser-safe; if the text turns into a jumbled mess, so will whatever the ATS extracts.
Photo and date of birth: honest conventions, not rules
There is no universal law requiring or forbidding a photo or a date-of-birth line on an Indian student resume — what you see is convention, and it varies by placement cell, by generation of template, and by sector. Older Indian resume formats, and some government or public-sector-style applications, still commonly include both. Most current campus-placement and corporate hiring guidance, in India and internationally, treats them as optional at best and discourages them at worst, partly because they add no assessable information and partly because they can introduce irrelevant bias into an early screen.
The practical rule that actually matters: check your placement cell's mandated format first. If your college circulates an official resume template with a photo box and a DOB field, follow it exactly — a format violation can get a submission rejected at intake regardless of what general best practice says. Outside a mandated template, the safer default for a resume you might also use off-campus is to skip both: your date of birth is collected separately by every application form and portal that needs it, and a photo is one more element that adds nothing a recruiter needs and can complicate ATS parsing.
A copyable resume skeleton
Below is a plain-text skeleton you can paste into any document editor and fill in — deliberately free of tables, columns, and graphics so it survives both a human skim and an ATS parse. Every value shown is a placeholder; replace all of it with your own, real information, and delete any section (like Internships) that does not apply to you rather than leaving it visibly empty.
FULL NAME
City, State | +91-XXXXXXXXXX | you@email.com | linkedin.com/in/yourname | github.com/yourhandle
EDUCATION
B.Tech, Computer Science Engineering — [Institute Name] 2022–2026
CGPA: 7.6/10 (up to Sem VI)
Class XII (CBSE) — [School Name], 2022 — 84.2%
Class X (CBSE) — [School Name], 2020 — 88.6%
SKILLS
Languages: Python, Java, C++, SQL
Frameworks/Tools: React, Node.js, Git, Docker, Firebase
Core: Data Structures & Algorithms, DBMS, Operating Systems, Computer Networks
PROJECTS
[Project Name] — Personal project | github.com/yourhandle/project-repo
- What you built and for whom, in one line.
- A specific technical decision you made and why.
- A measurable outcome: users, % improvement, problem solved.
- Tech: [stack used]
[Project Name] — Course project ([Course]) | github.com/yourhandle/project-repo
- What you built and for whom, in one line.
- A specific technical decision you made and why.
- A measurable outcome: users, % improvement, problem solved.
- Tech: [stack used]
INTERNSHIPS / EXPERIENCE (delete this whole section if you have none — do not pad it)
[Company Name] — [Role] [Mon–Mon Year]
- What you did and the result, in one line.
- A second concrete contribution or number.
CERTIFICATIONS
- NPTEL: [Course Title] — [Elite / Silver / etc.] (Year)
- Coursera: [Course Title] (Year)
ACHIEVEMENTS / EXTRACURRICULARS
- [Placement/rank], [Event name] ([context, e.g. "out of 40 teams"]), Year
- [Role], [Club/Society] — one line on what you organized or led
- [Any competitive-programming rating, badge, or similar, if relevant]Turning duties into evidence: two more examples
The single biggest quality gap between a weak fresher resume and a strong one is not content — most students genuinely did interesting project work — it is how that work gets described. A duty-based bullet says what you were assigned; an evidence-based bullet says what changed because of you.
"Responsible for developing the backend for a college project using Flask and MySQL."
"Designed a normalized MySQL schema and Flask backend for a library seat-booking system used by 200+ students, adding conflict detection that cut double-booking disputes to zero over a 3-week trial."
"Worked as an intern at a startup, helped the team with various tasks related to the frontend."
"Fixed 14 bugs and shipped 2 features in a React dashboard used by internal operations; wrote unit tests that raised module coverage from 40% to 72%."
If you genuinely do not have a number to attach — not every task produces one — describe the scope and the specific technical choice instead of falling back to a duty phrase; "built the login flow using Firebase Auth with email and Google sign-in" is still more concrete and verifiable than "worked on authentication."
Mistakes to avoid
- Leaving out CGPA or marks to "hide" a weak number. It reads as evasive, and the placement cell already has the real figures from your registration data regardless.
- Writing an objective paragraph instead of leading with projects. It is the most common fresher-resume habit, and it is almost always worth cutting.
- Describing projects in one vague line. "Made a website in React" tells an interviewer nothing to ask about; what-tech-outcome does.
- Using a multi-column or graphics-heavy template for anything you might submit off-campus. It can parse incorrectly in ATS software even if it looks great to a human.
- Copying a photo or DOB field from an old template without checking whether your placement cell actually requires it.
- Letting a long, generic certification list crowd out the Projects section. Depth beats a badge collection.
- Submitting with typos or inconsistent formatting. This is the one document explicitly meant to demonstrate attention to detail — a stray typo undermines that claim on contact.
- Misstating an active backlog on a form that explicitly asks for it. It is checked against your transcript and can surface during document verification after an offer.
Frequently Asked Questions
What should a resume include when I have no work experience?
Lead with what you have actually done: your education (degree, institute, CGPA), a skills list, and — most importantly — 2 to 4 projects with concrete outcomes. Add internships if you have any, even short or unpaid ones, plus relevant certifications (NPTEL, Coursera) and achievements like hackathon placements or club leadership. Skip a generic objective statement; it wastes space a project bullet could use better.
How long should a fresher's resume be — one page or two?
One page. Recruiters and placement cells skim resumes in seconds, and a fresher rarely has enough substantive content to justify a second page without padding. If you are tempted to spill onto page two, that is usually a sign to cut weaker bullet points — vague club memberships, filler adjectives, an objective statement — rather than to add a page.
Should I put my CGPA on my resume?
Yes. CGPA is one of the first fields placement cells and recruiters check for eligibility, so omitting it looks evasive rather than strategic and can get your resume set aside before anyone reads further. Put it plainly next to your degree line — 'CGPA: 7.4/10 (up to Sem VI)' — and let the rest of the resume, especially projects, carry the persuasion.
What if my CGPA is below 7 — should I still include it?
Yes, include it honestly — recruiters cross-check it against your marksheet and transcript, so hiding or inflating it is a verification risk, not a strategy. What changes is emphasis: keep the CGPA line small and factual, do not bold or enlarge it, and put your visual weight on Projects and Skills instead. See the decision tree below for what to actually do about a sub-7 CGPA beyond the resume itself.
Do I need a photo on my resume?
Usually no, unless your college's placement cell explicitly mandates a specific template that includes one — check that first, since a format violation can get a submission rejected regardless of general advice. Outside a mandated template, skip the photo: it adds no information recruiters need, can introduce unconscious bias, and embedded images sometimes break ATS parsing when a resume is scanned by software instead of read by a human.
Should I include my date of birth?
Generally not on the resume itself. Placement portals and application forms collect your date of birth separately as structured data, so repeating it on the resume adds personal information without adding value. Some older Indian resume templates still include a DOB line out of convention rather than any requirement — if your placement cell's official format asks for it, follow that format; otherwise, leave it off.
Is an objective statement necessary for freshers?
No, and in most modern formats it actively hurts you. A generic line like 'seeking a challenging role to utilize my skills' tells a recruiter nothing they cannot already infer from your resume being in front of them. If you want a two-line summary, make it specific — degree, standout skill, one measurable project outcome — otherwise skip the section entirely and give that space to a fourth project bullet.
Do projects count as experience on a resume?
Yes — for freshers, projects are usually your strongest experience section, often stronger than a short internship. A well-documented project (what you built, the tech stack, your specific contribution, and a measurable outcome) demonstrates the same skills an interviewer would probe for in a work-experience bullet: initiative, technical ability, and the ability to finish something.
How many projects should I list?
Two to four is the practical range. Fewer than two makes the section look thin; beyond four, on a one-page resume, each project gets so little space that none of them land. Prioritize depth over count — one project explained with a clear tech stack and a quantified outcome beats four one-line project titles.
Where do 10th and 12th marks go on the resume?
In the Education section, listed below your current degree in reverse-chronological order — school/board name, percentage, and year for each. Many mass-recruiter drives specifically screen on 10th and 12th percentages alongside degree CGPA, so this is not filler; it is one of the fields placement-cell eligibility checks actually read. Our CGPA cutoffs guide covers which employer tiers typically check school marks.
What is an ATS and why does it matter for fresher resumes?
An Applicant Tracking System (ATS) is software that companies use to receive, sort, and sometimes parse resumes before a human sees them — most relevant when you apply directly through a company's careers portal rather than through your college's placement cell. A heavily designed resume with columns, tables, icons, or an embedded photo can parse incorrectly or lose text in these systems, which is why a simple, single-column, text-based format is the safer default for any resume you might submit off-campus.
What file format should I submit my resume in — PDF or Word?
PDF, unless a specific portal explicitly asks for Word (.docx) — some older or very rigid ATS installations still parse .docx more reliably than PDF, but this is now the exception. Export your PDF from a text-based document rather than saving a scanned image, so any parser can actually read the words rather than just seeing a picture of them.
Should I disclose active backlogs on my resume?
There usually is not a dedicated backlog field on the resume document itself — that information is normally collected in the placement cell's eligibility form or the company's application form, and it must be answered truthfully there, since it is checked against your transcript. Do not try to obscure a backlog by omission on a form that explicitly asks for it; our backlogs guide covers how active and cleared backlogs actually affect eligibility.
Do NPTEL and Coursera certificates matter on a fresher resume?
They can help, especially when they fill a gap your coursework does not cover or reinforce a skill your target role needs — list them under a short Certifications section with the platform, course name, and year. They rarely outweigh a strong project, so do not let a long certificate list crowd out the Projects section; two or three relevant certificates communicate initiative better than ten generic ones.
What is the difference between how campus placements and off-campus applications screen resumes?
In most campus drives, your college's placement cell first checks structured eligibility data — CGPA, 10th/12th percentage, branch, active backlogs — against the company's criteria, often before anyone reads your resume as a document; the resume then matters for shortlisting within the eligible pool and for the interview itself. Off-campus and direct online applications usually go straight into the company's own applicant tracking software, where your resume as a parsed document is the first filter. Format your resume for the stricter (off-campus/ATS) case and it will work for both.
Should I use a Canva or fancy-template resume?
Be cautious. Heavily designed templates — multi-column layouts, graphics, colored sidebars, icon-based skill bars — can look sharp to a human eye but are exactly the elements that confuse ATS parsers and placement-portal upload tools. If you use a designed template, verify it is genuinely single-column and text-selectable, or keep a plain-text backup version ready for portals that clearly state 'simple format only.'
What should I name my resume file?
Your full name plus the word Resume, such as Firstname_Lastname_Resume.pdf. Avoid generic names like resume_final_v3(2).pdf — recruiters and placement cells handle hundreds of files, and a clearly named one is easier to find again, including when they search their own inbox for you later.
Do I need a separate resume for every company?
Not a full rewrite, but a light pass is worth it. Keep one strong master resume, then for each application scan the job description or drive notice and check whether the skills and keywords it emphasizes appear on your resume in matching language — reordering a few bullet points or swapping which project leads is usually enough. Full rewrites are rarely necessary at the fresher stage.
Should I include a LinkedIn and GitHub link?
Yes, if they are genuinely worth visiting. A LinkedIn profile that mirrors your resume and a GitHub with your actual project code both let a recruiter verify and go deeper on what you have already claimed — put both as clickable links (or short, readable URLs) right in your header. Do not link a near-empty profile; an outdated or bare page can hurt more than including nothing.
How do I write project bullet points that don't sound generic?
Follow a simple pattern: what you built, the specific technology you used, and a measurable outcome or scope — a number of users, a percentage improvement, a problem it actually solved. 'Worked on a web app' is generic; 'Built a Flask + MySQL seat-booking system that replaced a paper register used by 200 students and cut double-booking disputes to zero in a 3-week trial' is specific and verifiable in an interview.
Is "references available on request" necessary?
No — drop it. It states the obvious, wastes a line on a one-page resume, and no recruiter contacts references from a line like this; they ask for them separately later in the process if needed at all. Use the line's worth of space for one more project detail instead.
Should hobbies and interests go on the resume?
Usually not worth the space on a one-page fresher resume, unless a hobby is genuinely relevant or unusual enough to be a talking point — competitive chess, a sport at state level, an open-source project you maintain for fun. Generic entries like 'reading, traveling, music' add nothing a recruiter will remember or ask about, so they are one of the first things to cut when you need room.
What are the most common mistakes fresher resumes make?
The recurring ones: a generic objective statement instead of a real summary or none at all; projects described in one vague line instead of what-tech-outcome; CGPA and marks left out or, worse, misstated; a photo or DOB copied from an old template without checking if it is needed; multi-column designs that confuse ATS parsers; and typos in the one document meant to prove attention to detail.
Is a resume different from a CV for freshers in India?
In Indian usage the two terms are often used interchangeably for students, but strictly, a CV is longer and comprehensive (used for academic, research, or international applications), while a resume is a concise, one-page, role-targeted document — which is what campus placements and most Indian corporate hiring expect from freshers. When a drive notice says 'CV', in practice it almost always wants what this guide describes: a one-page resume.
Can I use the same resume for internships and full-time placement drives?
Largely yes, with the same one-page, projects-first structure — the core content freshers have (education, projects, skills, certificates) does not change much between an internship and a full-time application. The main adjustment is emphasis: for an internship application, foreground coursework and any prior mini-projects since you have less to show; for full-time drives in your final year, foreground your most substantial and most recent project.
Key Takeaways
- Structure a fresher resume around what you actually have: Education, Skills, Projects, and any internships — not around an Experience section you have to leave blank.
- Campus drives usually screen eligibility (CGPA, 10th/12th %, backlogs) as structured data first; your resume document then decides shortlisting within the eligible pool and matters immediately for off-campus applications.
- CGPA, 10th %, and 12th % all belong in the Education section — never omit them, and never let them be the visual focus of the page.
- Below a 7 CGPA, the fix depends on how many semesters remain: repair the number if credits are left, or lead with Projects and go off-campus if you're in your final year.
- Backlogs are disclosed truthfully on forms, not hidden on the resume document — recruiters verify against your transcript.
- Projects beat an objective statement almost every time; write them as what-tech-outcome, not as duties.
- Keep formatting single-column, text-based, and boring by design — it is what survives both a human skim and ATS software.
- Photo and date of birth are conventions, not universal rules — follow your placement cell's mandated template if one exists; otherwise, skip both.
- One page, always — cut weaker content rather than adding a second page.
References
- National Career Service (NCS), Ministry of Labour & Employment, Government of India — career guidance and resume-building resources
- UNC Career Center — Resume Guide for Students
- TCS — All India NQT Hiring (published eligibility criteria, referenced for the campus-eligibility mechanics described here)
- Your college's Training and Placement Officer (TPO) / placement cell — the authoritative source for your institution's mandated resume format and drive-specific eligibility criteria.
Related Guides & Free Tools
