Technical Lead – Onboard Experience Team

Edinburgh
2 months ago
Applications closed

Related Jobs

View all jobs

Procurement Manager

Procurement Manager

Head of Manufacturing Engineering

Electronic Design Engineer, Automotive cellular device

Engineering Project Manager

Systems Architect

Technical Lead – Onboard Experience Team (Autonomous Vehicle Software)

Location: Edinburgh – Hybrid (3 Days On-Site)
Contract Type: Full-time, Permanent
Salary: £60,000 - £70,000

About the Role:

As the Technical Lead for the Onboard Experience Team, you will collaborate with a team of Android and full-stack engineers to shape the software experience for autonomous vehicle operators. You will guide technical strategy and execution, contributing to the development of reliable, scalable, and user-centred software. Your work will enhance operational efficiency and create exceptional in-vehicle experiences for internal stakeholders and demo participants.

What We’re Looking For:

  • Proven experience designing and delivering complex systems, with a focus on frontend development and backend integration at scale.

  • The team stack includes React, Typescript, Kotlin, and Rust.

  • Experience leading technical decisions and contributing to architectural strategies.

  • Strong commitment to high engineering standards, including testing, observability, and automation.

  • Ability to deliver user-focused solutions informed by operational feedback and real-world challenges.

    Key Responsibilities:

  • Technical Leadership: Collaborate with the team to shape the technical vision and guide architecture and implementation of software solutions.

  • Collaboration and Innovation: Partner with teams across the organisation to solve unique challenges and enhance the onboarding experience.

  • System Scalability and Reliability: Drive development of scalable, maintainable systems with strong testing, observability, and performance.

  • Developing for Unique Environments: Optimise solutions for compute and networking constraints where your app-server resides in a car navigating unpredictable city environments.

  • Hands-On Testing with Users: Test changes directly in vehicles and gather feedback from operators to refine software in real-world scenarios.

  • Safety and Regulatory Excellence: Ensure compliance with safety requirements and regulatory constraints.

  • Innovation and Problem Solving: Apply technical expertise to design user-focused solutions for diverse operational use cases.

  • Fostering Growth: Promote collaboration, knowledge sharing, and continuous learning within the team.

    Desirable Skills:

  • Familiarity with in-vehicle systems, including Android Auto or similar platforms.

  • Experience with gRPC or other strongly typed API interfaces.

  • Interest in AI, robotics, or autonomous vehicle technology.

  • Degree in Computer Science, Software Engineering, or equivalent experience

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.