Role & Responsibilities
Own the Client's Outcome:
- Embed with enterprise customers – on-site and remotely – to understand their supply chain operations, data estate, and what success actually looks like for their business.
- Scope and design technical solutions for messy, real-world logistics problems – with a clear line to measurable impact: cost per delivery, SLA performance, empty kilometres.
- Own the full deployment lifecycle: architecture through go-live through steady-state. You're accountable for the outcome, not just the code.
Build and Ship:
- Design, build, and maintain backend services in Node.js or Python that power routing, planning, and execution at enterprise scale.
- Build and own the integrations connecting Locus to client ERPs, TMS, WMS, and OMS platforms – these integrations are often the riskiest part of a deployment.
- Write production code that runs under real load. If it isn't in production, it hasn't shipped.
Be the Technical Interface with the Client:
- Run architecture reviews, lead integration workshops, and represent Locus in executive steering meetings. You need to be credible at every level of the client organisation.
- Bring field learnings back into the product and platform teams. Some of Locus's best features started as a client workaround.
- Push back when a client request would compromise platform integrity – and propose a better alternative.
Show Up On-Site:
- Travel to client sites – domestic and international, up to 30% of the time – for kick-offs, integration sprints, go-lives, and post-live reviews.
- Build the kind of relationship where the client's ops lead calls you directly when something goes wrong at 2am, not a support ticket.
- Be comfortable wherever the work is: a warehouse floor, a logistics control tower, a C-suite boardroom.
Make the Next Deployment Easier:
- Document architecture decisions, integration patterns, and deployment playbooks – every engagement should make the next one faster.
- Work closely with Product, Customer Success, and Platform Engineering. Share what you're seeing in the field; don't wait to be asked.
- Mentor junior FDEs and raise the technical bar across the team.
