MERIDIAN
Two engineers in dark workwear at an open shelf-carrying robot under a single work light in a dark warehouse hall
Scene 01 / Bristol · Leipzig

Build what moves the work.

We build autonomous mobile robots for warehouses and factories. Come make the machines, software and field work that keep stock moving.
See 23 open rolesMeet the teams
Frame 001 / Co-founded 2018
Two cities, one line
240
People in Bristol and Leipzig
6,100
Robots deployed since 2019
14
Countries running a fleet
23
Roles open right now
Scene 02 / Why Meridian

The robot is the visible part.

Behind it: navigation, perception, fleet software, assembly, test, commissioning and support. That is the work. One drive unit, one navigation stack and one fleet controller let a mixed fleet behave like one fleet — we are hiring the people who make every layer hold together.

From final assembly in Bristol to commissioning across fourteen countries.

Hands torque-checking a brushed-aluminium wheel module on an assembly bench
Scene 03 / The machines

One fleet. Four parts.

One drive unit, one navigation stack, one fleet controller. Different loads; one operating system for the building.

  • A shelf-carrying robot under a mobile shelving unit of black totes in a warehouse aisle

    M40 · Shelf carrier

    Lifts and moves a 400 kg mobile shelving unit. The workhorse — about seventy per cent of everything we have shipped.

  • A low tote-runner robot carrying one black tote across a factory floor

    M12 · Tote runner

    A low, fast unit for totes and small parts between stations. Built for factories rather than warehouses.

  • A pallet-moving robot under a euro pallet of plain cardboard boxes

    M80 · Pallet mover

    Lifts a full euro pallet and works alongside people and forklifts — which is the hard part.

  • Several robots seen from above crossing a warehouse junction

    Meridian Fleet · Orchestration

    Up to 140 robots in one building, one console, and an API that talks to eleven warehouse systems.

23 ways in.

Straight from our applicant tracking, so nothing here closed three weeks ago. Every role carries its salary band, its team and its location.

6 open roles

Scene 05 / Check the terms

Ask us. Check it. Then decide.

Six things you can verify before you accept an offer. Each is written down on this site or is a number we will show you in the interview.
01
Salary bands published on every role
02
Four-day interview process, start to offer
03
Paid interview exercises, always
04
On call one week in eight, paid
05
Six months' parental leave at full pay
06
No unlimited holiday — thirty days, taken

Scene 06 / Three teams

240 people. Three ways to build.

The robots only work when the disciplines meet. Every open role says which team, and which group inside it, you would join.

Find your team in the open roles
Two engineers leaning over a bench of parts, working through a problem together

Engineering · 94

Navigation, perception, fleet software and the embedded platform. C++, Rust, Python and TypeScript.

A technician doing final electrical work inside an open robot

Manufacturing · 61

Final assembly, electrical and functional test, and quality. Two day shifts in Bristol. No nights.

A field engineer crouching to measure in a warehouse aisle

Field operations · 44

Surveying, commissioning, training and support across fourteen countries.

Scene 07 / Last twelve months

The numbers we publish.

4
Days, median, from first interview to offer
9
Days, median, from joining to your first deploy
14
Robots a week off the Bristol line, up from four
30
Days' holiday a year, and taken — not unlimited
Scene 08 / How we hire

Four steps. Four days.

A short process, a real problem and a decision with reasons. If we are slower than this for you, we will tell you why.

  1. A conversation · 30 minutes

    With Sanne, head of people, about what you want rather than what you have done. You get the band, the team and the hiring manager's name.

  2. The hiring manager · 45 minutes

    The person you would report to, talking about the work. No whiteboard, no puzzles.

  3. A paid working session · 2 hours

    A real backlog problem with one of our engineers. £250 whether or not you get the job, and it can be an evening.

  4. Team and offer

    Coffee with two people from the team, then a decision with the reasons, either way. Marcus is in the last conversation for every role.

Scene 09 / First week

The people behind the machine.

Not a leadership wall. These are the six people you would meet in your first week, in the order you would probably meet them.
Portrait of Sanne de Vries, head of people, in the assembly hall
Sanne de Vries
Head of people
Bristol
Runs hiring and pay, and reads every application.
Portrait of Priya Raman, chief technology officer, in the assembly hall
Priya Raman
Chief technology officer
Bristol
Was employee four. Still reviews code most weeks.
Portrait of Daniel Reyes, head of operations, beside the line
Daniel Reyes
Head of operations
Bristol
Took the line from four robots a week to fourteen without a night shift.
Portrait of Samuel Hart, field operations lead, in a warehouse aisle
Samuel Hart
Field operations lead
Leipzig
Has commissioned fleets in eleven of our fourteen countries.
Portrait of Nadia Brenner, safety engineering lead, in safety glasses
Nadia Brenner
Safety engineering lead
Bristol
Owns functional safety certification. Can stop a shipment, and has, twice.
Portrait of Marcus Ellery, chief executive, in the assembly hall
Marcus Ellery
Chief executive
Bristol
Co-founded the company in 2018. Sits in the last interview for every role.
Scene 10 / In the field

What operations directors notice.

  • A shelf-carrying robot in a long grocery distribution aisle, a worker in the distance
    Hanne Lauritzen, Operations director · National grocery distributor
    The robots were the easy bit. What actually made this work was that their field team told us on week one that two of our aisles would not work, rather than finding out in month three.
  • A robot carrying a parts rack across a manufacturing floor, people at work behind it
    Ravi Chandrasekar, Head of automation · Contract manufacturer
    We ran a mixed fleet of forty M40s and twelve M12s in the same building for eighteen months before we hit anything the console could not explain to us.
  • A pallet robot carrying a wrapped pallet across a logistics cross-dock
    Marta Nowak, Site lead · Third-party logistics
    Their out-of-hours line is answered by an engineer who can see our fleet. After three vendors where it was a ticket queue, I cannot overstate what that is worth at two in the morning.
The Bristol assembly line seen from above, robots at different build stages and technicians at work
Built here, working there

From fourteen a week to fourteen countries.

6,100 robots deployed since 2019, all of them built on the Bristol line — which went from four robots a week to fourteen on two day shifts, with no night shift.
Scene 11 / 2019 — now
Bristol line
Scene 12 / Contact

Tell us why you're here.

A role, a deployment or something else — it reaches the right people. If it is about a role, it goes straight to Sanne.
Candidates
people@meridianrobotics.exampleRead by Sanne — including when nothing is open. We keep letters for a year.
Customers and partners
hello@meridianrobotics.exampleSite surveys, fleet expansion and integration questions. An engineer will be on the first call.
Bristol and Leipzig
Arrange a visitUnit 4, The Printworks, Bristol (final assembly) · Karl-Heine-Straße 82, Leipzig. Visits by arrangement.
Or write to us here

Two engineers seen from behind walking beside a robot down a long warehouse aisle at the blue hour
Final scene / The next build

Come build the part that isn't finished.

Engineering, manufacturing and field operations, in Bristol and Leipzig. Every role carries its band, and every exercise is paid.
See 23 open rolespeople@meridianrobotics.example
Meridian Robotics Ltd. / End frame
Applications open