🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
WHO WE ARE AT BASH We are a team of leaders, bold thinkers and friends, and we’re on a mission to create remarkable omni-channel experiences for our customers. We believe that by being Bold, Accountable, Simple and Human , our values will lead us forward, keeping us real, connected and directed. By leveraging the power of technology and exceptional talent , we are building products that bring the physical and digital world together to create communities that prosper. This journey requires grit, ambition and teamwork as we transform SA retail for the better . And we’re only just getting started. Now is the time to jump onboard. Life at Bash Bash is TFG's digital and omnichannel retail division. We build the technology, products, and commercial capability that connect 27 retail brands to customers. Our customers can shop online, in-app, and increasingly inside 3,400+ stores nationwide. The work is hard, the hours are long, and we hold each other to a high standard. We're product and tech led but rooted in retail, which means everything we ship has to work at the counter, not just on a screen. We grow through every new person, every new idea, and through our collective wins and failures. We are only just getting started. Three teams, one mission: Catalogue Discovery & Shop Cart, Checkout & Post Purchase Every product a customer sees on Bash - searches for, scrolls past, adds to their cart, and eventually gets a delivery notification about - passes through the systems Omnicom owns. It starts with wrangling catalogue data flowing in from every one of TFG's 27+ store brands and hundreds of labels, and building the pipelines that turn that into something to surprise and delight our customers. From there it's the experience itself: search that actually understands what someone's after, display pages that load instantly and convert across web and app, and a cart that never buckles under load. Then checkout has to be frictionless, and everything after - order tracking, delivery comms, returns - has to keep people coming back for more. It's a genuinely hard product-and-scale problem dressed up as "shopping." That's the part we like, and it all has to hold up when hundreds of thousands of people hit 'add to cart' in the same ten minutes on Black Friday. We're hiring Go Engineers across various teams You'll be placed where your strengths and interests line up best: Catalogue - the front door for every product TFG sells. This team owns the pipelines that take raw catalogue data from dozens of brands and turn it into clean, structured, sellable product data - every image, spec, price, and variant on the site starts life here. Discovery & Shop - the online shopping experience: search, PDP, PLP, and everything else that turns "just browsing" into "add to cart." This is where relevance ranking, real-time stock, and page speed all have to work together, or the sale is lost. Cart, Checkout & Post Purchase - carrying the customer from cart to confirmed order and everything after: checkout journeys, delivery promises, order tracking, notifications, and returns. We stop just short of payments - everything else on that journey is ours. What you'd actually work on Search and discovery systems that have to be relevant and fast at the same time. Every keystroke, filter, and scroll hits live stock and pricing, not yesterday's cache, across the hundreds of millions of shopping sessions Bash sees a year. Event-driven pipelines (we lean heavily on Kafka) that keep product data in sync across 200+ brands' worth of catalogue. Every price change, image upload, and spec update has to land correctly downstream, or it's wrong on the site within minutes. Cart and checkout logic where "close enough" isn't good enough - vouchers, promos, and pricing have to work identically across web, app, and in-store checkout, because a rounding error here is real money in the wrong pocket. Integrations with external systems - the kind that don't expose clean APIs and don't care about your sprint. Post-purchase tooling people actually rely on: order tracking, delivery promise dates, and the notifications that keep customers in the loop, shaped by real usage rather than what looks good in a spec doc. The Stack Go is our primary backend language, and we mean it - this isn't a "we have one Go service" job. Around it: AWS , Kubernetes , and a strong observability culture (you build it, you can see it, you own it). Internal tools and admin surfaces are built in Retool , and we plan and track work in Linear . You won't be reaching for new tech for its own sake, but you also won't be fighting a decade of legacy to ship something sensible. You'll fit well if you have 3+ years building production backend systems , ideally in Go - or you're strong in another language (Java, C#, Python, Node, Rust, whatever) and genuinely keen to go deep on Go. We hire for engineering ability, not language trivia. Solid instincts for databases, data structures, and algorithms , and real curiosity about distributed systems - consistency, failure modes, and what happens at 2am when one node disagrees with the rest. You don't need to have all the answers here yet. You do need to find the questions interesting. The ability to take a feature and drive it to done. You can break it down, spot the ambiguity, ask the right person the right question, and ship. You'll have senior engineers to lean on for the gnarliest calls - knowing when to lean is part of the skill. A habit of writing code others can live with. Well-tested, readable, debuggable. You give useful code review feedback, not just an approve button. A bias toward observability and monitoring - you'd rather know than guess. You care whether the thing you shipped actually worked, and you know how to check. Clear communication. You can explain a technical trade-off to a product manager, flag a delay before it becomes a surprise, and write documentation that saves the next person a day. Comfort with agentic coding tools , but you still read and validate everything "you" commit. A BSc in Computer Science (or equivalent) is a nice-to-have, not a gate. Strong, demonstrable experience speaks louder. How we work We're a cross-functional, Agile team, but we care less about ceremony than about how engineers actually operate day to day: You own your work. Senior here means you remove ambiguity from your own tickets, shape the solution, and drive it to done - not wait to be told. You build to last. Resilient, maintainable, observable. You hold a high bar on testing and code review, and you lift it by example, so the team ships solutions that don't page anyone six months from now. You share the load. That includes pitching in on operational work and an on-call rotation for critical alerts - because the people who built the systems are the people best placed to keep them healthy. We take on-call seriously and we don't make it miserable. You build relationships with other engineers, product managers, and the wider org. The best supply-chain engineers are the ones people want in the room. You make the team better. Senior is a leadership level here. You mentor without being asked, spot gaps and bring solutions, and set a technical bar others want to meet. 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. JOINING THE BASH TEAM We empower our people to choose where they would like to do their best work, with the tools they need to get there but we also encourage our teams to travel so we can also make magic happen face to face . Our offices are a vibe, which doesn’t hurt. They ar
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.