Campus placements for data roles from a non-CS branch: 16-week plan
In this article (6 sections)
Related programme: the FDE for Freshers course (6–7 months; EMI from ₹8,000/month · full fee shared on your counselling call). See also open Forward Deployed Engineer jobs in India, updated daily.
A non-CS student can prepare for data and software roles in campus placements in about 16 weeks if the plan covers four things in parallel: aptitude for the first filter, one programming language plus SQL for the coding round, one project that connects your branch to data, and a clear answer to "why are you leaving your core branch?". Check each company's eligible-branch list in the placement notice before you invest in its specific pattern.
Read the eligibility line first
Every campus drive notice from your training and placement cell carries an eligibility section: branches, minimum percentage or CGPA, backlog rules, sometimes a year-of-passing condition. Build a small table of the companies coming to your campus with three columns — eligible branches, academic cut-off, and role type — and colour the ones you can actually sit for. Preparing for a company that excludes your branch is time lost. If your cell publishes last year's list of recruiters, use that as a rough guide, but confirm each year's notice.
The 16-week plan
Plan for about 12 hours a week. Adjust if your semester load is heavy.
| Weeks | Aptitude (3 h/wk) | Programming (5 h/wk) | Project (3 h/wk) | Interview (1 h/wk) |
|---|---|---|---|---|
| 1–4 | Percentages, ratios, time and work | Python basics: loops, functions, lists, dictionaries | Choose a branch-linked problem, find data | Write your "why data" answer |
| 5–8 | Logical reasoning: series, arrangements, syllogisms | Problem practice: strings, arrays, sorting; start SQL | Clean data, first analysis | Explain your project in 2 minutes |
| 9–12 | Verbal and mixed timed mocks | SQL joins and GROUP BY; output-prediction questions | Build a dashboard or small app, write README | Mock technical round with a friend |
| 13–16 | Two full mocks per week | Timed coding sets, revise errors | Final polish, deploy or publish | HR round practice, company research |
Aptitude usually decides whether your coding is ever seen, which is why it starts in week 1. For worked examples, see quantitative aptitude questions solved. Output-prediction and pseudocode questions appear in many online tests for engineering graduates; they are covered in output-prediction questions in campus tests.
A project that uses your branch
Your branch is an advantage when the project uses it. An interviewer will ask about your core subject anyway, so let the answer lead to data work.
| Branch | Project idea with real data shape |
|---|---|
| Mechanical | Sensor log from a lab machine: detect when vibration readings drift out of range and flag them |
| Civil | Daily progress reports from a site (synthetic): planned vs actual quantities and cost variance by activity |
| Electrical | Smart-meter style hourly readings: find peak hours and unusual consumption days |
| Chemical | Batch process records: which input conditions go with off-spec batches |
| ECE | Signal samples from a lab exercise: filter noise, report error rates before and after |
Keep the data synthetic or from your own lab work with permission, and say so in the README.
Answering "why not your core branch?"
This question comes in almost every HR and many technical rounds. A weak answer sounds like escape ("core jobs pay less"). A strong answer shows a direction and evidence. A model answer from a hypothetical mechanical student:
"In my fifth semester I worked on a vibration-analysis lab and spent more time on the data than on the machine. I learnt Python to process the readings and found I enjoyed finding patterns in the logs. Since then I have learnt SQL and built a project that flags abnormal readings automatically. I still use my mechanical background — I know what a reading should look like physically, which helps me spot bad data."
Notice the structure: a specific moment, the action you took, evidence since then, and how the old branch still helps. Write yours in under 100 words and practise saying it without reading.
Things non-CS students get asked that CS students often do not
- Basic data structures in plain words: what is the difference between a list and a dictionary, when would you use each?
- A core-subject question to test honesty: expect at least one question from your branch. Revise your two strongest subjects.
- "Which programming language do you know best?" Pick one and be able to write a function in it on paper.
- Complexity at a simple level: why is searching a sorted list faster with binary search?
Keeping your core options open
You do not have to choose permanently in pre-final year. Sit for core companies you are eligible for if you want, but decide by week 8 where your main preparation hours go. Splitting evenly across core and software preparation usually leaves you under-prepared for both.
Students who want to go beyond analytics into building and deploying AI systems for clients can look at the FDE for Freshers programme, which starts from software fundamentals and does not assume prior coding.
Frequently asked questions
Can mechanical or civil students sit for software and data roles in campus placements?
Often yes, but it depends on each company's eligibility criteria, which your placement cell circulates with the job notification. Many drives list eligible branches explicitly, so read that line before preparing for a specific company.
What should a non-CS student study first for data roles?
Start with one programming language, usually Python, and SQL, because online tests and technical interviews for data roles lean on both. Aptitude practice runs alongside from the first week because it is often the first filter.
Pankit Kumar has 10 years in Data Science & AI, building and shipping production systems in regulated pharma and clinical environments. He is a freelance trainer at Boston Institute of Analytics, AnalytixLabs and Scaler, and has taught this material to thousands of working professionals.
This article is part of our FDE for Freshers programme — 6–7 months. Build your engineering foundations, then take AI from discovery to delivery.
Explore FDE for Freshers