Chris Medhurst

Why this persona fits the audience

Oversees engineering for a 50-person B2B API company in Chicago with two SREs and one DevOps engineer. He reviews outage patterns, incident summaries, and MTTR trends each month, and his team maintains internal dashboards for alert volume and service health.

• Age: 42
• Location: Chicago, Illinois, USA
• Occupation: VP of Engineering
• Income: $250k-$320k total compensation
• Education: B.S. Electrical Engineering
• Company size: 50 employees
• Years in role: 4 years

“If you can't measure it, you can't fix it, and if you can't fix it, you don't own the customer's trust.”

Chris Medhurst is a 42-year-old VP of Engineering based in Chicago, overseeing a lean but critical team at a B2B API startup. Holding a B.S. in Electrical Engineering from a state university, he spent the first decade of his career in hardware manufacturing before pivoting to software, a transition that informs his rigorous, systems-thinking approach. Currently managing a 50-person organization, he operates with a distinct advantage: deep technical empathy combined with a ruthless focus on operational efficiency. Unlike many executives who delegate stability entirely, Chris remains hands-on, personally reviewing MTTR trends and outage patterns every month. He has built a culture where 'blameless post-mortems' are standard, yet accountability for process improvement is absolute. His workspace is a testament to his personality: organized, minimal, and dominated by multiple monitors displaying real-time telemetry. He has invested heavily in custom internal dashboards to visualize alert volumes, as he finds off-the-shelf tools too noisy for his specific architecture. Recently, he made the strategic decision to freeze new feature development for six weeks to tackle technical debt, a move that alienated some sales stakeholders but solidified the platform's uptime. He is deeply concerned with the fragility of modern cloud architectures, particularly the 'alert fatigue' plaguing his two SREs and one DevOps engineer. While he earns a robust $250k-$320k, he views money as a tool for stability rather than status, reinvesting savings into his children's futures and a diversified portfolio. His life outside of work is structured around discipline: marathon training, golf, and a strong emphasis on family presence. He is not a disruptor looking for the next big thing; he is a steward ensuring the engine doesn't stall while others drive the car.

Background & daily life

A day in their life

Chris wakes at 5:30 AM, immediately hitting the treadmill for 45 minutes while listening to a podcast on organizational behavior. By 7:00 AM, he is helping his daughter pack her lunch before heading to his office in the River North district. His morning begins with a 'standup' that doubles as a review of overnight alerts, where he spots a spike in latency errors and immediately pages the on-call SRE. Between 9:00 and 11:00, he attends a product roadmap meeting, pushing back on a feature request that would compromise API stability. Lunch is usually eaten alone at his desk while reading a whitepaper on distributed tracing. Afternoon hours are dedicated to code reviews and a recurring meeting with his direct reports to discuss career growth and burnout signs. At 6:00 PM, he leaves, runs errands to pick up groceries, and spends the evening coaching his son's soccer team or playing rounds of golf on weekends. He goes to bed by 10:30 PM to ensure seven hours of sleep, knowing his cognitive performance is his primary asset.

Lifestyle

Chris lives in a renovated Victorian home in Lincoln Park, valuing proximity to downtown but prioritizing quiet streets for family life. His routine is rigid: 5:30 AM wake-up for an hour of running before the kids are up. He and his wife share household management duties, though he handles all financial planning and major repairs due to his analytical nature. Money is managed conservatively; they invest heavily in index funds and education savings, avoiding luxury splurges unless it serves a specific purpose like high-end golf equipment or a reliable car. Socially, he keeps a tight circle of 3-4 friends, mostly other tech leaders or former colleagues, meeting monthly for dinner or a round of golf. He takes fitness seriously, treating his body like another system that requires maintenance, often logging heart rate data alongside his work metrics.

Work life

At his 50-person API firm, Chris acts as the bridge between executive strategy and engineering reality. With only three infrastructure specialists (two SREs, one DevOps), he personally audits every post-mortem and spends significant time refining their internal dashboards. His days are fragmented by context switching: reviewing alert fatigue logs, mediating architectural disputes, and presenting operational health metrics to the CEO. The pressure stems from the sheer lack of headcount; he cannot afford downtime because his small team cannot absorb the manual triage required after an incident. He relies heavily on Jira, Datadog, and custom Python scripts to aggregate data, spending hours manually correlating logs to find root causes that his automated tools miss. He feels a constant tension between pushing for new features and maintaining the stability of the core API.

Relationships

Chris's primary influence comes from his wife, who grounds him emotionally, and his mentor, a retired CTO who challenges his assumptions about scaling. He maintains a close bond with his two children, often involving them in simple logic puzzles or coding basics. His professional network is deep but narrow, consisting of VP-level peers in Chicago's tech scene whom he trusts implicitly. He rarely seeks public validation, preferring private feedback loops. In his community, he is known as the 'fixer'—the person called when a project stalls—but he keeps these interactions transactional to preserve his energy for his immediate family and core engineering team.

How they decide

Chris operates with a 'measure twice, cut once' philosophy. He is neither impulsive nor paralyzed by analysis; rather, he gathers quantitative evidence until the risk curve flattens, then executes decisively. He dislikes ambiguity and will not commit to a path without seeing historical data or a clear pilot result. Peer recommendations carry weight only if backed by concrete metrics, and he is skeptical of marketing fluff. Once a decision is made based on logic, he rarely second-guesses himself, even under pressure.

How they sound

His speech is clipped, precise, and devoid of filler words. He uses industry terminology freely (e.g., 'toil,' 'blast radius,' 'circuit breaker') but avoids jargon when speaking to non-engineers. He speaks with a midwestern cadence—direct and unpretentious—and rarely raises his voice, even during crises. He tends to pause before answering complex questions, preferring to structure his thoughts logically rather than reacting emotionally. He avoids vague phrases like 'maybe' or 'I think,' opting instead for 'based on the data' or 'here is the probability.' He values brevity and clarity above all else.