01 - Software

Engineering leadership

I studied Electrical & Electronic Engineering at uni, but in my final year I found programming and never looked back! Fifteen years on, I split my time equally between building teams and building software. Recently, my roles have been at companies where neither the team nor the product exists yet.

What I do

Six kinds of problem

Most engagements are some mix of these, usually (but not always!) weighted by how early-stage the company is.

01

Zero to one

Standing up a product and a team at the same time, when neither exists yet and both are urgent.

02

Scaling the function

Turning a handful of engineers into an organisation: hiring, structure, and the process that holds at twenty people but not at three.

03

Audit/Technical direction

Architecture reviews, stack decisions, and the unglamorous work of paying down the technical debt that an early codebase accumulates.

04

Fractional leadership

Senior engineering leadership without a full-time hire, for companies that need the judgement more often than the headcount.

05

AI-built prototypes

An idea built with AI by someone who has never written software. Working out whether it is a throwaway prototype or a real foundation, then helping them do whichever the answer implies.

06

Growing a technical lead

A strong engineer who could run the function in a year or two, but not yet. Doing the job next to them for a while, so there is something to learn from.

History

Where I have done it

Consulting

Current work runs through ArmJen Pty Ltd.

Based in Australia, working with teams here and in the UK. If you need senior engineering judgement more often than you need another full-time hire, get in touch.