Why this persona fits the audience
Helps run a 2-person New York startup with a live analytics API. The stack includes a paid auth service, Stripe subscriptions, organization-level access, and metered API limits; she keeps some account-state logic in Postgres and admin spreadsheets.
- Age: 38
- Location: New York, NY, US
- Occupation: Technical cofounder
- Income: $120k-$180k combined founder draw and consulting income
- Education: Master's in software engineering
- Company size: 2
- Years in role: 5
“The elegance of a well-designed system isn't just about how it looks on paper; it's about the quiet confidence it gives you when it handles complexity without breaking a sweat.”
Hazel Kertzmann, 38, is the technical cofounder of a nascent SaaS startup based in New York City, specializing in a live analytics API for indie developers and small teams. With a Master's in Software Engineering from Carnegie Mellon, she possesses a deep understanding of system architecture and robust coding practices. Her career path wasn't a straight line; she spent her early years in larger tech firms, contributing to backend systems and data pipelines, but felt stifled by the bureaucracy and slow pace. The allure of building something from the ground up, where her contributions directly shaped the product's success, led her to co-found her current venture five years ago. Her market fit is defined by her current role: managing the technical complexities of a two-person operation, which includes a paid authentication service, Stripe for subscriptions, and intricate organization-level access controls, all while maintaining a precarious balance between in-database account state logic and manual oversight via admin spreadsheets. This dual approach reflects her pragmatism and resourcefulness, leveraging powerful tools where necessary and manual processes when they offer a quicker, more manageable solution for their current scale. She views her income, a combined founder draw and consulting fees from early clients, as capital to be strategically deployed back into the business, prioritizing growth and stability over personal extravagance. She's acutely aware of the fragility of a startup and approaches decisions with a strong sense of responsibility, favoring measured growth and meticulous system design over reckless expansion. Her personal life is deliberately streamlined to maximize her focus on the company, finding solace and clarity in her early morning runs and the quiet satisfaction of solving intricate technical puzzles.
Background & daily life
A day in their life
Hazel's weekday typically begins around 6:00 AM with a 5-mile run through Central Park. By 8:00 AM, she's at her laptop, fueled by strong coffee, diving into urgent bug fixes or code reviews. The morning is dedicated to focused development, often tackling complex API logic or database optimizations. Lunch is a quick, often solo affair at her desk. Afternoons involve a mix of planning sessions with her cofounder, responding to critical support tickets, and refining the product roadmap. She tries to wrap up by 7:00 PM, though late-night coding sessions are not uncommon when a critical deadline looms or inspiration strikes.
Lifestyle
Hazel lives a focused and somewhat solitary life in her Manhattan apartment, which doubles as her primary workspace. Her income, while comfortable for a founder, is carefully managed, prioritizing reinvestment in the startup over lavish spending. Her routine is structured: early morning runs, followed by a long stretch of deep work, punctuated by quick, healthy meals. Social life is minimal, often revolving around occasional meetups with a few trusted tech-industry friends or a quiet evening with a book. She finds satisfaction in solving intricate problems and the steady progress of her venture.
Work life
As technical cofounder of a two-person startup, Hazel shoulders immense responsibility for the product's technical architecture and execution. Her days are a constant juggle between coding, system design, database management, and client communication, often requiring her to pivot rapidly based on user feedback or urgent issues. She relies heavily on her IDE, Git, a robust Postgres database, and surprisingly, a collection of meticulously maintained Google Sheets for managing customer accounts and administrative tasks. Her cofounder handles sales and business development, creating a symbiotic but demanding partnership.
Relationships
Hazel's primary relationship is with her cofounder, a dynamic and relationship-driven individual who complements her technical focus. They operate with a high degree of trust and open communication. Her family, though supportive, is largely disconnected from her current professional world. She maintains a small circle of close friends, mostly fellow engineers, with whom she can discuss technical challenges and share industry insights.
How they decide
Hazel's decision-making is highly analytical and research-driven. She prefers to thoroughly investigate options, weigh pros and cons based on technical feasibility and long-term impact, and often seeks out data or expert opinions before committing. She is not prone to impulsive choices, especially regarding core technology stacks or significant architectural changes. She values evidence and logic over hype.
How they sound
Her speech is precise and measured, with a tendency towards technical jargon when discussing her work. She avoids overly casual slang, preferring clear, direct language. When explaining complex topics, she’ll often pause to gather her thoughts, ensuring accuracy. Her tone is generally calm and rational, even when discussing stressful situations. She rarely engages in hyperbole and is direct about challenges.
Personality traits
- analytical
- methodical
- detail-oriented
- resourceful
- internally motivated
- pragmatic
- reserved
- deeply focused
- patient
Goals
- Achieve sustainable profitability for the startup within two years
- Refactor core API logic for enhanced scalability and maintainability
- Build a robust, self-service onboarding experience for new customers
- Develop a deeper understanding of distributed systems
- Maintain a consistent work-life balance that prevents burnout
Problems & frictions
- Struggles to allocate sufficient time for long-term technical debt reduction due to urgent feature requests
- The current mix of Postgres logic and spreadsheets for account management is becoming unwieldy and error-prone
- Balancing the need for rapid iteration with the imperative for robust, secure system design
- Finding moments for genuine relaxation amidst constant entrepreneurial pressure
- Occasional imposter syndrome when dealing with complex financial infrastructure components
Values
- precision
- system design
- responsibility
- measured growth
Interests
- data APIs
- payments infrastructure
- SaaS metrics
- running
- complex spreadsheets
Media habits
- Subscribes to Hacker News and Lobste.rs for industry news
- Listens to tech podcasts during runs (e.g., Software Engineering Daily, The Changelog)
- Reads technical blogs and documentation extensively
- Follows key figures in FinTech and developer tools on Twitter
- Occasional dips into The New Yorker for broader intellectual stimulation