Insights
Software-defined vehicle talent scarcity in the Nordics: Build, buy, or partner?
Software increasingly shapes vehicle functionality, customer experience, and lifecycle value, intensifying competition for software-defined vehicle (SDV) talent across the Nordics. Keeping pace with SDV transformation requires a workforce strategy that combines internal capability development, strategic recruitment, and engineering partnerships. Automotive organizations should retain ownership of the architecture, intellectual property, and expertise that differentiate their vehicles while using partners to access scarce specialists, expand engineering capacity, and accelerate delivery. This balanced approach strengthens Nordic automotive innovation without sacrificing long-term control.
DIVIDER
Introduction: The talent bottleneck behind SDV transformation
Automotive competition is shifting toward software-controlled functionality, connected experiences, continuous improvement, and digital services that extend value beyond the initial sale. Yet access to the required expertise remains a significant obstacle. According to the World Economic Forum’s Future of Jobs Report 2025, skills gaps in the labor market are the primary barrier to business transformation, cited by 63% of surveyed employers.
Across the Nordics, OEMs, suppliers, and mobility companies are advancing electrification and SDV programs while competing for the same software-defined vehicle talent. Addressing the SDV talent shortage involves securing the right combination of automotive, software, systems, cloud, cybersecurity, and data expertise, not merely filling positions. Building every capability internally can lengthen timelines and increase costs Leaders must decide which capabilities to develop, hire for, or acquire through engineering partnerships. These decisions make workforce strategy central to software-defined vehicle transformation.
DIVIDER
Why are SDVs changing automotive talent requirements?
A software-defined vehicle uses software as the primary means of controlling, updating, and enhancing functionality throughout its lifecycle. This model replaces many distributed, hardware-bound functions with centralized or zonal architectures, supported by integrated vehicle software platforms and operating systems.
That transition changes what vehicles can deliver and how they are developed. Software enables connected services, personalization, feature activation, security improvements, and over-the-air updates that introduce new capabilities after production. It also creates opportunities for subscription services and other recurring revenue models. As a result, automotive software development continues long after a vehicle leaves the factory.
Software-defined vehicle engineering requires coordinated expertise across vehicle hardware, embedded software, cloud platforms, data, cybersecurity, functional safety, and systems engineering. Mechanical engineering remains fundamental to performance, safety, and reliability. Software capability is becoming an equally important source of differentiation. Integrating physical systems with continuously evolving digital functionality depends on multidisciplinary teams.
DIVIDER
Why is SDV talent difficult to secure in the Nordics?
Nordic automotive organizations recruit from a highly skilled but limited engineering labor market. According to Statistics Sweden’s 2025 employer survey, Swedish employers reported shortages of 4,000 highly educated IT professionals, primarily software and systems developers, and 4,300 engineers and technicians. Automotive companies must compete for this limited talent across multiple industries.
OEMs and suppliers also compete with telecom, cloud, AI, defense, energy, and other technology employers. The Gothenburg automotive ecosystem brings manufacturers, suppliers, mobility companies, and researchers together, but concentrates demand for similar capabilities. Electrification, connected mobility, autonomous-driving initiatives, and SDV programs are advancing at the same time.
Global companies can also recruit Nordic engineers remotely without establishing a substantial regional presence. The rarest candidates combine software expertise with vehicle architecture, functional safety, cybersecurity, validation, or regulatory knowledge. These intersections make the software-defined vehicle talent shortage in Europe more difficult to resolve through conventional hiring alone. Lengthy recruitment cycles and rising compensation can leave critical Nordic EV and SDV development programs without the specialized talent required to maintain delivery schedules.
DIVIDER
What skills are required for software-defined vehicle development?
SDV programs require more than additional software developers. They depend on automotive software talent that can connect traditionally separate engineering domains:
- Vehicle software and embedded engineering: Embedded systems, in-vehicle software, Classic AUTOSAR and Adaptive AUTOSAR, vehicle operating systems, middleware, zonal architectures, and hardware-software integration form the vehicle’s digital foundation.
- Cloud, data, and connected services: Cloud-native development, edge computing, data engineering, AI, APIs, connected vehicle platforms, and digital services extend vehicle functionality through connected data and off-vehicle systems.
- Security, safety, and lifecycle management: Automotive cybersecurity, secure OTA updates, functional safety, software maintenance, traceability, and regulatory compliance protect vehicles as their software evolves.
- Engineering integration and delivery: Model-based systems engineering, DevOps, automated testing, validation, product engineering, and cross-domain architecture coordinate development across complex systems.
The greatest talent shortages occur at the intersections, where engineers must apply modern software practices within automotive-grade requirements for safety, reliability, performance, and long product lifecycles. These hybrid capabilities take years to develop and rarely align neatly with conventional job descriptions or functional silos.
DIVIDER
Should automotive companies build, buy, or partner for SDV talent?
The right model depends on a skill’s strategic importance, how quickly it is needed, and whether demand will persist. Strong SDV workforce planning assigns each capability to the model best suited to its business value and delivery requirements.
Build capabilities that create lasting differentiation
Building means reskilling employees, creating internal career paths, establishing engineering practices, and developing institutional knowledge. This approach best fits capabilities tied to product strategy, platform architecture, differentiating software, proprietary data, and critical IP. Keeping these areas internal strengthens strategic control, knowledge retention, engineering continuity, and alignment between product engineering and the vehicle roadmap.
Organizations considering how to build software-defined vehicle teams must also account for the time needed. Experienced instructors and mentors are scarce, employees need opportunities to apply new skills, and retention pressure can undermine progress. Internal development creates durable capability, but it rarely resolves an immediate capacity gap or accelerates near-term delivery.
Buy permanent expertise where ownership matters
The buy strategy can include hiring software-defined vehicle engineers and technical leaders or acquiring a specialist company or established team. Both approaches provide direct access to scarce SDV talent and can help build lasting internal capabilities. In some cases, an acquisition may be undertaken primarily to secure specialized technical capabilities.
This approach works best when permanent technical authority is required, or the expertise will remain strategically important. Priority hires may include platform architects, cybersecurity leaders, systems engineering authorities, and senior product owners who can guide SDV development teams.
Recruiting individuals and acquiring a company are materially different decisions. The automotive software engineer shortage can produce lengthy hiring cycles, rising compensation, and retention pressure. Acquisitions introduce additional questions involving valuation, cultural integration, and technology compatibility. Neither approach provides instant capability if new hires or acquired personnel can't integrate into existing teams and decision structures.
Partner when speed, specialization, or scale is critical
Partners can provide established teams, rare expertise, flexible engineering capacity, and global delivery resources without the delay of recruiting an entire internal organization. They can be particularly effective in software platform modernization, cloud and connected services, cybersecurity, testing, large transformation programs, and product acceleration.
Partnering does not eliminate the need for internal leadership. Successful engagements require clear accountability, architectural ownership, security controls, IP provisions, performance measures, and structured knowledge transfer. Global engineering services should extend internal capability and accelerate delivery without surrendering control of the product, platform, or decisions that drive lasting differentiation.
DIVIDER
Why are hybrid SDV workforce models often the strongest?
No single sourcing model can meet every SDV requirement. A hybrid SDV workforce strategy allows automotive organizations to retain product vision, platform architecture, governance, differentiating IP, and critical technical authority while gaining access to capabilities they cannot develop quickly enough internally.
Organizations can recruit selectively for leadership and enduring strategic roles, then reskill experienced automotive engineers to connect vehicle knowledge with software-centric development. Partners can supplement these teams with specialized skills, flexible capacity, global engineering services, and delivery support during major programs or periods of peak demand.
The right balance will differ by capability and evolve as internal maturity, product priorities, and technology requirements change. Partnerships should strengthen the organization rather than create unmanaged dependency. Joint teams, shared engineering practices, and structured knowledge transfer help employees build new capabilities while external specialists accelerate delivery. This approach makes software-defined vehicle workforce planning an adaptable part of long-term automotive innovation.
DIVIDER
A practical framework for SDV talent decisions
A repeatable framework begins by evaluating each capability individually rather than applying one sourcing model across the entire program. Leaders addressing the software-defined vehicle skills gap should consider:
- Does the capability differentiate the vehicle or customer experience?
- Must its knowledge and IP remain inside the organization?
- Is demand permanent, temporary, or likely to fluctuate by program?
- How quickly must the capability become operational?
- Can you realistically recruit sufficiently experienced people?
- Does the work require a rare combination of automotive and software expertise?
- Does the work require permanent technical leadership, or is the need primarily for execution capacity?
- What are the business and delivery consequences of waiting?
- Can a partner transfer knowledge instead of supplying capacity alone?
- How will architecture, security, quality, IP, and accountability be governed?
The answers inform a build-buy-partner strategy. Build when a capability creates durable competitive differentiation and warrants long-term institutional investment. Buy when permanent internal expertise or technical authority is essential. Partner when delivery speed, specialized skills, or flexible scale matter most, particularly for major programs such as software platform modernization.
DIVIDER
What should Nordic automotive leaders do next?
Software-defined vehicle workforce planning should begin with the product roadmap, not a list of vacancies. Leaders can create an actionable plan by:
- Mapping the capabilities required by product and technology priorities.
- Assessing current skills, engineering capacity, dependencies, and delivery risks.
- Identifying the capabilities that create meaningful competitive differentiation.
- Assigning a build, buy, partner, or hybrid model to each capability.
- Prioritizing gaps by business consequence and program urgency.
- Establishing governance, security, IP, accountability, and knowledge-transfer expectations.
- Reassessing the SDV workforce strategy as platforms, technologies, and internal maturity evolve.
This process integrates workforce decisions with product, platform, automotive R&D, and investment planning rather than reducing workforce strategy to recruitment.
DIVIDER
Conclusion: Talent strategy is now product strategy
Technology alone does not determine the pace of software-defined vehicle transformation. Progress often depends on securing the right talent and engineering capacity at the right time. Building every capability internally can slow delivery, while excessive dependence on external teams can weaken strategic ownership. Nordic automotive organizations need an intentional hybrid model that protects differentiating knowledge while expanding access to scarce expertise.
Companies that align workforce decisions with product differentiation, delivery urgency, and long-term capability needs can innovate, scale, and compete more effectively in the software-defined future.
Accelerate your software-defined vehicle strategy
Execution requires the right engineering talent, delivery scale, and platform support. UST combines specialized SDV capabilities, global engineering services, and digital and product engineering to help OEMs and suppliers modernize vehicle platforms and deliver complex SDV programs. This approach strengthens internal teams while providing access to specialized skills and flexible delivery capacity. Discover how UST supports Nordic automotive software development.
DIVIDER
FAQs
What is a software-defined vehicle?
A software-defined vehicle uses software to control, update, and enhance functionality throughout its lifecycle. Manufacturers can deliver new features, services, performance improvements, and security updates after production.
Why is SDV talent difficult to find?
SDV development requires professionals who combine software engineering with automotive architecture, embedded systems, cybersecurity, functional safety, validation, and regulatory knowledge. Few professionals possess this multidisciplinary combination, and they are in demand across competing industries.
What skills are needed for SDV development?
Core SDV capabilities include embedded software, AUTOSAR, vehicle operating systems, cloud development, data engineering, AI, automotive cybersecurity, OTA updates, DevOps, automated testing, validation, and systems engineering.
How can automotive companies address the SDV skills gap?
Companies can address SDV talent shortages by reskilling employees, recruiting permanent technical leaders, and partnering for specialized expertise, flexible capacity, and faster delivery.
Should organizations hire or partner for SDV expertise?
Hire when permanent internal ownership or technical authority is essential. Partner when specialized skills, speed, or flexible scale matter most. Many organizations need both approaches.
What roles are most difficult to recruit?
Scarce roles include vehicle software architects, embedded engineers, AUTOSAR specialists, cybersecurity leaders, cloud and data engineers, systems engineers, validation experts, and professionals who bridge multiple domains.
How does software-defined vehicle development differ from traditional automotive engineering?
Automotive software development continues throughout the vehicle lifecycle. It integrates hardware, software, cloud services, data, security, and continuous updates rather than ending when a vehicle enters production.
What is the best workforce strategy for SDV transformation?
A hybrid model is usually strongest: build differentiating capabilities internally, recruit enduring leadership and technical authority, and partner for specialized software-defined vehicle talent, flexible capacity, and faster delivery.
DIVIDER
Resources:
UST helps European engineering firm bolster automotive division and deliver 50% faster solutions
The automotive industry is redefining its foundation in the age of software and intelligence