A large share of working developers in India did not study computer science. Mechanical and civil graduates who taught themselves during a placement season that ignored them. Commerce students who built a billing tool for a family shop and never went back. ECE graduates who found they liked the software half more. If you are one of them, this post is for you, and the first thing to say is that the door is real — it is just not the door most people are pointing you at.
What actually filters you out
It is worth being precise about where the degree hurts, because it is narrower than it feels.
- Campus placements — many companies restrict eligibility by branch. If you are not CS/IT, you often cannot sit the test at all. This is the most visible wall and the least important one, because campus hiring is a small slice of developer jobs.
- Job portals with a degree filter — some large-company postings on Naukri and LinkedIn are pre-filtered to B.E./B.Tech CS. Your application is discarded before a human sees it.
- Recruiters skimming resumes — a non-CS degree at the top of a PDF sets an expectation the rest of the page has to fight.
What does not filter you out: the actual work. Nobody has ever been unable to fix a bug because of their branch. Startups, product companies, agencies, and most mid-size firms hire on what you can do, and they are the majority of the market. The route, then, is to spend as little time as possible in the pipelines that filter on paper and as much as possible in the ones that look at work.
The six-month plan
This assumes you can code a little and have evenings. Adjust the timeline, keep the order.
Months 1–2: one stack, one finished thing
Pick a single stack that has jobs near you — for most Indian cities today, that is JavaScript/TypeScript with React and Node, or Python with a web framework — and ignore everything else. Build one small, complete project with a real user (you count). Deploy it. This is where most people stall, because they keep starting courses instead of finishing things. Finish the thing.
Months 3–4: the project that becomes your degree
Now build the project that will carry your applications — something with a hard part, deployed, used by at least one other person. These seven ideas are scoped for exactly this. Build it in the open: commits every day, a README that explains the hard part, a two-minute demo at the top.
This project is your answer to the degree question. When someone asks "but you're mechanical?", you send a link.
Month 5: make the work findable
- Clean your GitHub: one strong pinned project, coursework archived, no empty forks — here is what reviewers check.
- Rewrite the top of your LinkedIn to say what you build, not what you studied.
- Contribute one small fix to an open-source project you actually use. A merged pull request with your name on it is evidence no degree can match.
- Learn to explain the project out loud, with a timer.
Month 6: apply where work is the filter
- Startups and small product companies. Founders read GitHub links. Email them directly with the demo — two lines and a URL beat a cover letter.
- Referrals. Developers you have met in communities, meetups, or Discord servers can refer you past the portal filter. Ask specifically: "Can you refer me for this role? Here is the demo."
- Proof-of-work platforms. Iber was built for exactly this case: there is no resume, so there is no degree box. Your profile is verified projects, the demo, and an AI interview about your own code. A company sees what you built before it sees anything else — often before it ever learns your branch.
- Contract and freelance work. A paid three-week project for a local business is experience, a reference, and often a portfolio piece at once.
Handling the degree question
It will come up. Have a two-sentence answer and do not apologise: "Mechanical, and I moved to software in third year because I liked building tools more than the coursework. The billing app is what I built in the last six months — happy to walk through it." Then walk through it. The person who asked is usually checking whether you are defensive about it, not whether the degree matters.
What about a "conversion" course or bootcamp?
Useful if it gives you structure and a cohort; unnecessary if you can finish things on your own. The certificate itself carries almost no weight with the companies that would hire you anyway, and none with the ones that filter on degree. Spend the money only if it buys you finished projects faster.
Things to be honest about
- The first job is the hard one. The second one, nobody asks.
- Some companies will never hire you without the degree. They are a minority, and they are not the interesting ones.
- Fundamentals matter. You do not need a CS degree, but you do need to understand how a request travels through your app, what a database index is for, and why your code is slow. Learn those from the project, not before it.
The short version
The degree filter is real and mostly avoidable: it lives in campus placements and portal checkboxes, not in the work. Build one finished, deployed, explainable project; make it findable; apply through people and platforms that look at work first. Six months of this beats four years of the wrong branch, and a lot of people already working as developers are the proof.