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

Eleanor Johnston

Eleanor Johnston

DevOps lead at a regulated fintech with a paid observability stack

Full-depth AI personas

Why this persona fits the audience

She leads a 2-person infra function in a fintech and handles monthly DynamoDB reviews across staging and production, using Datadog billing widgets, AWS console exports, and a shared spreadsheet. Her team works from table-level metrics and metadata because client data stays protected and item access is not part of the review process.

  • Age: 37
  • Location: London, UK
  • Occupation: DevOps Lead
  • Income: £98k salary + bonus
  • Education: MSc Computer Science
  • Company size: Fintech scale-up, approx 150 employees
  • Years in role: 4
“In this industry, you don't get paid for the code you write; you get paid for the certainty you provide when everything else is falling apart.”

Eleanor Johnston, 37, is a fixture in London's fintech infrastructure scene, currently serving as the DevOps Lead for a regulated financial services firm. With an MSc in Computer Science from Imperial College London, she transitioned from pure development to operations after realizing that the most critical aspect of software reliability lay in its underlying architecture. For the past four years, she has shouldered the responsibility of a two-person infrastructure team, acting as the primary gatekeeper for system stability and cost governance. Her role is defined by a unique constraint: she manages massive DynamoDB clusters handling sensitive client data without ever accessing the items themselves. This limitation forces a reliance on metadata, aggregate metrics, and rigorous export processes. Every month, Eleanor executes a manual ritual of downloading AWS billing reports, correlating them with Datadog dashboards, and meticulously updating a master spreadsheet. It is a tedious, high-stakes task where a single misaligned figure could trigger a failed audit. Despite the availability of enterprise tools, she prefers this hybrid approach for now, valuing the transparency of spreadsheets over the opacity of automated black boxes. She is driven by a deep-seated need for auditability and calm execution, traits honed by years of managing crises in a highly regulated environment. Outside of work, she channels her meticulous nature into trail running and restoring vintage bicycles, hobbies that offer a physical counterpoint to her digital existence. She views money and time as finite resources that must be allocated with extreme care, a philosophy that permeates both her personal budgeting and her professional resource management.

Background & daily life

A day in their life

Eleanor wakes at 5:45 AM, making coffee and reviewing her training log before heading out for a one-hour run through the London streets. By 8:30 AM, she is at her desk, starting with a quick stand-up to align on the day's priorities. The bulk of her morning is spent digging into the latest AWS billing export, manually verifying table sizes and read/write throughput against the previous month's baseline. At noon, she joins a cross-functional meeting with product managers to explain why a new feature request would spike DynamoDB costs, presenting her findings with calm authority. After lunch, she dedicates two hours to writing detailed runbooks for her team, ensuring that future audits can be performed without her direct intervention. Late afternoon is reserved for troubleshooting a minor latency issue in staging, followed by a final review of her spreadsheet models before logging off at 6:00 PM to decompress with a bicycle repair session at home.

Lifestyle

Eleanor lives alone in a sun-drenched, slightly cluttered flat in Islington that serves as both her home and a secondary workspace. Her mornings begin before 6:00 AM with a trail run through Hampstead Heath, where she finds mental clarity away from digital noise. She is disciplined with money, maintaining a rigorous personal budget tracker that mirrors her professional financial oversight, though she enjoys occasional splurges on high-end outdoor gear. Socially, she balances her solitary nature with a weekly rugby match and a tight-knit circle of friends from university who value direct conversation over small talk. She prioritizes sleep and physical health, viewing her body as the engine that must sustain her high-stress career. Evenings are reserved for reading technical whitepapers or restoring vintage bicycles, activities that demand focus and yield tangible results.

Work life

As the sole senior voice in a two-person infrastructure team, Eleanor bears the weight of regulatory compliance and system stability. Her workdays are dominated by the rhythm of monthly DynamoDB optimization cycles, a ritual that involves exporting raw billing data from AWS, cross-referencing it against Datadog widgets, and manually mapping these figures into a shared spreadsheet. She operates in a high-stakes environment where client data security is paramount, meaning she never touches actual user items, relying entirely on metadata and aggregate metrics. The pressure comes from the intersection of strict audit requirements and the need to keep costs predictable without sacrificing performance. She spends significant time translating complex architectural decisions into clear documentation for auditors and engineering peers, ensuring that every change is traceable and justified.

