Closing the gap between software engineering education and industrial needs

According to different reports, many recent software engineering graduates often face difficulties when beginning their professional careers, due to misalignment of the skills learnt in their university education with what is needed in industry. To address that need, many studies have been conducted to align software engineering education with industry needs. To synthesize that body of knowledge, we present in this paper a systematic literature review (SLR) which summarizes the findings of 33 studies in this area. By doing a meta-analysis of all those studies and using data from 12 countries and over 4,000 data points, this study will enable educators and hiring managers to adapt their education / hiring efforts to best prepare the software engineering workforce.

💡 Research Summary

This paper presents a systematic literature review (SLR) and meta‑analysis of 33 empirical studies that investigate the alignment between software engineering (SE) education and industry needs. The authors followed the established SLR protocol for software engineering, searching Google Scholar with a Boolean query that combined terms related to educational or knowledge needs, desired skills, and software engineers/developers. From an initial pool of 94 papers (published between 1995 and 2018), a voting process among the authors narrowed the set to 33 papers that met two strict inclusion criteria: (1) the study must be based on empirical data (surveys, interviews, or similar) and (2) it must explicitly address the alignment of SE curricula with industry requirements.

The selected studies span 12 countries and collectively contain up to 4,132 respondents, providing a geographically diverse evidence base. The United States contributes the largest share (15 papers), followed by Canada (4), South Africa (4), New Zealand (2), and Spain (2); the remaining seven countries each appear in a single study. Because each primary study used its own set of SE topics—ranging from SWEBOK versions (1999, 2004, 2014) to IEEE SEEK, ACM curricula, or ad‑hoc lists—the authors harmonized all topics to the latest SWEBOK 3.0 framework, which defines 15 Knowledge Areas (KAs): Requirements, Design & Architecture, Development (Programming), Testing, Maintenance, Configuration Management, Project Management, SE Process, SE Models & Methods, Quality, Professional Practice, Economics, Computing Foundations, Engineering Foundations, and Mathematical Foundations.

For each primary study, the authors extracted the ranking of importance that respondents assigned to individual SE topics. Rankings were normalized to a 0‑1 scale, then transformed into an “importance metric” by computing 1 – (normalized rank). This allowed aggregation across studies despite differing numbers of topics and different ranking scales. The metric was then averaged for each KA across all papers, producing a composite importance score per knowledge area. The same procedure was repeated for the subset of papers published in the most recent five years (2013‑2018) to capture temporal trends.

The overall meta‑analysis reveals that Requirements, Design, and Testing receive the highest importance scores across the entire corpus, confirming that traditional technical competencies remain central to industry expectations. However, the recent‑paper subset shows a shift: Professional Practice, Project Management, and Testing become the top three areas. This indicates a growing emphasis on non‑technical, “soft” competencies such as ethics, teamwork, communication, and project coordination. The authors interpret this shift as evidence that while core engineering skills are still needed, the ability to work effectively in multidisciplinary, agile environments is becoming equally critical.

In addition to identifying the most valued KAs, the review extracts reported knowledge gaps. Four recurring gaps emerge across multiple studies: (1) Requirements elicitation and management – industry expects graduates to handle complex stakeholder negotiations and traceability, which curricula often under‑represent; (2) Design and architectural patterns – depth of coverage on modular design, architectural styles, and design patterns is insufficient; (3) Automated testing and CI/CD pipelines – practical skills in unit, integration, and system testing, as well as continuous integration, are frequently lacking; (4) Collaboration and communication – agile team dynamics, conflict resolution, and professional etiquette are not systematically taught.

The paper discusses methodological limitations. The search was limited to English‑language, peer‑reviewed sources indexed by Google Scholar, potentially omitting relevant gray literature or non‑English studies. The reliance on self‑reported survey data introduces response bias, and the uneven geographic distribution (e.g., heavy U.S. representation) may affect the generalizability of findings. Moreover, the heterogeneity of survey instruments and sample sizes across primary studies reduces the statistical power of the meta‑analysis.

From a practical standpoint, the authors propose concrete actions for educators and hiring managers. Universities should re‑align curricula with the SWEBOK 3.0 knowledge areas, placing greater weight on professional practice and project management modules, and adopt project‑based learning (PBL), capstone projects, and industry‑sponsored internships to embed real‑world contexts. Soft‑skill development—teamwork, communication, ethical decision‑making—should be embedded throughout the program rather than relegated to isolated workshops. For recruiters, the study recommends augmenting technical assessments with structured behavioral interviews, situational judgment tests, or portfolio reviews that explicitly evaluate professional practice and project‑management capabilities.

In conclusion, by aggregating data from 33 empirical investigations and over four thousand respondents, this work provides a robust, evidence‑based picture of the current and evolving skill demands in software engineering. It demonstrates that while foundational technical knowledge (requirements, design, testing) remains indispensable, the industry’s appetite for professional practice and project‑management expertise is rising sharply. Aligning educational programs with these insights can reduce the persistent “skills gap,” improve graduate employability, and ultimately strengthen the software engineering workforce.