30-Day Placement Preparation Plan: Week-by-Week Guide for Engineering Students

You just realized placements are in 30 days. Maybe your college sent that email last week. Maybe your friend just got shortlisted and you felt a jolt of panic. Maybe you scrolled through LinkedIn, saw someone celebrating an offer, and thought, "I have done nothing."

Don't panic. 30 days is enough.

Not enough to become a coding wizard or rewrite your entire college career. But absolutely enough to go from "completely unprepared" to "competitive enough to get shortlisted and clear interviews." Thousands of students have done it. You can too.

Here is the thing most people get wrong: they think preparation means studying 18 hours a day for a month. It doesn't. It means doing the right things in the right order. A focused 30-day plan beats six months of aimless grinding.

This guide gives you an exact day-by-day, week-by-week breakdown. Every task is specific. Every resource is free. No fluff, no motivation speeches, just the plan.

Step 0: Know Your Starting Point (Day 0)#

Before you start anything, you need to honestly assess where you stand. Most students skip this and waste their first week studying topics they already know while ignoring critical gaps.

Take 10 minutes right now and answer these questions:

1. Can you write a basic sorting algorithm (bubble sort, selection sort) from scratch without Googling?
2. Do you have a resume? Is it updated?
3. Have you solved at least 50 coding problems on any platform (LeetCode, HackerRank, GeeksforGeeks)?
4. Can you explain your college projects clearly in 2 minutes?
5. Have you ever done a mock interview (even with a friend)?
6. Do you know which companies are visiting your campus and what their hiring process looks like?

If you answered "no" to 4 or more of these, you are starting from scratch. That is perfectly fine. This plan is built for you.

If you answered "yes" to most, you can move faster through Week 1 and spend more time on Weeks 3 and 4.

Your first action: Take the JobRise Employability Score quiz to get a detailed breakdown of your strengths and gaps. It takes 5 minutes and tells you exactly what to prioritize. More on what to do with your score at the end of this guide.

---

Week 1 (Days 1 to 7): Build the Foundation#

Week 1 is about getting the basics right. You are laying the groundwork that everything else builds on. No shortcuts here.

Day 1: Research and Plan

Spend this entire day on research. Do not write a single line of code.

Morning (2 hours):

• Find out exactly which companies are coming to your campus. Ask your placement cell, seniors, or TPO office.
• For each company, note down: package offered, number of rounds, what they test (coding, aptitude, HR, GD).
• Categorize companies into three buckets: Dream (high package, tough process), Target (realistic, decent package), and Safety (mass recruiters, easier process).

Afternoon (2 hours):

• Go to GeeksforGeeks Interview Experiences and read 5 to 10 recent interview experiences for your top 3 target companies.
• Note the common patterns. What topics come up repeatedly? What kind of projects do they ask about?

Evening (2 hours):

• Create accounts on LeetCode, GeeksforGeeks, and HackerRank if you haven't already.
• Set up your coding environment. Pick one language and stick with it. Java or C++ for service companies, Python or Java for product companies.
• Make a simple spreadsheet or Notion page to track your daily progress.

Days 2 to 4: DSA Basics (Arrays, Strings, Sorting, Searching)

These three days are purely about coding fundamentals. If your target companies are service-based (TCS, Infosys, Wipro, Cognizant, Accenture), focus on easy and medium problems. If targeting product companies, push toward medium difficulty.

Topics to cover:

• Arrays: traversal, insertion, deletion, two-pointer technique, sliding window
• Strings: reversal, palindrome check, anagram detection, substring problems
• Sorting: bubble sort, selection sort, merge sort (understand the logic, not just the code)
• Searching: linear search, binary search (this one is critical, comes up everywhere)

Problems to solve each day (6 to 8 problems):

Day 2 (Arrays):

