A significant share of capable early-career software candidates in India did not study computer science. Most technology hiring filters them out before anyone reads their work.
Live from our candidate database
Counted at render time and refreshed every six hours. This is a supply-side view of one platform, not a national labour-market statistic.
The self-selection argument
A mechanical engineering graduate who taught themselves to build software did so with no curricular support and no institutional pressure. That is a stronger motivation signal than a CS graduate who followed the default path.
The honest trade-off
They will typically have gaps in fundamentals — operating systems, networks, complexity analysis. These are real and they matter, and they are also closable within months for a motivated hire with a mentor.
Where they do best
Roles where domain knowledge compounds with software ability: manufacturing tech, fintech, healthtech, logistics platforms. A mechanical graduate building factory software understands the factory, and that is not teachable in months.
How to screen fairly
Same rubric, applied identically. Do not lower the bar and do not add an implicit surcharge for the unfamiliar degree — the second is what happens by default in most panels.
Key takeaways
- Self-taught non-CS candidates carry a stronger motivation signal by construction.
- The fundamentals gap is real and closable within months with a mentor.
- Domain-plus-software roles are where these candidates outperform outright.
- Apply the same rubric — an implicit surcharge for an unfamiliar degree is the default failure.
Questions
Do non-CS hires retain as well?+
In our experience of employer feedback, retention tracks role fit and mentorship quality rather than degree. Candidates hired into domain-adjacent roles retain particularly well.
Should we run a separate funnel for them?+
No. A separate funnel becomes a lower-status funnel. One funnel, one rubric, degree not weighted.