Technical Team Lead

Leadership

• Puts the team's success before personal technical contribution.
• Creates an environment where engineers feel safe to raise problems, take risks, and ask for help.
• Models the behaviours they expect to see - in code quality, communication, and attitude.
• Gives credit generously and takes accountability seriously.
• Makes decisions clearly and confidently, even under ambiguity, and explains the reasoning behind them.
• Protects the team from unnecessary noise and distraction, creating space for focused delivery.
• Sets a tone of high standards and collective ownership - quality is everyone's responsibility.
• Acts as a consistent and dependable presence; the team knows what to expect from their lead.

Delivery

• Holds the team accountable to commitments without resorting to pressure or micromanagement.
• Identifies delivery risk early and surfaces it clearly to the EM.
• Keeps delivery moving by removing blockers actively rather than waiting for them to resolve.
• Maintains a clear picture of what the team is working on, at what pace, and where the risks lie.
• Ensures ceremonies are purposeful and time-boxed - stand-ups, retrospectives, and planning sessions drive decisions, not discussion.
• Tracks work at the right level of detail - visible enough to spot problems, not so granular that it becomes micromanagement.
• Escalates early and transparently - communicates bad news quickly, with context and a proposed response.
• Keeps quality and pace in balance, making trade-offs visible rather than quietly absorbing technical debt.

People Development

• Invests consistently in 1:1s, treating them as the most important recurring meeting in their week.
• Gives feedback that is specific, timely, and genuinely intended to help.
• Notices when engineers are struggling - technically or personally - and responds with care.
• Understands each engineer's ambitions and connects day-to-day work to longer-term development goals.
• Advocates for their team's growth - actively seeking stretch opportunities, cross-team exposure, and meaningful challenges.
• Recognises and celebrates good work visibly, reinforcing the behaviours and standards the team values.
• Builds psychological safety within the team - engineers challenge each other's ideas, not each other's worth.
• Works with the EM to build individual development plans that are grounded, honest, and action-oriented.

Technical Direction

• Maintains enough technical contribution to retain credibility and context, without crowding out the team.
• Makes technical decisions transparently, explaining reasoning and inviting challenge.
• Keeps up with technology trends and brings relevant insight back to the team.
• Sets and upholds clear technical standards - code review expectations, testing coverage thresholds, and documentation norms.
• Facilitates design reviews and architecture conversations, ensuring the team thinks through implications before building.
• Identifies and prioritises technical debt that poses real risk to quality or velocity, not just theoretical imperfection.
• Escalates significant architectural decisions to the right people rather than making them alone or avoiding them.
• Encourages a culture of technical curiosity - the team is always learning, not just delivering.

Communication

• Communicates clearly with the team about priorities, context, and decisions - no one is left guessing.
• Translates upward and outward - represents the team's work, blockers, and progress to stakeholders and the EM accurately.
• Runs meetings with purpose and structure - outcomes are clear, actions are owned, and time is respected.
• Listens actively in 1:1s and team conversations - hears what is said and notices what is not.
• Shares context freely - the team understands why they are building what they are building.
• Writes clearly and concisely - whether in tickets, design notes, or status updates.
• Adapts communication style to the audience - speaks differently to engineers, product managers, and senior stakeholders.
• Raises concerns and disagreements constructively - directly, respectfully, and with proposed alternatives.

Emotional Intelligence

• Manages their own emotions under pressure - maintains composure and models stability when things go wrong.
• Demonstrates genuine empathy - understands the human experience of their engineers, not just their output.
• Recognises signs of stress, disengagement, or burnout in the team and responds with care and action.
• Accepts feedback about their own leadership with openness and without defensiveness.
• Builds trust through consistency - does what they say, says what they mean.
• Navigates difficult conversations - performance, conflict, or disappointment - with honesty and compassion in equal measure.
• Does not let personal frustrations bleed into team interactions - is self-aware enough to manage their own state.
• Creates space for engineers to be human - acknowledges that wellbeing and performance are connected.

Collaboration

• Partners effectively with the EM - sharing honest upward feedback, not just good news.
• Builds strong working relationships with other TTLs - shares knowledge, patterns, and approaches across team boundaries.
• Engages constructively with Product and Delivery colleagues - understands their priorities and constraints.
• Represents the team's interests in cross-team conversations without becoming territorial or defensive.
• Participates actively in engineering communities of practice, guilds, and cross-team forums.
• Brings the team's work and learnings into wider conversations - the team's knowledge does not stay siloed.
• Seeks input from peers when facing unfamiliar problems - collaboration is a strength, not a weakness.
• Maintains healthy working relationships under pressure - conflict is resolved with professionalism and care.