Placement season is different from off-campus job applications. The companies, the process, the filters, and the resume expectations are all different. This guide covers everything — from what mass recruiters like TCS actually look for, to how product company shortlisting really works, to the exact resume format that passes India's campus placement portals in 2026.
Build my placement resumeCampus placement resumes operate in a different ecosystem from off-campus applications. You're not applying through LinkedIn or a company careers page — you're uploading to a placement portal (often AMCAT, CoCubes, or a company-specific platform) where your resume gets parsed automatically, your CGPA gets filtered before a human sees anything, and the competition is hundreds or thousands of students from the same institution.
This context changes everything. The resume format that works perfectly for a LinkedIn application may fail on a campus portal. The project descriptions that impress a startup recruiter may not differentiate you from 300 other students with similar backgrounds at a mass recruiter like TCS.
At the same time, the resume expectations of a product company like Flipkart or Google visiting campus are completely different from TCS. They're looking for depth, not breadth. One exceptional project beats five generic ones. Competitive programming rankings matter. CGPA matters less.
This guide is structured around that distinction. Use the right section for your target company type.
Different companies visit campus with different hiring objectives. Understanding what each company is screening for lets you tailor your resume more effectively rather than sending one generic version everywhere.
Process
TCS NQT → Technical Interview → HR Interview
What they screen for
CGPA filter (typically 6.0–6.5 minimum), consistent academic performance, basic programming knowledge, communication skills.
Resume approach
Single-column, clean format. CGPA must be visible. List all technical skills explicitly — TCS NQT filters on skill keywords. Include certifications. Keep to 1 page.
Avoid
Do not leave CGPA gaps or format it inconsistently. Avoid multi-column templates — TCS portals have strict upload requirements.
Process
InfyTQ / Online Test → Technical Interview → HR Round
What they screen for
CGPA above 6.0, good fundamentals in CS/IT, InfyTQ certification is a strong differentiator.
Resume approach
Standard single-column format. Mention InfyTQ certification prominently if you have it. List core CS subjects as coursework. Projects with clear tech stack.
Avoid
Don't over-list soft skills without evidence. Don't submit without checking the portal's file size and format requirements.
Process
NLTH → Technical Interview → HR
What they screen for
Wipro NLTH score, CGPA above 6.0, articulate communication, teamwork evidence.
Resume approach
1-page clean resume. Include National Level Talent Hunt (NLTH) status if applicable. Emphasize projects that show problem-solving.
Avoid
Avoid vague project descriptions. 'Developed a website' tells the interviewer nothing — describe what it does and what stack you used.
Process
GenC / GenC Next test → Technical Interview → HR
What they screen for
CGPA filter, programming aptitude, cloud or digital skills (for GenC Next track), communication.
Resume approach
Mention the track you're targeting (GenC or GenC Next). GenC Next candidates should highlight cloud, AI/ML, or DevOps skills. Standard 1-page format.
Avoid
Don't apply to GenC Next with only basic programming skills — mismatches show up in the interview.
Process
Online Assessment → Communication Test → HR Interview
What they screen for
Any CGPA (no strict cutoff for some tracks), good communication skills, analytical thinking.
Resume approach
Lead with communication-forward experiences — internships, presentations, clubs. Technical skills still matter but communication is weighted heavily.
Avoid
Don't neglect the communication and leadership sections. Accenture values soft skills alongside technical ability.
Process
Resume shortlist → Coding rounds → System design → Behavioral interviews
What they screen for
Competitive programming profile, strong projects, internships at good companies, CGPA typically 7.5+, DSA depth.
Resume approach
Quality over quantity. 2–3 exceptional projects with clear technical depth. Competitive programming achievements prominently placed. GitHub link essential.
Avoid
Don't include weak or generic projects. Product companies reject resumes with vague bullet points. Every achievement needs specificity.
CGPA is the first filter in most mass recruitment processes. Here's a realistic guide to what your CGPA means for your placement options — and what you can do to compensate if it's lower than you'd like.
8.5+
Excellent
You qualify for all placement tracks. Ensure your projects and competitive programming match the caliber of your academic performance.
7.5 – 8.4
Strong
Qualifies for most product companies and all mass recruiters. Build strong projects and a competitive programming profile to compensate where CGPA isn't your differentiator.
6.5 – 7.4
Acceptable
Qualifies for TCS, Infosys, Wipro, Cognizant, Accenture, and many mid-tier companies. Focus on project quality and certifications. Competitive programming rankings help.
6.0 – 6.4
Minimum
Meets the minimum cutoff for most mass recruiters. Your projects, certifications, and placement test performance will carry more weight than CGPA.
Below 6.0
Limited
Below the cutoff for many mass recruiters. Focus on off-campus applications, startups, and product companies that don't filter strictly on CGPA. Build exceptional projects.
Important note
CGPA cutoffs vary by institution and by the company's tie-up with your college. The figures above are general market standards. Always check your college's placement cell for the exact cutoff for each company visiting your campus.
Each section of your placement resume needs to answer a specific question a recruiter or automated system is asking. Here's what to include in each section and how to optimize it for campus placement.
What to include: Full name, phone, professional email, city, LinkedIn, GitHub (if active). Place in document body — not in header/footer.
Placement tip: Many placement portals have strict file size limits. Keep your contact block minimal — no elaborate header designs.
What to include: 2 sentences. State your degree, target role/domain, and one key strength. Tailor to the company when applying.
Placement tip: For mass recruiters like TCS and Infosys, keep this generic. For product companies, make it specific to their tech stack.
Example
Final-year B.Tech Computer Science student at NIT Trichy seeking a software development role. Proficient in Java and Python with hands-on experience in REST API development and cloud deployment on AWS.
What to include: Degree, institution, graduation year, CGPA/percentage. Also include 10th and 12th percentage — many mass recruiters require it.
Placement tip: Mass recruiters (TCS, Infosys, Wipro) often require 10th and 12th marks. Include them in a clear table-free format. Product companies don't need school marks.
What to include: Grouped by category: Languages, Frameworks, Databases, Tools, Cloud. Be specific.
Placement tip: Mass recruiter portals often auto-parse skills for keyword matching. Ensure you use exact standard terms: 'Python' not 'Python3', 'React.js' not 'ReactJS'.
Example
Languages: Java, Python, C++ | Frontend: React, HTML5, CSS3 | Backend: Node.js, Spring Boot | Database: MySQL, MongoDB | Tools: Git, Docker, AWS EC2
What to include: 2–4 projects with tech stack, your role, and outcome. Include GitHub or live link.
Placement tip: For product company shortlisting, your top project needs to demonstrate real technical depth — not just a CRUD app. Include the scale, the problem, and your specific contribution.
Example
Distributed Task Scheduler · Java, Spring Boot, Redis, PostgreSQL — Built a distributed task scheduler supporting 10,000 concurrent jobs with sub-100ms scheduling latency. Implemented Redis pub/sub for real-time job status updates. Deployed on AWS EC2 with auto-scaling. github.com/user/task-scheduler
What to include: Company, role, duration, and 2–3 bullet points on what you built or contributed.
Placement tip: Even a 4-week internship is valuable for mass recruitment shortlisting. Focus on what you delivered — not just 'gained experience in'.
What to include: Hackathon rankings, LeetCode/CodeChef ratings, open source contributions, scholarships, academic awards.
Placement tip: For product companies, a LeetCode Knight badge or top 10% CodeChef rating is a meaningful shortlisting signal. State the exact rating or ranking — vague 'active on LeetCode' adds nothing.
Example
LeetCode: 1,850+ rating (Knight badge) · 500+ problems solved | CodeChef: 4-star (1,920 rating) | Smart India Hackathon 2025: Grand Finale, Top 25 teams nationally
What to include: AWS, Google, Microsoft, NPTEL, Coursera. Include issuer and year.
Placement tip: For Infosys: InfyTQ certification is specifically valued. For mass recruiters generally: any recognized cloud or platform certification helps.
One of the most impactful things you can do before placement season is maintain two distinct resume versions — one for mass recruiters and one for product/selective companies. The differences are significant enough that a single "universal" resume consistently underperforms in both tracks.
These are the exact types of rewrites that separate shortlisted resumes from rejected ones during placement season.
Project description
❌ Weak version
Developed an e-commerce website using various technologies. Implemented frontend and backend features.
✅ Strong version
Built a full-stack e-commerce platform with React (frontend), Node.js (backend), and MongoDB (database). Implemented JWT authentication, Razorpay payment integration, and inventory management. Handles 500+ product listings with sub-200ms API response time. Deployed on AWS EC2 with NGINX. github.com/user/ecommerce
Skills section
❌ Weak version
Skills: Programming, web development, database management, communication, teamwork, problem-solving, Microsoft Office, Java, Python, HTML, CSS
✅ Strong version
Languages: Java, Python, C++ | Frontend: React, HTML5, CSS3, Tailwind CSS | Backend: Node.js, Express, Spring Boot | Database: MySQL, MongoDB, Redis | Tools: Git, Docker, AWS (EC2, S3), Postman | CS Fundamentals: DSA, OS, DBMS, CN
Internship bullet point
❌ Weak version
Worked on backend development during internship. Helped the team with various tasks and learned new technologies.
✅ Strong version
Developed 3 REST APIs in Python (Django) for the internal reporting dashboard, reducing manual report generation time by 5 hours/week. Wrote unit tests achieving 85% code coverage. Deployed to staging environment using Docker.
Achievement entry
❌ Weak version
Active on competitive programming platforms. Good at solving problems.
✅ Strong version
LeetCode: 1,780+ rating, 480+ problems solved (Knight badge) | HackerRank: 5-star in Problem Solving | Smart India Hackathon 2025 Finalist — Top 60 / 15,000+ registered teams
These are the most common errors seen on placement resumes — errors that result in silent rejections at the shortlisting stage.
Including 10th/12th marks in product company resumes
Fix: School marks are irrelevant for product company applications. Remove them and use that space for project details or competitive programming achievements.
Omitting 10th/12th marks in mass recruiter resumes
Fix: TCS, Infosys, Wipro, and Cognizant explicitly require school marks on the resume. Include the board, year, and percentage for both.
Generic objective statement
Fix: Replace 'Seeking a challenging position...' with a 2-sentence summary that names your degree, target role, and one specific technical strength.
Listing every language ever touched
Fix: Only list skills you can confidently discuss in a technical interview. Skills you can't back up in an interview are worse than not listing them.
Vague project titles with no context
Fix: Rename 'My Project' to the actual application name and add the tech stack in the subtitle. Recruiters need to know what you built in under 3 seconds.
Multi-column Canva or design template
Fix: Many campus placement portals have strict ATS upload requirements. Single-column PDF format avoids parse failures and file compatibility issues.
No GitHub link for technical roles
Fix: GitHub is expected for any technical campus application in 2026. If your profile is empty, build at least 2–3 repositories before placement season.
Listing CGPA inconsistently
Fix: Use the same format throughout: either percentage or CGPA, not both. If converting, use the official conversion formula from your institution.
The students who get the best placement outcomes don't build their resume in the week before the company visits campus. Here's the timeline that produces placement-ready profiles.
Campus placement portals vary widely in their technical requirements. Some portals — like TCS iON, Infosys' placement system, and Amrita's AUMS — have upload parsers that extract candidate data into structured fields. Others display your PDF directly to a recruiter without automated parsing.
Regardless of whether the portal uses ATS parsing, these formatting rules protect you in all scenarios:
Portal parsers and some older enterprise systems can't handle two-column formats. Information from the second column often gets merged or dropped.
PDF preserves your exact formatting across all portal viewers. DOCX can render differently on the university server or recruiter's system.
Many campus portals have file size limits. Embedded fonts and high-res images bloat file size — Resumeora exports are optimized automatically.
Table-based layouts break in most portal parsers. Use plain text with spacing — not HTML or LaTeX tables.
Custom fonts embedded in PDFs sometimes fail to render in portal viewers. Arial, Calibri, and Helvetica are universally safe.
Portal parsers categorize sections by heading labels. 'Work Experience' gets recognized. 'Professional Journey' does not.
ATS-structured templates, guided section prompts, and instant PDF export. Free account available.