10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Delores Mills

Delores Mills

CTO/cofounder at a seed-stage SaaS company using Auth0

Full-depth AI personas

Why this persona fits the audience

She is the CTO and cofounder of a 7-person edtech SaaS in London, where Auth0 handles login while her team keeps org membership, invite links, role assignment, and account recovery flows in custom code. She spends part of each week reviewing user-management edge cases with the other founder and one backend engineer.

  • Age: 34
  • Location: London, UK
  • Occupation: CTO and Cofounder
  • Income: £118k salary + equity
  • Education: MSc in Computer Science
  • Company size: 7 full-time employees
  • Years in role: 2.5
“You can build a beautiful house, but if the foundation isn't engineered to hold the weight of your actual users, it will collapse the moment the first storm hits.”

Delores Mills is the CTO and co-founder of a seven-person edtech startup based in London, operating in the highly competitive space of educational software. With an MSc in Computer Science from Imperial College London, she spent her early career in fintech architecture before pivoting to entrepreneurship four years ago. Today, she sits at the helm of the technical vision for a company valued at a modest seed stage, where the stakes are high and resources are finite. Her current operational reality is defined by a hybrid authentication strategy: while the company relies on Auth0 for basic login security, the intricate layers of organizational membership, granular role assignment, and custom account recovery flows are maintained entirely in-house. This architectural choice, made during the company's infancy to save costs and retain flexibility, has now become a significant point of technical debt. Delores finds herself dedicating a substantial portion of her weekly capacity to reviewing edge cases in this custom code, often engaging in late-night debates with the CEO and their sole backend engineer to prevent regression bugs. Despite the stress of managing these legacy constraints, she remains driven by a desire to create reliable, scalable systems. She balances this intense professional focus with a disciplined personal life, including competitive rowing and classical piano, which serve as essential outlets for her high conscientiousness. Her reputation among peers is one of quiet competence and unwavering reliability, though she privately grapples with the fatigue of being the only person who fully understands the nuances of the company's identity infrastructure.

Background & daily life

A day in their life

Delores wakes at 5:30 AM, rows for an hour along the canal, and returns home to shower and brew coffee. By 8:00 AM, she is at the office, spending the first block reviewing pull requests related to the custom permission engine. At 10:00 AM, she joins the daily stand-up, where she diplomatically navigates the team's confusion about the latest invite link bugs. Lunch is a quick salad eaten while reading a paper on distributed systems. Afternoon hours are reserved for deep work: architecting the migration path for the recovery flow or writing documentation for the new API endpoints. Around 5:30 PM, she steps away from the screen to coordinate with the CEO on the upcoming investor deck, focusing on how the tech stack supports the narrative. Evenings are strictly for piano practice or family calls, ensuring she disconnects completely from the digital noise before bed.

Lifestyle

Delores lives in a converted Victorian flat in Islington with two co-founders, maintaining a strict separation between home and work despite the proximity. Her mornings begin at 5:30 AM with an hour of rowing on the Regent's Canal to clear her head before the commute. She avoids alcohol during the week, preferring sparkling water or black coffee, viewing physical stamina as critical for high-stakes decision-making. Financially, she is conservative; while her income is strong, she prioritizes cash reserves over luxury assets, reinvesting surplus into her startup's runway. Socially, she is selective, preferring deep conversations with close friends over large networking events, though she maintains a tight-knit community within the London technical founders' circle.

Work life

Her days are dominated by architectural decisions and code reviews, specifically regarding the friction points where their identity provider stops and their business logic begins. The team currently manages complex permissions and invitation flows manually, a burden Delores absorbs daily. She spends roughly 40% of her week debugging race conditions in custom invite logic and another 30% aligning with the CEO on product roadmaps that depend on these infrastructure bottlenecks. Her workspace is minimalist, featuring dual monitors and a whiteboard covered in state diagrams. She enforces a 'no meeting after 2 PM' rule to preserve deep work time, often leaving the office at 6:30 PM sharp to attend evening piano practice.

Relationships

Delores shares a domestic life with two fellow founders, creating a dynamic where professional boundaries often blur. Her parents live in Bristol and visit monthly, providing a grounding counterpoint to the startup intensity. She has a small circle of three close friends from university who understand the unique pressures of entrepreneurship. Professionally, she relies heavily on a single senior backend engineer, treating him as a sounding board for major architectural shifts, though she feels the isolation of being the sole C-level technical voice.

How they decide

Delores operates with a research-heavy, data-driven approach, rarely making impulsive choices. She tends to map out the long-term implications of any decision before acting, often creating detailed documentation to ensure accountability. While she values peer feedback, she ultimately trusts her own analysis of system integrity over market trends or competitor moves. She prefers to solve problems by building robust internal frameworks rather than adopting quick fixes, even if they require more upfront effort.

How they sound

Her speech is measured, precise, and devoid of filler words. She speaks with a Received Pronunciation accent but uses modern British tech slang casually when appropriate. She avoids hyperbole, preferring concrete metrics over adjectives like 'huge' or 'amazing'. When frustrated, she becomes quieter and more direct, cutting through ambiguity with surgical clarity. She rarely says 'I think' or 'maybe'; instead, she states observations as facts backed by her reasoning.

Personality traits

  • meticulous
  • stoic under pressure
  • systematically curious
  • quietly authoritative
  • time-conscious
  • pragmatic idealist
  • direct communicator
  • deep work oriented
  • structurally minded
  • disciplined

Goals

  • Achieve technical scalability to support 10x user growth without refactoring core auth logic
  • Complete a Bach cello suite recording project by year-end
  • Build a sustainable leadership culture that prevents burnout in the early team
  • Secure Series A funding to transition from 'survival mode' to 'growth mode'
  • Develop a public-facing engineering blog to attract top-tier talent
  • Maintain personal physical fitness through competitive rowing for the next five years

Problems & frictions

  • The increasing complexity of custom-coded role assignment logic creates maintenance debt
  • Time scarcity preventing deep engagement with new industry standards and tools
  • Difficulty finding senior engineers willing to join a small, unproven team in London
  • Frustration with the gap between generic authentication solutions and specific business needs
  • Balancing the emotional weight of being the primary technical decision-maker alone
  • Managing the cognitive load of context-switching between strategic planning and low-level debugging

Values

  • reliability
  • clear systems
  • learning
  • accountability

Interests

  • startups
  • piano
  • rowing
  • product design

Media habits

  • The Changelog podcast
  • Lobsters discussion threads
  • Financial Times Tech section
  • Local rowing club newsletter
  • Spotify classical playlists for coding

Questions & answers

Delores Mills’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://clerk.dev/blog/all-of-user-management-not-just-authentication (Clerk) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core message is clear: Clerk handles user management beyond just authentication, which is precisely the pain point we're experiencing. However, the article is light on specifics regarding pricing, which is a significant omission for a product I'd consider. While the promise of "user management as-a-service" is appealing, I'd need to see detailed documentation on the API, SDKs, and especially the pricing tiers before signing up. The mention of "minimum viable product" also raises a flag; I'd need to understand the roadmap's commitment and the stability of existing features.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.