Principal Software Engineer

High Wycombe
4 days ago
Create job alert

Principal Software Engineer

We are seeking an experienced Principal Software Engineer to lead the development of advanced scientific instrumentation within a multidisciplinary R&D environment.

This is a hands-on technical leadership role requiring deep expertise in software architecture, embedded systems, and a strong foundation in physics. You will translate physical principles and user requirements into robust, production-ready systems spanning firmware, hardware integration, and high-level applications.

Key Responsibilities

  • Lead architecture across embedded firmware (C/C++) and application software (C#/.NET).

  • Provide technical leadership and mentorship to Software, Firmware, and Electronics Engineers.

  • Develop physics-based algorithms for signal processing, instrument control, and data interpretation.

  • Integrate software with complex opto-electronic and hardware systems.

  • Define development standards, drive Agile practices, and implement CI/CD pipelines.

  • Contribute to next-generation product innovation in thermal analysis and materials characterisation.

    Requirements

  • Honours degree in Physics, Mathematics, or Engineering (with strong Physics basis).

  • 10+ years’ commercial software development experience.

  • Expert in C#/.NET; strong C/C++ for embedded systems.

  • Experience with hardware communication protocols (I2C, SPI, USB, Ethernet).

  • Proven leadership within multidisciplinary engineering teams.

  • Background in scientific instrumentation, industrial automation, or similar hardware-integrated environments.

    Desirable

  • Signal processing (FFT, digital filtering) or image processing

  • MATLAB or Python for prototyping

  • Cloud/IoT connectivity (Azure/AWS)

  • Experience leading multi-discipline teams

    This is a high-impact role for a technically strong leader with a “first principles” mindset who can bridge physics and software to deliver innovative, market-leading products.

    Principal Software Engineer, Software Architecture, Embedded Systems, Firmware, C#, C/C++, Physics-Based Algorithms, Signal Processing, Opto-Electronics, Instrument Control, R&D, Multidisciplinary Team, Technical Leadership, Scientific Instrumentation, Industrial Automation, Hardware Integration, CI/CD, Agile, MATLAB, Python, IoT, Cloud Connectivity, Thermal Analysis, Materials Characterisation, Electronics Engineering, Mentorship, High-Level Applications, High Wycombe, Oxford, Swinton, Reading, Slough, London, VRS9380MP

Related Jobs

View all jobs

Principal Software Engineer

Principal Software Engineer

Principal Software Engineer

Principal Software Engineer

Senior Software Engineer

Principal Embedded Software Engineer

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Robotics Tools Do You Need to Know to Get a Robotics Job?

If you’re pursuing a career in robotics, it can feel like the list of tools you should learn never ends. One job advert asks for ROS, another mentions Gazebo, another wants experience with Python, Linux, C++, RobotStudio, MATLAB/Simulink, perception stacks, control frameworks, real-time OS, vision libraries — and that’s just scratching the surface. With so many frameworks, languages and platforms, it’s no wonder robotics job seekers feel overwhelmed. But here’s the honest truth most recruiters won’t say explicitly: 👉 They don’t hire you because you know every tool — they hire you because you can apply the right tools to solve real robotics problems reliably and explain your reasoning clearly. Tools matter — but only in service of outcomes. So the real question isn’t how many tools you should know, but which tools you should master and why. For most robotics roles, the answer is significantly fewer — and far more focused — than you might assume. This article breaks down what employers really expect, which tools are core, which are role-specific, and how to focus your learning so you look capable, confident, and ready to contribute from day one.

What Hiring Managers Look for First in Robotics Job Applications (UK Guide)

Robotics is one of the most dynamic, interdisciplinary fields in technology — blending mechanical systems, embedded software, controls, perception (AI/vision), modelling, simulation and systems integration. Hiring managers in this space are highly selective because robotics teams need people who can solve real-world problems under constraints, work across disciplines, and deliver safe, reliable systems. And here’s the reality: hiring managers do not read every word of your CV. Like in many tech domains, they scan quickly — often forming a judgement in the first 10–20 seconds. In robotics, those first signals are especially important because the work is complex and there’s a wide range of candidate backgrounds. This guide unpacks exactly what hiring managers look for first in robotics applications and how to optimise your CV, portfolio and cover letter so you stand out in the UK market.

The Skills Gap in Robotics Jobs: What Universities Aren’t Teaching

Robotics is no longer confined to science fiction or isolated research labs. Today, robots perform critical tasks across manufacturing, healthcare, logistics, agriculture, defence, hospitality and even education. In the UK, businesses are embracing automation to improve productivity, reduce costs and tackle labour shortages. Yet despite strong interest and a growing number of university programmes in robotics, many employers report a persistent problem: graduates are not job-ready for real-world robotics roles. This is not a question of intelligence or dedication. It is a widening skills gap between what universities teach and what employers actually need in robotics jobs. In this article, we’ll explore that gap in depth — what universities do well, where their programmes often fall short, why the disconnect exists, what employers really want, and how you can bridge the divide to build a thriving career in robotics.