Why this persona fits the audience
Leads infrastructure for an 8-person SaaS startup in Austin with two frontend apps, a Go API, and scheduled background jobs. He currently splits services between Render and GKE and is the person who keeps the deployment paths, secrets, and rollback steps documented for the rest of the team.
- Age: 35
- Location: Austin, TX, USA
- Occupation: Co-founder and CTO
- Income: $165,000/year
- Education: MS Computer Science
- Company size: 8
- Years in role: 4
“The goal isn't just to build it fast, it's to build it in a way that we can still understand and fix it next week, next month, next year.”
Johnnie Bradtke, 35, is a co-founder and CTO at an early-stage SaaS startup in Austin, Texas. Holding an MS in Computer Science from the University of Texas, he's spent the last four years building the technical foundation for his company, which now employs eight people. His professional journey has been marked by a deep dive into distributed systems and cloud infrastructure, driven by the need to create a scalable and reliable platform for their two frontend applications and a core Go API, complemented by scheduled background jobs. Johnnie's current technical landscape is a pragmatic mix of Render for simpler services and Google Kubernetes Engine (GKE) for more complex workloads, a decision born from balancing ease of use with granular control. He is the de facto keeper of the operational knowledge, meticulously documenting deployment paths, secret management strategies, and rollback procedures, understanding that this discipline is crucial for team autonomy and system resilience. His income of $165,000 reflects his critical role and the high demand for his expertise in the Austin tech scene. He lives alone, finding solace in the structured routine of his work and his passion for trail running, which serves as a mental reset from the constant pressures of startup life. Johnnie is driven by a desire for 'speed with discipline,' aiming to move quickly without sacrificing the long-term health and maintainability of the systems he builds. He values cost awareness, constantly seeking efficient ways to leverage cloud resources, and believes strongly in empowering his team with the autonomy to make technical decisions within well-defined boundaries. His approach to technology is grounded in pragmatism, favoring robust, well-understood solutions over fleeting trends, and he dedicates time to understanding the intricacies of observability and system design. He sees his role not just as building software, but as architecting a sustainable technical future for his company.
Background & daily life
A day in their life
Johnnie's typical weekday begins around 7:00 AM with a quick check of monitoring dashboards and urgent alerts, followed by a run or workout. After a strong coffee and a light breakfast, he's at his desk by 8:30 AM. The morning is usually dedicated to deep work: refining the Go API, optimizing background job performance, or architecting new infrastructure components. He attends a brief stand-up meeting with the team around 10:00 AM. The afternoon involves code reviews, responding to Slack messages, troubleshooting any emerging issues, and planning deployment strategies. He often has a virtual meeting with investors or partners late in the afternoon. He tries to wrap up by 6:30 PM, but late-night alerts or critical deployments can extend his day.
Lifestyle
Johnnie's life in Austin is structured around his demanding startup role. He lives a relatively minimalist lifestyle, prioritizing experiences and personal growth over material possessions. His mornings often start with a quick run on the Barton Creek Greenbelt or a strong pour-over coffee before diving into work. Weekends might involve longer trail runs, catching up on reading about distributed systems, or occasionally attending a local tech meetup, though he prefers smaller, focused gatherings. He's mindful of his finances, balancing a comfortable income with the inherent uncertainty of startup life, and enjoys cooking simple, healthy meals at home.
Work life
As CTO of an 8-person SaaS startup, Johnnie is the primary architect and guardian of the company's technical infrastructure. His days are a blend of hands-on coding, system design, and ensuring the operational health of their Go API and two frontend applications. He juggles managing deployments across Render and GKE, meticulously documenting every step, secret, and rollback procedure. The pressure is constant to deliver features rapidly while maintaining stability and controlling costs, often requiring him to wear multiple hats, from DevOps engineer to occasional backend developer.
Relationships
Johnnie maintains a close-knit circle of friends, many of whom are also in the tech industry, providing a sounding board for technical challenges and startup anxieties. He has a good working relationship with his co-founders and the small engineering team, valuing direct communication and mutual respect. His family lives out of state, and he connects with them via weekly video calls. He's currently dating someone he met through a mutual friend, enjoying the companionship without immediate pressure.
How they decide
Johnnie is a research-heavy, pragmatic decision-maker. He thoroughly investigates options, weighing technical merits against operational complexity and cost. He values input from his team but ultimately trusts his own judgment based on data and experience. He's not easily swayed by trends and prefers solutions that offer long-term stability and maintainability, often creating internal proofs-of-concept before committing to a new technology or service.
How they sound
Speaks with a measured, clear cadence. Avoids excessive jargon when speaking to non-technical people but uses precise technical terms with his team. His tone is generally calm and analytical, even when discussing stressful situations. He tends to use analogies related to systems or engineering. He avoids hyperbole and focuses on factual descriptions. Occasional dry wit surfaces, often related to the absurdities of startup life.
Personality traits
- Systematic problem-solver
- Proactive documentation
- Values clear ownership
- Slightly introverted but effective communicator
- Pragmatic about technology choices
- Detail-oriented
- Calm under pressure
- Focuses on long-term maintainability
- Skeptical of hype, prefers proven solutions
Goals
- Scale the company's infrastructure to support significant user growth.
- Build a robust, resilient, and cost-effective cloud platform.
- Foster a culture of technical excellence and autonomy within the engineering team.
- Achieve a sustainable work-life balance without sacrificing company progress.
- Contribute meaningfully to the open-source community in areas related to distributed systems.
Problems & frictions
- Balancing the need for rapid feature development with the imperative for stable infrastructure.
- Managing the complexity of a hybrid cloud environment (Render + GKE).
- Ensuring consistent deployment practices across a small, fast-moving team.
- The constant pressure to optimize cloud spend without compromising performance.
- Finding time for deep technical research amidst daily operational demands.
- Onboarding new engineers to a complex, evolving system.
Values
- speed with discipline
- team autonomy
- cost awareness
- system reliability
- pragmatism
Interests
- distributed systems
- trail running
- startup operations
- observability tools
- functional programming patterns
Media habits
- Hacker News
- Lobsters
- The Verge (for tech news)
- Specific tech podcasts (e.g., Software Engineering Daily)
- YouTube channels on systems design and DevOps