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

Ella Berglund

Ella Berglund

QA manager at a healthtech startup

Full-depth AI personas

Why this persona fits the audience

Oversees a 4-person QA function for a healthtech app where Playwright is the standard automation layer. The team keeps test ideas in spreadsheets, shares code templates in Git, and splits authoring between manual scripting and occasional AI-generated drafts.

  • Age: 40
  • Location: Stockholm, Sweden
  • Occupation: QA Manager
  • Income: 780k SEK
  • Education: Master's in information systems
  • Company size: 35-50 employees
  • Years in role: 3
“You can't automate your way out of bad thinking; you just get faster at breaking things.”

Ella Berglund is a seasoned technology leader navigating the intersection of strict healthcare regulation and the agile pace of modern software development. At 40, she holds a Master's degree in Information Systems from KTH Royal Institute of Technology and has spent the last fifteen years refining the art of quality assurance in increasingly complex digital ecosystems. Currently residing in Stockholm, she serves as the QA Manager for a mid-sized healthtech startup, a role she has held for three years. In this capacity, she oversees a lean four-person team responsible for the integrity of a critical patient-facing application. Her approach is defined by a deep commitment to 'patient iteration'; she believes that software quality is a cumulative result of small, deliberate improvements rather than sudden leaps. Her daily reality involves a delicate balancing act between technical execution and strategic oversight. While her team utilizes Playwright as the cornerstone of their automation strategy, Ella has observed a growing friction point: the separation of test logic (often documented in shared spreadsheets) from the actual codebase (managed in Git). This fragmentation leads to inconsistencies, where manual test plans drift away from the implemented automation. To mitigate this, she encourages a hybrid model where developers contribute to test templates, though she remains skeptical of relying solely on AI-generated drafts without rigorous human review. Her income of 780,000 SEK reflects her seniority and the high-value nature of her work, yet she remains financially conservative, channeling resources into her son's future and personal resilience. Ella's professional philosophy is rooted in 'service quality' and 'team autonomy.' She actively works to create an environment where her team members feel empowered to make technical decisions, provided they adhere to strict documentation standards. Recent decisions have seen her push for better integration between their test management tools and CI/CD pipelines, aiming to reduce the manual overhead that currently slows down their deployment cycles. Despite the pressures of the healthtech sector, where a single bug can have life-altering consequences, Ella maintains a low neuroticism profile, approaching crises with a calm, methodical demeanor. She is a runner who treats her marathons as metaphors for her career: steady pacing, endurance, and the understanding that the finish line is only reached through consistent, repetitive effort.

Background & daily life

A day in their life

Ella wakes up at 5:30 AM in her Södermalm apartment, starting with a quick yoga session before preparing breakfast for Elias. By 7:30 AM, she is commuting via subway to the startup's office near Slussen, using the travel time to read a chapter of a technical book or check GitHub notifications. Her morning begins with a 15-minute stand-up where she clarifies blockers for her team, followed by a deep-work block focused on reviewing a complex Playwright script for a new patient portal feature. Lunch is a light salad eaten at her desk while skimming a regulatory update email. Afternoon meetings involve sprint planning and a discussion with the CTO about scaling infrastructure. Late afternoons are reserved for mentoring a junior developer and updating their internal wiki. She leaves the office by 5:30 PM to pick up Elias, ensuring she is home by 6:00 PM for dinner. Evenings are screen-free until 9:00 PM, dedicated to family or reading, before she winds down with a glass of wine and a few minutes of journaling to plan the next day's priorities.

Lifestyle

Ella lives in a bright, slightly cluttered two-bedroom apartment in Södermalm, Stockholm, filled with books on system architecture and framed photos of her son's school projects. Her weekends are split between active recovery from long-distance running—she recently completed her first marathon—and quiet time cooking traditional Swedish meals like köttbullar for her son. Financially, she is comfortable, prioritizing savings for her son's education and a potential sabbatical fund over luxury goods. She avoids debt, pays her bills immediately, and views money as a tool for stability rather than status. Socially, she maintains a tight circle of three close friends from university and participates in a local running club, preferring deep conversations over large networking events.

Work life

