India's engineering employability rose to 56.35% in 2026 — but only 30–40% of eligible students convert on-campus offers. This complete campus placement preparation guide gives you the exact week-by-week plan, comparison tables, company-specific strategies, and actionable checklists to be in the placed column.
TCS NextStep →How do you prepare for placements in 2026? Start 3–4 months before your campus placement season. Build a one-page ATS-friendly resume in Week 1, solve 30–40 aptitude questions daily (timed), solve 50 Easy + 100 Medium DSA problems on LeetCode for service companies (add 30 Hard for product companies), practice group discussions twice a week, prepare 8–10 HR interview answers using the STAR method, build 2 resume-worthy projects, and take at least 10–15 mock interviews. Follow the 12-week timeline below, and you will walk into placement season confident and ready. Jump to the week-by-week plan →
India's engineering employability rate in 2026 (up from 51.25% in 2024)
Of eligible students who convert on-campus placement offers
Minimum structured preparation needed for most campus drives
Fresher salary range across service and product companies in 2026
Understanding the three types of campus placements in India helps you allocate preparation time and register on the right platforms. Most students should pursue all three simultaneously — not just on-campus.
| Factor | On-Campus Drives | Off-Campus Drives | Pool Campus Drives |
|---|---|---|---|
| Who conducts | Individual college placement cell | Company directly or via hiring portals | Company + regional placement consortium (multiple colleges) |
| Competition level | Moderate — your batch size | High — open to all colleges | Very High — 500–2000+ students |
| Application mode | Through college placement cell (mandatory registration) | Company portals, LinkedIn, TCS NextStep, InfyTQ, referrals | Through college placement cell (auto-registered if eligible) |
| Best for | Students who want a guaranteed first shot at hiring | Students targeting specific companies or missed campus window | Students in colleges with fewer company tie-ups |
| Preparation focus | Aptitude + company-specific prep (process shared in advance) | Strong resume + LinkedIn + referral network + DSA | High-speed aptitude + DSA (higher cutoffs expected) |
| Timeline | Aug–Jan (peak), some colleges extend to Mar | Year-round, peaks Jul–Dec | Aug–Nov (typically mid-week announcements) |
| Key platforms | College placement portal | TCS NextStep, InfyTQ, LinkedIn, company websites | College placement cell + regional placement bodies |
| Conversion rate | 30–40% of eligible students | 5–15% (higher competition, but unlimited attempts) | 15–25% (higher cutoffs, larger applicant pool) |
Only 30–40% of engineering freshers get placed through campus drives alone. Students who register on TCS NextStep, InfyTQ, Wipro careers portal, and Cognizant hiring platform — all of which accept off-campus applications from any college — dramatically increase their chances. Build a referral network with seniors at target companies. Off-campus hiring has never been more accessible in India.
Compare the top free and paid resources across every placement preparation area so you can pick the right tools for your plan. Use this table as your weekly reference throughout your 90-day preparation.
| Area | Best Free Resources | Best Paid / Premium | Daily Target | Goal |
|---|---|---|---|---|
| Quantitative Aptitude | IndiaBIX, RS Aggarwal (free PDF) | PrepInsta, Testbook | 30–40 questions/day, timed | 90%+ accuracy |
| Logical Reasoning | IndiaBIX Reasoning, RS Aggarwal | PrepInsta company-specific packs | 20–25 questions/day | 60 sec/question |
| Verbal Ability | IndiaBIX English, daily newspaper reading, Word Power Made Easy | Grammar workbooks | 1 RC passage + 10 vocab/day | 85%+ accuracy |
| DSA / Coding | LeetCode, HackerRank, GeeksForGeeks | InterviewBit Premium, Striver's A2Z sheet | 3–5 Easy or 5–7 Medium/day | 50E + 100M problems |
| CS Fundamentals | GeeksForGeeks topic-wise, GFG Last Minute Notes | Neso Academy (YouTube), NPTEL | 1 hour/day on OOP, DBMS, OS, CN | 80% interview Qs |
| Resume Building | TaskVeda Resume Guide | Canva premium templates | One-time: complete in Week 1 | ATS-ready, 1 page |
| Mock Interviews | Pramp (free peer mocks) | Interviewing.io, Mock platforms | 2–3 mocks/week | 15+ mocks done |
| Group Discussion | Practice with batchmates, record yourself, current affairs reading | PrepInsta GD practice sets | 2 GDs/week from September | 10+ GDs practiced |
| HR Interview | TaskVeda HR guide, record yourself answering aloud daily | Mock HR platforms | 30 min HR practice/day | 25 HR Qs mastered |
| Company-Specific Prep | IndiaBIX, GFG company sections | PrepInsta company-specific tests | 1 company-specific mock/week | 10 companies researched |
| Projects | GitHub, Vercel/Netlify (free deploy) | Udemy project courses | 2–3 strong projects total | Deployed + README |
| AI Skills | TaskVeda AI Skills Guide, ChatGPT, Google AI Studio | DeepLearning.AI courses | 30 min/day learning AI tools | 3 AI tools mastered |
Service companies like TCS, Infosys, Wipro, and Cognizant filter 60–70% of candidates in the aptitude round alone. A strong coder who fails aptitude never gets to show their coding skills. Aptitude is not about intelligence — it is about familiarity with question types and speed of solving them. Both come purely from practice.
1. Number System — HCF, LCM, factors, remainders, divisibility rules for 2–13
2. Percentages — successive changes, increase/decrease, multiplier method
3. Averages — weighted average, age problems
4. Ratio & Proportion — mixtures, partnerships
5. Time & Work — pipes, cisterns, efficiency, unit work method
6. Time, Speed & Distance — trains, boats, races, relative speed
7. Profit & Loss — discounts, marked price
8. Simple & Compound Interest — installments
9. Permutation & Combination — arrangements
10. Probability — cards, dice, coins
Reasoning:
• Series — number, letter, mixed patterns
• Coding-Decoding — letter shifting, word coding
• Blood Relations — draw the family tree
• Direction Sense — distance and direction
• Syllogisms — Venn diagram method
• Seating Arrangements — linear, circular
• Puzzles — floor-based, scheduling
• Data Interpretation — bar, pie, line, table graphs
Verbal:
• Reading Comprehension — read questions before the passage
• Para Jumbles — find the sentence that cannot be first
• Error Spotting — subject-verb agreement, tenses
• Vocabulary — learn 10 new words daily
Week 1–2: Number System, Percentages, Averages — solve 150+ problems. Week 3–4: Ratio, Time & Work, Time Speed Distance — 150+ problems. Week 5–6: Profit & Loss, Interest, P&C, Probability — 150+ problems. Week 7–8: Logical Reasoning all types — 200+ problems. Week 9–10: Data Interpretation — 100+ problems. Week 11–12: Full-length mocks, weak area revision — 20+ timed mocks. Every Sunday, take one full company mock test under real conditions. Track three numbers: accuracy %, average time per question, and weak topics.
Students who combine this aptitude plan with a virtual internship with certificate from TaskVeda gain project experience that most of their batch doesn't have — and interviewers remember candidates who go beyond the textbook.
TCS NextStep →DSA is the single most important skill for placement at any tech company. For service companies, solve Easy to Medium problems. For product companies, you need consistent Medium to Hard performance. Solving 500 random LeetCode problems does not build pattern recognition — solving 50 pattern-focused problems builds the muscle needed for timed exams.
Arrays, Strings, Basic Sorting, Searching, Two Pointer. Solve 50 Easy + 30 Medium problems. Learn time complexity analysis. Set up GitHub and push daily.
Linked Lists, Stacks, Queues, Binary Search, Sliding Window, Hashing, Trees. Solve 50+ Medium problems across these patterns. Start one project.
Graphs (BFS/DFS), Dynamic Programming, Greedy, Backtracking. Solve 30+ Medium + 20 Hard problems. Finalize 2–3 deployed projects with READMEs.
| Topic | Priority | Problems to Solve | Companies That Test This |
|---|---|---|---|
| Arrays | Must-Do | 20–25 Easy + 15 Medium | TCS, Infosys, Wipro, Amazon, Cognizant |
| Strings | Must-Do | 15 Easy + 10 Medium | TCS, Infosys, Wipro, Cognizant, Capgemini |
| Linked Lists | High | 10 Easy + 8 Medium | Infosys SP, Amazon, Microsoft |
| Binary Search | High | 10 Medium | Wipro Turbo, Cognizant GenC Next |
| Sliding Window | High | 8 Medium | TCS Digital, Amazon, HCL Polaris |
| Trees | Medium | 15 problems (traversals, BST, LCA) | Amazon, Microsoft, Infosys SP |
| Graphs (BFS/DFS) | Medium-High | 10–15 problems | Amazon, Microsoft, Google |
| Dynamic Programming | Critical for Product | 20–30 problems (Knapsack, LCS, Coin Change) | Amazon, Microsoft, Google, HCL Polaris |
| Hashing | High | 10–12 problems (Two Sum, Group Anagrams) | All companies — most frequently tested pattern |
OOP: 4 pillars, classes vs interfaces, constructor types, method overloading vs overriding — tested at every service company. DBMS: SQL (SELECT, JOINs, GROUP BY), normalization (1NF to BCNF), ACID, transactions — write SQL on paper, not just on screen. OS: Process vs thread, deadlock, scheduling algorithms (FCFS, SJF, Round Robin), memory management (paging, segmentation). Computer Networks: OSI model (all 7 layers), TCP vs UDP, HTTP vs HTTPS, DNS resolution, IP addressing.
Want to go deeper? Read our DSA Interview Questions guide and System Design Interview for Freshers for product company prep.
TCS NextStep →Group discussions are one of the most underprepared stages of campus placements. Students spend months on aptitude and coding and then walk into a GD having never practised one. A GD does not test how much you know — it tests whether you can listen actively, add value to a conversation, and disagree respectfully.
1. Active Listening: Acknowledge what others have said before responding. Build on their points rather than waiting for your turn to speak.
2. Specific Contributions: Two or three strong, specific points beat ten vague ones. Enter early — within the first 60 seconds — with something that adds to the conversation.
3. Respectful Disagreement: "I see your point, but I think..." is stronger than "No, you are wrong." Evaluators note how you handle disagreement.
4. Group facilitation: If the discussion stalls, ask a question or summarise the group's progress. This shows leadership without dominating.
September onwards: Practice GDs with friends twice a week. Pick any topic — current affairs, technology trends, abstract topics. Give yourself 10 minutes per discussion.
Topics to prepare: AI replacing jobs, remote work vs office, social media impact, climate change policy, online education, startup vs MNC culture, India's tech growth.
Self-assessment: Record yourself if possible. Listen back. Notice whether you are contributing meaningfully or just filling air time. Count how many times you spoke — quality over quantity.
The tip that works: Read one English article daily. GD topics frequently draw on recent events, technology trends, and social issues. Being aware gives you material even on unfamiliar topics.
Do not: Speak without a clear point, interrupt others, raise your voice, repeat what someone else said, stay completely silent, or look at the evaluator instead of the group. Do: Enter early with a specific point, listen actively, build on others' ideas, help the group move toward a conclusion, and maintain eye contact with the group. The students who impress evaluators are rarely the ones who speak the most — they are the ones who make the discussion more productive.
Technical skills get you through the door. Soft skills get you the offer. Companies test communication, confidence, teamwork, and cultural fit in every HR and group discussion round.
Practice explaining technical concepts clearly and concisely. Record yourself answering interview questions and review the recording. Read one English article daily to build vocabulary and comprehension speed.
Maintain eye contact during interviews. Sit upright, use hand gestures naturally, and speak at a measured pace. Practice mock interviews in front of a mirror or record video to self-assess.
Group discussions test your ability to listen, build on others' points, and contribute meaningfully without dominating. Practice GDs with friends twice a week from September onwards.
Interviewers value candidates who can break down ambiguous problems into manageable parts. Practice thinking aloud while solving DSA problems — explain your approach before writing code.
Be ready to discuss how you learned a new technology quickly or adapted to a challenging project. Companies want freshers who can learn fast, not just those who already know everything.
Dress formally, arrive 30 minutes early, carry 5–10 resume copies, and always thank the interviewer. Small details create a strong first impression that persists through the evaluation.
Strengthen your communication further with our Communication Skills for Students guide and LinkedIn Profile Optimization for Students (2026).
TCS NextStep →The HR round is not a formality. Students get rejected there after strong technical rounds every single year because they gave generic answers, spoke about salary too early, or had not thought through basic questions about themselves. The HR interview is structured, predictable, and entirely preparable.
1. Tell me about yourself: 60–90 seconds. Name + Degree + 2 strongest skills + 1 significant project + what you are looking for. Not your entire life history.
2. Why this company?: Research the company before the interview. Name one specific thing — a technology, a product, a growth initiative. Generic answers fail this question.
3. Strengths: Name 2 specific strengths with a brief example each. "Problem-solving" is too generic. "I break complex problems into sub-problems — in my project I decomposed the database design into three stages" is specific.
4. Weaknesses: Name a real weakness not critical to the role, and follow with what you are doing to address it.
5. Why should we hire you?: Three specific differentiators that align with what this company is hiring for. Your 60-second sales pitch.
6. Where do you see yourself in 5 years?: Show ambition that aligns with the company's growth. "I want to become a senior full-stack engineer who has worked on products and possibly led a small team."
7. Are you willing to relocate?: Always say yes if you genuinely are. Ambiguous answers create doubt that the next candidate does not have.
8. Expected salary?: "I am open to the standard fresher package — I am focused on the learning opportunity." Never quote lower than market standard.
9. Do you have questions for us?: Always have 2–3 genuine questions. "What does a typical first month look like for a fresher?" Never say "No."
10. STAR method for behavioral questions: Situation → Task → Action → Result. Use this for every "Tell me about a time when..." question. Structure gives completeness to answers that otherwise tend to be vague.
Read our Interview Preparation for Freshers guide for deeper technical and HR interview preparation.
TCS NextStep →Reading solutions and doing mocks are fundamentally different activities. Mocks expose your communication gaps, time pressure failures, and gaps in understanding that solo practice never reveals. Students who do mock interviews consistently outperform those who only solve problems.
Week 1–2: Practice explaining your approach out loud while solving problems. Do not code silently. Interviewers grade your thinking process, not just the solution.
Week 3–4: Solve problems on paper or whiteboard without IDE autocomplete. Write code by hand to understand it at a deeper level.
Week 5–6: Full mock interviews with peers — 2 coding problems + project discussion in 60 minutes.
Week 7–8: Company-specific mocks on Pramp or Interviewing.io. Record and review.
Prepare 8–10 core answers: Tell me about yourself, Why this company?, Strengths, Weaknesses, Why should we hire you?, Where do you see yourself in 5 years?, Are you willing to relocate?, Do you have questions for us?
Practice daily: Answer aloud for 30 minutes. Record yourself. Review for filler words, pace, and clarity. Use the STAR method for behavioral questions. The difference between preparation that stays in your head and preparation that sounds natural in the room is practice aloud — not reading silently.
Target: 15+ mock interviews before your first real drive. Use Pramp.com (free peer-to-peer mocks), practice with batchmates, and record yourself answering HR questions. After every mock, note what went well and what needs improvement. The compounding effect of consistent mock practice is the single most reliable predictor of interview performance.
For deeper interview preparation, read our Interview Preparation for Freshers guide and System Design Interview for Freshers.
TCS NextStep →Most colleges start campus placements between August and November. Work backwards 12 weeks from your first expected drive date. This timeline covers both service company and product company preparation in parallel, prioritising service company preparation since those drives happen first.
| Week | Focus Area | Daily Target | Milestone |
|---|---|---|---|
| Week 1 | Resume + LinkedIn + Aptitude Foundation | 30 aptitude Qs + 3 Easy DSA problems + complete resume | ATS-ready resume completed. LinkedIn profile optimized. GitHub set up. |
| Week 2 | Aptitude Foundation + DSA Arrays | 30 aptitude Qs (timed) + 3 Easy DSA problems | Number System, Percentages, Averages mastered. 20 Array problems done. |
| Week 3 | Aptitude Speed + DSA Strings & Sorting | 30 aptitude Qs + 5 Easy/Medium DSA problems | Aptitude accuracy 70%+. Strings section started. |
| Week 4 | Aptitude Speed + DSA Binary Search | 30 aptitude Qs + 5 Medium DSA problems | Aptitude accuracy 80%+. Arrays & Strings complete. 50 Easy problems done. |
| Month 2 — Week 5 | DSA Linked Lists + CS Fundamentals (OOP) | 5 Medium DSA + 1 hour CS subjects | Linked Lists done. OOP concepts revised. |
| Month 2 — Week 6 | DSA Trees + CS Fundamentals (DBMS) | 5 Medium DSA + 1 hour CS subjects | Trees, Hashing done. DBMS revision complete. Start first project. |
| Month 2 — Week 7 | DSA Graphs + Project Build | 5 Medium DSA + project work | BFS/DFS basics covered. First project deployed on GitHub. |
| Month 2 — Week 8 | DSA DP Basics + Project #2 + Company Mocks | 5 Medium DSA + 1 company mock/week | DP fundamentals done. 2 projects deployed. First company-specific mock taken. |
| Month 3 — Week 9 | Mock Interviews + HR Prep + GD Practice | 3 mocks/week + 30 min HR practice + GD practice | 5+ mocks done. HR answers rehearsed. GDs practised twice. |
| Month 3 — Week 10 | Company Research + DSA Hard Problems | 3 mocks/week + 5 Medium/Hard DSA + 1 company mock | 10+ mocks done. Top 10 companies researched. DSA Hard problems attempted. |
| Month 3 — Week 11 | Weak Area Revision + Peak Mocks | 2–3 problems/day + 2 mocks/week | Weak aptitude topics fixed. 15+ mocks total. Interview-ready. |
| Season (Drive Week) | Final Revision + Execute | Light revision + 1 mock + company-specific prep | Formal clothes ready. Resume copies printed. Confident and prepared. |
90 days left: Focus on aptitude (3 weeks), DSA Easy/Medium (4 weeks), projects + resume (2 weeks), and mocks + HR (3 weeks). 60 days left: Aptitude + DSA (5 weeks), projects (1 week), mocks + HR (2 weeks). 30 days left: Aptitude daily, 100 Easy DSA problems, complete resume, 5 mocks, target service companies only. Starting early is always better, but even a compressed plan works with consistent daily effort. The compounding effect of 90 days of structured preparation beats 10-hour weekend binges.
Your resume is shortlisted before any human reads it — an ATS (Applicant Tracking System) scans it first. A weak resume stops you before the process even starts. Two things need to be in perfect shape before your first placement drive.
✅ Single-column, clean format — no tables, no graphics, no columns
✅ One page if you have under 2 years of experience
✅ Lead with skills, then projects, then education
✅ Use action verbs: Built, Designed, Reduced, Improved
✅ Quantify impact: "Reduced load time by 40%"
✅ Include GitHub links for all projects
✅ No spelling mistakes — use Grammarly
✅ Save as PDF with your name in filename
❌ No photo, no DOB, no religion, no hobbies
✅ Professional headline: "B.Tech CSE Student | Python & DSA | Aspiring SDE"
✅ About section: 5 sentences on skills, projects, and goals
✅ Add all projects with descriptions and GitHub links
✅ 15+ relevant skills with LinkedIn assessments
✅ Open to Work enabled with 5+ job titles
✅ Post about projects weekly to build visibility
✅ Connect with seniors at target companies
Read our Resume Building for Students and LinkedIn Profile Optimization guides for detailed templates and tips.
TCS NextStep →Service companies (TCS, Infosys, Wipro, Cognizant) filter primarily on aptitude. Product companies (Amazon, Microsoft, Google) filter on DSA and coding. You must know which type you're targeting before dividing your prep time. Most students should target 2–3 service companies as their primary goal while preparing for 1 dream company as a stretch goal.
| Factor | Service Companies | Product Companies |
|---|---|---|
| Primary Filter | Aptitude test — eliminates 60–70% of candidates | DSA coding — 1 to 3 hard problems in timed assessment |
| Fresher Package | ₹3.36 LPA to ₹7.5 LPA | ₹10 LPA to ₹25 LPA |
| DSA Depth Required | Easy to Medium — arrays, strings, sorting | Medium to Hard — graphs, DP, advanced algorithms |
| Preparation Time | 6–8 weeks focused preparation | 3–6 months intensive DSA prep |
| Interview Rounds | 2–3 rounds (online test + tech + HR) | 4–6 rounds (coding + multiple tech + HR/Bar Raiser) |
| Resume Importance | Less critical — many do not shortlist by resume | Critical — screened before coding round |
| Key Tip | Nail aptitude first. A coder who fails aptitude never reaches the coding round. | 150+ Medium DSA problems minimum. Amazon Leadership Principles for HR round. |
Target 2–3 service companies as your primary goal — these give you a job and financial stability. Simultaneously prepare for 1 dream company as a stretch goal. Service company prep (aptitude + basic coding) takes 6–8 weeks. Dream company prep (advanced DSA) requires 4–8 additional weeks. Run both in parallel, prioritising service company preparation since those drives happen first. Weeks 1–4 handle service company first rounds. Weeks 5–8 handle premium tracks and product company first rounds. Weeks 9–12 are primarily for product company preparation.
For company-specific guides, read our How to Get a Job After BTech and How to Become Job Ready Before Graduation.
TCS NextStep →These are the errors that separate students who get placed from those who wait until February still hoping. Every single one is avoidable.
Aptitude accuracy cannot be built in days — it compounds over weeks. DSA pattern recognition requires consistent practice, not cramming. Start 90 days before your first expected drive.
Service companies filter 60–70% of candidates in the aptitude round. A strong coder who fails aptitude never reaches the coding round. Spend equal time on aptitude and coding for the first 4 weeks.
Solving 500 random LeetCode problems does not build pattern recognition. Solving 50 pattern-focused problems builds the muscle needed for timed exams. Follow a topic-wise sequence.
Placement tests have strict time limits. Speed and accuracy under pressure cannot be developed through untimed practice. Take one full timed mock every Sunday starting from Week 1.
Interviewers probe every line of your resume. A project you barely touched becomes your weakest point when probed. List only projects you built yourself and can explain in detail.
Generic answers to "Why do you want to join us?" immediately signal you applied without thinking. Spend 30 minutes on the company's website and LinkedIn before every HR interview.
Companies like TCS, Wipro, and HCL deploy freshers across multiple cities. Ambiguous answers create doubt that the next candidate does not have. Say clearly: "Yes, I am open to relocation."
The difference between preparation that stays in your head and preparation that sounds natural in the room is practice aloud. Record yourself answering 5 HR questions and 1 technical explanation daily.
Campus drives are limited to your college's company ties. Only 30–40% of freshers get placed through campus. Register on TCS NextStep, InfyTQ, Wipro portal, and LinkedIn job alerts.
Recruiters check LinkedIn and GitHub before and after interviews. A sparse LinkedIn and missing GitHub URL signals a candidate who is not genuinely engaged. Complete both before your first drive.
Preparation is done. Now execute with calm confidence. Follow this checklist on the day of your campus drive.
Prepare 5–10 resume copies, ID proofs, photos. Iron your formal clothes. Set multiple alarms. Sleep early (minimum 6 hours). Quick revision of key formulas only — do not learn anything new.
Wake up early, have a healthy breakfast. Reach the venue 30 minutes early. Stay calm, breathe deeply. Quick revision of aptitude shortcuts. Stay hydrated. Keep your intro under 60 seconds.
Listen carefully before answering. Think for 3–5 seconds before responding. Explain your thought process aloud during coding. Be honest if you don't know something. Always ask the interviewer one question back.
Answers to the most common questions engineering students ask about campus placement preparation in India.
Ideally start 3–4 months before your campus placement season begins. A 90-day structured plan covering aptitude, DSA, resume building, projects, and mock interviews is sufficient for most students. If you are in your pre-final year, starting 8–12 months early gives you the strongest position. Students who start early consistently outperform those who start late — not because they are smarter, but because they have more time to build genuine skills rather than cramming.
Focus on quantitative aptitude, logical reasoning, and verbal ability daily. Solve 30–40 aptitude questions every day using platforms like IndiaBIX and resources like RS Aggarwal. Take at least one full-length mock test every weekend under timed conditions. Track accuracy and speed each week. The gap between 65% accuracy and 85% accuracy is often the gap between placed and not placed.
For service companies like TCS, Infosys, and Wipro, solving 50 Easy and 100 Medium LeetCode problems across arrays, strings, and core patterns is sufficient. For product companies like Amazon and Microsoft, aim for 150 Medium and 30 Hard problems covering DP, graphs, and advanced algorithms. Quality and pattern understanding matter more than raw count. Solving 500 random problems does not build pattern recognition — solving 50 pattern-focused problems does.
Most service companies require a minimum of 60% or 6.0 CGPA with no active backlogs. Product companies like Amazon and Microsoft do not publish strict CGPA cutoffs but typically expect 7.0 or above. Beyond the cutoff, your skills, projects, and interview performance matter significantly more than your CGPA. A student with 6.2 CGPA and three strong GitHub projects regularly gets shortlisted over a student with 7.8 CGPA and no practical work.
Yes. Many students crack placements with 3–6 months of focused preparation. Start with aptitude and basic DSA for service companies, build 2 strong projects, and take at least 10 mock interviews. Consistency of 3–4 hours daily for 6 months is more effective than cramming 10 hours a day for one month. The compounding effect of daily practice beats weekend binges.
Python is recommended for service company coding rounds because its shorter syntax allows faster implementation in timed assessments. Java is better for product company interviews where OOP depth is tested. C++ works well for competitive programmers comfortable with STL. Pick one language and stick with it throughout your preparation — switching languages mid-preparation is one of the most common avoidable mistakes.
Prepare answers for the most common HR questions: Tell me about yourself (60–90 seconds), Why this company? (research their products), Strengths and weaknesses (be specific with examples), and Why should we hire you? Use the STAR method for behavioral questions. Practice answering aloud daily so responses sound natural, not rehearsed. Record yourself and review for filler words, pace, and clarity.
Service companies like TCS, Infosys, and Wipro filter primarily on aptitude in the first round. Product companies like Amazon and Google filter on DSA and coding ability. Service company preparation takes 6–8 weeks focused on aptitude plus basic coding. Product company preparation requires 3–6 months of intensive DSA, system design awareness, and project depth.
Practice GDs with friends twice a week from September onwards. Pick a topic and discuss for 10 minutes. Enter early — within the first 60 seconds — with a clear, specific point. Acknowledge what others have said before responding. Do not dominate or stay silent. Read current affairs daily for material. Record yourself to identify filler words and improve. GDs test listening, contribution, and respectful disagreement — not volume.
Starting too late (less than 30 days before the drive), skipping aptitude in favour of only coding, solving DSA problems randomly without a pattern-based approach, not taking full mock tests under timed conditions, listing projects on resume that you cannot explain in interviews, not researching the company before HR rounds, and applying only through campus while missing off-campus opportunities.
Yes. Only 30–40% of engineering freshers get placed through campus drives. Register on TCS NextStep, InfyTQ, Wipro's careers portal, and Cognizant's hiring platform — all accept off-campus applications from any college. Use LinkedIn job alerts, attend company-organised mega drives, and build a referral network with seniors at target companies. Off-campus hiring has never been more accessible.
The typical campus placement process in India follows these stages: (1) Company registers with the college training and placement cell, (2) Pre-placement talk where the company presents the role and package, (3) Online aptitude or coding test, (4) Group discussion or technical screening, (5) Technical interview (1–2 rounds), (6) HR interview, (7) Offer letter. The entire process from registration to offer usually takes 2–4 weeks per company. Peak placement season runs from August to January for most engineering colleges.
Pool campus placements are drives where multiple colleges in a region participate together, increasing competition significantly. To prepare: (1) Register through your college placement cell — pool drives are announced 1–2 weeks in advance, (2) Focus on aptitude since pool drives use standardized online tests with higher cutoffs, (3) Practice DSA problems on LeetCode daily — pool drives often include coding rounds, (4) Prepare a strong resume since more candidates means stricter screening, (5) Research the conducting company thoroughly. Pool drives attract 500–2000+ students, so your preparation must be sharper than on-campus drives.
AI skills have become a differentiator in 2026 placements. Companies increasingly look for freshers who can use AI tools like ChatGPT, GitHub Copilot, and Google AI Studio in their workflow. Having 2–3 AI-powered projects on your resume — an AI chatbot, a content generator, or a data analysis tool — sets you apart. Learn prompt engineering basics, integrate AI APIs into one project, and mention AI tool proficiency in your resume skills section. Read our AI Skills for Freshers guide for specific tools and project ideas.
Join 3,500+ students who are building real-world skills, projects, and confidence through TaskVeda's live cohorts. Free to apply — no hidden fees.
Apply Free →