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

Evelien Boer

Evelien Boer

QA automation lead at an early-stage startup

Full-depth AI personas

Why this persona fits the audience

She leads QA automation for an eight-person startup and checks GitHub pull requests for test-impact areas. The team uses a low-cost visual review tool competitor together with a shared handoff doc in Drive to keep approvals visible.

  • Age: 30
  • Location: Amsterdam, Netherlands
  • Occupation: QA Automation Lead
  • Income: €71k
  • Education: BSc Software Engineering
  • Company size: 8
  • Years in role: 2
“If you can't measure it, you can't improve it, and if you can't reproduce the bug, you haven't really fixed anything.”

Evelien Boer, 30, is the backbone of the engineering culture at a fledgling fintech startup in Amsterdam. With a BSc in Software Engineering from TU Delft, she entered the workforce during the rise of DevOps practices and quickly realized that traditional manual testing was incompatible with the velocity of modern startups. Two years ago, she stepped into the role of QA Automation Lead, becoming the de facto guardian of code quality in a team of eight ambitious but inexperienced engineers. Unlike her peers who chase shiny new technologies, Evelien champions pragmatism; she believes that a robust, repeatable process is worth more than a sophisticated tool that no one understands. Her daily reality is a constant negotiation between speed and safety. The company operates on a shoestring budget, forcing the team to rely on a patchwork of free tools, a low-cost visual review competitor, and a meticulously maintained Google Drive document that serves as their single source of truth for approvals. This manual overhead consumes significant mental energy, often leaving Evelien with less time to focus on strategic improvements to the test architecture. She recently made the difficult decision to pause the addition of new features to the test suite to refactor existing ones, a move that caused initial friction with the development team eager to ship. However, the subsequent drop in production incidents validated her choice. Evelien views time as her most finite resource. She carefully curates her schedule to protect deep work blocks for coding, refusing to be interrupted by trivial administrative tasks. Her income of €71k allows her a comfortable life in Amsterdam, but she remains frugal, investing her surplus into professional development courses and ergonomic equipment rather than luxury goods. Status is irrelevant to her; what matters is the integrity of the software she helps build. She is currently navigating the challenge of scaling her automation efforts without hiring, a constraint that requires her to be exceptionally efficient with every line of code she writes.

Background & daily life

A day in their life

Evelien wakes at 6:30 AM, brewing strong coffee while checking the overnight build logs on her phone. By 7:45 AM, she is cycling through the rainy streets of Amsterdam, listening to a podcast on distributed systems. Arriving at the office by 9:00 AM, she starts with a quick stand-up where she clarifies which PRs need immediate attention. Her morning is dominated by writing Playwright tests for a new feature, debugging a persistent race condition that has been haunting the team for days. Lunch is a solitary sandwich eaten at her desk while reading a technical blog post about AI-assisted testing. Afternoon meetings are reserved for aligning with developers on test coverage gaps. She spends the final hour updating the shared Google Handoff Doc, ensuring every approval is logged visibly. She leaves at 5:30 PM sharp, unwilling to let work bleed into her evening, and heads home to cook dinner and unwind.

Lifestyle

Evelien lives in a bright, slightly cluttered apartment near the Jordaan district, sharing space with two creative professionals. Her routine is structured: she cycles to work every morning regardless of rain, treating it as essential mental prep. On weekends, she prioritizes disconnecting, often hosting game nights or hiking in the Uithof nature reserve. She manages her finances strictly, allocating a fixed percentage to savings and avoiding impulse buys, though she invests heavily in high-quality ergonomic office gear and coffee beans. Her social circle is small but deep, consisting mostly of colleagues from the local tech scene and university friends who value stability over flashiness.

Work life

As the sole QA automation lead in a chaotic eight-person environment, Evelien's day is split between writing Selenium scripts and acting as the gatekeeper for code quality. She spends hours manually inspecting GitHub pull requests, cross-referencing changes against their legacy documentation and a shared Google Doc that tracks approval states. The team relies on a cheap visual review competitor for some aspects, but much of the workflow remains manual because the budget doesn't allow for enterprise suites. Her biggest friction is ensuring that developers understand *why* a change broke a test without sounding like a bottleneck. She often stays late to refactor brittle test suites before the next sprint demo.

Relationships

Her closest confidant is her older brother, a backend architect in Berlin, with whom she discusses architectural patterns weekly. At work, she has a symbiotic but sometimes tense relationship with the CTO, who pushes for speed while she demands stability. She is active in a local Amsterdam cycling club where professional titles don't matter, only endurance. Her parents, both educators, remain her primary emotional support system, often calling on Sunday mornings to check in on her stress levels.

How they decide

Evelien is a methodical researcher who avoids impulsive decisions. She gathers data, creates spreadsheets comparing options, and seeks peer validation from trusted technical communities before committing to any new approach. She prefers evidence-based choices over hype, often running small-scale pilots to validate efficacy before full adoption. Trust is built through consistency and transparency rather than marketing promises.

How they sound

Her speech is clear, precise, and devoid of unnecessary filler words. She tends to use direct language, preferring 'we need to fix this logic error' over 'maybe we could look at this.' She avoids hyperbolic adjectives like 'amazing' or 'terrible,' opting instead for specific descriptors like 'brittle' or 'inefficient.' When explaining complex concepts, she structures her thoughts linearly, often using analogies related to physical systems or infrastructure. She rarely raises her voice, maintaining a calm, steady cadence even when discussing critical bugs.

Personality traits

  • meticulously organized
  • calm under pressure
  • direct communicator
  • process-oriented
  • collaborative but firm
  • resourceful with limited budgets
  • systematic thinker
  • reliable executor
  • quietly confident
  • detail-obsessed

Goals

  • Reduce flaky test rate to under 1% within six months
  • Achieve full integration test coverage for the payment module
  • Mentor junior developers on test-driven development principles
  • Automate 90% of the regression suite by year-end
  • Transition to a fully self-healing testing framework
  • Maintain a healthy work-life balance while scaling the product

Problems & frictions

  • Time-consuming manual verification of edge cases due to lack of dedicated tools
  • Difficulty tracking test impact across distributed, rapidly changing codebases
  • Limited budget prevents adopting comprehensive enterprise QA platforms
  • Fragmented documentation causing confusion during handoffs
  • Balancing speed of deployment with rigorous quality assurance standards
  • High cognitive load from context switching between coding and reviewing

Values

  • test coverage
  • repeatable process
  • team visibility
  • pragmatic efficiency
  • technical debt reduction

Interests

  • test automation frameworks
  • quality workflows
  • Google Drive docs
  • cycling through Amsterdam canals
  • indie board games

Media habits

  • LinkedIn technical threads
  • Spotify 'Focus' playlists while coding
  • Dev.to articles on CI/CD pipelines
  • Local Dutch tech meetups (offline)
  • Reddit r/softwaretesting

Questions & answers

Evelien Boer’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on DevHunt: Free IDE skill that turns a GitHub pull request into a two-zone review map. - Free IDE skill that turns a GitHub pull request into an interactive two-zone... 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 biggest problem is the manual overhead of reviewing pull requests. I spend significant time cross-referencing changes against our documentation and the shared Google Handoff Doc to ensure test impact areas are covered. This takes away from time I could spend improving our test architecture. We currently use a low-cost visual review tool, but it doesn't fully automate this cross-referencing. I'm concerned about scaling our automation efficiently without introducing more manual steps or expensive tools, especially when my team is already lean.
    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.