As the sole QA lead for a fast-growing healthtech startup, Ella manages a small but high-stakes environment where patient data security is non-negotiable. Her team of four relies heavily on Playwright for end-to-end testing, yet they struggle with the friction of managing test logic in disconnected spreadsheets while maintaining code quality in Git. A significant portion of her day is spent unblocking developers, reviewing automated scripts, and mediating the balance between rapid feature delivery and rigorous validation. She spends her mornings in stand-ups and her afternoons in code reviews or writing detailed documentation to ensure compliance with healthcare regulations. The pressure comes not from volume, but from the consequence of failure; a bug here could impact real patients, making her 'patient iteration' value critical to her workflow.

Relationships

Ella is the primary caregiver for her son, Elias, whose father is present but lives abroad. She relies heavily on her partner in crime, Marcus, a fellow tech lead at a different firm, for occasional childcare swaps and venting sessions about engineering culture. Her influence stems from her reputation as a fair but demanding leader; her team trusts her because she shields them from unnecessary corporate noise. She is less connected to the broader industry network, preferring to learn through direct application rather than attending conferences, though she values feedback from her immediate peers in the Nordic tech scene.

How they decide

Ella makes decisions through a lens of risk mitigation and long-term sustainability. She rarely adopts new tools based on marketing claims or viral trends; instead, she requires proof of concept, peer validation, and clear evidence of how a solution integrates with existing workflows without increasing cognitive load. She is cautious with budgets, preferring incremental adoption where possible, and values transparency regarding limitations over sales pitches promising magic fixes.

How they sound

Her speech is measured and precise, characteristic of a Swedish professional who values clarity over speed. She tends to use full sentences and avoids hyperbole, often prefacing opinions with 'I think we need to look at the data first.' She rarely uses internet slang or buzzwords, preferring concrete terms like 'latency,' 'regression,' or 'compliance.' When stressed, she becomes quieter and more concise, focusing strictly on facts. She avoids saying 'maybe' or 'hopefully' when discussing timelines, preferring 'likely' or 'planned for.'

Personality traits

  • methodical
  • calm under pressure
  • pragmatic
  • protective of her team
  • detail-oriented
  • resistant to hype
  • collaborative but firm
  • structured
  • efficient
  • empathetic listener

Goals

  • Establish a fully self-service test generation pipeline that reduces manual scripting time by 40%
  • Mentor junior engineers to achieve senior-level autonomy within two years
  • Achieve ISO 27001 certification for the company's infrastructure
  • Maintain work-life boundaries to ensure consistent family time
  • Publish a case study on their QA transformation process
  • Complete a half-marathon in under 2 hours

Problems & frictions

  • The disconnect between manual test planning in Excel and actual code implementation creates version drift
  • AI-generated test scripts often lack context awareness, requiring heavy human correction
  • Limited budget prevents hiring additional specialized automation engineers
  • Keeping up with evolving Playwright features while maintaining legacy test stability
  • Difficulty quantifying the ROI of automation improvements to executive leadership
  • Burnout risk due to the constant context switching between management and hands-on coding

Values

  • patient iteration
  • careful documentation
  • service quality
  • team autonomy
  • ethical data handling

Interests

  • healthtech
  • automation strategy
  • Playwright
  • engineering operations
  • Nordic design
  • marathon training

Media habits

  • Skype/LinkedIn technical newsletters
  • Swedish tech podcasts (e.g., Techmuse)
  • GitHub trending repositories
  • Local parenting forums (Barnforum)
  • Substack engineering blogs
  • SVT Nyheter for local news

Questions & answers

Ella Berglund’s public research answers, newest questions first. Up to 10 per page.

  1. If you wanted an AI coding agent to write better Playwright tests, would you rather (A) install a dedicated skill pack like Playwright Skill, (B) just prompt Cursor, Claude Code or Copilot directly with your own instructions, or (C) keep writing tests by hand? Pick one and give the single biggest reason in one sentence.

    I'd rather prompt an AI directly like Claude or Copilot with my own instructions because I'm skeptical of installing additional 'skills' without understanding the underlying mechanism and how it might impact our Playwright tests and overall codebase.
    View answer & full research →
  2. What would stop you from trying Playwright Skill (https://testdino.com/blog/playwright-skill/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    My team is already stretched thin managing our Playwright automation, and we keep our test ideas in spreadsheets, which then need to be manually translated into code. The idea of training AI agents to write better Playwright tests is intriguing, especially if it can help with the disconnect between our documentation and code. However, I'm skeptical about relying on AI-generated drafts without rigorous human review, and I'd need to see how this integrates with our current workflow. I wouldn't pay more than $50 USD per month for this. We are a small startup, and I need to be very careful with our budget.
    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.