Good campus placement preparation starts well before the final year. Recruiters judge four years of grades, skills, projects and communication in a few hours of tests and interviews. This roadmap breaks the work into a year-by-year plan for B.E./B.Tech students in any branch, with concrete outputs for each year. It also covers what to do if campus placement does not work out.
- Placements usually run in the final year, but eligibility depends on grades and backlogs from Semester 1 onwards.
- Most selection processes combine an online test (aptitude and/or coding), technical interviews and an HR interview, sometimes with a group discussion.
- Internships and real projects are the strongest proof of skill on a résumé.
- Core-engineering routes (including GATE-based PSU hiring) need different preparation from software roles.
- Never pay anyone for a job offer. Legitimate employers do not charge candidates.
How campus placement actually works
Most engineering colleges have a placement and training cell that invites employers, sets the schedule and enforces rules. The old SJCE site, for example, described a Placement and Training Centre that ran mock interviews, group discussions, skill tests, personality development courses and employer talks, as well as arranging campus interviews. The details vary, but the pattern is familiar:
- Registration: You register with the placement cell and agree to its rules, which may include limits on how many offers you can accept.
- Eligibility filter: Each employer sets criteria, commonly a minimum CGPA or percentage, limits on active backlogs, and eligible branches.
- Online assessment: Quantitative aptitude, logical reasoning, verbal ability and, for many roles, coding problems or core-subject questions.
- Group discussion (some employers).
- Technical interview(s): Fundamentals, your projects and problem-solving.
- HR interview: Communication, motivation, fit, relocation and terms.
- Offer: Followed by onboarding, which may be delayed, so read offer letters carefully.
The biggest lesson is that eligibility is decided early. A low CGPA or a backlog from the second year can keep you out of a test you would otherwise pass. See our placements and recruiters pages for background on campus recruitment.
The four-year roadmap at a glance
| Year | Main focus | Concrete outputs by year end |
|---|---|---|
| 1st year | Foundations: grades, one programming language, communication | Clean first-year grades with no backlogs; 50–100 basic programming problems solved; one club or professional-body membership |
| 2nd year | Core subjects, data structures, first projects | Solid grades in core subjects; one small working project on a public repository or in a portfolio; first online course certificate |
| 3rd year | Depth, internships, aptitude | At least one internship or substantial industry/research project; a one-page résumé; regular aptitude and coding practice |
| 4th year | Placement season and final project | Mock interviews done; résumé reviewed; strong final-year project; a backup plan (GATE, off-campus, higher studies) |
First year: protect your eligibility and build habits
First-year subjects feel unrelated to jobs, but the grades count towards the CGPA cut-offs employers use. Aim to clear every course the first time. Alongside that:
- Learn one programming language properly. Use C, C++, Java or Python, whichever your curriculum uses, and practise with short daily problems. This matters even for non-CS branches, because many online assessments include coding.
- Work on communication. Read, write short summaries and speak in class or club meetings. Fluency improves with practice.
- Join something. A technical club, an IEEE, CSI or ISTE student chapter, a sports team or a cultural group. These build teamwork stories you will later need in HR interviews. See our page on professional bodies.
Second year: core subjects and your first project
This is when the subjects that technical interviews draw on are taught: data structures and algorithms for computing roles; circuits, signals and digital electronics for ECE and EEE; mechanics, thermodynamics and materials for Mechanical; structures and surveying for Civil. Learn them for understanding, not just for the exam.
- Build one complete project, however small, that solves a real problem and that you can explain end to end. Hardware students can build an IoT or embedded project; software students can build a web or mobile app; core students can do a design or simulation study.
- Take a structured online course in a gap area. The government-funded NPTEL platform from the IITs and IISc offers courses with proctored certification exams.
- Start a simple portfolio: a public code repository or a one-page document listing projects with short descriptions.
Third year: internships, depth and aptitude
The third year usually decides how strong your placement profile looks.
- Get real-world experience. Apply for summer internships through your placement cell, departmental contacts, government portals such as AICTE’s internship portal, company programmes and research internships with faculty. A well-documented research project can count as much as an industry internship. Our article on industry–institute partnerships and internships explains how colleges arrange these.
- Specialise a little. Choose electives and a second, more substantial project in one direction, such as web development, data, embedded systems, VLSI, design and simulation, or construction management.
- Start aptitude practice. Do 30–45 minutes a few times a week on quantitative aptitude, logical reasoning and verbal ability. These are skills built through practice, not cramming.
- Write your résumé. One page: education, skills, projects (with your specific contribution), internships and activities. Every line should be something you can discuss for five minutes.
- Decide on GATE. If you are interested in an M.Tech, research or PSU roles, GATE preparation fits best from the third year. GATE 2027 is organised by IIT Madras.
Final year: the placement season
- Before the season: Revise core subjects, take timed mock tests, and do at least two or three mock interviews with seniors, faculty or the placement cell.
- Research each employer: what it does, the role on offer, location and bond terms if any.
- In technical interviews: think aloud, start with a simple correct solution and then improve it, and be honest when you don’t know something.
- In HR interviews: prepare short, true stories about teamwork, a failure, a conflict and a project you are proud of.
- Keep the final project strong: it often comes up in interviews and matters for later applications.
Group discussions
Where employers use a group discussion, they are usually judging how you think and work with others, not how loudly you speak. Open with a clear point if you can. Build on others’ arguments by name, bring in a fact or example, and help the group reach a summary towards the end. Interrupting, repeating yourself or staying silent throughout tend to count against you. Practise with friends on current-affairs and technology topics, and take turns observing and giving feedback.
Making your résumé interview-ready
Interviewers often pick one line on your résumé and keep asking “why?” and “how?” about it. For each project, be ready to explain the problem, your specific contribution, the design choices you made and the alternatives you rejected, what went wrong, and what you would do differently. Remove anything you cannot defend. Use plain, specific wording: “built a sensor logger that recorded temperature every minute to a cloud dashboard” says more than “worked on IoT”. Keep separate versions for software and core roles if you are applying to both.
Want structured practice? SJCE Mysore‘s independent 6-week online Placement Readiness Bootcamp covers aptitude, coding practice, résumé reviews and mock interviews. It is not affiliated with any college placement cell, and no bootcamp can guarantee a job offer.
Core engineering versus software routes
The roadmap above applies to everyone, but preparation differs by the jobs you want:
- Software and IT roles: Focus on data structures and algorithms, one language in depth, databases, basic system design and projects. Many such employers recruit across branches.
- Core private-sector roles: Interviews go deeper into branch fundamentals and practical tools such as CAD/CAE, PLC/SCADA, circuit simulation or structural software, plus internship experience in the domain.
- PSUs and government: Several public sector undertakings have used GATE scores to shortlist graduate engineer trainees, and other government jobs have their own exams. Read each organisation’s current notification for the process.
- Apprenticeships: The government’s National Apprenticeship Training Scheme (NATS) portal lists apprenticeship opportunities for graduates and diploma holders, with a government-supported stipend.
If you are still choosing a branch, our guide on how to choose an engineering branch explains how each one maps to these routes.
If you are not placed on campus
Many capable graduates find their first job off campus. If the season ends without an offer:
- Apply off campus through company career pages, verified job portals and the National Career Service portal.
- Consider an apprenticeship through NATS, or a paid internship that could convert to a job.
- Use the time to add one strong project or certification in your target area.
- Consider higher studies, such as an M.Tech through GATE or other routes. See our guide to research and higher studies after B.E.
- Stay in touch with alumni and seniors. Referrals are one of the most effective routes to interviews.
Keep a simple weekly routine during an off-campus search: a fixed number of targeted applications, an hour of practice most days, and one improvement to your portfolio each week. A steady routine is easier to sustain than intense bursts.
Red flags: fake offers and job scams
Students who are anxious after a placement season are frequent targets for job scams, so stay careful.
Never pay for a job. Be wary of offers that ask for “registration”, “training” or “security deposit” fees, arrive from personal email addresses, skip interviews, or pressure you to decide within hours. Check the company’s official website and confirm with your placement cell before sharing documents or money. The government’s National Career Service portal also advises jobseekers never to pay employers.
Frequently asked questions
When should I start preparing for campus placements?
Start in the first year by protecting your grades and learning programming. Focused aptitude and interview preparation usually begins in the third year, before the placement season in the final year.
Does CGPA really matter for placements?
Yes, mainly as an eligibility filter. Many employers set a minimum CGPA and limit active backlogs. After you clear the filter, skills, projects and interviews matter more.
Can non-CS students get software jobs through campus placement?
Yes. Many IT employers recruit across branches through aptitude and coding tests. Regular coding practice and one or two software projects make a big difference.
Are internships necessary to get placed?
Not strictly, but a relevant internship or substantial project is one of the strongest things you can put on a résumé. It also gives you concrete examples to talk about in interviews.
How do PSU jobs for engineers work?
Several public sector undertakings have used GATE scores to shortlist graduate engineer trainees, followed by interviews or other rounds. Each PSU sets its own process, so read its current recruitment notification.
How can I tell if a job offer is fake?
Warning signs include requests for money, no proper interview, personal email addresses and extreme time pressure. Verify the employer independently and check with your placement cell.
