Why this persona fits the audience
He is a backend engineer in Seattle and spends evenings on a two-person side project where the UI is in React Native and the AI features are assembled from public docs, snippets, and a shared spreadsheet. For the project he uses a competitor boilerplate on the paid side and keeps the rest of the setup in Notion and GitHub issues.
- Age: 30
- Location: Seattle, USA
- Occupation: Backend engineer
- Income: $128k
- Education: Bachelor's in Computer Science
- Company size: Mid-sized tech firm (500-1000 employees)
- Years in role: 6
“I don't need another tool to tell me what I can build; I need a foundation that gets out of my way so I can actually ship something that matters.”
Leonard Schaefer, 30, is a backend engineer residing in Seattle, Washington, earning an annual salary of $128,000. Holding a Bachelor's degree in Computer Science, he has spent the last six years navigating the complexities of enterprise software development. Currently employed at a mid-sized tech firm, Leonard specializes in API design and system scalability, though he finds himself increasingly drawn to the chaotic, fast-moving world of AI application development. Outside of his day job, Leonard dedicates his evenings to a two-person side project, a mobile application built with React Native that leverages various AI features. This project is a testament to his pragmatic approach to development: he utilizes a paid competitor boilerplate for the foundational UI to save time, while assembling the AI logic from a patchwork of public documentation, code snippets, and a meticulously maintained shared spreadsheet. His workflow is a hybrid of organization and improvisation, relying heavily on Notion for project management and GitHub issues for bug tracking. Leonard is driven by a desire for technical depth and self-direction, often feeling constrained by the rigid structures of corporate environments. He values momentum above all else, constantly seeking ways to streamline his development process without sacrificing quality. Despite the demands of his full-time role, Leonard remains committed to his side project, viewing it as both a creative outlet and a potential pathway to future independence. His life is a careful balance of professional responsibility and personal ambition, marked by a relentless pursuit of efficiency and a deep curiosity for the evolving landscape of artificial intelligence.
Background & daily life
A day in their life
Leonard wakes up at 5:30 AM for a quiet hour of reading and planning before his wife leaves for her shift. By 7:30 AM, he's commuting via light rail, listening to technical podcasts or reviewing GitHub issues. His workday starts at 9:00 AM with a quick sync, followed by three hours of uninterrupted coding on backend services. Lunch is a brisk affair, often eaten at his desk while watching a tutorial on vector databases. Afternoons are filled with meetings and code reviews, breaking his flow but necessary for team alignment. He leaves the office by 5:30 PM to grab groceries and exercise. Evenings are sacred: from 7:00 PM to 10:00 PM, he codes on his side project, wrestling with React Native navigation and integrating AI APIs. He winds down with a book and sleep by 11:00 PM, ready to repeat the cycle.
Lifestyle
Leonard lives in a modern, minimalist apartment in Ballard, sharing rent with a graphic designer. His life is structured around high-intensity work blocks; mornings are for family and coffee, while evenings are fiercely guarded for his side hustle. He maintains a strict health routine, running three times a week to clear his head after long coding sessions. Financially, he is comfortable but deliberate, prioritizing savings over luxury experiences. Socially, he prefers one-on-one dinners or small gatherings with other engineers rather than large parties. He avoids unnecessary consumption, viewing time as his most scarce resource, often spending weekends optimizing his home automation or debugging legacy code at a local coffee shop.
Work life
At his day job, Leonard is the go-to person for API reliability and database scaling. His days are a mix of stand-ups, code reviews, and deep-dive architecture meetings. He uses Jira for task management, Confluence for documentation, and VS Code with a heavily customized Rust/Go environment. The pressure comes from maintaining uptime for critical internal services and mentoring junior developers who often struggle with the company's complex legacy systems. He finds the corporate bureaucracy stifling, particularly the endless meetings that interrupt his flow state. However, he appreciates the stability and the access to enterprise-grade tools, even if they feel heavy-handed compared to the agility he craves in his personal projects.
Relationships
Leonard is married to Sarah, a pediatric nurse who works rotating shifts, making their schedule a delicate dance of coordination. They have a golden retriever named 'Byte' who anchors their evening routines. His closest friends are a trio of fellow developers from college, with whom he discusses everything from startup ideas to the best local breweries. He is part of a small, private Slack community of indie hackers, which serves as his primary peer group for technical validation and emotional support regarding his side project.
How they decide
Leonard is a research-heavy, data-driven decision-maker who relies on empirical evidence before committing to new tools. He prefers to test concepts in isolation using free tiers or open-source alternatives before considering paid solutions. He values transparency in pricing and functionality, often dissecting feature sets against his specific workflow needs. While he is open to innovation, he is naturally cautious about vendor lock-in and tends to favor modular, composable solutions over monolithic platforms unless the value proposition is undeniable.
How they sound
Leonard speaks in a measured, precise cadence, favoring technical terminology when discussing his work but simplifying his language when explaining concepts to non-technical partners. He rarely uses slang, preferring clarity over humor in professional settings. He tends to pause frequently to structure his thoughts, often saying things like, 'Let me rephrase that,' or 'Technically speaking...' He avoids hyperbole and emotional exaggeration, sticking to facts and logical deductions. In casual conversation, he is warm but brief, often steering topics back to systems, processes, or interesting technological developments.
Personality traits
- methodical
- curiously skeptical
- time-poor but energy-rich
- systems-oriented
- quietly competitive
- pragmatic idealist
- detail-obsessed
- socially reserved
- adaptable to chaos
- deep-work focused
Goals
- Launch a profitable SaaS product within the next 18 months
- Master the latest LLM inference optimization techniques
- Build a sustainable work-life balance that allows for consistent side-project progress
- Contribute meaningfully to an open-source AI framework
- Achieve financial independence through passive income streams
- Mentor a junior developer into a senior role
Problems & frictions
- Fragmented information sources make it hard to keep up with rapid AI changes
- Spending too much time configuring basic app scaffolding instead of building features
- Difficulty coordinating with his partner due to conflicting schedules and communication gaps
- The lack of a unified system for tracking AI prompt engineering iterations
- Feeling overwhelmed by the sheer volume of new libraries and tools available weekly
- Struggling to find time for deep learning amidst constant context switching
Values
- technical depth
- momentum
- self-direction
- pragmatic efficiency
- intellectual autonomy
Interests
- side projects
- API design
- AI apps
- system architecture
- open source contributions
Media habits
- Loom for async updates
- Hacker News daily digest
- GitHub trending repositories
- Niche Substack newsletters on AI infrastructure
- YouTube deep dives into compiler theory