Trevor Block

Why this persona fits the audience

Owns the service map for a payments platform with multiple APIs, worker queues, and third-party integrations. Maintains diagrams in Structurizr and Markdown notes, and periodically updates them when the team changes services or split deployments. Works closely with two other engineers and the CTO, and spends time translating architecture decisions into artifacts the rest of the team can follow.

• Age: 34
• Location: Manchester, UK
• Occupation: Staff Software Engineer
• Income: £98k base + equity
• Education: MEng Computer Science
• Company size: 12 people
• Years in role: 4

“A diagram that doesn't change when the code changes isn't documentation; it's just decoration.”

Trevor Block, 34, is a Staff Software Engineer based in Manchester, UK, currently serving as the primary architectural guardian for a nascent fintech startup. Holding an MEng in Computer Science from the University of Manchester, he spent five years at a larger financial institution before joining the current twelve-person team four years ago. His role has evolved from pure coding to becoming the bridge between abstract strategy and concrete implementation. Trevor owns the entire service map for their payments platform, which navigates a labyrinth of multiple APIs, asynchronous worker queues, and fragile third-party integrations. Unlike many of his peers who rely solely on code comments, Trevor insists on maintaining rigorous diagrams in Structurizr, supplemented by detailed Markdown notes. However, this process is labor-intensive; he frequently battles against 'documentation drift,' where the visual representation lags behind the rapidly evolving codebase. He works in close proximity with two other senior engineers and the CTO, spending a disproportionate amount of his week translating high-level architectural decisions into artifacts that the rest of the team can follow. Despite his technical prowess, he feels the weight of the 'single point of failure' risk inherent in being the sole owner of such critical documentation. He is pragmatic about money, valuing stability and long-term growth over immediate gains, and views his equity as a bet on the company's survival rather than a guaranteed payday. His life is a careful balance of high-stakes technical problem-solving and a quiet personal existence centered around his daughter and his hobbies in mechanical engineering and photography.

Background & daily life

A day in their life

Trevor wakes at 6:00 AM for a 5km run along the canal, then returns to his loft to brew coffee and scan industry newsletters while his dog sleeps nearby. By 8:30 AM, he joins the team on Slack, diving straight into a review of a pull request concerning the new fraud detection service. His morning is dominated by a 45-minute sync with the CTO to align on a critical API versioning strategy. Lunch is a quick salad eaten at his desk while debugging a race condition in the settlement worker queue. Afternoon hours are reserved for deep work: updating the System Context diagram in Structurizr to reflect the latest microservice split. He attends a retrospective at 4:00 PM, where he gently pushes back on a proposal that lacks sufficient error handling. He leaves the office by 6:30 PM, often taking a walk to decompress before picking up his daughter or cooking dinner. Evenings are for restoration—either tinkering with a keyboard switch mod or reading fiction—before bed.

Lifestyle

Trevor lives in a stark, industrial-style loft in Ancoats, filled with vintage furniture he's restored himself and a wall of high-end mechanical keyboards. His routine is rigid: 6:00 AM wake-up, a run along the Rochdale Canal, followed by black coffee and reading before work. He treats his health seriously, meal-prepping lean proteins and vegetables on Sundays to avoid fast food during crunch weeks. Financially, he is conservative; despite his solid income, he maximizes pension contributions and keeps cash reserves for market volatility, viewing his equity as a long-term gamble rather than liquid wealth. Socially, he is selective, preferring deep one-on-one conversations over loud pub crowds, though he maintains a tight-knit circle of fellow engineers from his university days in Manchester.

Work life

As the de facto architect for a twelve-person fintech startup, Trevor shoulders the burden of the entire service map. His day involves wrestling with the complexities of payment reconciliation across three distinct banking APIs and ensuring worker queues don't deadlock during peak transaction times. He relies heavily on Structurizr for formal diagrams but keeps informal context in Markdown files scattered across their internal wiki. The pressure is constant; with only two other engineers, any misstep in deployment logic cascades immediately. He spends significant time translating high-level strategic decisions made by the CTO into concrete, actionable artifacts that the wider team can actually read and implement without ambiguity.

Relationships

Trevor is divorced, with shared custody of his daughter, who stays with him every other weekend. He maintains close contact with his parents in Leeds, calling them weekly. His professional network is anchored by the CTO, who acts as both boss and intellectual sparring partner, and two senior colleagues he trusts implicitly. He occasionally mentors students at the University of Manchester, finding value in explaining complex concepts simply. He has no strong political affiliations but engages deeply with local community initiatives regarding digital literacy.

How they decide

Analytical and evidence-based. Trevor rarely makes impulsive choices, preferring to gather data, simulate outcomes, and consult trusted peers before committing. He values open-source solutions that offer transparency over proprietary 'black box' tools. If a solution requires a significant shift in workflow, he will demand a pilot period with clear success metrics. He is generally resistant to hype cycles and prefers tools that demonstrate tangible ROI in terms of reduced cognitive load or improved reliability.

How they sound

Trevor speaks with a clipped, precise Mancunian cadence. He avoids filler words and jargon unless it serves a specific technical purpose. When explaining complex ideas, he uses analogies related to physical infrastructure or logistics. He is direct but not rude, often prefacing corrections with 'Actually, I think we need to consider...' rather than blunt negation. He dislikes corporate buzzwords like 'synergy' or 'disruption' and finds them annoying. In conversation, he listens more than he speaks, pausing thoughtfully before responding. He tends to use short, declarative sentences to convey authority and clarity.