Job Title: Software Development Engineer - 3 

Location: Bangalore (On-site; full-time)
About Locus

Battle-tested in 350+ deployments across 30+ countries, Locus is an agentic Transportation Management System for all-mile, all-channel, trusted by enterprises like Unilever, Nestlé, and Siam Makro.

The platform unifies orders, capacity, and carrier networks into one living plan, aligning planning, execution, and settlement so promises become proof. AI co-pilots with guardrails surface risk early and recommend the next best move to protect SLAs and reduce empty miles.

In 2025, Locus joined the Ingka Group (IKEA Retail) family, marking a major milestone in our journey. Backed by the scale and strength of IKEA, we continue to operate independently while accelerating our mission to make global supply chains faster, smarter, and more sustainable.

Our Journey and Impact

Since 2015, Locus has been on a mission to make logistics decision-making intelligent, sustainable, and real-world ready. Our platform has powered billions of deliveries across 30+ countries for global enterprises, driving measurable impact in cost savings, carbon reduction, and SLA performance. With the strength of the IKEA ecosystem behind us, we’re scaling that impact even further.

Our Global Footprint

Headquartered in Bangalore, with teams across the U.S., U.K., UAE, and Southeast Asia, Locus brings together 170 + engineers, designers, and problem-solvers united by a single goal: to reinvent how the world moves goods.

Traits We ValueWe look for people who are:

● Global in mindset: curious about diverse markets and ideas.

● Unrelenting in drive: energized by complex challenges.

● Intelligent in approach: analytical, creative, and thoughtful.

● Dynamic in execution: adaptive and decisive in fast-moving contexts.

● Exact in craft: detail-oriented and committed to excellence.

Why This Role Exists

Enterprise logistics is messy. Every client’s supply chain runs on different constraints, different data, and a different definition of what “good” looks like. A great product alone doesn’t fix that. Someone has to sit with the client, earn their trust, and make the technology work in their environment – not in a demo environment.

SDEs at Locus don’t feed a roadmap. They own the outcome of a client’s deployment – from the first architecture conversation to the day the system is live and moving real trucks. If you’re the kind of engineer who gets restless building things no one uses, and you’d rather see your code cut costs and protect SLAs for a Fortune 500 shipper, this is the role.

What You Will Do

Think of this as a startup CTO role, embedded inside a client’s operation. You work in a small team with high autonomy and full accountability for delivery.

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.

  
  

Make the Next Deployment Easier

• Document architecture decisions, integration patterns, and deployment playbooks – every engagement should make the next one faster.