How to Prepare for Campus Placements From Third Year

Third year is the last full runway you get before placement season. Most Indian colleges run their main on-campus drives in the 7th semester, which means the 5th and 6th semesters are the only stretch where you can build aptitude, DSA depth, and a deployed project without competing against interview calls. This post gives you a block-by-block roadmap — what to do in the 5th semester, what changes in the 6th, and how to use the summer before the 7th. It also separates the service-company track from the product-company track, because preparing for both equally is how most students end up ready for neither.

What does the campus placement calendar actually look like for a third-year student?

For most Indian engineering colleges, the main on-campus drives happen in the 7th semester — roughly July to December of the final year. That gives a third-year student somewhere between 12 and 15 months of usable preparation time. The mistake is treating that runway as one long block. It is not. It has three distinct phases, and each one rewards a different kind of work.

The 5th semester is your fundamentals-and-aptitude block. Course load is still manageable, and you are not yet close enough to placement season to panic. Use it. The 6th semester is where DSA depth, project shipping, and resume work happen — this is the heaviest block. The summer before the 7th semester is for mock interviews, company-specific patterns, and closing whatever gaps the first two blocks exposed.

If you want the wider version of this sequencing — including how the 4th year fits in — the campus placement preparation timeline walks through the full four-year arc. For now, the third-year slice is what matters.

Service companies vs product companies: which track gets your time?

These two tracks test different things, and third year is when you decide which one gets roughly 70% of your preparation hours. Service companies — the TCS NQT, Infosys, Wipro, Cognizant pattern — typically lead with aptitude, logical reasoning, and verbal, then a basic coding round. Product companies and GCCs lead with DSA, CS fundamentals, and project depth.

You cannot optimize for both at the same intensity. What you can do is sequence them. Aptitude first, because it is the faster lever and it appears in the first elimination round of most service-company drives. DSA depth second, because it takes longer to build and it is the gate for product roles.

If your target is service companies, give aptitude and verbal 40–50% of your prep time and keep DSA at a functional level. If your target is product companies or GCCs, flip it: 70%+ on DSA and CS fundamentals, with aptitude as maintenance. The aptitude preparation for service companies breakdown covers the first track in detail.

Why aptitude is the highest-ROI lever most tier-3 students ignore

Aptitude is the most neglected part of third-year prep, and for tier-3 students it is often the highest-return one. Quant, logical reasoning, and verbal can be built to a competitive level in 8–10 weeks with daily 45-minute practice. That is a short window for a skill that appears in the first round of most service-company recruitment drives.

The mechanism is straightforward. Aptitude rounds are timed and elimination-based. They do not reward brilliance; they reward speed and accuracy on a known set of question types. Once you have seen enough permutations of time-speed-distance, percentages, and seating arrangement problems, the round stops being a knowledge test and becomes a pattern-recognition test.

That means timed practice, not passive reading. Solve under a clock from week one. Track accuracy separately from speed, because the two fail for different reasons — accuracy failures are conceptual, speed failures are usually hesitation on familiar question types.

A practical weekly structure: 30 minutes of new-topic learning, 45 minutes of timed problem sets, and one full-length mock on the weekend. Adjust the ratio after your first mock tells you where you actually stand.

How should DSA be sequenced in the 6th semester?

Sequence DSA by topic, not by problem count. The order that works for most students is arrays and strings, then hashing, two pointers, stacks and queues, linked lists, trees, graphs, and finally dynamic programming. Spend two to three problems per topic before moving on — enough to recognize the pattern, not enough to burn a month on one category.

The target by the end of the 6th semester is 150–200 problems solved with understanding. Not 500 rushed ones. If you can explain your approach, the time complexity, and the edge cases for 150 problems, you are in better shape than someone who pattern-matched their way through 500.

Depth beats breadth here for a specific reason: interviewers probe. They ask why you chose a hashmap over sorting, what happens when the input is empty, how your solution scales. A rushed problem count collapses under that questioning. A smaller, well-understood set holds up. The DSA roadmap for placements lays out the topic order with problem counts per stage.