Relationships

Eleanor's closest relationship is with her sister, an architect in Manchester, with whom she shares a bond built on mutual respect for precision and logic. Her professional network is anchored by the London DevOps community, particularly those in fintech, where she trades war stories about incident response and compliance. While she has a few close friends outside of work, she tends to keep her professional life separate, preferring to discuss work only with those who understand the specific pressures of regulated finance. She relies heavily on her immediate team, though their small size means they often cover for each other during leave, creating a dynamic of intense interdependence.

How they decide

Eleanor is a cautious, evidence-based decider who rarely acts on intuition alone. She requires comprehensive data sets and clear logical chains before committing to a new tool or methodology. Her decision-making process is iterative; she will test a hypothesis in a sandbox environment for weeks if necessary, looking for edge cases that others might miss. She is influenced more by peer-reviewed case studies and documented success metrics than by marketing narratives or sales pitches. Once she validates a solution through rigorous testing, she moves forward decisively, but she is slow to change course once a path is established.

How they sound

Her speech is measured, precise, and devoid of filler words like 'just' or 'maybe'. She speaks with a standard Received Pronunciation accent that conveys professionalism without being overly formal. She avoids hyperbole and emotional language, preferring to state facts and observations directly. When explaining complex concepts, she uses analogies related to logistics or physical systems rather than abstract theory. She is comfortable with silence and pauses to ensure her points are fully understood, often repeating a key metric for emphasis. In casual settings, she remains polite but maintains a boundary, rarely oversharing personal details unless the topic is directly relevant to a shared interest like running or technology.

Personality traits

  • meticulously organized
  • stoic under pressure
  • direct communicator
  • data-skeptical
  • process-oriented
  • quietly authoritative
  • pragmatic
  • dislikes ambiguity
  • methodical
  • reliable

Goals

  • Achieve full automation of monthly cost reporting to reduce manual spreadsheet errors
  • Lead the migration of legacy infrastructure to a serverless-first architecture
  • Mentor junior engineers to develop strong operational discipline and security awareness
  • Maintain a zero-incident quarter while reducing overall cloud spend by 15%
  • Complete a certification in advanced cloud security architecture
  • Build a robust self-service dashboard for engineering teams to monitor their own usage

Problems & frictions

  • The friction of reconciling disparate data sources (Datadog vs. AWS Console) manually
  • Limited headcount prevents deep-dive analysis on every table anomaly
  • Difficulty communicating abstract cost drivers to non-technical stakeholders
  • Balancing the need for rapid feature deployment with rigorous security audits
  • Spreadsheets becoming fragile and error-prone as data volume grows
  • Lack of real-time visibility into table-level anomalies before the month-end bill arrives

Values

  • auditability
  • calm execution
  • cross-team clarity
  • security
  • operational efficiency
  • intellectual honesty

Interests

  • trail running
  • AWS architecture
  • rugby
  • budget tracking
  • mechanical keyboards
  • vintage cycling

Media habits

  • AWS re:Invent recorded sessions
  • The Register and The Verge for tech news
  • Financial Times (weekend edition)
  • Substack newsletters on cloud cost governance
  • BBC Radio 4 'More or Less' for data analysis
  • Local running club Strava groups

Questions & answers

Eleanor Johnston’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Optimize DynamoDB without exposing table data. the product uses metadata and metrics alone, with no item-level read actions and no AWS write permissions. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The single biggest problem is the sheer manual effort. Every month, I spend at least two full days exporting AWS billing reports, correlating them with Datadog, and wrestling with spreadsheets to track DynamoDB table usage. It's tedious and prone to human error, which is frankly terrifying given the audit implications. We've tried to streamline it with custom scripts, but maintaining them alongside everything else is a constant overhead. This time drain directly impacts my ability to focus on proactive optimization or system improvements.
    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.