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

Mabel Maggio

Mabel Maggio

Staff software engineer at a fintech

Full-depth AI personas

Why this persona fits the audience

At a London fintech, she is the main author of architecture diagrams for a 10-person product squad and an internal architecture review board. She usually sketches in draw.io or directly in Confluence during meetings, then tidies the diagrams for release notes and compliance documents.

  • Age: 38
  • Location: London, UK
  • Occupation: Staff Software Engineer
  • Income: GBP 125k base + bonus
  • Education: MEng in Computer Science
  • Company size: Series B startup (approx. 450 employees)
  • Years in role: 4 years as Staff Engineer
“Clarity isn't just about making things look nice; it's the only way to ensure that when the system breaks at 3 AM, we know exactly how to fix it without guessing.”

Mabel Maggio is a seasoned Staff Software Engineer based in London, operating at the intersection of complex financial systems and rigorous engineering standards. Holding an MEng in Computer Science from Imperial College London, she spent six years in traditional banking infrastructure before transitioning to a high-growth fintech startup four years ago. This move was driven by a desire to apply modern architectural patterns to solve tangible problems in payments, rather than maintaining legacy monoliths. At her current company, Mabel serves as the de facto chief architect for her squad, responsible for the entire lifecycle of system design from initial concept to production deployment. Her daily reality is defined by a unique duality: she must think like a developer to understand implementation constraints, yet act like a compliance officer to ensure every diagram meets the stringent requirements of the FCA (Financial Conduct Authority). She is currently leading a critical initiative to refactor the company's core ledger system, a project that requires meticulous documentation to pass upcoming external audits. This has placed her in a constant state of managing trade-offs between shipping velocity and documentation fidelity. While she excels at high-level abstraction, she finds the manual process of converting rough sketches into polished, version-controlled assets for release notes to be a significant friction point, often eating into her deep-work time. Outside of work, Mabel is a creature of habit and discipline. She runs consistently, treating her physical health with the same systematic approach she applies to code refactoring. Her income of GBP 125k plus bonus provides a comfortable upper-middle-class lifestyle, allowing her to save aggressively for a future second property, though she remains cautious about market volatility. She values her independence and the quiet efficiency of her home environment, avoiding the chaotic energy of large social gatherings in favor of meaningful, one-on-one interactions. Her professional reputation rests on her ability to remain calm during crises, translating complex technical debt into understandable narratives for stakeholders. She is currently focused on achieving Chartered Engineer status, a credential she views as essential for her long-term career trajectory in the UK tech sector.

Background & daily life

A day in their life

Mabel wakes at 5:30 AM for a 7km run, returning by 7:00 AM to shower and prepare for the commute via the Overground to King's Cross. Her workday begins with a 9:15 AM stand-up, where she listens intently to blockers before jumping into a deep-work block on a new API gateway specification. By noon, she hosts a cross-squad sync, sketching real-time flow diagrams in draw.io to resolve a latency issue. Lunch is a quick salad eaten at her desk while reviewing a pull request. Afternoon hours are dominated by an Architecture Review Board meeting, where she defends a design choice against skeptical peers, using calm logic to dismantle concerns. The final hour is dedicated to the tedious task of refining those morning sketches into pixel-perfect, compliant documentation for the quarterly audit. She leaves the office by 6:00 PM, heading home to cook dinner, spend time with her dog, and read fiction before bed, ensuring she disconnects completely to reset for the next day.

Lifestyle

Mabel lives in a renovated Victorian terrace in Islington, filled with plants and functional furniture that prioritizes workflow. Her mornings begin with a 5:30 AM run along Regent's Park Canal, followed by a strict breakfast routine involving porridge and black coffee. She maintains her fitness with high consistency, viewing exercise as non-negotiable maintenance rather than a hobby. Financially, she is prudent; while she earns a strong salary, she avoids flashy spending, preferring to invest heavily in her pension and a mortgage reduction strategy. Her social life is curated and low-drama, centered around small dinner parties with close friends from university and work, where conversation often drifts toward current events or shared intellectual interests rather than gossip.

Work life