What kind of project actually signals competence to a recruiter?

One deployed project with a live URL beats five CRUD clones. The signal recruiters and placement cells look for is not that you can follow a tutorial — it is that you made decisions, hit a wall, and resolved it. A project with a working deployment, a clean README, and a short "what I would do differently" section communicates that better than a GitHub full of half-finished repos.

Third year is the last realistic window to build and ship this. In the 7th semester you will be juggling drives, and the project will either already exist or it will not. Pick something you can finish in 6–8 weeks: a full-stack app with authentication and a database, or an ML project with a real dataset and a deployed inference endpoint.

The README matters more than most students think. State the problem, the stack, the architecture in three lines, and the trade-offs you made. If a recruiter reads only that file, they should understand what you built and why. The projects that signal competence to recruiters guide covers what separates a portfolio project from a tutorial follow-along.

Does CGPA still matter if your coding is strong?

Yes — as a filter, not as a ranking. Service companies commonly report a 60% or 6.0 CGPA cutoff for fresher eligibility, and some product companies and GCCs use higher bars. These cutoffs are eligibility gates, not scoring criteria. Below the cutoff, you are filtered out before anyone sees your DSA. Above it, extra CGPA points buy you very little.

So the trade-off is bounded. If you are below the cutoff for your target companies, spend 5th and 6th semester fixing it — clearing backlogs, retaking papers, protecting your internal marks. If you are comfortably above it, marginal CGPA gains are worth less than an extra 50 DSA problems or a shipped project.

The mistake is treating this as a binary. It is not "CGPA or skills." It is "clear the gate, then stop optimizing for it."

What should your resume and GitHub look like by the end of third year?

By the end of the 6th semester, you should have a one-page resume with quantified bullets and a GitHub that a recruiter can scan in 30 seconds. Quantified means numbers: "reduced API response time from 800ms to 200ms," not "improved performance." One page, no exceptions, for a fresher.

On GitHub, pin your best two or three repositories. A green contribution graph helps, but pinned repos with real READMEs help more. On LinkedIn, the headline should say what you build — "Backend developer | Node.js, PostgreSQL" — not "aspiring software engineer." Recruiters and placement cells screen these profiles before the first round, and a vague headline gives them nothing to remember you by.

The fresher engineering resume guide covers the bullet structure and the common mistakes that get a resume filtered in the first pass.

How do you build an off-campus pipeline in parallel?

Treat on-campus as one channel, not the only one. From third year, build the off-campus pipeline alongside your prep: a complete Naukri and LinkedIn profile, a habit of applying to off-campus drives, and a small network of seniors and alumni who can refer you. Many students report that their first offer came through an off-campus channel rather than the college drive — particularly at colleges where few product companies visit.

The good news is that the same preparation serves both channels. Aptitude, DSA, and a deployed project are what off-campus recruiters screen for too. You are not splitting your effort; you are widening the surface area where that effort can convert. The off-campus placement guide for tier-3 students covers the channels and the application cadence.

Is third year too late to start preparing for campus placements?

No. Third year is the ideal start for most students. You have roughly 12–15 months before the 7th-semester placement season, which is enough to build aptitude, cover core DSA topics, and ship one solid project. Starting in the 4th year is when it becomes genuinely tight, especially for product-company roles that need DSA depth.

If you want a quick read on where you currently stand before you commit to a plan, the placement readiness assessment benchmarks your background against the roles you are targeting and shows which gaps to close first.

The one decision that determines whether third year works

Pick your primary track now — service companies or product companies — and let it allocate your hours. Everything else in this roadmap follows from that choice. Students who try to prepare for both at equal intensity usually end up with shallow aptitude and shallow DSA, which is the worst of both.

The second decision is to start the off-campus pipeline in parallel, not as a fallback. It costs you almost nothing extra because the preparation overlaps, and it widens the number of places your effort can convert into an offer.