• Two Sum (LeetCode #1)
• Best Time to Buy and Sell Stock (LeetCode #121)
• Maximum Subarray / Kadane's Algorithm (LeetCode #53)
• Move Zeroes (LeetCode #283)
• Contains Duplicate (LeetCode #217)
• Rotate Array (LeetCode #189)

Day 3 (Strings + Sorting):

• Valid Anagram (LeetCode #242)
• Reverse String (LeetCode #344)
• First Unique Character in a String (LeetCode #387)
• Longest Common Prefix (LeetCode #14)
• Practice implementing merge sort and quick sort from scratch

Day 4 (Searching + Mixed):

• Binary Search (LeetCode #704)
• Search Insert Position (LeetCode #35)
• Find Minimum in Rotated Sorted Array (LeetCode #153)
• Two Sum II (LeetCode #167, uses binary search/two-pointer)
• Plus 5 to 6 easy problems from GeeksforGeeks Must Do Questions

Free resources for DSA basics:

• Striver's A2Z DSA Sheet on Take U Forward, the single best free DSA resource for Indian placements
• Striver's YouTube Channel, watch the array and string playlists
• NeetCode, excellent for visual explanations of problem patterns
• Apna College YouTube, Hindi explanations of DSA concepts

Day 5: Resume Writing

Stop coding for one day. Your resume needs full attention because it is the first thing that decides whether you even get a chance to show your coding skills.

Morning (3 hours): Write your resume from scratch.

Use a clean, single-column format. No fancy Canva templates, no photos, no colors. ATS software (used by 75% of companies) cannot read complex designs.

Resume sections in order:

1. Name and Contact at the top. Full name, phone, email, LinkedIn URL, GitHub URL (if you have projects).
2. Education. College name, degree, branch, CGPA/percentage, graduation year.
3. Technical Skills. List programming languages, frameworks, tools, and databases you actually know. Do not list things you cannot discuss in an interview.
4. Projects (2 to 3). This is where most freshers make or break their resume. For each project, write 3 to 4 bullet points using this format: "Built [what] using [technologies] that [result/impact]." Use numbers wherever possible.
5. Internships/Experience (if any).
6. Certifications (only relevant ones).
7. Achievements (hackathons, competitive coding ranks, paper publications).

Afternoon (2 hours): Optimize for ATS.

• Use standard section headings: "Education," "Skills," "Projects," "Experience." Not creative alternatives like "What I Know" or "My Journey."
• Include exact keywords from job descriptions of your target companies.
• Save as PDF (not Word).
• Keep it to one page. Absolutely one page for freshers.

Check your resume's ATS score for free on JobRise. Upload your PDF and see exactly what is missing. The first scan is free.

Helpful resources:

• Resume for Freshers with No Experience, our detailed guide
• ATS Resume Format Guide, understand what ATS software looks for
• Harvard Resume Template, simple and clean format that works
• Jake's Resume Overleaf Template, a popular LaTeX template used by thousands of placed students

Days 6 to 7: Stack, Queue, Linked List, and Basic Math

Back to coding. These data structures appear in almost every service company coding round and many product company interviews.

Topics:

• Stack: push, pop, peek, applications (balanced parentheses, next greater element)
• Queue: enqueue, dequeue, circular queue basics
• Linked List: traversal, reversal, detect cycle, merge two sorted lists
• Basic Math: GCD/LCM, prime check, factorial, modular arithmetic

Problems to solve (8 to 10 per day):

Day 6:

• Valid Parentheses (LeetCode #20)
• Min Stack (LeetCode #155)
• Reverse Linked List (LeetCode #206)
• Merge Two Sorted Lists (LeetCode #21)
• Linked List Cycle (LeetCode #141)
• Middle of the Linked List (LeetCode #876)

Day 7:

• Implement Queue using Stacks (LeetCode #232)
• Remove Nth Node From End of List (LeetCode #19)
• Palindrome Linked List (LeetCode #234)
• 5 to 6 basic math problems from GeeksforGeeks (GCD, prime sieve, power function)

End of Week 1 checkpoint: You should have solved 40 to 50 problems, have a ready resume, and know your target companies. If you are behind, adjust the schedule but do not skip the resume.

---

Week 2 (Days 8 to 14): Build and Deepen#

Week 2 is about going deeper on DSA, starting a project (if you need one), and polishing your resume with ATS optimization.

Days 8 to 10: Trees, Graphs, and Recursion

If you are targeting service companies only, you can go lighter on graphs. But trees and recursion are universal.

Topics:

• Recursion: factorial, Fibonacci, power set, backtracking basics
• Binary Tree: traversals (inorder, preorder, postorder), height, diameter
• Binary Search Tree (BST): search, insert, validate
• Graphs (basics only): BFS, DFS, connected components

Problems:

Day 8 (Recursion + Trees):

• Climbing Stairs (LeetCode #70)
• Subsets (LeetCode #78)
• Maximum Depth of Binary Tree (LeetCode #104)
• Invert Binary Tree (LeetCode #226)
• Same Tree (LeetCode #100)

Day 9 (BST + More Trees):

• Validate BST (LeetCode #98)
• Lowest Common Ancestor of BST (LeetCode #235)
• Level Order Traversal (LeetCode #102)
• Symmetric Tree (LeetCode #101)
• Path Sum (LeetCode #112)

Day 10 (Graphs):

• Number of Islands (LeetCode #200)
• Flood Fill (LeetCode #733)
• Clone Graph (LeetCode #133)
• Practice BFS and DFS on GeeksforGeeks graph problems

Resources:

• Striver's Tree Series, the best free tree playlist
• WilliamFiset Graph Theory, clear and concise graph explanations
• Abdul Bari's Algorithm Playlist, great for understanding recursion intuitively

Days 11 to 12: Build or Polish a Project

If you already have 2 to 3 decent projects on your resume, skip to Day 13. If you don't, these two days are for building one quick, impressive project.

The ideal 2-day project has these qualities:

• Solves a real problem (not just a tutorial copy)
• Uses at least 2 technologies from your target company's tech stack
• Has a working demo (deployed or screen-recorded)
• Has clean code on GitHub with a proper README

Project ideas you can build in 2 days:

1. Personal Expense Tracker (React/HTML + LocalStorage or Firebase). Tracks daily expenses, shows category-wise breakdown, generates monthly summary.
2. URL Shortener (Node.js + MongoDB or Python Flask + SQLite). Takes a long URL, gives a short one, tracks click count.
3. Weather Dashboard (React + OpenWeatherMap API). Shows weather for any city, 5-day forecast, clean UI.
4. Student Marks Analyzer (Python). Reads a CSV of marks, calculates averages, identifies toppers, generates a PDF report.
5. Quiz Application (Java or Python). Multiple-choice quiz with score tracking, timer, and question bank from a JSON file.

How to make any project resume-worthy:

• Deploy it. Use Vercel (free) for React apps, Render (free) for backends, GitHub Pages for static sites.
• Push code to GitHub with a clear README: what it does, tech stack, how to run it, screenshots.
• Add 1 to 2 "advanced" features. For example, if it's an expense tracker, add chart visualization using Chart.js. This gives you something to talk about in interviews.

GitHub profile matters. If your GitHub is empty, interviewers notice. Even if your projects are simple, having them on GitHub with clean READMEs shows initiative. Read our guide on GitHub Profile for Freshers for quick tips.

Days 13 to 14: Dynamic Programming Basics + Resume ATS Optimization

Day 13: Dynamic Programming (DP)

DP scares most students, but you only need to know 10 to 15 classic problems for placements. Service companies rarely ask DP. Product companies ask it frequently.

Must-know DP problems:

• Fibonacci (memoization vs tabulation, understand both approaches)
• Climbing Stairs (LeetCode #70, if not done already)
• House Robber (LeetCode #198)
• Coin Change (LeetCode #322)
• Longest Common Subsequence (LeetCode #1143)
• 0/1 Knapsack (GeeksforGeeks, the classic)
• Longest Increasing Subsequence (LeetCode #300)

The trick with DP: Don't try to "see" the solution. Follow this framework every time:

1. Define the state. What changes from subproblem to subproblem?
2. Define the recurrence relation. How does the current state depend on previous states?
3. Define the base case. What is the smallest subproblem you can solve directly?
4. Decide top-down (recursion + memoization) or bottom-up (tabulation).

Watch: Striver's DP Series, hands-down the best DP playlist for Indian placements.

Day 14: Resume ATS Optimization Round 2

Go back to your resume and refine it.

• Pull up job descriptions from 3 to 5 of your target companies (check Naukri, LinkedIn Jobs, or your college placement portal).
• Highlight the keywords they use: specific technologies, skills, and phrases.
• Incorporate those exact keywords into your resume naturally. If they say "REST APIs" and you wrote "APIs," change it to "REST APIs." If they say "Agile methodology" and you have worked in a team, mention it.
• Run your resume through the JobRise ATS Checker again. Aim for a score above 70.

End of Week 2 checkpoint: You should have solved 80 to 100 problems total, have a project on GitHub (or polished existing ones), and have an ATS-optimized resume scoring 70+.

---

Week 3 (Days 15 to 21): Practice Under Pressure#

You know the theory. Now it is time to practice like it is the real thing. Week 3 is about simulating actual placement conditions.

Days 15 to 16: Timed Coding Practice

From now on, every coding session is timed. In real interviews, you get 30 to 45 minutes per problem. You need to build speed.

Daily routine:

• Pick 3 to 4 medium problems on LeetCode.
• Set a timer: 30 minutes per problem.
• If you cannot solve it in 30 minutes, look at the hint (not the full solution). Try for 10 more minutes.
• Only then read the editorial. Understand the approach, close it, and solve it yourself from scratch.

Platforms for timed practice:

• LeetCode Contest, weekly contests every Sunday. Participate in at least one.
• CodeChef, monthly long challenges and short contests
• Codeforces, great for building speed (Div 2 A and B problems)
• HackerRank, many companies use HackerRank for actual tests, so the interface familiarity helps

Days 17 to 18: Aptitude and Verbal Preparation

Service companies (TCS, Infosys, Wipro, Cognizant, Accenture, HCL, Tech Mahindra) put heavy weight on aptitude rounds. Ignoring this is a common mistake. You can be great at coding and still get eliminated in the aptitude round.

Topics to cover:

• Quantitative: percentages, profit and loss, time and work, time speed distance, probability, permutations and combinations
• Logical Reasoning: blood relations, seating arrangements, coding-decoding, syllogisms, puzzles
• Verbal: reading comprehension, error spotting, sentence completion, para jumbles

Free resources:

• IndiaBix, the classic aptitude practice site. Solve the top 20 questions in each category.
• Prepinsta, has company-specific aptitude question banks (TCS, Infosys, Wipro sections with previous year questions)
• CareerRide, good for logical reasoning and verbal sections
• RS Aggarwal Quantitative Aptitude, if you prefer a book, this is the gold standard. Solve selected chapters.
• YouTube: Placement Preparation by Prepinsta, Career Ride

How much time to spend: 2 hours per day on Days 17 and 18. Focus on speed, not just accuracy. In real tests, you get 60 to 90 seconds per question.

Read our detailed guide: Aptitude Test Preparation Guide

Days 19 to 20: Mock Interviews

This is where most students skip and then regret it. Solving problems on a screen is very different from explaining your approach to a human being while they stare at you.

Day 19: Technical Mock Interviews

Option 1 (Best): Find a friend who is also preparing. Take turns being the interviewer. Ask each other to solve problems on a whiteboard or shared screen. The interviewer should ask clarifying questions and push for optimization.

Option 2 (Solo): Use these free platforms.

• Pramp, free peer mock interviews. You get matched with another candidate and take turns interviewing each other. Excellent platform.
• Interviewing.io, free mock interviews with real engineers (limited slots, but try to get one)
• Record yourself solving a problem and explaining it out loud. Watch it back. You will notice awkward pauses, unclear explanations, and confidence gaps.

What to practice in technical mocks:

• Start by clarifying the problem. Ask about edge cases, input constraints, expected output format.
• Think out loud. Interviewers want to hear your thought process, not just see your final code.
• Start with a brute force approach, then optimize. Never jump to the optimal solution without discussing trade-offs.
• Test your code with examples before saying "done."

Day 20: HR Mock Interviews

HR rounds eliminate more candidates than you think. Common reasons: poor communication, lack of confidence, no knowledge of the company, and bad answers to behavioral questions.

Prepare answers for these questions (write them down, then practice saying them):

1. "Tell me about yourself." (2-minute pitch: education, skills, 1 project highlight, career goal)
2. "Why do you want to join [Company Name]?" (Research the company. Mention something specific they do.)
3. "What are your strengths and weaknesses?" (Give real answers. For weakness, mention one you are actively improving.)
4. "Where do you see yourself in 5 years?" (Show ambition but stay realistic. "I want to grow into a senior developer role and contribute to impactful products.")
5. "Tell me about a time you faced a challenge." (Use the STAR method: Situation, Task, Action, Result.)
6. "Why should we hire you?" (Connect your skills to what the company needs. Be specific.)
7. "Do you have any questions for us?" (Always say yes. Ask about team structure, tech stack, growth opportunities.)

Read our full guide: STAR Method for Interview Answers

Day 21: Group Discussion (GD) Practice

Many service companies and some product companies include a GD round. Even if your target companies don't have one, practicing GDs improves your communication skills for HR rounds.

Current GD topics trending in 2026 placements:

• AI replacing jobs: threat or opportunity?
• Work from home vs work from office
• Is social media helping or hurting job seekers?
• Should coding be mandatory for all engineering branches?
• India's startup ecosystem: boom or bubble?
• Education system reform: what needs to change?

GD tips:

• Speak within the first 2 minutes. If you stay silent too long, it is hard to break in.
• Use data and examples, not just opinions. "According to NASSCOM, India's tech industry hired 3 lakh freshers in 2025" beats "I think tech hiring is good."
• Don't interrupt others. Build on their points: "I agree with [Name]'s point about X, and I would add that..."
• Summarize at the end if you get the chance. It shows leadership.

Read more: Group Discussion Topics 2026

End of Week 3 checkpoint: You should have done at least 2 mock technical interviews and 2 mock HR interviews. Your aptitude speed should be improving. Total problems solved: 100 to 120.

---

Week 4 (Days 22 to 30): Polish and Peak#

The final week. Everything comes together now. You are not learning new concepts. You are sharpening what you already know and building confidence.

Days 22 to 24: Company-Specific Preparation

Now narrow your focus. Pick your top 3 to 5 target companies and prepare specifically for them.

For each company:

1. Read 10 to 15 recent interview experiences on GeeksforGeeks and Glassdoor. Note down the most frequently asked questions.
2. Solve their most-asked coding problems. Every company has patterns. TCS loves arrays and strings. Infosys asks DP occasionally. Amazon loves sliding window and trees. Wipro focuses on basic logic.
3. Understand their hiring process. How many rounds? What is the cutoff? Is there a coding round, aptitude round, technical interview, HR interview, or all of them?
4. Research the company. Know their recent news, products, revenue, CEO, and values. This helps in both HR rounds and "Why this company?" questions.

Company-specific guides on JobRise:

• TCS Interview Questions for Freshers
• Infosys Interview Questions for Freshers
• Wipro Interview Questions for Freshers
• Cognizant Interview Questions for Freshers
• Accenture Interview Questions for Freshers
• HCL Interview Questions for Freshers
• Capgemini Interview Questions for Freshers
• Amazon Interview Preparation
• Google Interview Preparation
• Microsoft Interview Preparation

Days 25 to 26: Final Mock Interviews and Feedback

Do at least 2 more full mock interviews. This time, simulate the complete flow.

Full simulation (90 minutes):

1. Start with a coding problem (30 minutes)
2. Then a technical Q&A on your resume projects and CS fundamentals (20 minutes)
3. Then an HR round (20 minutes)
4. Then get feedback (20 minutes)

CS fundamentals to revise (commonly asked in technical interviews):

• DBMS: normalization (1NF, 2NF, 3NF), ACID properties, SQL queries (JOIN, GROUP BY, HAVING), indexing
• Operating Systems: process vs thread, deadlock conditions, CPU scheduling (Round Robin, SJF), virtual memory, paging
• Computer Networks: OSI model, TCP vs UDP, HTTP vs HTTPS, DNS, IP addressing
• OOP Concepts: 4 pillars (encapsulation, inheritance, polymorphism, abstraction), design patterns (Singleton, Factory), SOLID principles

Free resources for CS fundamentals:

• Gate Smashers YouTube, best Hindi explanations for DBMS, OS, CN
• GeeksforGeeks Last Minute Notes, quick revision pages for every subject
• InterviewBit, structured questions on CS fundamentals

Days 27 to 28: Resume Final Review and Application Setup

Day 27: Final resume polish.

• Re-read every single line of your resume. Check for typos, grammatical errors, inconsistent formatting.
• Ask a friend or senior to review it. Fresh eyes catch mistakes you've gone blind to.
• Run it through the JobRise ATS Checker one final time. Your score should be 75 or above.
• Print 5 to 10 copies on good quality white paper. Some campus drives still collect physical copies.

Day 28: Set up your online profiles.

• LinkedIn: Complete your profile. Professional photo, headline ("B.Tech CSE | Java Developer | Open to Opportunities"), About section with your pitch, add all projects and skills. Read our guide: LinkedIn Profile Optimization
• Naukri/Indeed: Create profiles if your target companies post there. Use the same keywords from your resume.
• GitHub: Make sure your profile README looks clean and your project repos have proper READMEs.
• Email: If your email is something like "[email protected]," create a professional one: [email protected].

Days 29 to 30: Rest, Revise, and Ready

Day 29: Light revision only.

• Skim through your notes on DSA patterns (don't solve new problems).
• Re-read your HR answers one more time.
• Review your project explanations. Practice explaining each project in 2 minutes.
• Glance through company-specific notes for the first company visiting your campus.
• Go for a walk. Exercise. Eat well. Sleep by 10 PM.

Day 30: Pre-placement checklist.

• Formal clothes ready and pressed. For men: collared shirt, formal trousers, polished shoes. For women: formal shirt/kurta, trousers/formal salwar, clean footwear.
• Printed resumes in a folder.
• Laptop charged (if needed for coding rounds), with your preferred IDE set up.
• Government ID card and college ID.
• Pen, notebook, and water bottle.
• Phone on silent. Backup alarm set.
• Get to the venue 30 minutes early.
• Believe in yourself. You have done more in 30 days than most students do in 6 months.

---

The Daily Schedule Template#

Here is a realistic daily schedule that covers everything without burning you out. Adjust based on your college hours, but protect the study blocks.

Weekday Schedule (Days when you have college)

Weekend Schedule (Full study days)

Total study hours: ~6 to 7 hours on weekdays, ~9 to 10 hours on weekends.

---

Complete Free Resource List#

Here is every free resource mentioned in this guide, organized by category.

DSA and Coding

Aptitude and Reasoning

CS Fundamentals

Mock Interviews

Resume and Profile Building

GitHub Repos Worth Bookmarking

• freeCodeCamp/freeCodeCamp, learn to code for free
• kamranahmedse/developer-roadmap, visual roadmaps for different tech careers
• jwasham/coding-interview-university, complete interview prep study plan
• yangshun/tech-interview-handbook, curated interview preparation materials
• donnemartin/system-design-primer, system design for interviews (more relevant for experienced roles)

---

What to Do if You Score Below 40 on the Employability Quiz#

If your JobRise Employability Score is below 40, it means you have significant gaps in one or more areas. Here is how to handle it without spiraling into panic.

First, understand what the score means. A score below 40 does not mean you cannot get placed. It means you need to prioritize ruthlessly. You cannot prepare for everything in 30 days with a low starting point, so focus on what gets you through the door at your specific target companies.

If your coding score is low (below 30):

Focus 80% of your time on coding for the first 2 weeks. Skip graphs and DP if you are targeting service companies. Master arrays, strings, sorting, and searching. These cover 60% of questions in TCS, Infosys, Wipro, and Cognizant coding rounds.

Minimum viable problems to solve: 30 easy problems from Striver's SDE Sheet (just the Easy column).

If your resume score is low (below 30):

Spend an entire day on Day 1 writing your resume. Don't touch anything else until you have a one-page, ATS-optimized resume. Use the ATS Resume Format Guide. Upload it to JobRise and iterate until you score above 60. A bad resume means you won't even get a chance to show your coding skills.

If your communication score is low (below 30):

Start practicing immediately. Record yourself answering "Tell me about yourself" every single day. Watch it back. You will cringe at first, that is normal. By Day 15, you will be noticeably better.

Join Toastmasters (many colleges have a chapter) or start a daily speaking practice with a friend. Even 15 minutes a day makes a visible difference in 30 days.

If your aptitude score is low (below 30):

Spend 1 hour daily on IndiaBix starting from Day 1. Don't delay this to Week 3. Focus on the top 5 topics: percentages, profit and loss, time and work, number series, and coding-decoding. These cover 70% of aptitude questions in service company tests.

If everything is low:

Target service companies (TCS, Infosys, Wipro) first. Their bar is lower than product companies, and getting one offer takes massive pressure off. Follow this modified priority:

1. Resume (Days 1 to 2)
2. Basic coding, arrays and strings only (Days 3 to 14)
3. Aptitude (1 hour daily from Day 1)
4. HR preparation (Days 15 to 21)
5. Company-specific prep (Days 22 to 28)

One placed student with a 3 LPA package has better options than a student with zero offers. You can always switch companies later. Get placed first, optimize later.

---

Frequently Asked Questions#

Is 30 days really enough for placement preparation?

Yes, for service companies like TCS, Infosys, Wipro, Cognizant, and Accenture, 30 days of focused preparation is enough. For top product companies (Google, Amazon, Microsoft), you ideally need 3 to 6 months. But 30 days of focused work beats 6 months of unfocused preparation every time. Many students crack placements with just 4 to 6 weeks of serious effort.

I have a low CGPA (below 7). Can I still get placed?

Absolutely. Many companies have a cutoff of 6.0 or even no cutoff at all. TCS NQT, Cognizant GenC, and many startups look at skills over CGPA. Focus on building strong projects, getting a good coding score, and performing well in interviews. Your CGPA matters less than your ability to solve problems and communicate clearly. Read about companies hiring with low CGPA.

Should I focus on DSA or aptitude first?

It depends on your target companies. For service companies (TCS, Infosys, Wipro), aptitude rounds come first and eliminate more candidates than coding rounds. Focus on aptitude. For product companies, DSA is everything. If you are applying to both, split your time 50-50 in Week 1 and then focus on whichever feels weaker.

How many coding problems should I solve in 30 days?

Aim for 100 to 120 problems. Quality matters more than quantity. It is better to solve 100 problems and understand every pattern than to "solve" 300 by copying solutions. Focus on understanding the approach, not memorizing code.

What if I don't have any projects on my resume?

Build one in 2 days (see the Week 2 section). It doesn't have to be complex. A simple CRUD application, a weather app, or a quiz game with clean code on GitHub is enough for service companies. For product companies, you need at least one project that demonstrates problem-solving, not just tutorial following.

Which programming language should I use for placements?

Java is the safest choice, accepted everywhere and most commonly used in Indian placements. C++ is great for competitive coding and product companies. Python is fastest for solving problems but some service companies don't accept it in coding rounds. Pick one and stick with it. Do not switch languages mid-preparation.

I get nervous during interviews. What can I do?

Practice is the only cure. Do at least 5 mock interviews before the real thing. Start with friends (less pressure), then move to platforms like Pramp. Record yourself and watch it back. Also, remember that nervousness is normal. Even placed students were nervous. The difference is they practiced enough to perform despite the nervousness.

Should I prepare for off-campus placements too?

Yes. Do not put all your eggs in the campus basket. Create profiles on Naukri, LinkedIn, Internshala, and Unstop (formerly Dare2Compete). Apply to off-campus drives and hiring challenges. Many students get better offers off-campus than on-campus.

What should I do the night before my placement interview?

Do not study anything new. Re-read your resume, review your project explanations, and skim your HR answers. Eat a proper meal. Set 2 alarms. Keep your clothes, documents, and bag ready. Sleep by 10 PM. A well-rested brain outperforms a sleep-deprived one that crammed all night.

My college does not have good placement support. What can I do?

Most tier-2 and tier-3 colleges don't. That is why off-campus preparation matters. Follow this 30-day plan, apply off-campus on Naukri, LinkedIn, and Unstop, participate in hiring challenges (TCS CodeVita, Infosys HackWithInfy, Wipro Elite NLTH), and connect with seniors who got placed through off-campus drives. Also read: Job Search Strategy for India

---

Your 30-Day Placement Plan Summary#

The students who get placed are not always the smartest ones. They are the ones who follow a plan, put in consistent effort, and show up prepared. You have 30 days. That is 720 hours. Even using just 6 hours per day, that is 180 hours of focused preparation. It is more than enough.

Start now. Not tomorrow. Not after one more YouTube video. Now.