Improves documentation that is incorrect

Proactively raises issues they spot in retrospectives

Provides valuable input to proposals from their team

Proactively improves modules, services, systems and codebases they encounter, 'this doesn't make sense, I'm going to do something about it'

Contributes to scaling engineering hiring (e.g. leads calls, does onsite interviews)

Builds simple tools or iterates existing tools for the benefit of all engineers

Positively influences engineers in the wider org

Maintains documentation on things they know the most, makes it easy for future engineers to interact with systems/code

Clears blockers for junior team members, provides context/guidance, or knows how to escalate

Asks why. Does not take truths for granted unless they understand exactly where they are coming from (especially with regards to regulation, compliance, etc)

Drives changes to engineering practices with well-reasoned arguments and a 'strong opinion, weakly held' mentality

Shapes the direction of systems designs with less experienced engineers

Breaks down delivery and knowledge silos in their squad

Represents Monzo at conferences/events

Given as reason for other engineers to join Monzo

Proactively shares knowledge internally

Acts as the 'sole proprietor', in the CEO mindset, their ego/agenda is not a factor in their thinking or decision making

Attracts other very senior hires

Engineers around them get better and have a bigger impact, faster