Home
/
Blog
/
Developer Insights
/
Why 80% of India's engineers remain unemployable in the software sector

Why 80% of India's engineers remain unemployable in the software sector

Author
Raghu Mohan
Calendar Icon
December 4, 2016
Timer Icon
3 min read
Share

Explore this post with:

Key Takeaways:

  • Only a small fraction of Indian engineering graduates are employable in the software sector, with just 18.43% meeting industry standards.
  • Outdated curricula and rote-based exam culture leave students unfamiliar with modern programming languages and practical engineering methods.
  • Most graduates struggle to apply theoretical knowledge to real-world problems, creating a gap between academic learning and industry needs.
  • Poor English communication and cross-cultural collaboration skills prevent many engineers from succeeding in global software environments.
  • Addressing this issue requires curriculum redesign, practical problem-solving, continuous learning, and development of soft skills.

It's common knowledge that India has a lot of educated people. That’s wonderful. But the lacuna casts a pall over the mood.

Reality bites, rarely pleasant…You might agree with me if you read the National Employability Report by Aspiring Minds, an employability evaluation and certification company, released earlier this year. The New-Delhi based company’s research study tracks more than 150,000 engineers who graduated in 2015 from over 650 colleges in India.

Did you know?

  • Only 18.43% of the engineers are employable in the software sector
  • Only 3.84% engineers suited to tech roles in startups
  • Nearly 27% of engineers failed to even snag an interview

Most numbers in the report are grim, from an employability percentage of 3.67% of Software Engineers for IT product companies to 17.91% of Software Engineers for IT service companies. Design engineers are not too lucky either with electronic engineers being the most employable at 7.07%.

Finding these abysmal statistics thought-provoking, we had a rather animated discussion at work about the “whys” and the “hows” and have come up with a few key observations:

Outdated learning and exam culture:

outdated classroom teaching

Whatever the reasons might be for the poor show, I believe it is sad that India's best universities are nowhere in the Top 100 in the world. The best India could do as of now: The Indian Institute of Science (IISC) in Bengaluru is at 152 and the Indian Institute of Technology (IIT)-Delhi is at 185 in the QS World University Rankings.

Indian curriculum is behind times as far programming languages are concerned. They stick with BASIC, FORTRAN, and some “marked for death” like PERL, Flash, Algol, and Object Pascal; how are these students expected to make headway into a world of Java, C, C++, Python, Ruby on Rails, etc.? (Those fortunate enough to go to some Tier I institutions do reap benefits of excellent professors and course design.)

The situation is worse in the case of core engineering such as mechanical or civil profiles. Like Aspiring Minds CTO, Varun Aggarwal, said, "The science of manufacturing has moved way ahead but we continue to teach outdated concepts to students. For India to become the world's manufacturing hub, we need to lead from the front in our understanding of cutting edge methods, knowledge-driven management and implementation capability."

Exams still force the students to memorize by rote ancient textbooks, with no comprehension of the basic concepts. It is no surprise then if they don’t bring the Nobel home, right? Most Indian children are expected to spend hours in “coaching” classes to get into engineering or medical colleges. Somehow many manage to, merit, money, no one really cares. With no passion to learn, to apply, to create, these engineers are only interested in finishing their 4-or 5-year degrees. What happens after is something else altogether.

Theory vs. Practice

theory vs practice

“It’s the learning ability. It’s the ability to process on the fly. It’s the ability to pull together disparate bits of information.” This what Laszlo Bock, Senior Vice President of People Operations at Google, Inc. told the New York Times in an interview in 2015. The tech giant apparently doesn’t care much about GPAs. Analytical and logical skills, please.

Most Indian engineering graduates, be it IT or Electronics engineers, fail when they are expected to apply basic principles to solve real-world problems. With neither the requisite analytical skills nor a commendable command of the domain, they flounder. They need “specific” training. That’s an expense that not everyone in the industry wants to incur. Universities need to bridge this gap and soon. For instance, they can encourage participation in coding challenges that companies like HackerEarth, SPOJ, and CodeChef conduct and introduce IT engineering students to competitive programming or hackathons.

Even companies like Wipro, TCS, and Infosys are committed to re-skilling or up-skilling their people—they promise to pay you more if you learn newer technologies. For example, with applications being moved to cloud computing, the engineers would need to know Go. For self-learners, the options are aplenty with premier e-learning providers like Udacity and Simplilearn offering you what the market demands. All of this sounds easy, but it is not—quite capital and labor-intensive.

