Closing the Industry-Academia Skill Gap: A Guide for HODs & Deans

Every few months a Dean or an HOD asks me to recommend the one course that will close their industry gap. I never have a good answer, because the question itself contains the mistake. There is no single course that does it, and treating the gap as a missing course is exactly the reason it stays open year after year.

Eighteen years of sitting between universities and the companies that hire from them have taught me a consistent pattern. The colleges that close the gap do not find a better syllabus. They build a continuous connection to what industry actually does, and the curriculum stays current as a result of that connection rather than as a substitute for it.

The gap is a connection problem, not a content problem

The most useful reframe I can offer a college is this. The industry-academia gap is not mainly a problem of which topics appear in the syllabus. It is a problem of connection between the place that teaches and the place that hires.

You can see why in how the gap reopens. A college updates its curriculum, adds the subjects everyone says are important, and within two or three years the content is dated again, because the people teaching it have no live link to how the work has moved, and the course contains no real industry problem to keep it honest. The content was refreshed; the connection was not, so the refresh aged just as quickly as the version before it. A college that fixes the connection, by contrast, finds the content stays current almost on its own, because the teaching is plugged into live practice. That is the difference between chasing the curriculum and connecting it.

This is good news for a Dean, because connection is something a college can build deliberately, through relationships it controls, rather than a race against a syllabus it can never quite catch.

Think about the two colleges that produce different graduates from the same syllabus. On paper their curricula match, approved by the same university, listing the same subjects. One college’s faculty have recent industry contact, its courses carry real problems, and practitioners pass through its classrooms; the other’s teaching has none of that. The first college’s students graduate fluent in how the work is actually done, the second’s fluent only in how it is described. The syllabus did not separate them; the connection did. A Dean who has seen this happen stops believing the next content revision is the answer.

What industry wants from a graduate

Before building the connection, it helps to be clear about what industry is connecting the college to, because that has shifted too. The thing employers want from a fresh graduate has moved from specific tools toward durable capability.

Sangeeta Gupta, a Senior Vice President and the Chief Strategy Officer at NASSCOM, described the shift directly. She noted that companies are moving away from assessment-based hiring toward a student’s learning experience and problem-solving ability, and that hiring decisions now rest less on whether a candidate knows a particular language like Java or C++ and more on their ability to learn quickly and solve problems, because the specific skill in demand keeps changing. The same NASSCOM work points at the scale of the field a college is preparing students for: India’s engineering and research-and-development talent pool numbers in the high hundreds of thousands and is growing, with sharp increases in demand for digital engineering skills.

The implication for the classroom is liberating rather than daunting. If what industry wants is the ability to learn and reason, grounded in fundamentals, then a college does not have to teach every tool. It has to teach students to learn, give them real problems to reason about, and keep its teaching connected enough to industry that the problems are real ones.

Four ways to build the connection

When a college asks me how to build that connection in practice, I point to four things, in rough order of impact.

The first, and the highest-leverage, is faculty industry exposure. A teacher who has spent recent time inside industry, or who teaches alongside practitioners, refreshes not one course but every cohort they teach for years. Faculty connection is the multiplier that keeps the whole programme current, which is why NASSCOM’s own industry-designed skilling work places structured train-the-trainer effort at its centre.

The second is co-designed curriculum. Rather than writing the syllabus alone and hoping it matches, a college builds key modules with industry input, so the content reflects how the work is actually done. This does not mean handing the curriculum to a vendor; it means designing it together, with the college owning the result.

The third is real industry problems inside the course. A student who has worked on an actual problem from a real organisation, with its messiness and constraints, graduates connected to practice in a way no lecture delivers. Internships are one route to this; embedded project work using real industry problems is another, and often more controllable.

The fourth is practitioners in the classroom, as adjunct faculty who teach regularly rather than visit once. A working engineer teaching a module brings the current state of the field with them, and the continuity is what matters, the regular presence rather than the one-off talk. The four reinforce each other: a practitioner who teaches well is the natural person to host a faculty stint, and a co-designed module is the obvious place to set a real problem. Built together, they form a standing connection rather than four separate initiatives, which is why a college that pursues all four steadily ends up far more connected than one that does any of them in isolation.

Matching depth to where students are headed

Building connection raises a fair question: connection to what depth. Not every student needs the same intensity, and treating them as if they do wastes effort at both ends.

