QNX Research Finds Automotive Developers Spend More than a Third of Their Time on Software "Plumbing" Slowing SDV Innovation

A 2026 global survey of 1,100 automotive software developers found that software integration below the vehicle application layer consumes an average of 35% of developer effort; 19% spend at least half their time on it. Persistent integration challenges and rising security concerns accompany a more practical view of AI, while 76% say OEMs should prioritize application-layer innovation over software infrastructure.

Analysis

The investable signal is a cost-allocation problem, not evidence of near-term software revenue growth. Persistent integration work can absorb engineering capacity and delay customer-visible features, making delivery cadence and software-related cost control more important than broad “SDV” positioning. If OEMs respond by standardizing platforms or buying more middleware, integration-tool and engineering-service providers could benefit; if they instead build proprietary stacks, supplier leverage may weaken. Security pressure adds a potential recurring spend category, but the survey does not establish budgets, vendor wins, or realized losses. A more practical AI posture also argues against assuming rapid developer productivity gains: near-term value may accrue to validation, testing, and code-assurance workflows before OEMs reduce engineering headcount. The sample is useful as a friction indicator, not proof of industry-wide economics. Over 1–3 months, look for OEM software-spend disclosures, platform consolidation, and supplier design wins. Over 6–18 months, the key test is whether integration effort falls while release cadence and monetization improve. No clean directional trade is justified from this survey alone.

Key Decisions for Investors

• Stay neutral on broad automotive software exposure for now; the report provides no company-level spending, margin, or adoption data. Treat it as a diligence prompt, not an earnings revision.
• Watch for evidence that OEMs are consolidating software platforms or outsourcing integration. If confirmed in contracts or guidance, prioritize companies with demonstrable middleware, integration, testing, or automotive cybersecurity revenue—not firms relying only on SDV narrative.
• Avoid underwriting near-term labor-cost savings from AI. Revisit that view only if OEMs or suppliers disclose measurable reductions in development cycle time, validation costs, or engineering expense without slower releases.
• Falsifiers: OEM disclosures showing integration costs or release delays are declining; conversely, continued software program delays, cybersecurity incidents, or supplier guidance cuts would strengthen the view that execution friction is weighing on the sector.