A featured contribution from Leadership Perspectives: a curated forum reserved for leaders nominated by our subscribers and vetted by the Construction Tech Review Advisory Board.
Applus+ Idiada
A Blueprint for Leading Modern Software Engineering Teams
As Software Engineering Manager at Applus+ IDIADA, I create digital solutions that connect engineering and enterprise technology. My teams develop platforms that modernize test management systems, approval workflows and data infrastructure for global vehicle engineering programs.
On the technical side, I lead the architecture of systems like our Test Management platform. Our Data Fabric project turns raw test results into useful engineering insights through analytics tools.
For team building, I develop hybrid teams that combine experienced computer engineers with newer digital talent through targeted hiring and ongoing training in new technologies. This mix creates solutions that respect engineering fundamentals while improving operations.
Core Principles for Nurturing High Performance Engineering
My leadership approach balances innovation with practicality through three main principles:
First, I create psychological safety. Teams perform best when engineers can challenge ideas and analyze mistakes without fear, especially when building critical systems.
Second, I apply the right standards to the right projects. We build enterprise data platforms with high reliability, while internal tools focus on development speed. This prevents over-engineering and technical shortcuts across our work.
Third, I encourage continuous learning focused on real-world impact. Our training programs cover emerging concepts like vibe coding and adaptive cloud architectures, keeping our solutions cutting-edge and reliable.
Ultimately, I serve as both technical strategist and culture builder. My task is to align engineering excellence with business goals through systems that empower teams, embrace smart innovation and turn complex requirements into effective digital solutions.
Balancing Innovation with Scalable Architectures
I balance innovation with technical quality through structured flexibility. We use modular designs like microservices, creating safe spaces for experimentation while maintaining solid core systems.
Our continuous integration systems act as safety nets, with tests that validate new features against reliability standards. Every development cycle includes time for foundation work such as improving critical code, optimizing data handling and strengthening security.
We roll out changes gradually. New features first operate in shadow mode or with feature flags, allowing real-world testing without disrupting production. When updating legacy systems, we run old and new systems in parallel during transitions to ensure continuity while measuring performance. This approach keeps us focused on delivering value while systematically integrating proven innovations through yearly architecture reviews that align technical changes with business priorities.
A Culture of Growth
Continuous learning drives our technical progress and team unity. We include learning sprints, which are dedicated periods where engineers explore new concepts and apply them through challenges tied to current projects. Our mentorship program pairs senior architects with junior staff in alternating teacher/learner roles, creating two-way knowledge sharing that values experience while speeding up new skill adoption.
Every sprint allocates 15 percent of time for exploration, encouraging teams to analyze production issues as learning opportunities and try new tools in test environments. We use architecture whiteboards where engineers visualize complex systems, promoting collaborative learning.
This growth mindset continues in monthly meetings through learning talks, making knowledge sharing a regular habit rather than a special occasion.
Teams perform best when engineers can challenge ideas and analyze mistakes without fear, especially when building critical systems
Building Resilient, Future-Ready Teams
Build teams that value both stability and reinvention. Start by showing intellectual humility; openly review your own design decisions to normalize learning from mistakes. Establish “architectural foresight” through simple risk assessment exercises where junior staff lead discussions on future technology changes.
Treat your technology stack as a portfolio. Keep 70 percent in proven solutions, 25 percent in related innovations and 5 percent in experimental projects, adjusting yearly through collaborative tech reviews. Implement “innovation safeguards” such as automated compliance checks and failure limits that allow controlled risk-taking without major exposure.
Most importantly, build diverse teams through unconventional hiring. Some of our most transformative ideas came from engineers with non-traditional backgrounds seeing old problems in new ways. Remember, being future-ready isn't about predicting tomorrow's technology, but building teams that adapt to change naturally.