Poor language skills

poor communication skills

And by language, I mean English. Effective communication is key to succeeding in the corporate world. This is not to put down our Indian language mosaic any way. We have come a long from the popular BBC sitcom Mind your English in the 70s, but going by this video, I’d say we have miles to go.

According to the Aspiring Minds’ National Spoken English Skills Report (SES), 52% of Indian engineers can’t get jobs because their spoken English skills are nothing to write home about. Fluency, sentence construction, pronunciation, and basic grammar would seem to be alien skills to some. Obviously, watching reruns of “Friends” and listening to Taylor Swift don’t seem to be working.

In the software sector, especially, engineers interact with an English-speaking workforce spread across the world. Cross-cultural team communication and client-handling skills are not taught in our colleges, unfortunately. Although an engineer could be brilliant, the inability to put forward his views effectively could well cost him his chance. There is much to be said in favor of behavioral, personality development, and people management skills helping engineers land their dream jobs. We need to reinforce these additional competencies as key elements of continuous learning.

I am sure you can think of so many more reasons why our engineering graduates are feeling the pinch of rising unemployment more than ever. These problems have been around for a while now and if they still haven’t changed, I don’t expect them to change either. Well, not to be predicting doom, but they won’t change fast. People need to think beyond just getting a job. While learning for learning’s sake and doing the job that you love to do is utopia; the first step toward it would be to find a middle ground between the ideal and reality. Keep jobs as a priority, but make people attain different goals to achieve it. Put out industry relevant problems and a job opportunity for everyone who can solve the problem within constraints. Not only is this industry relevant, it also lays emphasis on the importance of learning the basics, as the stronger your foundations, the quicker and better you can solve these programs. Apart from redesigning curricula and getting competent tutors, students need awareness and exposure via industry interaction.

Like they say, it is insanity to keep doing the same thing again and again and expecting a different result. Understanding is the first step, resolving the next.

On-Demand Webinar

Popular posts like this

1. How to hire the best developer talent at your next career fair

2. How to ensure your tech talent pool is poaching proof

3. 5 Tips to source tech talent without your local staffing agency’s help

Here is a Free trial to tech recruitment software to hire your first candidate!

Subscribe to The HackerEarth Blog

Get expert tips, hacks, and how-tos from the world of tech recruiting to stay on top of your hiring!

Author
Raghu Mohan
Calendar Icon
December 4, 2016
Timer Icon
3 min read
Share

Hire top tech talent with our recruitment platform

Access Free Demo
Related reads

Discover more articles

Gain insights to optimize your developer recruitment process.

The Mobile Dev Hiring Landscape Just Changed

Revolutionizing Mobile Talent Hiring: The HackerEarth Advantage

The demand for mobile applications is exploding, but finding and verifying developers with proven, real-world skills is more difficult than ever. Traditional assessment methods often fall short, failing to replicate the complexities of modern mobile development.

Introducing a New Era in Mobile Assessment

At HackerEarth, we're closing this critical gap with two groundbreaking features, seamlessly integrated into our Full Stack IDE:

Article content

Now, assess mobile developers in their true native environment. Our enhanced Full Stack questions now offer full support for both Java and Kotlin, the core languages powering the Android ecosystem. This allows you to evaluate candidates on authentic, real-world app development skills, moving beyond theoretical knowledge to practical application.

Article content

Say goodbye to setup drama and tool-switching. Candidates can now build, test, and debug Android and React Native applications directly within the browser-based IDE. This seamless, in-browser experience provides a true-to-life evaluation, saving valuable time for both candidates and your hiring team.

Assess the Skills That Truly Matter

With native Android support, your assessments can now delve into a candidate's ability to write clean, efficient, and functional code in the languages professional developers use daily. Kotlin's rapid adoption makes proficiency in it a key indicator of a forward-thinking candidate ready for modern mobile development.

Breakup of Mobile development skills ~95% of mobile app dev happens through Java and Kotlin
This chart illustrates the importance of assessing proficiency in both modern (Kotlin) and established (Java) codebases.

Streamlining Your Assessment Workflow

The integrated mobile emulator fundamentally transforms the assessment process. By eliminating the friction of fragmented toolchains and complex local setups, we enable a faster, more effective evaluation and a superior candidate experience.

Old Fragmented Way vs. The New, Integrated Way
Visualize the stark difference: Our streamlined workflow removes technical hurdles, allowing candidates to focus purely on demonstrating their coding and problem-solving abilities.