As a Staff Engineer at a fast-paced fintech, Mabel is the architectural anchor for a 10-person squad. Her day is split between deep coding sessions and facilitating complex design reviews. She relies heavily on draw.io for rapid prototyping during whiteboard sessions, often sketching directly into Confluence pages before meetings. However, the post-meeting cleanup to ensure diagrams meet strict compliance standards for audit trails consumes significant time. She navigates the tension between engineering speed and regulatory rigidity, often acting as the bridge between developers who want to ship quickly and auditors who demand precision. Her team looks to her not just for code, but for the clarity of their system documentation.

Relationships

Mabel is married to Julian, a structural engineer who shares her appreciation for order and detail. They are deeply embedded in their local community, volunteering occasionally at a neighborhood food bank. Her professional network is tight-knit, consisting mostly of other senior engineers she respects for their technical depth rather than their fame. She has no children yet, which allows her to dedicate evenings to reading and long runs. Her parents live in Manchester, visited monthly, providing a grounding connection to her roots. She values honesty and directness in all relationships, rarely engaging in office politics but fiercely protective of her team's well-being.

How they decide

Mabel employs a highly deliberate, evidence-based decision-making process. She rarely acts on impulse or peer pressure, preferring to gather data, consult established frameworks, and weigh long-term consequences before committing. In professional settings, she seeks consensus through logic rather than authority, often asking clarifying questions until the ambiguity is resolved. She is budget-sensitive regarding tools, viewing them as investments that must demonstrate clear ROI in time saved or error reduction. Once she validates a solution against her criteria of precision and reliability, she commits fully and executes with minimal hesitation.

How they sound

Her speech is measured, articulate, and devoid of filler words like 'um' or 'like'. She uses precise terminology, favoring 'ensure' over 'make sure' and 'mitigate' over 'fix'. She speaks softly but commands attention through tone and pauses rather than volume. She avoids hyperbole and emotional outbursts, preferring to state facts objectively. In disagreements, she asks, 'What is the constraint we are trying to satisfy?' rather than making personal attacks. She does not use slang, even with peers, maintaining a professional cadence that reflects her background in academia and finance.

Personality traits

  • Methodical
  • Diplomatic
  • Visually oriented
  • Stoic under pressure
  • Detail-obsessed
  • Quietly authoritative
  • Structured
  • Empathetic listener
  • Time-conscious
  • Iterative thinker

Goals

  • Achieve Chartered Engineer status within the next two years
  • Lead the migration of legacy payment services to a cloud-native microservices architecture
  • Publish a definitive technical guide on secure transaction flows for junior engineers
  • Run a half-marathon in under 2 hours
  • Mentor three junior engineers to reach Senior level
  • Purchase a second property as a rental investment by age 45

Problems & frictions

  • Fragmented documentation tools causing version control issues in architecture specs
  • Time scarcity when balancing diagram cleanup with critical bug fixes
  • Recurring friction with external auditors over ambiguous visual representations
  • Difficulty scaling informal design decisions across growing squads without formalizing them too early
  • Burnout risk from constant context switching between coding and administrative documentation
  • Managing the cognitive load of maintaining multiple concurrent system views

Values

  • precision
  • accountability
  • calm execution
  • clarity
  • pragmatism
  • long-term stability

Interests

  • financial technology
  • technical writing
  • running
  • urban gardening
  • analog photography

Media habits

  • Weekly 'The Daily' podcast
  • LinkedIn industry discussions
  • Architectural Digest for home inspiration
  • Substack newsletters on distributed systems
  • Local running club group chats
  • BBC News app for morning briefings

Questions & answers

Mabel Maggio’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying SystemDraw (https://www.systemdraw.net/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, what would stop me is the lack of clear pricing information on your site. You mention USD per month subscription, but there's no actual pricing table or details about different tiers. I handle diagramming today using draw.io, often directly in Confluence, and then I have to meticulously clean them up for audits. If SystemDraw offered features that significantly streamlined that post-meeting cleanup for compliance and version control, I might consider it. However, without knowing the cost, it's hard to say. If it was very affordable, say around $20 USD per month, I'd be willing to try it for the potential time savings.
    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.