Software built around the people who use it
I’m Edward Haigh, a senior software engineer from West Yorkshire with ten years of professional experience across enterprise software, Formula 1 and Formula E.
I build applications that help people understand data, operate complex systems and get their work done. That has included enterprise web platforms, vehicle-programming tools, automated data processing and statistical analysis software.
I enjoy getting to grips with unfamiliar problems and taking responsibility for making the solution work, from the first conversation with a user through to deployment and ongoing support.
From apprenticeship to motorsport
I started my software career at 17 through a Level 3 apprenticeship at Marshalls, before progressing to a degree apprenticeship with Manchester Metropolitan University. Studying alongside a full-time development role meant applying what I learned to production systems from the outset.
Over four and a half years, my responsibilities grew from building web applications and APIs to shaping application architecture, introducing new technology and evaluating whether proposed projects were worth pursuing. As my experience developed, I also began mentoring newer apprentices.
The COVID pandemic became a turning point. It put me in a position where I needed to reconsider my next step and look for a change. I left the degree apprenticeship with a DipHE in Digital and Technology Solutions and moved south to join Haas F1 in 2021.
That move brought me closer to the connection between software and physical engineering: applications interacting with vehicle systems, telemetry and garage equipment, used by people making decisions during live operations.
My career subsequently took me to Jaguar TCS Racing and Mercedes-AMG F1 before I returned to Jaguar as a contractor. Along the way, my software contributed to three Formula E World Championship-winning campaigns.
Alongside my enterprise background, those environments have given me experience I can bring to a wide range of engineering and business problems, including system integration, data processing, application performance and legacy modernisation.
How I work
I like understanding the problem before committing to a solution. That means talking directly with the people doing the work, tracing how information moves through a system and identifying where time is lost or failures occur.
From there, I turn the findings into a practical plan: what needs to change, what matters first and which trade-offs we can reasonably make. I stay involved through implementation and adoption, because a sound design only becomes useful when it works in practice.
I take responsibility for the direction of the work as well as its implementation. I’ve owned technical roadmaps, presented planned development to engineers and stakeholders, and made the case for additional software resource. That included bringing in the team’s first software secondment, delegating work and reviewing its progress.
I also help others take ownership. When introducing Rx.NET, I planned gradual adoption across existing applications and delegated initial implementations so colleagues could gain practical experience. Across my roles, I’ve mentored apprentices and junior engineers, established development standards and designed the team’s software-engineering interview framework.
My approach is to make priorities clear, explain the reasoning behind decisions and give people the support and responsibility to contribute. I value useful documentation and honest technical discussions, and involve the people who will use, support and maintain the software.
Beyond software
Outside work, I enjoy cooking and baking, particularly lasagna and fresh pasta using techniques passed down through my Italian family. I’m learning Italian too, with a 1,000-day Duolingo streak.
I also enjoy gaming, following esports and trying new beers. Practical renovation work and countryside jobs regularly get me away from a screen, usually with a Yorkshire brew somewhere nearby.
What’s next
I’m based in West Yorkshire and looking for my next senior software-engineering role, with opportunities to take technical ownership and help other engineers develop.
I’m interested in engineering software, technical platforms, internal tools, data-intensive systems and complex business applications. I’m open to permanent and contract work across northern England, UK-remote roles and hybrid arrangements involving occasional travel.