Software Engineer; Web SDK

Direct message the job poster from Storyteller

🇿🇦 Up to ZAR 700,000 salary on a full time, permanent employment contract

🌎 Fully remote working anywhere in South Africa!

🏖️ 33 Days Paid Leave and Benefits

✨ High-growth SaaS product trusted by major global sports brands

💻 Modern stack, great tooling, AI-first engineering culture

We’re looking for engineers who take initiative, spot opportunities, and move ideas forward proactively. Builders who are excited to use AI as a core part of how they work, think from first principles, and keep things simple – not people who just want to hand-craft every line of code.

You’ll be hands‑on in the Web SDK and backend services that support it, working on real features used by major sports and media organisations, and using AI heavily to design, build and refine solutions.

Storyteller is a high‑growth B2B SaaS platform that lets companies integrate Stories into their own apps and websites. Popularised by Instagram and Snapchat, Stories boost engagement, retention and revenue for our clients.

Our platform includes SDKs for Web, iOS and Android, publishing tools, analytics and ad support – giving enterprises a complete Stories solution in days. We work with globally recognised sports and media brands, and you’ll see your work used live by millions.

You’ll join the team responsible for our Web SDK and the services it talks to. The SDK is how customers embed fast, beautiful, interactive Stories experiences into their own products, so integration quality, performance and developer experience really matter.

This is a hands‑on coding role, but not a “shut the door and code in isolation” one:

• You’ll use AI tools by default to explore, scaffold and refactor.
• You’ll think in terms of problems, constraints and outcomes, not just tickets.
• You’ll care about how easy we are to integrate with as much as how elegant the code looks.

You won’t be managing people or owning a team – but you will be expected to own your work end‑to‑end, contribute to how we solve problems, and help us keep raising the bar.

• Own features end‑to‑end: understand the problem, design a simple solution, build it (often with AI assistance), test it, and refine based on feedback.
• Improve performance, reliability and developer ergonomics of the Web SDK and supporting services.

• Work with Product and Delivery to understand real customer use‑cases and constraints.
• Propose simple, pragmatic solutions instead of over‑engineering.
• Help streamline the integration experience so partners can get to “ story live” quickly and safely.
• Enhance documentation, code examples, and integration guides, often using AI to draft and then editing for clarity.
• Identify friction points for integrators and proactively champion improvements.
• Make small, continuous DX improvements (tooling, scripts, templates) rather than waiting for a big “clean‑up project”.
• Use AI tools by default for exploration, scaffolding and refactors – and then verify outputs with tests, types, and your own judgement.
• Use first‑principles thinking to cut through complexity: start from the goal and constraints, choose the simplest thing that works, and be willing to delete your own code when a better approach appears.
• Participate in thoughtful code reviews: give clear, kind, direct feedback and be open to having your own ideas challenged.
• Help improve CI pipelines, test suites and dev scripts so the whole team moves faster and more safely over time.
• Maintain high ownership and follow‑through from idea to release: surface blockers early, communicate clearly, and finish what you start.

• Familiarity with APIs/HTTP, performance tuning, and SQL/No
  
  SQL basics.
• A proactive mindset – you look ahead, anticipate problems, and propose solutions instead of waiting to be told what to do.
• AI‑native working style – you’re comfortable adopting new tools early, especially AI‑assisted coding, and you see AI as the default starting point rather than a last resort.
• Clear reasoning and trade‑off thinking – you can explain why you chose one approach over another in simple language.
• Stron…