Quantifiable Impact on Hiring Success

A seamless and authentic assessment environment isn't just a convenience, it's a powerful catalyst for efficiency and better hiring outcomes. By removing technical barriers, candidates can focus entirely on demonstrating their skills, leading to faster submissions and higher-quality signals for your recruiters and hiring managers.

A Better Experience for Everyone

Our new features are meticulously designed to benefit the entire hiring ecosystem:

For Recruiters & Hiring Managers:

  • Accurately assess real-world development skills.
  • Gain deeper insights into candidate proficiency.
  • Hire with greater confidence and speed.
  • Reduce candidate drop-off from technical friction.

For Candidates:

  • Enjoy a seamless, efficient assessment experience.
  • No need to switch between different tools or manage complex setups.
  • Focus purely on showcasing skills, not environment configurations.
  • Work in a powerful, professional-grade IDE.

Unlock a New Era of Mobile Talent Assessment

Stop guessing and start hiring the best mobile developers with confidence. Explore how HackerEarth can transform your tech recruiting.

Vibe Coding: Shaping the Future of Software

A New Era of Code

Vibe coding is a new method of using natural language prompts and AI tools to generate code. I have seen firsthand that this change makes software more accessible to everyone. In the past, being able to produce functional code was a strong advantage for developers. Today, when code is produced quickly through AI, the true value lies in designing, refining, and optimizing systems. Our role now goes beyond writing code; we must also ensure that our systems remain efficient and reliable.

From Machine Language to Natural Language

I recall the early days when every line of code was written manually. We progressed from machine language to high-level programming, and now we are beginning to interact with our tools using natural language. This development does not only increase speed but also changes how we approach problem solving. Product managers can now create working demos in hours instead of weeks, and founders have a clearer way of pitching their ideas with functional prototypes. It is important for us to rethink our role as developers and focus on architecture and system design rather than simply on typing c

The Promise and the Pitfalls

I have experienced both sides of vibe coding. In cases where the goal was to build a quick prototype or a simple internal tool, AI-generated code provided impressive results. Teams have been able to test new ideas and validate concepts much faster. However, when it comes to more complex systems that require careful planning and attention to detail, the output from AI can be problematic. I have seen situations where AI produces large volumes of code that become difficult to manage without significant human intervention.

AI-powered coding tools like GitHub Copilot and AWS’s Q Developer have demonstrated significant productivity gains. For instance, at the National Australia Bank, it’s reported that half of the production code is generated by Q Developer, allowing developers to focus on higher-level problem-solving . Similarly, platforms like Lovable or Hostinger Horizons enable non-coders to build viable tech businesses using natural language prompts, contributing to a shift where AI-generated code reduces the need for large engineering teams. However, there are challenges. AI-generated code can sometimes be verbose or lack the architectural discipline required for complex systems. While AI can rapidly produce prototypes or simple utilities, building large-scale systems still necessitates experienced engineers to refine and optimize the code.​

The Economic Impact

The democratization of code generation is altering the economic landscape of software development. As AI tools become more prevalent, the value of average coding skills may diminish, potentially affecting salaries for entry-level positions. Conversely, developers who excel in system design, architecture, and optimization are likely to see increased demand and compensation.​
Seizing the Opportunity

Vibe coding is most beneficial in areas such as rapid prototyping and building simple applications or internal tools. It frees up valuable time that we can then invest in higher-level tasks such as system architecture, security, and user experience. When used in the right context, AI becomes a helpful partner that accelerates the development process without replacing the need for skilled engineers.

This is revolutionizing our craft, much like the shift from machine language to assembly to high-level languages did in the past. AI can churn out code at lightning speed, but remember, “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” Use AI for rapid prototyping, but it’s your expertise that transforms raw output into robust, scalable software. By honing our skills in design and architecture, we ensure our work remains impactful and enduring. Let’s continue to learn, adapt, and build software that stands the test of time.​

Ready to streamline your recruitment process? Get a free demo to explore cutting-edge solutions and resources for your hiring needs.

Guide to Conducting Successful System Design Interviews in 2025

What is Systems Design?

Systems Design is an all encompassing term which encapsulates both frontend and backend components harmonized to define the overall architecture of a product.

Designing robust and scalable systems requires a deep understanding of application, architecture and their underlying components like networks, data, interfaces and modules.

Systems Design, in its essence, is a blueprint of how software and applications should work to meet specific goals. The multi-dimensional nature of this discipline makes it open-ended – as there is no single one-size-fits-all solution to a system design problem.

