David Lawson · Data & Solution Architect

Architect. Builder. Coach.

I design data platforms, write production code alongside your engineers, and grow the team until it doesn't need me. People call it player coach. I call it the only way architecture actually sticks.

The player-coach thing

One graph, two jobs

DLingestionlakehousemodelsAPIsanalyticsengineerengineeranalystgradlead

systems I build

The player

I still ship. Ingestion frameworks, dimensional models, the gnarly orchestration code nobody wants to own — I write it, review it, and get paged for it. An architect who stopped coding is a historian with opinions.

The coach

Every design session doubles as teaching. Pairing on the hard parts, handing decisions away deliberately, and building the confidence of the people who'll run this platform long after I'm gone. Mentoring isn't a side quest — it's how the architecture survives.

The point

Systems and people are one graph. Design decisions shape careers; team shape decides what architectures are even possible. The best work happens when someone deliberately tends both — hands on the keyboard, eyes on the team.

0+ years building data systems
0+ engineers mentored, six now in senior roles
0 platforms shipped to production
0 platforms that still need me on speed-dial

The job, in three words

Same person, whole job

Architect

noun

Gives the system its shape. Target architectures, data models, and decisions with the trade-offs written down — owned in daylight, defended in review.

Builder

verb, permanently

Keeps hands on the keyboard. Production code, the first vertical slice of every design, a name in the commit history and a slot on the on-call rota.

Coach

multiplier

Makes the other two compound. Pairing, mentoring, and decisions deliberately given away — so the platform outlives the person who designed it.

The longer version — how the three fit together, and why I refuse to pick one — is on the about page.

Writing

Essays with moving parts

All posts