BlackBerry QNX Research Reveals Rising Pressure on Software Engineers Leads to Critical Trade-Offs in Safety and Security

Mounting Pressure on Developers to Meet Tight Deadlines

The BlackBerry QNX survey, which included 1,000 embedded software developers and engineers worldwide, reveals that 75% of respondents often feel compelled to compromise on essential safety requirements due to urgent project deadlines. This growing tension highlights a critical challenge in the software development lifecycle: delivering innovative features quickly without sacrificing functional safety.

Such compromises are not without consequences. Nearly one-third of organizations reported that their operating systems lack the necessary safety certifications or only partially meet them. This gap leads to costly delays, with companies spending an average of $591,000 and 154 hours of resources to address evolving safety standards. These delays can cascade, affecting overall product launch schedules and market competitiveness.

The pressure to meet tight deadlines often forces teams to prioritize speed over thorough safety verification, increasing the risk of non-compliance with international safety standards. This environment creates a challenging balancing act for developers who must innovate rapidly while ensuring their products remain safe and reliable.

The Operating System Dilemma: Security, Cost, and Certification

Selecting the right operating system (OS) is a pivotal decision for embedded software projects. Developers prioritize security (54%), cost control (52%), and safety certifications (48%) when choosing an OS. However, the survey found that 74% of developers are considering switching their current OS, driven by challenges in meeting safety standards, security concerns, and performance issues.

Particularly, 61% of those required to comply with international safety standards find it extremely or very challenging to do so with their current OS. Security vulnerabilities and subpar performance are significant pain points, prompting developers to explore alternatives that better align with their safety and security needs.

This widespread dissatisfaction reflects the complexity of balancing multiple critical factors when selecting an OS. While cost and security remain top priorities, the inability to efficiently meet safety certifications often outweighs other considerations, leading to a high willingness among developers to change platforms.

Open-Source vs. Proprietary Platforms: Trade-Offs in Safety and Security

Open-source operating systems are the preferred choice for 44% of developers, with an additional 25% expressing no strong preference between open-source and proprietary options. The appeal of open-source platforms lies in their familiarity and accessibility, which can accelerate initial development phases.

However, open-source platforms often fall short in meeting rigorous safety certifications. Unlike proprietary systems that undergo extensive verification and testing to comply with international safety standards, many open-source options lack these certifications. This shortfall can lead to increased risk and additional work to achieve compliance, ultimately impacting project timelines and costs.

Security is another concern. The survey indicates that open-source OSs are more prone to security breaches (46%) compared to proprietary systems (40%). When breaches occur, 72% of affected developers report project delays, underscoring the operational impact of security vulnerabilities.

These findings highlight the trade-offs developers face: while open-source platforms offer flexibility and cost advantages, they often require additional effort to meet safety and security demands. Proprietary systems, though potentially more costly, provide pre-certified assurances that can reduce compliance burdens and improve reliability.

The Importance of Pre-Certified, Secure-by-Design Solutions

John Wall, SVP and Head of BlackBerry QNX, emphasizes that as the industry moves toward a 'Software-Defined Everything' era, prioritizing functional safety and security is essential. Pre-certified software solutions that are secure by design can help organizations meet regulatory requirements without sacrificing innovation speed or budget constraints.

Such solutions reduce the burden on development teams by minimizing the need for extensive verification and troubleshooting. This approach enables developers to focus on creating new features and enhancing system capabilities rather than addressing foundational safety and security issues.

Moreover, organizations that adopt pre-certified operating systems report fewer delays and lower costs associated with compliance, making these solutions a strategic investment for long-term success. This shift toward pre-certified platforms is crucial as software increasingly defines the functionality and safety of connected devices and infrastructure.

Security Patch Management and Project Timelines

Security remains a persistent challenge across the embedded software landscape. Although 73% of organizations prioritize OS security, the frequency of applying security patches varies widely, with an average gap of five weeks between updates. This delay can leave systems vulnerable to attacks and increase the risk of breaches.

Operating system issues have tangible impacts on project delivery. About 34% of organizations have missed deadlines due to OS-related problems, with an average delay of one month globally. These disruptions highlight the critical need for robust, secure, and well-maintained operating systems to support timely project execution.

The combination of delayed security updates and OS-related problems underscores the importance of selecting platforms that not only meet safety certifications but also maintain strong security postures through timely patching and proactive vulnerability management.

What this means

The findings from BlackBerry QNX’s research paint a clear picture of the complex environment in which embedded software developers operate. The pressure to innovate rapidly often conflicts with the rigorous demands of safety and security compliance, leading to compromises that can affect product quality and timelines. Choosing the right operating system—one that offers robust safety certifications, strong security features, and reliable performance—is critical to navigating these challenges. Pre-certified, secure-by-design solutions emerge as a promising path forward, enabling development teams to focus on innovation without sacrificing compliance or security. As embedded software continues to underpin critical systems across industries, addressing these trade-offs will be essential to building safer, more secure, and more reliable technology ecosystems.