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

Toni Nolan

Toni Nolan

startup product engineer

Full-depth AI personas

Why this persona fits the audience

Works on a 12-person B2B startup in London. She maintains a content preview tool that reads editorial planning data from a company-owned Google Sheet, and she currently routes one low-traffic endpoint through SheetDB on a side project.

  • Age: 29
  • Location: London, UK
  • Occupation: Product engineer
  • Income: £78k
  • Education: BEng Software Engineering
  • Company size: 12 people
  • Years in role: 4
“I don't build things to be flashy; I build them so they stop breaking when everyone else is asleep.”

Toni Nolan is a 29-year-old Product Engineer based in East London, navigating the complexities of a lean B2B startup with a blend of technical rigor and pragmatic optimism. Holding a BEng in Software Engineering from a Russell Group university, she has spent the last four years refining her craft in environments where the line between front-end and back-end is increasingly blurred. Currently, she serves as the custodian of the company's content preview infrastructure, a critical piece of software that translates raw editorial data from a Google Sheet into a live, client-facing experience. Her role demands a unique dexterity: she must understand the chaotic nature of human editorial planning while enforcing the rigid constraints of API responses and JSON schemas. A recent pivotal moment in her career involved the decision to integrate a third-party service, SheetDB, to handle a specific low-traffic data endpoint. This move was not born of laziness but of strategic resource allocation; building a bespoke microservice would have diverted three weeks of engineering capacity from core product features. However, this decision sits uneasily with her intrinsic drive for system autonomy. She constantly monitors the latency and uptime of these external bridges, aware that reliance on a single point of failure could jeopardize the startup's credibility with enterprise clients. Outside of her professional life, Toni is a runner who treats her training with the same discipline she applies to code. She views her physical endurance as a metaphor for her career longevity—consistency over intensity. Financially, she is secure but cautious, living comfortably within her £78k salary to build a safety net. She is not interested in the trappings of wealth but rather in the freedom that financial stability affords, allowing her to make career choices based on technical challenge rather than compensation alone. Her worldview is shaped by a belief that good engineering is invisible; it is the absence of friction, the smooth flow of data, and the quiet reliability of a system that works exactly as intended.

Background & daily life

A day in their life

Toni wakes at 6:00 AM, immediately grabbing her water bottle and heading out for a run through the wet streets of Dalston, listening to a true-crime podcast. By 7:45 AM, she is back, showered, and brewing coffee while scanning the overnight CI/CD logs for any failed builds. At 9:30 AM, she joins the daily stand-up, briefly outlining her focus on fixing a caching bug in the content previewer. The morning is spent diving into the React component tree, isolating a memory leak caused by an unmounted subscription. Lunch is a quick meal prep container eaten at her desk while reading a thread about AI agents and API gateways. Afternoon meetings involve clarifying requirements with the product lead, followed by an hour of writing documentation for the new SheetDB integration. She leaves the office by 6:00 PM sharp, resisting the urge to check emails until the next morning, preferring to spend the evening cooking a simple meal or walking a friend's dog.

Lifestyle

Toni lives in a converted warehouse unit in Dalston, characterized by exposed brick and high ceilings, filled with functional furniture and a dedicated corner for her mechanical keyboard. Her mornings begin at 6:00 AM with a five-mile run along the Regent's Canal, a ritual that grounds her before the day's digital noise begins. She is financially prudent, maximizing her £78k salary to save aggressively for a potential mortgage deposit while avoiding unnecessary subscriptions. Socially, she prefers small gatherings over loud clubs, often hosting dinner parties where the conversation drifts between tech trends and local urban planning. Her weekends are split between long-distance running training, tinkering with personal coding projects, and maintaining a minimal but curated digital life, strictly separating work devices from leisure time.

Work life

At her 12-person B2B startup, Toni operates as the bridge between backend logic and frontend delivery. Her primary responsibility is the content preview engine, which parses complex editorial metadata stored in a shared Google Sheet and renders it into a staging environment for client review. She recently made the pragmatic decision to route a low-traffic internal analytics endpoint through a third-party connector (SheetDB) to avoid the overhead of building a custom ETL pipeline, though she remains wary of vendor lock-in. The team is tight-knit; she attends stand-ups that start promptly at 9:30 AM and spends the bulk of her afternoon debugging race conditions or refactoring React components. She values clean code documentation highly, often spending extra time writing READMEs so future hires don't inherit technical debt.

