Jon Koelpin

Why this persona fits the audience

Leads a 12-person startup in Austin shipping a customer-facing app with an LLM assistant, API services, and Dockerized workers. He reviews code written by 5 engineers, keeps dependency alerts in GitHub Dependabot, and uses a spreadsheet to track a few container and library findings across releases.

• Age: 36
• Location: Austin, Texas, US
• Occupation: CTO
• Income: $210,000/year
• Education: B.S. in Computer Science
• Company size: 12
• Years in role: 3

“We're building something complex, and the goal is to make it feel simple and reliable for our users, which means we need to be obsessively rigorous about the foundations we lay.”

Jon Koelpin, 36, is the CTO of a burgeoning AI SaaS startup nestled in the vibrant tech scene of Austin, Texas. His journey into technology began not with a childhood fascination for robots, but a deep-seated curiosity about how complex systems could be built and understood, leading him to pursue a B.S. in Computer Science. He cut his teeth at larger tech firms, gaining valuable experience in scalable architectures and team dynamics, but the allure of building something from the ground up eventually led him to the startup world. For the past three years, he's been instrumental in shaping the technical direction of his current company, steering a team of five engineers in the development of a customer-facing application leveraging LLMs, robust API services, and containerized workers. His leadership style is defined by a commitment to pragmatic engineering and team autonomy, believing that well-defined responsibilities foster innovation and ownership. He's meticulous, ensuring code quality through thorough reviews and maintaining a keen eye on system health by tracking dependencies and container configurations, albeit currently through a somewhat manual spreadsheet process. Financially, Jon is in a strong position with an annual income of $210,000, which allows him to save aggressively for future financial security and reinvest in his professional development, often through courses or attending industry conferences. He views time as his most precious commodity, a constant balancing act between the urgent demands of a startup and the strategic investments needed for long-term success. His decisions are heavily influenced by a desire to ship reliable software, prioritizing solutions that offer clarity and minimize unforeseen risks.

Background & daily life

A day in their life

Jon's typical weekday starts around 7:30 AM with a quick scan of overnight alerts and his personal inbox while he makes coffee. By 8:30 AM, he's diving into Slack and Jira, triaging issues and planning the day's priorities. The morning is often packed with code reviews for the 5 engineers on his team, interspersed with quick syncs on ongoing features. Lunch is usually a hurried affair, eaten at his desk while catching up on industry news via Hacker News. Afternoons might involve architecting a new service, debugging a tricky production issue, or a planning meeting with the CEO. He usually wraps up formal work around 6:30 PM, but often logs back in for an hour or two later in the evening to catch up or work on a specific problem.

Lifestyle

Jon lives in a moderately sized rental house in South Austin with his partner, a graphic designer, and their rescue dog. His weekdays are intensely focused on work, often blurring the lines between work and personal time due to the startup grind. Evenings usually involve a quick home-cooked meal or grabbing takeout. He prioritizes staying physically active, hitting the gym or going for a run a few times a week to de-stress. Weekends are for catching up on personal projects, exploring Austin's food scene, or occasionally road-tripping to nearby state parks. Financially, he's disciplined, aggressively saving for future equity and managing his income to balance current needs with long-term goals.

Work life

As CTO of a lean AI SaaS startup, Jon is deeply hands-on. His team of five engineers relies on him for technical direction and code reviews, while he also manages the deployment pipeline for their customer-facing LLM application. He's constantly balancing feature velocity with the need for robust, secure infrastructure, juggling Docker configurations, API integrations, and dependency management. The pressure to ship reliable updates while keeping technical debt manageable is a daily reality. He relies heavily on tools like GitHub, Jira, and a carefully maintained internal Confluence space for documentation.

Relationships

Jon's closest professional relationships are with his engineering team, whom he trusts implicitly to execute. He maintains a strong working relationship with the CEO, providing technical feasibility assessments for business strategy. Outside of work, his partner is his primary confidante and sounding board. He stays in touch with a few college friends who are also in tech, sharing war stories and insights.

How they decide

Jon tends to be methodical and research-driven when making significant technical decisions. He'll weigh the pros and cons, consult with his senior engineers, and often prototype potential solutions. For operational tools, he prioritizes proven reliability and integration ease. He's not impulsive but will act decisively once he's confident in the path forward, often influenced by data and past experiences rather than pure hype.

How they sound

Speaks with a clear, measured cadence. Tends to use precise technical language but can explain complex concepts in simpler terms when needed. Avoids excessive jargon or buzzwords unless discussing specific technologies. His tone is generally calm and confident, even when discussing challenging issues. Uses phrases like 'the crux of it,' 'essentially,' and 'from a pragmatic standpoint.'