Career / Team Lead

What is a Team Lead at Ludotech?

Leadership at Ludotech isn't a title — it's a practice. As a Team Lead, you sit at the intersection of people, process, and code. You don't just manage delivery; you build the conditions in which your team can consistently perform at their best.

Responsibilities

You own the performance of your team — which starts with defining what performance looks like, making it measurable, and making it visible. You can't improve what you don't measure.

From there, your job is to surface systemic inefficiencies, remove blockers, and build a genuine culture of continuous improvement — not as a one-off initiative, but as a daily habit embedded in how your team operates.

We also believe you can only lead what you still practice. You'll contribute directly to the codebase, mostly through pair programming, keeping you close to the real problems your team faces and credible in how you help solve them.

Typical week

Your time splits roughly 40% hands-on, 60% hands-off — though the ratio shifts day to day based on what the team needs most.

Hands-off

  • 1:1s

    Prepare and lead meaningful one-on-ones. The goal is to identify what's blocking each person and actively help them grow.

  • Coaching

    When gaps are identified, you coach toward competence. Not by solving it for them, but by building their capability to solve it themselves.

  • Reporting & analysis

    Review team performance through data, then drive the conversations that turn insight into improvement. Numbers alone change nothing.

Hands-on

  • Bottleneck removal

    Identify the most critical constraint on the project and contribute to solving it directly alongside the team.

  • Code review

    Async and sync, following the ship / show / ask pattern.

  • Architecture

    Own the major technical decisions and ensure their rationale is understood across the team.

Competencies

This isn't a checklist of prerequisites — it's a map of what you'll develop and deepen within Ludotech.

Leadership & process

  • Lean management: Kanban, WIP limits, one-piece flow, queue management
  • PDCA (Plan–Do–Check–Act) cycles
  • Standardisation and process documentation

Technical

  • AI harness programming
  • Test-Driven Development (TDD)
  • Domain-Driven Design (DDD)
  • Distributed systems

Do you want to join us?

Get In Touch

Tell us a bit about yourself.

Send us your details and we will get back to you.