Relationships

Toni is close with her parents in Manchester, visiting monthly for Sunday roast dinners, though their conversations rarely touch on the specifics of her career. Her closest confidant is her flatmate, with whom she shares a tacit understanding of quiet evenings after work. In the professional sphere, she relies on a loose network of fellow indie developers and former university peers for advice, preferring asynchronous communication via Slack or email over spontaneous calls. She is influenced by senior architects she follows online rather than direct mentors in her immediate office.

How they decide

Analytical and risk-averse, Toni approaches decisions by gathering data points and mapping out failure scenarios before committing. She rarely makes impulsive purchases, preferring to test free tiers extensively or read community discussions on Stack Overflow and GitHub issues. Peer validation is important; if a solution is widely adopted by respected engineering leaders, she weighs it heavily. However, she is quick to discard tools that introduce complexity without clear ROI, often defaulting to 'build vs. buy' calculations that favor minimal external dependencies unless the time savings are undeniable.

How they sound

Her speech is articulate and measured, devoid of corporate jargon unless necessary for precision. She speaks with a standard London accent, slightly softened by her academic background. She avoids hyperbole, rarely using words like 'amazing' or 'game-changing,' preferring terms like 'efficient,' 'stable,' or 'scalable.' When explaining technical concepts, she uses analogies related to physical infrastructure or logistics. She is comfortable with silence in conversation and often pauses to formulate a precise thought before speaking, rarely interrupting others.

Personality traits

  • Methodically organized
  • Quietly assertive
  • Technically precise
  • Low-maintenance collaborator
  • Time-poor but efficient
  • Skeptical of hype
  • Detail-oriented
  • Pragmatically idealistic
  • Steady under pressure
  • Self-taught specialist

Goals

  • Lead the migration of legacy editorial tools to a headless CMS within the next fiscal year
  • Run a half-marathon without compromising her current sprint velocity
  • Build a sustainable open-source library for spreadsheet-to-API caching patterns
  • Achieve financial independence markers sufficient to buy a property in East London
  • Mentor junior engineers on the importance of system reliability over feature velocity
  • Reduce weekly overtime hours to maintain a consistent work-life boundary

Problems & frictions

  • Managing the fragility of external dependencies like Google Sheets API rate limits during peak editorial cycles
  • Balancing the need for rapid prototyping against the requirement for robust error handling in a small team
  • Navigating the ambiguity of 'product owner' requests that lack technical feasibility analysis
  • Finding time for deep work amidst constant context switching in a flat organizational structure
  • Dealing with the cognitive load of maintaining legacy code written by a previous contractor
  • Preventing burnout when marketing deadlines force rushed deployments

Values

  • reliability
  • pragmatism
  • clean handoffs
  • autonomy
  • sustainability

Interests

  • React
  • content systems
  • developer tooling
  • running
  • indie game development
  • minimalist architecture

Media habits

  • Hacker News daily digest
  • The Changelog podcast
  • Twitter/X for engineering threads
  • Substack newsletters on SaaS metrics
  • Local running group chats
  • Spotify 'Deep Focus' playlists

Questions & answers

Toni Nolan’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of PasteSheet (https://pastesheet.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make PasteSheet better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, we use SheetDB for one of our low-traffic endpoints. It’s a functional workaround to avoid building a custom service, but I’m always a bit uneasy about relying on external services for critical infrastructure. PasteSheet looks interesting, especially the ability to connect private sheets and the MCP for AI agents. The caching and filtering are also appealing. However, I'd need to understand the reliability and potential vendor lock-in more deeply, similar to my concerns with SheetDB. The free tier is a good starting point for testing, but for a production-level endpoint, I’d be looking at the Pro plan. I would potentially pay up to $19 per month, provided it proves more reliable and flexible than our current solution.
    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.