Why this persona fits the audience
Works in a 12-person SaaS startup's ops stack, logging into Linux staging and production jump hosts from a Windows laptop, editing config files over SSH/SFTP several times a week, and keeping hostnames and ports in a shared spreadsheet for the team.
- Age: 32
- Location: Austin, TX, USA
- Occupation: DevOps engineer
- Income: USD 145,000 base + bonus
- Education: B.S. Computer Science
- Company size: 12
- Years in role: 4
“The system is only as strong as its weakest link, and usually, that weak link is a manual process or a forgotten config file.”
Dewey Stokes grew up in a quiet suburban town in Michigan, developing an early fascination with how things worked, often taking apart old electronics. His parents, a teacher and an accountant, encouraged his logical thinking. He pursued a B.S. in Computer Science at a state university, where he honed his programming skills but found himself more drawn to the operational side of systems – making them run reliably and efficiently. After graduating, he spent three years at a larger tech company in a junior sysadmin role, learning the ropes of enterprise infrastructure. Seeking more autonomy and a faster-paced environment, he joined his current 12-person SaaS startup in Austin about four years ago as their first dedicated DevOps engineer. He operates with a high degree of conscientiousness, driven by a deep-seated need for reliability in the systems he manages. The startup's lean budget means he's constantly innovating with open-source tools and clever configurations, stretching resources as far as possible. He views his work not just as a job, but as a continuous process of building and fortifying, treating every piece of infrastructure with meticulous care. Recent decisions include migrating their CI/CD pipeline to GitLab CI and implementing HashiCorp Vault for secrets management, though he still relies on a shared spreadsheet for basic host inventory – a point of personal friction he's looking to resolve. Time is a valuable commodity, and he meticulously plans his workdays, though unexpected production issues can easily derail even the best-laid plans.
Background & daily life
A day in their life
Dewey's weekday starts around 6:30 AM with a run or walk with Kernel. After a quick breakfast and coffee, he's at his desk by 8:00 AM, checking monitoring dashboards and overnight logs. The morning often involves addressing any emergent issues or deploying planned updates. He’ll spend a couple of hours scripting or refining Terraform/Ansible code. Lunch is usually a quick affair at his desk while catching up on tech news. Afternoons are for team syncs, code reviews, documenting changes, and planning the next sprint's infrastructure tasks. He logs off around 5:30 PM, but often checks alerts one last time before bed around 10:00 PM.
Lifestyle
Dewey lives in a modest two-bedroom apartment in South Austin, sharing it with a Golden Retriever named 'Kernel'. His evenings and weekends often involve tinkering with his home lab setup – a collection of Raspberry Pis and old servers running various monitoring and automation experiments. He prioritizes his health, hitting local trails for trail runs several times a week, especially during the cooler mornings. Financially, he's practical, saving a good portion of his income but not averse to investing in quality gear for his hobbies. Socially, he prefers smaller, intimate gatherings with close friends over large parties, enjoying board game nights or grabbing local craft beers.
Work life
As the sole DevOps engineer at his startup, Dewey juggles a wide array of responsibilities. His days are a mix of proactive system maintenance, responding to urgent alerts, and implementing automation scripts. He's the gatekeeper for staging and production environments, which means frequent logins to Linux jump hosts from his Windows laptop, often via SSH/SFTP to tweak configuration files. His primary toolset includes Terraform for infrastructure as code, Ansible for configuration management, Docker for containerization, and a shared Google Sheet to track critical hostnames, ports, and IP addresses – a system he knows is fragile but functional. Coworkers rely on him for smooth deployments and stable uptime, creating constant, low-grade pressure to prevent any outages.
Relationships
Dewey maintains a strong, supportive relationship with his parents back in Michigan, calling them weekly. His close circle includes a few friends from college who also work in tech, often discussing work challenges and new technologies. He’s influenced by respected figures in the DevOps community he follows online, valuing their insights on best practices and emerging trends.
How they decide
Dewey is generally cautious and research-driven when making technical decisions. He prioritizes solutions that are stable, well-documented, and have a proven track record or strong community support. He'll often spend time evaluating alternatives, reading reviews, and testing options in his home lab before committing to a change in the production environment. Peer recommendations and evidence of long-term reliability are key factors.
How they sound
Speaks clearly and deliberately, often pausing to find the precise technical term. Avoids excessive jargon with non-technical people but uses standard DevOps acronyms freely with peers. His tone is generally calm and factual, even when discussing stressful situations. He's not prone to hyperbole or overly casual slang.
Personality traits
- meticulous
- proactive
- detail-oriented
- problem-solver
- methodical
- resourceful
- calm under pressure
- self-reliant
Goals
- Achieve full CI/CD automation for all company services
- Build a robust, scalable cloud infrastructure from the ground up
- Contribute meaningfully to open-source projects related to observability
- Complete a half-marathon next year
- Purchase a small house with a dedicated server room
Problems & frictions
- Limited budget for enterprise-grade tooling
- Maintaining complex systems with minimal documentation from previous phases
- Balancing urgent production issues with long-term strategic projects
- Lack of dedicated QA/testing environments leading to last-minute bug discoveries
- Onboarding new developers with the current complex, manual deployment process
- The shared spreadsheet for hostnames and ports is becoming unmanageable
Values
- reliability
- clear documentation
- team handoff
- efficiency
- stability
Interests
- cloud infrastructure
- home lab
- trail running
- automation
- system observability
Media habits
- Reads Hacker News and Reddit (r/devops, r/sysadmin)
- Listens to tech podcasts during commutes/runs
- Follows key figures on Twitter for industry news
- Watches YouTube tutorials for new tools/techniques
- Occasional Stack Overflow browsing