Technical Program Manager

Technical Programme Manager · Aviation & Defence

Permanent - UK based - Regular travel to project and customer sites

About us

Neuronstarted with a practical challenge in aviation: how independently operated sensors, drones and software systems can find one another and exchange useful data securely, without organisations giving up control of their systems or information.

We’ve built a platform that connects those systems through shared interfaces. It began with airspace awareness for drone operations and is now being applied to more complex work across aerospace, defence, physical AI, and critical infrastructure.

We’re still a small team, so the work stays close to real customers and operational environments. Engineers can see how their decisions affect an installation, a trial or the way somebody uses the product. There is plenty already working, alongside a lot still to shape as the platform and the company develop.

Joining now means having a genuine say in how we turn customer requirements into reusable product capabilities, how we deliver technical projects and how we build a more repeatable way of working. It should suit someone who enjoys understanding the technology, making practical decisions and staying involved until the system is working in the real world.

Why we’re hiring

Our portfolio of technical projects is growing, and we need one person to bring clear day-to-day ownership across customers, partners and engineering.

The work covers operational deployments, systems integration, testing and trials, alongside the technical evidence needed for customer and regulatory acceptance. Within a few months, you should be the person people turn to first when they need a clear answer on delivery.

What you’ll own

• Take technical projects from requirements through development, integration, testing and customer acceptance.
• Manage schedules, delivery budgets, scope, risks and dependencies across several projects running at the same time.
• Turn customer needs into clear engineering priorities and acceptance criteria.
• Work out where one shared product capability can support several projects, rather than creating separate versions for each customer.
• Personally write technical documents such as requirements baselines, interface control documents, test plans, assurance material and evaluation reports.
• Coordinate site surveys, installations, permissions and flight-test windows. Be present for key deployments and help investigate problems when they arise.
• Support integrations, demonstrations and deployments yourself. This is a practical technical role, although it does not require you to be a full-time software developer.
• Work directly with the CEO, engineers, customers and external partners. Bring enough structure to make delivery dependable without adding unnecessary process.

Skills/Experience we’re looking for

• You’ll need a genuine period of experience as a practising systems engineer, integration engineer or technical lead, followed by personal ownership of technical delivery through to customer acceptance. You should still be comfortable drawing on that engineering background.
• We’ll want to understand what you personally produced, how you handled technical trade-offs and how you knew the customer’s requirements had been met.
• A product or programme title is fine where the engineering and delivery evidence is there. An engineering degree is not a separate requirement.
• Experience in a smaller aviation, defence, drone, robotics or autonomous-systems business would be useful. Knowledge of UAS or BVLOS operations, surveillance, radar, sensor integration, flight trials, safety cases or regulatory evidence is helpful, but we care more about strong technical delivery and sound judgement than knowing every part of the sector already.

What success looks like

• Early on, you’ll establish a clear portfolio delivery plan, confirm responsibilities and acceptance criteria, and identify technical or site dependencies before they become problems.
• As you settle in, customers, partners and engineers should have a clear point of ownership. Projects should move towards acceptance with stronger technical evidence, fewer surprises and less day-to-day coordination sitting with the CEO.

Practical details

• The role is UK based and involves regular travel to customer and project sites for surveys, installations and trials. Some sites are rural, so a driving licence is essential.
• You must be eligible for UK security clearance. Existing clearance is not required when you apply; we’ll explain the requirement and verification process early.

Interview process

1. Screening call with Matt, our Talent Partner: an initial conversation about your background, what you have personally delivered and the practical details of the role.
2. Hiring conversation with our CEO and/or technical leadership: a deeper discussion about technical delivery, competing priorities, customer acceptance and working in a small team.
3. Short technical delivery exercise: a bounded, fictional scenario designed to explore how you approach integrations, milestones and technical evidence. We do not ask candidates to complete live customer work.
4. Exercise review and final discussion: a conversation about your decisions, assumptions and approach, with time for your questions