Jason Kuhic

Why this persona fits the audience

He works full-time as a backend engineer and maintains a small paid API tool on evenings and weekends. His Chrome sessions often include GitHub, Stripe, Linear, docs, and support inboxes, and he is comfortable testing browser tooling alongside scripts, shortcuts, and terminal workflows.

• Age: 24
• Location: San Francisco, CA, USA
• Occupation: Backend engineer and indie SaaS operator
• Income: $155k salary plus side-project revenue
• Education: Bachelor's degree in computer science
• Company size: 250-500 employees (full-time job)
• Years in role: 2 years as backend engineer, 1 year as SaaS operator

““The real magic happens when you can automate the tedious parts and just focus on building cool stuff.””

Jason Kuhic, 24, is a driven backend engineer based in San Francisco, who exemplifies the modern indie developer archetype. Holding a Bachelor's degree in Computer Science, he landed a competitive role at a mid-sized tech company, earning a solid $155k annual salary. This stability, however, fuels his ambition to carve out his own niche. Evenings and weekends are dedicated to his passion project: a niche paid API tool he built and maintains entirely on his own. His browser is a testament to his workflow: a constant stream of GitHub tabs for code, Stripe for payments, Linear for project management, and various documentation sites. He’s comfortable integrating new browser tooling, scripting tasks, and even venturing into terminal workflows to optimize his development and operational processes. Recently, Jason has been grappling with the scalability of his API's current architecture, considering whether to refactor a core component or invest in managed services to handle increased traffic without sacrificing performance. He’s also actively exploring the integration of small, specialized language models to automate certain support queries, a move driven by both efficiency and a keen interest in AI advancements. His financial strategy is conservative; the majority of his salary is saved, with a portion allocated to reinvesting in his side project’s infrastructure and a small buffer for unexpected expenses. He lives in a shared apartment, a pragmatic choice that allows him to maximize his savings rate. Jason’s relationship with time is one of constant optimization, always seeking ways to gain more productive hours, and his view on status is rooted in technical achievement and the ability to ship functional, valuable software rather than corporate titles or material possessions. He recently decided to fully document one of the more complex internal APIs he built for his SaaS tool, a task he’d been putting off, recognizing its importance for future maintainability and potential collaboration.

Background & daily life

A day in their life

Jason's typical weekday starts around 7:00 AM with a quick scan of Hacker News and his personal project's Slack channel before a brisk walk or a short workout. He then bikes to his office, arriving by 9:00 AM. His workday involves a mix of coding, stand-ups, and code reviews, often punctuated by debugging urgent issues. Lunch is usually a quick meal at his desk while catching up on industry news. After work, around 6:00 PM, he heads home, cooks a simple dinner, and then dedicates 2-3 hours to his API tool – responding to support emails, refining documentation, or writing new features. He tries to wind down by 11:00 PM with some light reading or a quick gaming session.

Lifestyle

Jason's life is a carefully balanced act between his demanding full-time job and his passion project. He lives frugally in a shared apartment in the Outer Sunset, prioritizing saving for future investments and the potential to go full-time on his own projects. His evenings and weekends are often consumed by coding, but he tries to carve out time for quick workouts at the local park and occasional board game nights with a small circle of friends. He enjoys optimizing his personal workflows, from automating chores with his home lab setup to meticulously planning his meals for the week.

Work life

At his full-time role, Jason is a backend engineer focused on building scalable microservices. His days are filled with code reviews, debugging production issues, and collaborating with product managers via Linear. He values the stability and the team's collective knowledge but sometimes feels the pace is slower than he'd like. He primarily uses Python and Go, relying heavily on internal documentation and Stack Overflow. The pressure to maintain high uptime and deliver features on schedule is constant, but he thrives on the challenge of solving complex technical problems and contributing to a well-architected system.

Relationships

Jason maintains a close but not overly dependent relationship with his parents, who live back in the Midwest and are supportive but don't fully grasp the intricacies of his work. His core social circle consists of a few college friends, mostly developers themselves, with whom he exchanges technical insights and occasional life advice. He's not actively dating but is open to meeting someone with shared intellectual curiosity.

How they decide

Jason is a highly analytical and research-driven decision-maker, particularly for anything related to technology or finance. He meticulously compares options, reads reviews, and often experiments with free tiers or trials before committing. For personal matters, he leans towards pragmatism and efficiency, often optimizing for long-term benefit over immediate gratification.

How they sound

Speaks with clear, precise articulation, often using technical jargon naturally. His cadence is steady, thoughtful, and avoids unnecessary filler words. He rarely uses overt slang, preferring more formal or neutral language, but can adopt a slightly more casual tone when discussing personal projects with peers. He tends to be direct but polite.