Head of Software Engineering in Cambridge

Head of Software Engineering in Cambridge

Cambridge Full-Time 72000 - 108000 £ / year (est.) Remote
U

At a Glance

  • Tasks: Lead a high-performing engineering team to deliver innovative software solutions.
  • Company: Join Ubisense, a leader in Industry 4.0 and IoT technology.
  • Benefits: Competitive salary, inclusive culture, and opportunities for professional growth.
  • Other info: Dynamic work environment with a focus on diversity and inclusion.
  • Why this job: Shape the future of smart technology and make a real-world impact.
  • Qualifications: Proven leadership in software engineering and hands-on coding experience.

The predicted salary is between 72000 - 108000 £ per year.

About Ubisense Limited

Ubisense is a company at the forefront of Industry 4.0 and the Industrial Internet-of-Things. We build products that transform physical space into “smart space”, enabling software to see, understand and participate in the real world of people and business activities. This unique ability to connect the physical to the digital has been our driving force for more than 18 years and has enabled Fortune 500 manufacturers like Daimler-Benz, Lockheed Martin and John Deere to revolutionise the way they build our cars, the most advanced aircraft and the machinery that grows our food.

We are a privately held company with around 60 employees, supporting customers across North America, Europe, UK, Japan and the Middle East. We have ambitious and well-funded growth plans, requiring talented people to help execute on our vision. We are looking for people who are interested in the future, who believe that technology will play a fundamental role in improving the world of tomorrow, and who want to be a part of making that happen.

At Ubisense, we believe that diversity, equity, and inclusion are fundamental to our success and growth. We are committed to creating a workplace where everyone feels valued, respected, and encouraged to contribute their unique perspectives. With that in mind, we welcome applicants from all backgrounds and uphold high standards within our recruiting and hiring practices. We look forward to seeing your application!

About The Role

Ubisense delivers solutions based on our SmartSpace® and Dimension4® products, providing real-time visibility and control to customers in advanced manufacturing, transit, pharmaceutical, and defence sectors. SmartSpace® is a highly configurable software platform targeted at complex problems in IoT and Industry 4.0. Many SmartSpace applications also use our world leading Dimension4® Real Time Location System.

The Head of Software Engineering is accountable for building and operating a high-performing engineering organisation that delivers secure, reliable, and maintainable software at pace. This role owns the end-to-end engineering lifecycle—from strategy and architecture to delivery, tooling, and quality—while cultivating engineering excellence and modern DevOps/CI/CD practices. The successful candidate is a hands-on technical leader who can write code, set engineering standards, and lead teams through change.

Key Outcomes (12-18 months)

  • Reliable, predictable delivery: Transparent quarterly release train and sprint cadences; measurable improvements on DORA metrics (lead time, deployment frequency, change failure rate, MTTR).
  • Modern delivery pipeline: A robust CI/CD platform with automated build, test, security scanning, and progressive delivery; trunk-based workflows and high-quality code reviews.
  • Fit-for-purpose architecture: Clear architectural runway, reference designs, and decision records (ADRs); reduced complexity and improved scalability.
  • Quality by design: Shift-left testing, high unit/integration test coverage, meaningful end-to-end test automation, and clear quality gates.
  • Engineering culture: Engaged teams with strong craftsmanship, documentation standards, and continuous improvement mindset (SPACE metrics for developer experience).

What You Will Do

Strategy and Planning

  • Define the engineering operating model, aligning architecture, delivery, and platform engineering to product goals.
  • Translate business objectives into technical roadmaps, capacity plans and quarterly OKRs.

Delivery Ownership

  • Own the what/when/how of engineering delivery: intake, prioritisation, estimation, sprint planning, release readiness.
  • Establish portfolio and release governance with clear stage gates (architecture, security, test, documentation).

Architecture and Technical Direction

  • Chair architecture forums; set standards for patterns, APIs, data, and cloud infrastructure; steward ADRs.
  • Ensure systems are observable (logs, metrics, traces) with SLOs and error budgets; lead major incident reviews and blameless post-mortems.

Methods, Tooling and Platform

  • Define and evolve SDLC and development methodologies (Agile/Scrum/Kanban, trunk-based development, code review practices).
  • Own the DevOps toolchain (source control, CI/CD, artefact management, IaC, secrets management, environments, test automation, security scanning).
  • Partner with IT on platform reliability, scalability, cost, and resilience.

Quality and Security

  • Set quality standards and test strategies (unit, integration, E2E, performance, security); implement coverage targets and defect escape thresholds.
  • Embed secure coding and secure release practices.

