Eric McKenzie

Why this persona fits the audience

Leads a 6-person platform squad in London that builds internal agents for compliance triage and report generation. The team routes requests through a homegrown gateway, uses both OpenAI and Azure OpenAI, and reviews usage and budget exports in weekly engineering meetings.

• Age: 41
• Location: London, UK
• Occupation: Engineering Manager
• Income: £118k salary plus bonus
• Education: MEng Software Engineering
• Company size: Mid-sized fintech firm (approx. 400 employees)
• Years in role: 3

“If you can't measure the cost of every single request your system makes, you aren't running an engine; you're just driving blindfolded into a fog bank.”

Eric McKenzie is a seasoned engineering leader based in Richmond, London, who has spent over fifteen years navigating the complexities of software architecture and team dynamics. Holding an MEng in Software Engineering, he transitioned from hands-on coding to management five years ago, driven by a belief that the most effective leaders are those who understand the underlying mechanics of their systems. Currently, he oversees a specialized platform squad within a prominent fintech firm, where his primary mandate is to build and maintain robust internal AI agents. These agents handle critical compliance triage and automated report generation, serving as the digital backbone for the company's regulatory adherence. Eric's leadership style is defined by an unwavering commitment to reliability and process discipline. He views the engineering organization not merely as a cost center but as a steward of resources, particularly in the volatile landscape of AI consumption. His recent focus has been on refining the homegrown gateway that routes traffic between OpenAI and Azure OpenAI instances. This system is the linchpin of his team's operations, requiring meticulous tuning to balance speed, accuracy, and cost. He is intimately familiar with the nuances of token pricing, context window limits, and the hidden overheads of large-scale inference. Despite his technical prowess, Eric remains acutely aware of the human element in engineering. He fosters a culture where transparency about resource usage is paramount, ensuring his six direct reports understand the financial implications of their architectural choices. He regularly presents detailed usage and budget exports in weekly engineering meetings, transforming raw data into actionable insights for the wider business. While he enjoys the intellectual challenge of optimizing these systems, he is constantly vigilant against the creeping inefficiencies that come with rapid iteration. For Eric, true success is measured not by the number of features shipped, but by the predictability and safety of the infrastructure that supports them.

Background & daily life

A day in their life

Eric wakes at 6:00 AM for a run along the river, followed by a shower and breakfast while scanning the FT and Hacker News. By 7:30 AM, he is on the train to Waterloo, reviewing the latest incident reports from the overnight shift. Upon arriving at the office, he attends the daily stand-up at 9:30 AM, focusing on blockers related to the new compliance agent deployment. Mid-morning is dedicated to a deep-dive session with a senior engineer to debug a latency issue in the routing logic. Lunch is a quick sandwich eaten at his desk while answering emails. The afternoon involves a cross-functional meeting with the compliance team to align on new regulatory requirements, followed by a detailed review of the Azure OpenAI usage dashboard to identify anomalies. He wraps up at 6:00 PM, taking a final walk to decompress before heading home. Dinner with his family is sacred, after which he might spend 30 minutes reading a technical paper before bed.

Lifestyle

Eric commutes via train from Richmond to the City, using the hour to read or review spreadsheets. He is an early riser, often up by 6 AM to run before work, maintaining a strict routine that leaves little room for spontaneity. His social life revolves around his immediate family and a small group of former university mates; he prefers quiet dinners at home over loud networking events. He is financially secure but frugal, viewing money as a tool for stability rather than indulgence. He actively manages household budgets and invests in long-term savings, avoiding unnecessary debt. On weekends, he cycles along the Thames Path or restores vintage furniture, activities that require focus and patience, mirroring his approach to professional challenges.

Work life

Eric spends his days balancing technical oversight with people management within his six-person squad. His primary concern is the stability and cost-efficiency of their internal AI gateway, which routes traffic between various LLM providers. Mornings are dominated by stand-ups and reviewing automated alert logs from the previous night's runs. Afternoons involve code reviews, architecture planning for new compliance agents, and one-on-ones with direct reports. He is deeply involved in the weekly budget reconciliation meeting, where he scrutinizes token usage against projected forecasts. The pressure comes not from aggressive sales targets, but from the need to prevent service outages and avoid unexpected cloud spend spikes that could impact the department's quarterly performance.

Relationships

Eric is married to Sarah, a primary school headteacher, whose pragmatic nature complements his structured approach. Their relationship is built on shared domestic responsibilities and mutual respect for each other's professional demands. He has a close-knit circle of three friends from university who meet monthly for dinner, mostly discussing local politics and cycling gear rather than work. He relies heavily on his direct reports for technical validation but defers to his CTO for strategic alignment. His parents live in Sussex and visit occasionally; they value his steady career but worry about his tendency to work late.

How they decide

Eric is a cautious, evidence-based decision-maker who rarely acts on impulse. He requires comprehensive data sets and clear comparative metrics before committing to any new process or tool. He tends to be skeptical of marketing claims and prefers peer-reviewed case studies or internal pilot results. When evaluating options, he prioritizes risk mitigation and long-term maintainability over short-term feature gains. He seeks consensus within his team but retains final veto power if the data suggests a path of high uncertainty.

How they sound

Eric speaks in a measured, articulate British accent, favoring precise terminology over colloquialisms. His cadence is deliberate, often pausing to ensure accuracy rather than filling silence. He avoids hyperbolic language like 'revolutionary' or 'game-changing,' preferring terms like 'incremental improvement' or 'operational efficiency.' In meetings, he asks probing questions about edge cases and failure modes. He rarely raises his voice, even when frustrated, instead using a tone of concerned inquiry to highlight risks. He values clarity and dislikes ambiguity, often asking for written summaries of verbal agreements.