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

Don Sporer

Don Sporer

Engineering manager in a small team who spends a lot of time in code review and chat

Full-depth AI personas

Why this persona fits the audience

Manages a 6-person backend team in Manchester and works from a MacBook Pro with GitHub, Slack, Jira, documentation, and terminals open side by side. He uses Rectangle and Mission Control every day and is comfortable with fairly technical setup changes.

  • Age: 34
  • Location: Manchester, UK
  • Occupation: Engineering Manager
  • Income: £96k
  • Education: BEng Software Engineering
  • Company size: 45-60 employees
  • Years in role: 2.5
“If I can't see the entire dependency graph on my screen without scrolling, I'm already working too hard.”

Don Sporer, 34, has navigated the transition from individual contributor to leadership with a distinct focus on structural integrity and process efficiency. Raised in a household that valued education and practical skills, he earned a BEng in Software Engineering from the University of Manchester, graduating with a focus on distributed systems. For five years, he worked as a Senior Backend Engineer, where he developed a reputation for writing clean, maintainable code and identifying bottlenecks in legacy systems. Two and a half years ago, he stepped into his current role as Engineering Manager for a mid-sized fintech company in Manchester. His management style is deeply rooted in his belief that structure enables creativity. He views his primary responsibility as removing friction for his six-person team, whether that means optimizing their development environments or shielding them from external stakeholder chaos. Don is technically proficient, often diving into the codebase himself to understand the nuances of a problem before guiding his team toward a solution. He is currently in the midst of a major initiative to refactor their monolithic payment gateway into microservices, a project that requires meticulous planning and constant communication. Outside of work, Don is a dedicated runner, treating the sport as a form of meditation and stress relief. He has completed several half-marathons and is training for a full marathon. His home life reflects his desire for order; his apartment is meticulously organized, and he takes pride in his ability to maintain a healthy work-life balance despite the demands of his role. Financially, he is prudent, having paid off his student loans early and now focusing on long-term investments. He is known among his peers as the person who always has a well-reasoned answer, making him a go-to resource for both technical and organizational challenges.

Background & daily life

A day in their life

Don starts his day at 5:30 AM with a run along the Rochdale Canal, using the quiet morning to mentally reset. By 7:15 AM, he is brewing coffee and reviewing overnight logs on his phone. At 8:30 AM, he arrives at the office (or logs in remotely), immediately tackling the most critical pull requests before the Slack noise begins. His morning is dominated by deep work: analyzing system diagrams and writing architectural RFCs. Lunch is a brief 30-minute walk to grab a sandwich, often listening to a podcast about distributed systems. Afternoons are reserved for synchronous collaboration: pair programming sessions, sprint planning, and 1:1s with direct reports. He ends his day by tidying his desktop, closing unnecessary tabs, and preparing a brief summary for tomorrow's priorities, ensuring he leaves the mental load low enough to enjoy his evening.

Lifestyle

Don lives in a converted warehouse apartment in Ancoats, Manchester, characterized by exposed brick and high ceilings. His routine is rigidly structured: he wakes at 5:30 AM for an hour of running before the city traffic begins, followed by a precise coffee ritual using a V60 pour-over. He maintains his financial health through a disciplined savings strategy, investing heavily in index funds while keeping his tech gear modern but not flashy. Socially, he is selective; he prefers deep one-on-one conversations or small group dinners over loud networking events. His home office is a sanctuary of minimalism, where every physical object has a designated place, mirroring his digital workspace philosophy.

Work life

As the sole engineering manager for a six-person backend team, Don balances strategic planning with hands-on coding. His days are fragmented by Slack pings and pull request notifications, requiring constant context switching. He relies heavily on a multi-monitor setup with a MacBook Pro, utilizing Rectangle for window snapping and Mission Control for rapid navigation between repositories, documentation, and terminal sessions. Recent decisions involved refactoring their CI/CD pipeline to reduce build times, a move that required significant coordination with the DevOps lead. He spends roughly 40% of his week in code reviews, ensuring architectural consistency without stifling developer velocity, and hosts daily stand-ups that strictly adhere to timeboxes.

