Lead Software Engineer

Technical Leadership

• Makes high-quality technical decisions with confidence and communicates the reasoning clearly to all levels of audience.
• Influences engineering direction across multiple teams without requiring formal authority - through expertise, evidence, and trust.
• Elevates the technical quality of everything they touch - directly through their own work and indirectly through the standards they set.
• Anticipates technical problems at system and organisational level, not just within the boundary of a single team or service.
• Steps into complex, ambiguous technical situations and brings clarity - structuring the problem before reaching for solutions.
• Earns the respect of engineers around them through visible technical depth, sound judgement, and consistent follow-through.
• Demonstrates mastery of the domain's core technologies while maintaining enough breadth to assess cross-domain trade-offs.
• Actively works to distribute technical knowledge across teams, reducing concentration of expertise in individuals including themselves.

Standards & Engineering Excellence

• Defines engineering standards that are specific, measurable, and genuinely adopted - not aspirational documents that gather dust.
• Identifies the delta between current practice and desired excellence, and builds credible plans to close it progressively.
• Holds teams accountable to agreed standards through review, coaching, and direct conversation - not just documentation.
• Contributes to organisation-wide standard-setting forums with prepared, well-reasoned positions rather than ad hoc opinions.
• Tracks standards adoption across teams systematically and uses the data to target coaching and improvement effort.
• Raises the quality floor rather than just rewarding high performers - improving average practice across the whole domain.
• Creates feedback loops between standards definition and real-world delivery experience, keeping standards grounded and useful.
• Champions engineering quality in forums where it is most under pressure - planning sessions, scope conversations, and release decisions.

Strategic Thinking

• Thinks in systems - understands how decisions in one area create constraints and opportunities across the whole domain.
• Engages with engineering strategy as an active contributor with a prepared point of view, not as a passive implementor of others' decisions.
• Balances technical idealism with commercial and delivery reality, making pragmatic calls without abandoning long-term quality.
• Identifies capability and technology gaps at domain level before they become delivery risks, and recommends investment priorities.
• Anticipates the second and third-order effects of architectural and technology decisions across multiple teams and time horizons.
• Connects technical investments to measurable business outcomes - making the case for engineering quality in terms stakeholders value.
• Shapes the engineering roadmap within their domain, balancing feature delivery, technical health, and capability building.
• Stays informed about industry direction and assesses its implications for the organisation's technical strategy with genuine rigour.

Developing Others

• Invests in building the next generation of technical leaders within their domain - not just developing good individual contributors.
• Creates conditions for senior engineers to take on meaningful technical leadership responsibilities with appropriate support and safety.
• Shares knowledge at scale - through documentation, internal talks, structured reviews, and community leadership.
• Provides mentoring that is structured, honest, and tailored to the individual's stage of development and specific growth edges.
• Gives stretch assignments deliberately - calibrated to challenge without overwhelming, with regular check-ins and honest feedback.
• Builds psychological safety across their domain, making it genuinely acceptable to raise technical concerns, admit uncertainty, and experiment.
• Identifies emerging technical leaders early and advocates for their development with engineering management.
• Measures their impact on others' growth, not just their own technical output - and adjusts their approach when the impact is insufficient.

Influence & Communication

• Influences decisions and direction through evidence, expertise, and credibility - not through position, volume, or persistence.
• Builds trust with engineering leadership, product, and delivery through consistent, grounded technical judgement over time.
• Advocates effectively for engineering excellence in forums where technical priorities are negotiated against commercial pressures.
• Communicates complex technical concepts to executive and non-technical audiences in ways that inform real decisions.
• Writes with clarity and precision - technical proposals, strategy documents, and standards that are genuinely read and used.
• Listens before advocating - understanding the constraints and perspectives of others before forming or asserting a position.
• Facilitates alignment across teams with differing technical approaches, finding workable common ground without forcing false consensus.
• Represents engineering perspective in senior forums with authority and preparation, not just as a delegate reporting upwards.

Architecture & Design

• Leads architectural decision-making at domain level with clear documentation of context, options considered, and rationale.
• Evaluates and evolves platform and technology choices with a long-term perspective and honest assessment of organisational trade-offs.
• Designs systems that are operable, observable, and maintainable by teams beyond the original builders.
• Reviews architectural proposals from others with rigour and generosity - improving the work rather than just approving or rejecting it.
• Identifies architectural drift and technical debt at domain level and builds structured plans to address it over time.
• Engages with cross-domain architects to ensure local decisions are compatible with wider organisational direction.
• Applies proven patterns with appropriate context-sensitivity rather than applying them mechanically regardless of fit.
• Maintains an honest view of the current architecture - including its weaknesses - rather than defending it for its own sake.

Community Leadership

• Leads or co-leads an engineering community of practice with genuine energy and a clear sense of purpose.
• Creates a community culture where engineers want to participate because it is genuinely valuable to them, not because attendance is expected.
• Curates and drives a community agenda that addresses real engineering challenges rather than defaulting to low-stakes topics.
• Brings external ideas and industry developments into internal engineering communities with relevant, applied framing.
• Identifies and develops community contributors, building a base of active participants beyond a small core.
• Uses community forums to surface emerging standards needs, common pain points, and cross-team alignment opportunities.
• Measures community health honestly - participation, outcomes, and perceived value - and adjusts the approach when it is not working.
• Creates artefacts that outlast individual sessions - documented decisions, shared playbooks, and reusable patterns.

Delivery & Execution

• Maintains credibility as a hands-on engineer - contributing meaningfully to technical work, not just advising from a distance.
• Helps teams unblock themselves from complex technical problems without creating dependency on their involvement.
• Identifies delivery risk at domain level and works with engineering management and delivery leads to address it proactively.
• Reviews cross-team delivery plans from a technical perspective, identifying incompatibilities and integration risks early.
• Holds the quality bar during periods of delivery pressure, ensuring short-term pragmatism does not erode long-term technical health.
• Contributes to post-incident reviews at domain level, identifying systemic causes and driving structural improvements.
• Ensures that technical standards remain operationally grounded - informed by what actually happens in production, not just what was planned.
• Tracks technical health metrics across their domain and uses them to make evidence-based arguments for engineering investment.