NASSCOM’s industry-designed framework is a useful guide here. It separates capability into core, applied, and advanced, and reserves the advanced depth for the roles that genuinely own real system outcomes, while most people need solid core and applied capability. Translated to a college, this means most students should reach a strong, connected, applied level, with the deeper specialisation built only for the minority heading into roles that demand it. A programme that pushes every student to the deepest level burns time the average student would spend better on breadth and fundamentals; one that stops at the shallowest fails the students headed for demanding work. Matching depth to destination is part of closing the gap intelligently rather than uniformly.

The distinction is practical, not abstract. Core capability is what every graduate needs to be useful: the fundamentals and an applied grasp of how they are used. Applied capability is being able to work on real systems competently, which is where the bulk of hiring sits. Advanced capability, the deep ownership of a system’s behaviour, safety, or scale, is genuinely needed only by a few, and it is expensive to build, so spending it on everyone is a poor trade. A connected curriculum makes this differentiation natural, because the industry link tells the college which depth each kind of role actually requires, rather than leaving it to guess and over-build.

Starting small: the first connection to build

A Dean hearing all this can feel it is too much to take on at once, so it is worth being concrete about the first, smallest version that still works. Connection does not have to be built across a whole department in a year; it is better built one solid link at a time.

The first link I usually suggest is a single co-taught module. Pick one important course, find one working practitioner from a firm within reach, and have them co-teach it and set one real problem from their work. That single move touches a faculty member, who learns alongside the practitioner, the students, who meet a live problem, and the relationship with the firm, which now has a reason to stay in touch. It is small enough to start this term and real enough to change something.

From that first link, the rest follows more easily than a Dean expects. The practitioner who co-taught well becomes the adjunct who returns. The firm that set one good problem becomes the partner that hosts a faculty stint. The faculty member who taught alongside industry carries it into their other courses. Connection compounds, which is why the first link matters more than its size: it is the seed of a network, not a one-off. A department that adds one real link a semester is, within a couple of years, genuinely connected, without ever having attempted a daunting all-at-once reform.

A department in Chhattisgarh that built the link

A department in a Chhattisgarh engineering college had updated its curriculum twice in four years and was frustrated that placements had not followed. The HOD was convinced the content was the problem and was preparing a third revision when we spoke.

The content was not really the problem. The two revisions had added current-looking subjects, but the teaching had no live link to industry: the faculty had not been inside a relevant company in years, and not one course contained a real industry problem. Students learned modern topics in a way disconnected from how the work was done, and recruiters read that disconnection in interviews.

Instead of a third content revision, the department built connection. It arranged short industry stints for a few core faculty, brought in two working engineers from firms in the region to co-teach modules and set real problems, and rebuilt one capstone around an actual problem from a local company. The syllabus on paper changed less than in either previous revision. The students changed far more, because they were now learning connected to practice, and the recruiter conversations improved within a cycle.

What the HOD noticed most was the change in the faculty, not just the students. The teachers who had spent time in industry came back with examples, war stories, and a sense of what mattered that no textbook had given them, and they carried it into every class, not only the co-taught one. The connection, in other words, kept paying out long after the stint ended, across cohorts the original effort never directly touched. The HOD’s third revision was quietly shelved; the connection had done what the content could not, and kept doing it.

What does not close the gap

It is worth being honest about the moves that look like closing the gap and do not, because colleges spend real effort on them. None of these is harmful; they simply do not substitute for connection.

A single guest lecture is a pleasant afternoon that changes little. An MOU that is signed and filed creates a record of intent and no activity. Buying a new tool or platform adds capability the faculty may not be connected enough to use well. Adding subjects to the syllabus, the most common move of all, refreshes content without refreshing the connection that keeps content alive. Each of these can become useful if it leads to continuous activity, faculty time in industry, students on real problems, practitioners teaching regularly, but as standalone gestures they produce the appearance of connection without its substance. The test for any initiative is simple: does it create a continuous link, or a one-time event that photographs well.

For a Dean or an HOD, the encouraging conclusion is that closing the gap is within reach and does not depend on a famous name or a big budget. It depends on building and keeping a connection to industry, relationship by relationship, which is exactly the kind of asset that compounds. To see how a continuous industry connection could be built into your department’s teaching, starting from a single link, the For Colleges / Universities page lays out the way we work with an institution on it.