From engineering education to engineering employability.

Executive summary

Graduation is not the same achievement as professional readiness.

Engineering employability deserves to be examined as a capability-development problem, not merely as a curriculum-completion, placement-training or software-tool problem.

A degree records serious academic achievement. Professional work asks a further question: can the graduate use that learning when the situation is unfamiliar, the evidence incomplete and the outcome consequential?

Technical knowledge is indispensable. So are the acts that give it force in practice: framing a problem, choosing relevant evidence, using tools with judgement, explaining a decision, working with others and taking responsibility for what follows.

This paper connects professional standards, research on engineering practice and learning science around one argument. Employability is broader than employment. Capability develops through disciplinary use, not alongside it as a generic add-on. And the path from remembering knowledge to coordinating professional performance contains educational achievements that a degree, by itself, may not fully reveal.

01 · The problem

The familiar pathway contains an untested assumption.

Students move through a familiar sequence: subjects, laboratories, projects, examinations, degree, labour market. Each step matters. The assumption is that completing the sequence also establishes readiness to perform engineering work.

But academic success and professional readiness do not ask exactly the same thing. Passing a subject can show understanding and procedural competence. It may not show whether a learner can recognise when that knowledge applies, work through ambiguity, evaluate incomplete evidence or stand behind a decision. Knowing a software package presents the same problem: operation is not yet engineering performance.

The International Labour Organization defines employability through portable competencies and qualifications that help people secure and retain work, move between jobs and adapt to changing technology and labour markets.1 Employment is messier. Growth, sectoral demand, geography and recruitment practice all shape it. A capable graduate may be unemployed; an employed graduate may still be developing the capabilities their role will eventually require. Placement rate, therefore, cannot stand as a complete measure of employability.

02 · What standards already say

Engineering education itself already recognises that knowledge is not enough.

Major professional standards already frame readiness as something graduates must both know and be able to do. ABET, for example, includes complex problem solving, design, communication, ethical and professional judgement, teamwork, experimentation, data interpretation and continued learning.2

The International Engineering Alliance expects graduates to investigate complex problems, select and use appropriate tools while recognising their limitations, consider societal and sustainability consequences, act ethically, collaborate, communicate, manage activity and engage in lifelong learning.3 India's National Board of Accreditation aligns its undergraduate framework with these attributes.4 India's National Skills Qualification Framework similarly distinguishes theoretical knowledge, professional and technical skill, employability-related capability, learning outcomes and responsibility.5

03 · What engineers do

Professional engineering intertwines technical work with human work.

Standards describe intended outcomes. Research on engineering practice asks what the work actually demands. Honor Passow and Christian Passow brought together 27 quantitative studies, 25 qualitative studies and evidence from approximately 36,100 engineering job advertisements.6

The synthesis resists a clean split between “technical” and “human” work. Engineers solve problems by coordinating communication, information gathering, decision making, initiative and responsibility with disciplinary knowledge.6 Winberg and colleagues reach a similar conclusion: engineering knowledge and professional skills are interdependent.7

Picture a system failure. The engineer reads the documentation, separates observation from assumption, chooses a test, interprets the measurement and decides whether the evidence is strong enough to release the system. Then the decision must be recorded and explained. The work never pauses to announce where the technical part ends and the human part begins.

Personal and professional capabilities should be treated separately enough to understand and develop them, but not separately enough to pretend that engineering work can succeed without them.

04 · Learning science

Knowing something and being able to use it are different educational achievements.

Learning science calls the crucial move transfer: using what has been learned appropriately in a new situation. Retention keeps information available. Transfer makes it usable. Deeper learning can support both.8

A student may reproduce a derivation and still miss the moment when its principle applies. A familiar numerical problem becomes harder when the same concept arrives inside a noisy, incomplete situation. Memory has not necessarily failed. The learning has not travelled.

Accumulated knowledge remains the foundation. Engineering competence appears when a person can judge what is relevant, why it applies and whether the result is credible.

05 · Context matters

Generic skills do not automatically transfer everywhere.

A course in communication or critical thinking can be valuable. What it cannot guarantee is automatic transfer into every engineering discipline, problem and context. More than a century of research offers little support for cognitive competencies that travel everywhere without relevant knowledge and practice.8

Context gives a capability its engineering meaning. Communication becomes the act of deciding what evidence matters, how much uncertainty to reveal and what an audience needs in order to act. Judgement depends on enough technical knowledge and experience to recognise consequences.

CDIO therefore integrates personal, interpersonal and professional capabilities with disciplinary learning rather than adding them after the curriculum is complete.9 An engineering subject can be both a body of knowledge and the place where students learn how to think, communicate and decide with that knowledge.

06 · Attainment, not exposure

“We taught it” and “the student can do it” are different statements.

Teaching is an input. Attainment is an observed outcome. The distinction matters because participation can look like progress: a student joins a team project, submits a laboratory report, gives a presentation or uses the same software many times. None of those events, on its own, shows how well the student can collaborate, reason from evidence, explain a decision or recognise a model's limits.

ABET requires programmes to assess the extent to which student outcomes are attained.2 NBA's outcome-based model makes the same boundary visible: curriculum inputs matter, but they cannot guarantee outcomes.4

The concern also has history. A 2011 World Bank study of employers recruiting newly graduated engineers in India found expectations extending beyond technical capability into employability and communication.10 That evidence cannot size a gap in 2026; it shows only that the education-to-work translation problem predates generative AI. A 2025 review of 26 engineering-employability measures adds a current warning: the field still lacks conceptual agreement and needs clearer, discipline-specific, better-validated approaches.11

08 · What can be established

The evidence supports five conclusions with reasonable confidence.

Together, these conclusions justify a sharper inquiry into capability. They do not yet justify one institutional response.

09 · What this paper does not conclude

Intellectual discipline matters at this stage.

The evidence establishes a problem worth investigating. It does not support a verdict that engineering curricula are fundamentally defective, that all graduates are unemployable or that employers possess a perfect definition of employability. It does not show that every capability belongs in every subject, that internships automatically produce competence or that AI is eliminating engineering employment.

One boundary matters most: the paper has not established what additional institutional structures are required. That decision needs a more precise model of capability and better evidence of how it develops.

10 · Change posture

The task is enablement, not sorting students.

This is not a story about inherent achievers and non-achievers. It is about opportunity. A student can carry real knowledge and potential yet have too few chances to practise, explain or demonstrate how they reason when the situation changes.

The practical response can begin small: one authentic task, one explanation of the reasoning, one review of the evidence. Repeated carefully, those moments can make capability visible early enough to develop it.

Conclusion

Engineering education does not end with what a student knows.

Technical knowledge remains indispensable. The issue is whether it alone adequately represents what an engineer must become capable of doing. The combined evidence indicates that it does not.

Engineering practice requires knowledge to be interpreted, transferred, combined, applied, tested, communicated and exercised with judgement and responsibility. Its professional value depends on what that knowledge enables the student to do, how effectively it can be applied in context and whether that capability can be demonstrated.

The next stage should not begin by adding more courses, tools or training programmes. It should begin by understanding the architecture of capability itself.