Software Engineer

Oxford
1 week ago
Create job alert

Software Engineer

Location: Abingdon, Oxfordshire (hybrid working available)

Salary: £45,000 – £65,000 DOE + Excellent Benefits

Overview

An innovative organisation specialising in engineering design, advanced manufacturing, and materials development is seeking a Software Engineer to develop bespoke software platforms supporting component design, alloy optimisation, additive manufacturing, and quality assurance workflows.

This role requires strong technical depth, particularly in C++, alongside experience in cluster computing or web application development. The successful candidate will collaborate with engineers and scientists to deliver scalable, production-grade solutions used in high-performance applications such as turbine components and advanced 3D printing.

 Key Responsibilities

Design, develop, and maintain modules across multiple custom software platforms.

Build and integrate tools for simulation, data analysis, component design, and workflow automation.

Develop scalable services, including wrapping in-house and third-party tools.

Contribute to cloud-based and distributed solutions (AWS/Azure), following modern DevOps practices.

Support use cases including complex component design, materials optimisation, additive manufacturing, and production monitoring.

Work within agile processes, contributing to requirements, testing, and iterative delivery.

 Essential Requirements

Degree (2:1 or above) in Computer Science, Engineering, Mathematics, or related field.

Strong programming expertise in C++ (in-depth knowledge required), plus Python and/or C#.

Experience in cluster computing and/or web application development.

Solid understanding of object-oriented design and software engineering principles.

Experience with agile methodologies and test-driven development.

Ability to deliver complex technical solutions independently in a multidisciplinary environment.

 Desirable

Full-stack development experience ( Core, Blazor, React, TypeScript, WPF).

Knowledge of 3D geometry, CAD integration, or simulation tools (FEA, CFD).

Familiarity with CI/CD, containerisation, and infrastructure-as-code tools (e.g. Terraform).

Experience or interest in machine learning applications within engineering contexts.

 Ideal Profile

An early to mid-career software engineer (2–5 years’ experience) with strong technical foundations and demonstrable depth in C++, ideally with exposure to distributed or web-based systems, and an interest in applying software expertise within advanced manufacturing sectors such as aerospace, automotive, defence, or energy

Related Jobs

View all jobs

Software Engineer

Software Engineer

Software Engineer - Autonomous Systems

Software Engineer - Robotics

Software Engineer (RTOS)

Software Engineering Team Lead

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.