What is a System Design Interview?

Conducting a System Design interview requires recruiters to take an unconventional approach and look beyond right or wrong answers. Recruiters should aim for evaluating a candidate’s ‘systemic thinking’ skills across three key aspects:

How they navigate technical complexity and navigate uncertainty
How they meet expectations of scale, security and speed
How they focus on the bigger picture without losing sight of details

This assessment of the end-to-end thought process and a holistic approach to problem-solving is what the interview should focus on.

What are some common topics for a System Design Interview

System design interview questions are free-form and exploratory in nature where there is no right or best answer to a specific problem statement. Here are some common questions:

How would you approach the design of a social media app or video app?

What are some ways to design a search engine or a ticketing system?

How would you design an API for a payment gateway?

What are some trade-offs and constraints you will consider while designing systems?

What is your rationale for taking a particular approach to problem solving?

Usually, interviewers base the questions depending on the organization, its goals, key competitors and a candidate’s experience level.

For senior roles, the questions tend to focus on assessing the computational thinking, decision making and reasoning ability of a candidate. For entry level job interviews, the questions are designed to test the hard skills required for building a system architecture.

The Difference between a System Design Interview and a Coding Interview

If a coding interview is like a map that takes you from point A to Z – a systems design interview is like a compass which gives you a sense of the right direction.

Here are three key difference between the two:

Coding challenges follow a linear interviewing experience i.e. candidates are given a problem and interaction with recruiters is limited. System design interviews are more lateral and conversational, requiring active participation from interviewers.

Coding interviews or challenges focus on evaluating the technical acumen of a candidate whereas systems design interviews are oriented to assess problem solving and interpersonal skills.

Coding interviews are based on a right/wrong approach with ideal answers to problem statements while a systems design interview focuses on assessing the thought process and the ability to reason from first principles.

How to Conduct an Effective System Design Interview

One common mistake recruiters make is that they approach a system design interview with the expectations and preparation of a typical coding interview.
Here is a four step framework technical recruiters can follow to ensure a seamless and productive interview experience:

Step 1: Understand the subject at hand

  • Develop an understanding of basics of system design and architecture
  • Familiarize yourself with commonly asked systems design interview questions
  • Read about system design case studies for popular applications
  • Structure the questions and problems by increasing magnitude of difficulty

Step 2: Prepare for the interview

  • Plan the extent of the topics and scope of discussion in advance
  • Clearly define the evaluation criteria and communicate expectations
  • Quantify constraints, inputs, boundaries and assumptions
  • Establish the broader context and a detailed scope of the exercise

Step 3: Stay actively involved

  • Ask follow-up questions to challenge a solution
  • Probe candidates to gauge real-time logical reasoning skills
  • Make it a conversation and take notes of important pointers and outcomes
  • Guide candidates with hints and suggestions to steer them in the right direction

Step 4: Be a collaborator

  • Encourage candidates to explore and consider alternative solutions
  • Work with the candidate to drill the problem into smaller tasks
  • Provide context and supporting details to help candidates stay on track
  • Ask follow-up questions to learn about the candidate’s experience

Technical recruiters and hiring managers should aim for providing an environment of positive reinforcement, actionable feedback and encouragement to candidates.

Evaluation Rubric for Candidates

Facilitate Successful System Design Interview Experiences with FaceCode

FaceCode, HackerEarth’s intuitive and secure platform, empowers recruiters to conduct system design interviews in a live coding environment with HD video chat.

FaceCode comes with an interactive diagram board which makes it easier for interviewers to assess the design thinking skills and conduct communication assessments using a built-in library of diagram based questions.

With FaceCode, you can combine your feedback points with AI-powered insights to generate accurate, data-driven assessment reports in a breeze. Plus, you can access interview recordings and transcripts anytime to recall and trace back the interview experience.

Learn how FaceCode can help you conduct system design interviews and boost your hiring efficiency.

Top Products

Explore HackerEarth’s top products for Hiring & Innovation

Discover powerful tools designed to streamline hiring, assess talent efficiently, and run seamless hackathons. Explore HackerEarth’s top products that help businesses innovate and grow.
Frame
Hackathons
Engage global developers through innovation
Arrow
Frame 2
Assessments
AI-driven advanced coding assessments
Arrow
Frame 3
FaceCode
Real-time code editor for effective coding interviews
Arrow
Frame 4
L & D
Tailored learning paths for continuous assessments
Arrow
Get A Free Demo