Randolph Nitzsche

Why this persona fits the audience

Co-founded a five-person agency and still reviews PostgreSQL and MySQL queries when client work gets hairy, especially during onboarding and data handoffs. He is also the person who standardizes dev tools for the team, while personally alternating between a paid desktop client and the command line.

• Age: 44
• Location: London, UK
• Occupation: CTO and cofounder
• Income: £110k salary + equity
• Education: BEng in Electronic Engineering
• Company size: 5
• Years in role: 8

“I don't have time to be a digital nomad. My workstation setup is a viable fire hazard and still more efficient than most people's services.”

Randolph Nitzsche's engineering career began with a now-embarrassing stint building sensor networks for agricultural drones, but his real education came from the London tech scene's post-dot-com wreckage. He cut his teeth rebuilding broken systems for agencies that were either too cheap to hire or too arrogant to anticipate failure. This experience later informed his own agency's design: minimal client fiddling, unapologetic technical rigor, and a strict 'no bullshit' policy with clients who think databases are just 'spreadsheets with more numbers'. His engineering background shows in his approach to tools - he'd rather write a quick Python script than spend hours configuring yet another 'modern' IDE, and his terminal tabs contain some Rust code that's been open for 18 months. The agency's hybrid open-source/paid toolchain reflects his own struggles: he's built enough migrations to distrust vendor lock-in, but as a five-person shop, open-source overhead is a luxury they can't often afford. His recent decisions have been shaped by two client disasters: one where a marketing agency's SQL ignorance nearly bankrupted a startup, and another where his own team's inconsistent tooling cost them a major contract. This dual legacy explains why he still personally reviews every complex query during onboarding, and why he's been quietly evaluating tools that might finally bridge his team's toolchain gap. He's painfully aware that his 'just fix it' mentality has created technical debt, but scaling the business means finding solutions that don't require him to be the bottleneck. Despite his grumbling about the state of database tools, he still gets vaguely excited by Rust's performance numbers and dreams of the day he can skip writing wrapper scripts for clients. His sailing analogies in team meetings are both dreaded and effective. While he'll never admit it, he secretly enjoys cleaning up the occasional messy database - it's the only time he feels completely in control.

Background & daily life

A day in their life

Randolph's weekday starts at 5:45am with cold water immersion (a sailboat-racing habit he can't quit) followed by a standing desk session before the team arrives. By 8am he's in the midst of a data handoff from a marketing client whose CSV files contain 17 inconsistent date formats. The morning devolves into querying PostgreSQL via his paid desktop client (too slow) and fall-back CLI (too manual) in alternating frustration. At lunch, he sketches a plugin architecture on his whiteboard for a tool that could combine both approaches. The afternoon is spent cleaning up a junior's failed data migration (again) while fielding calls from a former colleague now working at the same client. He wraps up by 7pm but spends an extra hour optimizing a query from this morning before heading to the sailing club where he silently judges a colleague's hull maintenance. Back home, he microwaves a ready meal, reads technical blogs until 11pm, and falls asleep to a podcast about 18th-century navigation.

Lifestyle

Randolph lives in a converted Hackney loft, where his only furniture purchases in the last five years consist of a standing desk, a 4K monitor, and an espresso machine he overpaid for. His ideal weekend involves long walks along the Thames with his aged German Pointer, Saturday mornings debugging a client's migration script while listening to BBC Radio 4, and Sunday afternoons tinkering with his 34-foot sloop in Portsmouth. He has a standing coffee date with a former colleague (now a rival at a larger agency) where they dissect the week's technical frustrations. Health-wise, he's strictly four coffee max before 2pm, tries to run 3-4 times a week (tracking distance scrupulously), and has been meaning to schedule a dentist appointment for months. His wardrobe consists of Patagonia fleeces, black jeans that look identical, and a single gym bag that serves as both gym bag and weekend sailing kit.

Work life

As CTO of a five-person agency, Randolph's days toggle between high-level architecture decisions and manual cleanup of client data messes. His team calls it 'the Nitzsche Repair Protocol' when he rolls up his sleeves to fix migration scripts or optimize queries that are running at 47% efficiency. He recently standardized the team on GitLab (after an acrimonious two-week debate) but still uses Bevy for his personal projects because 'it's just faster'. Most days start with a quick review of overnight monitoring alerts, followed by a 7am standup where he aggressively prunes conversation. He's currently rebuilding the agency's onboarding workflow from scratch after a client's data handoff went catastrophically wrong last quarter. 'It was like handing someone a car with the engine missing - technically complete, but you'll be lucky if it moves.'

Relationships

Randolph's immediate family is an absent ex-wife in Edinburgh and a teenage daughter who's recently discovered his name is embarrassing (she insists on 'Randy'). His closest relationships are with his sailing cohort, a group of engineers who meet annually to race a legacy yacht they collectively own. He admires his former professor from Imperial (now a database architect at Google) but finds his LinkedIn posts complacent. His only regular social commitment is a monthly dinner with his agency's sole non-technical hire - the account manager he can't decide is genius or maddening. Outside work, his biggest influences are the developers who write detailed migration guides on tech blogs and the one mechanic at Portsmouth Marina who doesn't sigh when Randolph shows up with a 'quick' question.

How they decide

Randolph makes decisions like someone who's been burned by both over-planning and improvisation. He'll research a technical choice exhaustively but deploy while still writing the documentation. Prefers tools with clear upgrade paths and hates 'beta quality' software. Delegates cautiously - will let a junior make a call if the stakes are low, but reverts to command when he smells a performance bottleneck. Dislikes consensus-building meetings but values brutal honesty in code reviews. Always buys the wrong tool first (once it's too late).

How they sound

Randolph's speech pattern is clipped and efficient, with pauses that suggest he's mentally compiling the next efficient explanation. Uses technical jargon precisely but cuts through bullshit quickly. Affects a mild impatience with abstractions ('Let's just look at the query plan'). Avoids grandiose language about his work ('It's not revolutionary, it's just not broken'). When annoyed, his sentences become shorter and his Cockney accent more pronounced. Never says 'disrupt' or 'synergy' (unless mocking). Has a quiet pet peeve about people who misuse 'asynchronous' and 'synchronous'.