Why this persona fits the audience
Uses Cursor's agent mode for feature branches and bug fixes on a MacBook Air, often leaving longer runs active while he grabs lunch or heads to the gym. He is already paying for another AI coding workflow and checks edit approvals from his phone when he is away from the desk.
- Age: 28
- Location: Seattle, WA, US
- Occupation: Product engineer
- Income: $150k-$190k
- Education: BS Software Engineering
- Company size: Series B startup (45-60 employees)
- Years in role: 3 years as Senior Engineer
“I don't just want the code to work; I want the process of writing it to disappear so I can focus on solving the actual problem.”
Leo Kirlin, 28, is a Senior Product Engineer living in Seattle, where the constant rain mirrors the steady hum of his keyboard. Born and raised in the Pacific Northwest, he earned his BS in Software Engineering from the University of Washington before diving into the startup ecosystem. Today, he navigates the high-stakes environment of a Series B company, balancing the demands of legacy maintenance with the pressure to innovate. His professional identity is deeply intertwined with his toolset; he is a devotee of Cursor, leveraging its agent mode to push boundaries that traditional editing cannot reach. He has developed a unique workflow where he initiates autonomous coding sessions on his MacBook Air, effectively decoupling his physical presence from the execution of complex tasks. This allows him to seamlessly transition between coding sprints and his rigorous fitness routine, treating both with equal discipline. Financially, Leo sits comfortably in the upper-middle class bracket, earning $150k-$190k annually. He views money not as a status symbol but as a resource to buy back time. Consequently, he invests heavily in premium software subscriptions and high-end hardware, viewing these expenses as essential infrastructure for his productivity. He is currently managing a portfolio of paid AI coding tools, constantly evaluating their ROI against his output. Recently, he made the strategic decision to migrate a critical microservice to a new architecture, a move that required him to trust AI agents to handle significant portions of the boilerplate while he focused on architectural integrity. His personal life is a study in optimization. He dedicates three mornings a week to the gym, tracking his lifts with the same precision he applies to code metrics. His social circle is small but potent, consisting of peers who challenge his thinking and share his passion for technology. Leo is a skeptic by nature, always looking for the edge case in any new tool or trend. He doesn't blindly follow hype cycles; instead, he experiments, fails, and iterates. Whether he is debugging a race condition or planning his next marathon, his approach remains consistent: identify the bottleneck, apply a targeted solution, and measure the result. For Leo, the ultimate goal isn't just to build software, but to build a life where technology serves his ambitions rather than dictating them.
Background & daily life
A day in their life
Leo wakes up at 6:00 AM, immediately heading out for a 45-minute run before his morning coffee ritual. By 8:30 AM, he's logged into his MacBook Air, reviewing GitHub notifications and starting his day with a deep-dive coding session. Around 10:00 AM, he initiates a complex refactoring task in Cursor, setting it to run autonomously while he steps out for a protein-packed breakfast. During this window, he might check his phone to approve a minor edit or let the agent continue its work. At noon, he hits the gym for an hour of weightlifting, mentally decompressing from the code. Back at the desk by 1:30 PM, he tackles meetings and pair programming. The afternoon is reserved for PR reviews and pushing code to production. He leaves the office around 5:30 PM, often taking a bike ride home to clear his head, ending the day with a few hours of reading about emerging AI models before bed.
Lifestyle
Leo lives in a modern, minimalist apartment in Seattle's Capitol Hill, filled with mechanical keyboards and ergonomic gear. His routine is strictly bifurcated: intense deep work blocks followed by vigorous physical training at a local CrossFit box or a long run along Lake Washington. He treats fitness like code—optimizing reps and macros. Financially, he is comfortable but not extravagant; he prioritizes spending on high-quality hardware and software subscriptions that directly impact his productivity. Socially, he prefers one-on-one coffee chats over large parties, often discussing side projects or the latest LLM breakthroughs rather than weekend gossip. He maintains a tight circle of three close friends from college who share his tech interests.
Work life
As a senior product engineer at a fast-paced Series B startup, Leo spends his days navigating a complex legacy codebase while trying to ship new features rapidly. His primary weapon is Cursor, which he uses heavily for refactoring and debugging. He frequently initiates long-running agent sessions on his MacBook Air, stepping away to eat lunch or hit the gym without pausing the workflow, trusting the agent to wait or self-correct. He manages multiple open contexts simultaneously, switching between browser-based reviews and terminal outputs. The pressure comes from the need to maintain high velocity without introducing technical debt, often requiring him to make quick architectural decisions under tight deadlines. Coworkers view him as the go-to person for untangling difficult logic puzzles.
Relationships
Leo is supported by a stable network of three college friends who remain in the Seattle area, providing a sounding board for career moves and technical debates. He has a distant but supportive relationship with his parents in Oregon, who are proud of his success but don't fully grasp the nuances of his daily work. At work, he mentors two junior engineers, fostering a collaborative environment where he encourages experimentation. His romantic life is casual; he dates occasionally but keeps relationships secondary to his career trajectory and fitness regimen. He values authenticity in connections, preferring deep conversations over superficial networking.
How they decide
Leo operates on a 'test-drive' philosophy. He rarely commits to a major tool change without first running a controlled experiment on a non-critical branch or a side project. He relies heavily on community sentiment and peer recommendations, particularly from trusted sources on Twitter or niche developer forums. Once he identifies a friction point in his current workflow, he researches alternatives aggressively, comparing feature sets and pricing models. However, he is wary of bloating his stack with redundant tools, preferring solutions that integrate seamlessly into his existing ecosystem. He makes decisions based on tangible efficiency gains rather than marketing hype.
How they sound
Leo speaks in a direct, efficient cadence, often using developer shorthand like 'refactor,' 'deploy,' and 'merge conflict.' He avoids corporate jargon, preferring plain English mixed with technical terms. When explaining concepts, he uses analogies related to sports or mechanics. He tends to be concise, cutting straight to the point without unnecessary pleasantries. In text messages, he uses emojis sparingly, mostly for emphasis on tone. He rarely complains openly about problems; instead, he frames challenges as opportunities for optimization. His slang includes terms like 'dogfooding,' 'tech debt,' and 'shipping,' reflecting his immersion in the engineering culture.
Personality traits
- Hyper-focused
- Tool-obsessed
- Time-poor
- Technically pragmatic
- Fitness-disciplined
- Iterative thinker
- Mobile-first
- Quietly competitive
- Solution-oriented
- Adaptable
Goals
- Architect a scalable microservice migration within the next fiscal year
- Launch a personal SaaS tool that generates passive income
- Achieve a sub-18-minute mile time in running
- Master Rust for systems-level development
- Reduce context-switching overhead during peak sprint weeks
- Build a robust, automated testing suite for legacy modules
Problems & frictions
- Fragmented attention when stepping away from the IDE during long agent runs
- Difficulty reviewing complex AI-generated diffs while commuting or at the gym
- Managing multiple subscription costs for overlapping AI tools
- Balancing deep focus time with urgent Slack pings and stand-ups
- Legacy codebases that resist automated refactoring attempts
- Keeping up with the rapid pace of new AI agent capabilities
Values
- speed
- experimentation
- mobile convenience
- autonomy
- continuous learning
- efficiency
Interests
- Cursor workflows
- fitness
- side apps
- GitHub
- LLM architecture
- urban cycling
Media habits
- Indie Hackers newsletter
- The Changelog podcast
- Twitter/X for dev tools news
- Reddit r/programming
- Local tech meetups
- GitHub trending repositories