The company is a small team inside a larger enterprise software group. It runs an AI-native logistics platform that brings transport data together, reduces carrier spend and automates shipment execution for enterprise shippers and logistics firms.
The platform was built and launched under a previous name before joining the group. The team sits on the commercial side of the business rather than in central R&D. The product is pure SaaS with no consultancy work.
The parent group has $1 billion+ in revenue and 7000+ employees across every continent.
The senior lead engineer runs engineering and owns the backend, but cannot also set the product approach alone. The company is moving from feature-driven engineering to agent-led product architecture, and this surface is where that shift has to work.
Responsibilities
You will own the product side of the transport execution product from start to finish: how customers book freight, set up carriers, configure their own rules and get the paperwork needed to move a shipment.
Transport execution and automation is the commercial core, since every enterprise shipper depends on it. You will set its direction, work closely with the squad's Product Lead and Designer, and act as the second technical voice in the squad.
You will mentor engineers early in their careers who join the squad, day to day. This is part of the role.
Your strength is frontend and product engineering, but everyone here works fullstack. You will write Django, define the API contract you consume, and understand what the data layer does beneath your screens.
Freight booking across road, sea and rail, including spot quotes and multi-leg or consolidated moves on the new shipment data model.
Carrier integration, including self-serve setup that customers complete without the company's help.
Self-serve configuration of fulfilment rules, packaging types, products and SKUs, managed by customers themselves.
Shipping and customs document generation.
Newer operational areas as the product grows: consolidation and load optimisation, dock scheduling, transport scheduling and own fleet.
The Django endpoints, data contracts and validation behind all of these.
Deciding where the agent acts in each flow, where a person reviews at the few points that matter, and the guardrails that keep live freight safe.
Requirements
5 to 8 years building and shipping production software, with deep React, TypeScript, and state and interaction design for complex multi-step workflows.
You have owned a product surface end to end, including its unclear parts, and closed open questions yourself rather than waiting for them to be closed.
You write Python and Django, challenge API contracts, and know when a client-side fix is the wrong fix.
You handle failure well in the interface: validation, partial failure, retries, and what the user sees when something breaks midway.
You build human-in-the-loop interfaces and treat traceability as a product feature rather than logging.
You raise the standard of others' work through review, pairing and direct feedback by default, and you enjoy mentoring less experienced engineers.
You use Cursor and Claude daily, give agents good context, and catch when their output is confidently wrong.
You take positions and state them. Ambiguity is part of the work, not a reason to stop.
Design system ownership, or close work with a designer on a complex data interface.
Django REST, BigQuery, dbt, Cube Cloud, GCP.
LLM agents, RAG or evals in production.
Experience shipping an agent that does real work, such as agentic audit or fulfilment rule automation, and building a simulation to test the logic first.
Logistics, supply chain, freight, or a finance-adjacent field where mistakes cost money.
Tech stack. Frontend: React, TypeScript. Backend and APIs: Python, Django REST Framework. Data and analytics: BigQuery, dbt, Cube Cloud, Superset. Streaming and ingestion: Pub/Sub, Datastream. Cloud and infrastructure: GCP, Kubernetes, Terraform, GitLab CI/CD. AI: LLMs, RAG, agent frameworks, evals. Developer tooling: Cursor and Claude, Notion (SDD Central), Jira.
Within 6 months you own the booking and carrier setup surface and close its open questions yourself.
Self-serve carrier setup is live and customers use it without the company's help.
Booking and configuration flows handle failure: no silent errors, and customers always see the state of their shipment.
Engineers earlier in their careers in the squad work independently on reviewed code and can name what they learned from you.
Squad standards are clearly higher: review on every merge request, nothing goes straight to production, and every ticket has real acceptance criteria.
Conditions
You must be based in the UK or the Netherlands. The team is remote, with clusters of people in London and Amsterdam.
Flexible and hybrid working is available.
The company welcomes applicants from all backgrounds and values diversity.