Can I switch to software from mechanical engineering mid-college?

I graduated from mechanical at an IIT and moved into backend engineering at a unicorn. Honestly, the transition was smooth because I'd started side projects in second year. Two concrete things: (1) get an internship in a tech role by summer of 3rd year—even a smaller company works, and (2) vet your resume to emphasize problem-solving over core coursework. Placements team might route you to core PSUs, but if your GitHub is solid, FAANG and startups will find you.

The key insight: recruiters hire on skills, not branch, especially for SDE roles. Start with competitive programming (CodeChef, Codeforces) and a structured DSA course—many paid platforms have 3-4 month intensive tracks. By your third year internship, aim for a tech company project; that internship letter carries huge weight in final placements. Your branch won't hurt you; lack of proof of coding ability will.

Totally doable, and honestly, more common than you'd think. I was civil and switched into product roles at startups. You don't need to formally change your branch—just start learning DSA and web dev now. Build a portfolio, contribute to GitHub, and by final year placements, you'll have proof of skills. Core branch guys often get picked by tech companies because they're seen as well-rounded.

To the parent: backup plan is solid. If software placements don't happen, you still have core companies visiting NITs/good state colleges. But honestly, with preparation, a mechanical grad will crack a tech internship by 3rd year—and once you have that, final placements into software become much easier. The real risk is doing nothing and hoping, not attempting the switch. Start now, and you have options.

For 6 months, focus on DSA and one language (Python or C++) strongly—that's your interview foundation. Competitive programming teaches problem-solving patterns you'll face in tech interviews. Once solid on DSA (3 months), pick a domain: backend, frontend, or data structures. Web dev is great for portfolio, but SDE interviews at bigger companies lean heavily on algorithms. Do both eventually, but prioritize the interview-critical skills first.

My son is in mechanical at a state college and thinking the same thing. My worry is: if he doesn't land a software role in placements, will his mechanical degree still get him core sector jobs? Or will he fall between two chairs? Can anyone reassure me about the backup plan?

This thread is really helpful, thanks everyone. Just wanted to add: my college also offers a minor in computer science—would doing that formally help, or is it overkill if I'm already self-learning? Or does it just look nice on paper?