Why this persona fits the audience
Owns the analytics stack for a 28-person SaaS company: maintains BigQuery, dbt models, and Metabase dashboards, while also keeping event and CRM data in sync for founders and customer success. Works mostly solo, with one part-time analyst reviewing definitions.
- Age: 32
- Location: Austin, TX, US
- Occupation: Analytics Engineer
- Income: $130k-160k salary
- Education: BS Computer Science
- Company size: 28
- Years in role: 3
““If the data isn't reliable, it's not just wrong – it's actively misleading. My job is to make sure that doesn't happen.””
Frankie Douglas grew up in a quiet suburban town, the son of two dedicated teachers who instilled in him a strong work ethic and a value for intellectual pursuits. From an early age, he was drawn to understanding how things worked, disassembling old electronics and meticulously organizing his belongings. This inclination naturally led him to computer science during his undergraduate studies at a state university. He found particular satisfaction in the logic and structure of database systems and programming. After graduating, he worked for a couple of years at a larger, more established tech company in a junior data analyst role, where he felt like a small cog in a vast machine. He craved more ownership and direct impact. When the opportunity arose to join a seed-stage SaaS startup in Austin as their first dedicated analytics engineer, he jumped at it. This role, now three years in, has allowed him to build the entire analytics infrastructure from the ground up. He revels in the challenge of creating order from chaos, meticulously documenting every table, model, and dashboard. He views his current salary as a means to achieve stability and independence, allowing him to focus on building a solid foundation rather than chasing status symbols. Time is a valuable resource; he allocates it carefully between work, personal development, and maintaining his physical health through running. He’s pragmatic about money, preferring to invest in durable, high-quality tools that enhance his productivity and enjoyment, like his meticulously maintained home espresso setup. He recently decided against a more senior role at a mid-stage company, prioritizing the hands-on control and foundational impact he has at his current startup, despite the inherent risks. His approach to his work is deeply rooted in a belief that clear, reliable data is the bedrock of sound decision-making, and he sees himself as the guardian of that bedrock.
Background & daily life
A day in their life
Frankie's typical weekday begins around 6:30 AM with a single-origin pour-over coffee and a quick review of his personal dashboard monitoring the previous night's data loads. After a 45-minute run, he's showering and getting ready for work by 8:00 AM. His commute to the office (or starting his remote session) is filled with a tech podcast. The core of his workday (9 AM - 6 PM) involves digging into BigQuery logs to debug a sudden spike in null values, writing and testing new dbt models for upcoming feature tracking, refining a Metabase dashboard for the sales team based on founder feedback, and responding to Slack messages requesting urgent data pulls. He tries to block out an hour mid-afternoon for focused work on refactoring a legacy data ingestion script. He finishes his workday by checking system alerts and planning tomorrow's priorities.
Lifestyle
Frankie lives a structured life centered around his work and personal pursuits. His Austin condo is minimalist but functional, reflecting his preference for order. Mornings start with a precisely dialed-in espresso and a quick check of overnight data pipelines before a run along Lady Bird Lake. Evenings often involve tinkering with his home lab setup or reading up on the latest cloud infrastructure trends. He prioritizes his health, views his income as a tool for financial security rather than status, and is generally frugal, preferring to invest in quality tools (like his espresso machine) over fleeting experiences. Socially, he’s selective, preferring deep conversations with a few close friends over large gatherings.
Work life
As the sole analytics engineer at a fast-growing SaaS startup, Frankie is the lynchpin of their data operations. His days are a blend of reactive problem-solving and proactive system building. He spends significant time wrangling data from event tracking and the CRM into a usable state in BigQuery, meticulously crafting dbt models for consistency, and building out Metabase dashboards for the founders and customer success team. The pressure is constant but quiet; any data downtime or ambiguity directly impacts product decisions and customer outreach. He juggles urgent requests for new metrics with the ongoing need to refactor and optimize existing pipelines. His only direct collaborator is a part-time analyst, Sarah, who helps validate metric definitions but relies on Frankie for the technical implementation.
Relationships
Frankie maintains a small but strong circle of friends, mostly met through university or running groups. His parents, retired teachers, live back in his home state and he calls them weekly. He has a cordial relationship with his manager and the CEO, who rely heavily on his output but don't always grasp the technical intricacies. He trusts Sarah, the part-time analyst, implicitly on definitions, but their collaboration is limited by her availability.
How they decide
Frankie is a highly research-driven and cautious decision-maker, especially concerning technical tools and processes. He meticulously evaluates options, compares specifications, reads documentation thoroughly, and often builds small proof-of-concepts before committing. He values long-term reliability and maintainability over short-term gains or flashy features. Recommendations from trusted technical blogs or engineers he respects carry weight, but he ultimately relies on his own deep analysis and understanding of his specific environment.
How they sound
Speaks clearly and precisely, with a moderate pace. He avoids excessive jargon unless explaining a technical concept, preferring straightforward language. His tone is generally calm and measured, even when discussing frustrating issues. He doesn't use much slang, occasionally dropping a mild 'heck' or 'darn' when encountering a particularly stubborn bug. He's not one for hyperbole or overly enthusiastic pronouncements.
Personality traits
- methodical
- detail-oriented
- self-sufficient
- analytical
- proactive
- principled
- slightly reserved
- persistent
Goals
- Achieve a fully automated, self-healing data pipeline.
- Mentor a junior analyst to eventually share the workload.
- Build a robust data governance framework for the company.
- Save enough for a down payment on a small house with a dedicated home office.
- Become recognized internally as the definitive source for reliable data insights.
Problems & frictions
- Constantly fighting data quality issues stemming from upstream application changes.
- Limited bandwidth to explore new tooling or architectural improvements.
- Pressure to deliver ad-hoc reports and dashboards with minimal lead time.
- Ensuring data consistency across disparate event streams and the CRM.
- Lack of formal training or peer support for advanced data engineering challenges.
- Burnout risk due to solo ownership of critical infrastructure.
Values
- clarity
- reliability
- documentation
- efficiency
- measurable progress
Interests
- SQL
- cloud tooling
- home espresso
- running
- data modeling
- backend architecture
Media habits
- Follows data engineering blogs and newsletters
- Listens to tech podcasts during commutes/runs
- Reads Hacker News and Reddit's r/dataengineering
- Watches YouTube tutorials on new cloud services
- Occasionally checks industry analyst reports