Gregory Cartwright

Why this persona fits the audience

Owns incident response for an 80-person SaaS running on AWS and Kubernetes. Rotates on-call with 5 engineers, writes postmortems in Google Docs, and spends time tracing alerts from Datadog, Grafana, and PagerDuty into Jira tickets after outages.

• Age: 38
• Location: Austin, Texas, USA
• Occupation: Senior Site Reliability Engineer
• Income: $175k-$210k base
• Education: B.S. Computer Science
• Company size: 80-person SaaS
• Years in role: 7

“There's a certain satisfaction in knowing that when the pager goes off, you've got the tools and the knowledge to bring things back from the brink, and more importantly, to understand *why* it happened.”

Gregory Cartwright's journey into the deep end of site reliability engineering began with a fascination for how complex systems function, a trait evident even in his undergraduate Computer Science studies at the University of Texas at Austin. After graduating, he spent several years in traditional software development roles, but found himself increasingly drawn to the operational challenges and the satisfaction of building resilient infrastructure. He transitioned into SRE about seven years ago, first at a smaller startup and then landing his current role at an 80-person B2B SaaS company where he has grown into a senior position. His expertise lies in AWS and Kubernetes environments, with a particular focus on observability and incident response. Gregory is deeply committed to the principle of system reliability, viewing it not just as a job requirement but as a core professional value. He believes that thorough, clear incident records are paramount for learning and improvement, which drives his meticulous approach to postmortems. His income allows for a comfortable lifestyle, but he remains pragmatic, focusing on long-term financial security rather than conspicuous consumption. This pragmatism extends to his work; he champions practical automation that demonstrably reduces toil and improves system stability, rather than chasing every new shiny tool. He recently championed a project to consolidate their primary alerting channels into a more unified view, a decision that required extensive data analysis and buy-in from his engineering peers. He views time as a finite, valuable resource, both personally and professionally, which fuels his desire for efficient solutions and clear processes. His current challenge is finding the optimal balance between the reactive demands of incident response and proactive system hardening, a perpetual SRE conundrum.

Background & daily life

A day in their life

Gregory's typical weekday starts around 7:30 AM. After a quick breakfast and checking family news, he's at his desk by 8:15 AM, often with a strong cup of coffee. His morning is usually dedicated to reviewing overnight alerts, triaging any new issues, and checking the status of ongoing incidents. He'll spend time digging into Datadog dashboards and Grafana graphs, tracing correlations. If an incident occurred, he'll start drafting the initial postmortem notes. Before lunch, he might have a brief sync with his team or a stakeholder about a performance issue. The afternoon involves coding automation scripts, refining Kubernetes configurations, or participating in a scheduled production review. He aims to log off by 5:30 PM to be present for his family, but PagerDuty notifications can easily disrupt this.

Lifestyle

Gregory lives in a comfortable but not ostentatious three-bedroom house in a mature Austin neighborhood. He's married with one young child, which has reshaped his evening routines, prioritizing family time over late-night tinkering. He enjoys brewing his own beer on weekends and is currently optimizing his home network with a Ubiquiti setup, finding it a refreshing change from enterprise-level complexity. Financially, he's a saver, prioritizing long-term security and investing steadily, viewing his income as a tool for stability rather than overt displays of wealth. His social life is quieter these days, mostly close friends and occasional meetups with former colleagues.

Work life

As the primary owner of incident response for his SaaS company, Gregory is acutely aware of the fragility of their AWS and Kubernetes infrastructure. His on-call rotation with five other engineers means he's frequently pulled into late-night or early-morning diagnostics. He feels the pressure to not just fix issues but to document them exhaustively in Google Docs postmortems, a task he takes very seriously. He spends a significant portion of his days sifting through alerts from Datadog and Grafana, meticulously correlating them with PagerDuty events and then creating detailed Jira tickets to track resolution and prevent recurrence. The constant stream of alerts is both a source of professional challenge and a nagging background hum.

Relationships

Gregory's primary influencer is his wife, Sarah, an elementary school teacher, who grounds him and reminds him of life outside of tech. He maintains strong ties with a few college friends who are also in engineering roles, often exchanging technical war stories and advice. His immediate team of five engineers are his main professional confidantes.

How they decide

Gregory is a research-heavy decision-maker. He thoroughly investigates technical solutions, often building small proof-of-concepts or running detailed benchmarks. He values data and evidence over hype and seeks consensus among his peers for significant changes, though he's not afraid to push for what he believes is technically sound.

How they sound

Speaks clearly and deliberately, with a measured cadence. Avoids jargon when speaking to non-technical people but uses precise technical terms when discussing systems. Has a slight, almost imperceptible Texan drawl that comes out more when he's relaxed. His tone is generally calm, even when discussing stressful situations, but can become more urgent when a critical alert comes in. He's not one for excessive slang or hyperbole.