Engineering Team Lead (Supply Chain | Logistics)

Lead one of the teams that own the hardest part of ecommerce

Every order placed on Bash, whether online or in one of TFG's stores, runs through Supply Chain. We orchestrate each order through its entire lifecycle: picking and packing it in our warehouses, routing it through hubs and our logistics network (including our own courier, BashDelivery), and handling the returns when things come back. It's a genuinely hard distributed-systems-at-scale problem dressed up as "Ecommerce".

We're looking for someone to lead one of the teams in Supply Chain: Each team is typically a group of 4–6 backend engineers working closely with the Team Lead and a Product Manager. You'll be responsible for the people, the delivery, and the long-term health of the systems they build.

We have fairly strong opinions about what leading actually means here, so let's get into those, because they're the reason this role is worth your time.

What we mean by "Team Lead"

• You still get to see the front. This is not a role where you trade your IDE for a calendar. We're an action-oriented, sleeves-rolled-up team, and we expect our leads to contribute to the codebase, dig into the dashboards, and jump into incidents alongside the team. A well-run team should leave you real time to do meaningful technical planning and architecting while still getting the opportunity to write code.
• You lead from the back. The fastest way to fail here is to become a glorified Scrum Master: running ceremonies and grooming tickets while the team waits to be told what to do. We want the opposite: engineers who own their scope, their planning, and their technical decisions, with you setting direction, removing obstacles, and stepping in with experience when the team is genuinely off track. Empower first; dictate rarely.
• You're the team's champion. When the team is under scrutiny from up the chain, you take the heat and you give them the credit. Carefully managing expectations, making hard decisions, and advocating for your team and the products they build is a critical part of the role.
• You fix root causes, not symptoms. We'd rather eliminate a whole class of incidents than repeatedly patch the same one. We expect you to push the team toward durable system health, balancing feature work, operations, and risk so velocity survives contact with reality.

What you'd own

• People. Growth and development of each engineer: regular 1-1s, honest feedback, career plans, and creating the kind of environment where people do their best work, grow, and want to stay.
• Delivery. Working with Product and your fellow leads on prioritisation and sequencing, breaking initiatives into tech specs and tickets, and driving them to done without becoming the bottleneck.
• Technical standards. Advocating for engineering excellence with a pragmatic, product-aware lens. Real code reviews, sound architecture, no rubber-stamping.
• Operations. A fair, humane on-call rotation (which you periodically take part in, to stay close to the team's day-to-day pain), strong incident response, and post-mortems that actually produce action.

You'll fit well if you have

• A track record of leading a team to high-quality output, with a genuine focus on enabling the people in it, roughly 5+ years engineering experience and 2+ year leading a team or project.
• A history of writing high-quality, scalable code in a modern, statically typed language. Go is our primary backend language and what you'll write day to day; we don't require prior Go experience (strong engineers pick it up fast), but we do expect a solid grasp of architectural patterns for both systems and code.
• Real, hands-on experience building and operating distributed, high-transaction, highly available systems in production. Familiarity with Kafka and/or Temporal is a bonus.
• A bias toward observability and monitoring: you want your team to know, not guess, how their services behave.
• Strong communication and a collaborative instinct: you make decisions with data, hold opinions loosely enough to change them, and welcome feedback as readily as you give it.

A BSc in Computer Science (or equivalent) is encouraged but not required. Strong, demonstrable experience speaks louder.

Most importantly, you'll be working hand-in-hand with other Team Leads and Directors in the Supply Chain division. Supply Chain at times feels like one big team, all working in lockstep. You'll be supported when making difficult decisions and helped when the challenges get complicated.

If this sounds like a real challenge, that's probably a fair assessment. Hard work, consistently striving to be the most organised person in the room, managing multiple projects with real deadlines are all part of the role. If that sounds exciting and just a little bit scary, we'd love to hear from you.

---

We ask a few optional demographic questions to monitor fairness in hiring and comply with South Africa’s Employment Equity requirements. Your responses are confidential—stored separately from your application and never shown to hiring panels. We review the data only in aggregate to strengthen our sourcing so pipelines are diverse and all candidates receive equitable support. You can skip any question.