People Leadership and Organisation

  • Lead architects, developers, testers, and tech authors; nurture craft disciplines and communities of practice.
  • Hire, onboard, mentor, and develop engineering talent; define career ladders, and competencies.

Stakeholder Management

  • Work closely with Product, Support, Professional Services, and IT to ensure the roadmap is feasible, valuable, and supportable.
  • Communicate plans, risks, and outcomes concisely to executives and non-technical stakeholders.

Financial and Vendor Ecosystem

  • In conjunction with the CIO, manage engineering budgets, cloud/runtime costs, and ROI on tooling.
  • Evaluate and govern vendors (cloud, tooling, testing services).

Documentation and Knowledge

  • Ensure clear, current documentation (architecture, APIs, runbooks, user guides) and a robust knowledge base.
  • Establish standards and workflows for Technical Authors integrated with release trains.

Required Qualifications And Experience

  • Track record of leading engineering at Head of Engineering level (or equivalent).
  • Hands-on coding capability in at least one modern language (e.g., C#, Java, Python, JavaScript) and willingness to contribute to reference implementations, reviews, and technical spikes.
  • Experience with DevOps/CI/CD (Git, pipelines, artifact repositories), IaC (e.g., Terraform/Bicep), containers/orchestration (Docker/Kubernetes), and cloud platforms (Azure/AWS).
  • Strong command of software architecture (domain-driven design, modular monoliths/microservices, eventing), APIs, and data design.
  • Proven quality leadership: test automation strategies, reliability engineering (SLOs, error budgets), performance engineering.
  • Demonstrated security leadership within engineering: secure coding practices, vulnerability management, SBOMs, supply-chain security, threat modelling.
  • Expertise in modern Agile delivery (Scrum/Kanban), product collaboration, and scaling patterns (e.g., lightweight portfolio cadence).

Nice-to-Have

  • Experience with manufacturing/location-based solutions or industrial interfaces (OPC, MQTT), data streaming, and edge deployment.
  • Familiarity with documentation workflows and tech’ authoring standards.
  • Exposure to ITIL-aligned change/release processes and ISO/IEC quality/security frameworks.

Qualifications

  • Bachelor’s degree in computer science, Engineering, Mathematics, or a related field with a high computing content.

Core Competencies

  • Technical leadership: Sets high bars, makes pragmatic decisions, and can deep dive when needed.
  • Delivery excellence: Turns strategy into outcomes, manages trade-offs, and drives predictability.
  • Communication: Explains complex topics to varied audiences; crisp executive updates.
  • People and culture: Builds inclusive, high-trust teams; coaches and multiplies talent.
  • Systems thinking: Optimises end-to-end flow and reliability, not just local focus.

Key Performance Indicators (KPIs)

  • DORA: Lead time for changes; Deployment frequency; Change failure rate; MTTR.
  • Quality: Defect escape rate; Test coverage health; Mean time between incidents; Performance SLAs/SLO adherence.
  • Flow and predictability: Throughput, cycle time, on-time delivery vs. plan, WIP limits adherence.
  • Security and compliance: Vulnerability remediation time; dependency hygiene; SBOM coverage; audit readiness.

Working Practices and Governance

  • SDLC policies and quality gates are enforced via automation (build, test, scan, deploy) with clear “go/no-go” criteria at each stage.
  • Documentation is a first-class deliverable; releases are accompanied by updated architecture notes, API references, and user guides.
  • Continuous improvement: Regular retrospectives across teams; quarterly engineering reviews; blameless culture.

Personal Attributes

  • You manage your time effectively.
  • You are willing to travel occasionally both nationally and internationally.

Head of Software Engineering in Cambridge employer: Ubisense

Ubisense Limited is an excellent employer, offering a dynamic work environment where innovation meets collaboration. With a strong focus on employee growth and development, you will have access to ongoing training and opportunities to advance your career in the cutting-edge field of real-time location systems. Our supportive culture encourages teamwork and creativity, making it a rewarding place to contribute to impactful projects across Europe and the US.

U

Contact Details:

Ubisense Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Head of Software Engineering in Cambridge

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Ubisense or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Ubisense.

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Ubisense.

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Ubisense that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Head of Software Engineering in Cambridge

Technical Leadership
Hands-on Coding Capability
DevOps/CI/CD
Infrastructure as Code (IaC)
Containerisation and Orchestration
Cloud Platforms
Software Architecture

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Ubisense.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Ubisense and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at Ubisense

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Ubisense uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.