Garrett Feil

Why this persona fits the audience

Manages a Chicago startup's customer-facing dashboard for a 2-person product team. The app already has login, teams, roles, subscription plans, and API metering implemented with Auth0, Stripe, and custom server logic.

• Age: 40
• Location: Chicago, IL, US
• Occupation: Technical founder
• Income: $145,000
• Education: Bachelor of Science in Computer Engineering, University of Illinois at Urbana-Champaign
• Company size: 5 employees (including himself)
• Years in role: 3 years

“The elegance of a system isn't in its complexity, but in its predictable, resilient behavior under load.”

Garrett Feil, 40, is the technical founder and CTO of a nascent Chicago-based startup focused on providing a customer-facing dashboard for businesses. Holding a Bachelor's in Computer Engineering from the University of Illinois, his career has been a steady progression through increasingly complex technical roles, culminating in the founding of his own company three years ago. He lives in a renovated bungalow in Lincoln Park with his wife, Sarah, and their six-year-old daughter. Garrett's professional life is deeply intertwined with the company's in-house stack, which he meticulously manages. The core of his current work involves refining the platform's authentication, team management, role-based access, subscription plans, and API metering, all built upon Auth0, Stripe, and significant custom server logic. This hands-on approach stems from his core value of control and a deep-seated belief in engineering discipline; he wants to understand every layer of the system he's responsible for. His income, around $145,000 annually, reflects his expertise and the demands of his role, though he prioritizes reinvesting in the company over personal extravagance. Garrett's decision-making is heavily influenced by his desire for predictability and accountability, meaning he meticulously plans and tests before implementing changes, especially concerning critical user-facing features like subscriptions and API usage tracking. He views his technical oversight as paramount to the company's long-term success and stability. His recent focus has been on hardening the subscription logic and ensuring the API metering is both accurate and scalable, a direct response to early customer feedback and the need to establish a reliable revenue stream. He recently decided against a third-party solution for subscription management, opting instead to enhance their existing custom implementation, a choice driven by his preference for maintaining full control over the codebase and data. This decision, while increasing his immediate workload, aligns with his long-term vision of an internally managed, highly optimized platform. He sees time as a critical resource, meticulously allocating it between product development, infrastructure maintenance, and the occasional, but highly valued, family outing. His relationship with money is pragmatic; he invests in tools and infrastructure that offer long-term value and reliability, rather than chasing the cheapest option. Status, for Garrett, is derived from building robust, well-engineered systems that perform reliably, not from external accolades or market hype.

Background & daily life

A day in their life

Garrett's day begins before dawn with a rigorous cycling session. After a quick breakfast and seeing his daughter off to school, he dives into work. Mornings are typically spent in deep technical work: architecting a new feature for the customer dashboard, optimizing database performance, or debugging a tricky integration issue between Auth0 and their custom subscription logic. He has a brief sync with his product manager to clarify requirements. Lunch is usually a pre-packed meal at his desk while reviewing code or scanning industry news. Afternoons involve team stand-ups, code reviews, and planning infrastructure upgrades. He often works late, especially when a critical bug arises or a new deployment is scheduled, ensuring everything is stable before he finally heads home.

Lifestyle

Garrett lives a structured life anchored by his morning routine: 5:30 AM wake-up, followed by a 20-mile bike ride through Lincoln Park, regardless of the weather. He prioritizes efficiency, packing his lunch and prepping his work clothes the night before. Weekends are a mix of family time, often involving park visits or building elaborate LEGO sets with his daughter, and dedicated 'tinker time' in his garage, where he's currently automating his home's irrigation system. He's financially prudent, preferring to invest in durable goods and experiences over fleeting trends, and rarely eats out during the week, viewing it as an unnecessary expense and time sink.

Work life

As CTO and lead engineer for his 5-person startup, Garrett lives and breathes the company's in-house stack. His days are consumed by architecting new features for their customer-facing dashboard, optimizing database queries, and ensuring the stability of their Auth0 and Stripe integrations. He works closely with the two-person product team, translating their user stories into actionable technical tasks. The pressure is constant to deliver robust functionality while maintaining high uptime and security, especially with their current focus on refining API metering and subscription tier logic. He spends a significant portion of his time debugging, reviewing code, and planning infrastructure upgrades, often feeling like he's juggling multiple critical systems simultaneously.

Relationships

Garrett is married to Sarah, a graphic designer, with whom he shares a pragmatic partnership. They discuss finances openly, and she understands his demanding work schedule, though she occasionally expresses concern about his long hours. His closest friends are a small group from his university engineering days, with whom he still exchanges technical articles and occasional weekend meetups. He has a cordial but distant relationship with his parents, who don't fully grasp the intricacies of his startup.

How they decide

Garrett is a highly analytical and research-driven decision-maker. He meticulously evaluates options, weighing technical feasibility, long-term maintainability, and potential risks. He prefers to gather data, consult documentation, and sometimes prototype solutions before committing. He trusts his own engineering judgment above all else but will solicit input from his small team on user-facing aspects. He is not easily swayed by hype or trends, focusing instead on proven methodologies and robust solutions.

How they sound

Speaks with a measured, precise cadence. Avoids jargon when speaking to non-technical people but uses precise technical terms with his team. His tone is generally calm and analytical, but can become more intense when discussing system failures or security vulnerabilities. He tends to be direct and to the point, rarely engaging in small talk unless it's about engineering challenges or cycling. He dislikes hyperbole and prefers factual statements.