Relationships

Don shares a flat with two colleagues from the same industry, fostering a supportive living environment focused on mutual growth. He maintains a close-knit circle of three university friends who meet monthly for dinner. His professional network is strong but functional, primarily consisting of peers from the Greater Manchester tech scene. He looks up to a former CTO who now runs a larger startup, often seeking their advice on scaling challenges. Family contact is limited to weekly video calls with his parents in Leeds, who take pride in his stability and career progression.

How they decide

Don approaches decisions with a methodical, evidence-based framework. He rarely acts on impulse, preferring to gather data, simulate outcomes, or consult trusted peers before committing to a change. He evaluates new tools by testing them in a sandbox environment first, weighing the long-term maintenance cost against immediate productivity gains. While he is open to innovation, he is skeptical of hype cycles and demands clear ROI on any time or money invested. Peer recommendations carry significant weight, provided they come from respected technical sources rather than marketing channels.

How they sound

Don speaks with a clear, measured Mancunian accent, avoiding slang unless among close friends. His tone is professional yet approachable, favoring direct language over corporate jargon. He tends to pause briefly before answering complex questions, signaling careful thought rather than hesitation. He avoids hyperbole, rarely saying 'amazing' or 'terrible,' preferring terms like 'efficient,' 'robust,' 'suboptimal,' or 'high-friction.' In meetings, he asks clarifying questions frequently to ensure shared understanding. He does not use filler words like 'um' or 'like' in professional settings, maintaining a crisp cadence that commands respect.

Personality traits

  • Methodical
  • Direct but polite
  • Efficiency-obsessed
  • Systematic thinker
  • Low-drama
  • Detail-oriented
  • Pragmatic
  • Steady under pressure
  • Technically self-sufficient
  • Protective of team focus time

Goals

  • Reduce technical debt accumulation in the core payment processing module
  • Mentor two junior engineers to senior levels within the next 18 months
  • Achieve a stable 40-hour work week consistently across the quarter
  • Implement a more robust observability stack to eliminate reactive debugging
  • Build a sustainable career path that allows for continued hands-on coding
  • Complete a marathon in under 3 hours and 45 minutes

Problems & frictions

  • Frequent context switching breaks deep work flow when managing urgent production incidents
  • Difficulty visualizing complex microservice dependencies across multiple open windows
  • Slack notification fatigue disrupts the rhythm of long code review sessions
  • Balancing the need for detailed documentation with the pressure to ship features quickly
  • Managing calendar fragmentation that leaves little room for strategic thinking
  • Keeping the team aligned on architectural decisions without holding excessive meetings

Values

  • structure
  • accountability
  • team throughput
  • technical clarity
  • predictable schedules

Interests

  • software architecture
  • running
  • coffee
  • mechanical keyboards
  • urban planning

Media habits

  • Listening to tech podcasts (e.g., Syntax, Software Engineering Daily) during commutes
  • Reading Hacker News and specific Substack newsletters on engineering management
  • Following niche Mac automation forums
  • Watching recorded conference talks on weekends
  • Checking Reddit r/sysadmin and r/mac for troubleshooting

Questions & answers

Don Sporer’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Ribbon (https://www.ribbonmac.com/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The $15 one-time purchase price for Ribbon seems quite reasonable, especially considering it's a lifetime license with all future updates. It aligns with my preference for a single, upfront cost rather than subscriptions. For that price, I'd expect it to function seamlessly with my existing setup, particularly how it integrates with Mission Control and my multi-monitor workflow. The promise of 'nothing ever shrinks' is compelling for maintaining productivity. If it truly delivers on its claims and significantly reduces my context-switching friction, I'd consider a no-brainer price to be around $25. However, anything over $40 would start to make me reconsider its necessity, especially given I already use Rectangle.
    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.