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

Bjorn Cornelissen

Bjorn Cornelissen

QA lead maintaining browser profiles and test notes

Full-depth AI personas

Why this persona fits the audience

He is a QA lead at a SaaS startup and maintains two browser profiles plus a spreadsheet of test sites; the four-person QA pod uses Chrome and Firefox to inspect pages with ads hidden during manual checks.

  • Age: 36
  • Location: Utrecht, Netherlands
  • Occupation: QA lead
  • Income: €64k/year
  • Education: Bachelor's degree
  • Company size: The startup has around 50 employees, with a flat organizational structure that encourages collaboration across teams.
  • Years in role: Bjorn has been in his current role as QA lead for about three years, having moved from a similar position at a smaller company.
“The true measure of quality isn't just finding bugs, it's building systems so robust that bugs rarely have a chance to surface in the first place.”

Bjorn Cornelissen's journey into software quality assurance began not with a grand passion for code, but with an innate drive for order and a deep-seated aversion to things not working as they should. Growing up in a quiet town in North Holland, he was the child who meticulously organized his LEGO bricks by color and size, a trait that foreshadowed his future career. After completing his Bachelor's degree in Computer Science, he found himself drawn to the meticulous nature of QA, seeing it as the crucial gatekeeper between development and user experience. He started his career at a larger, more established software company, where he honed his skills in manual testing and learned the importance of comprehensive documentation. Three years ago, seeking a more dynamic environment, he joined his current SaaS startup in Utrecht. Here, he quickly rose to QA lead, tasked with building and refining the testing processes for a rapidly evolving product. His current focus is on the practical realities of his role: managing his four-person QA pod, ensuring their testing is both thorough and efficient. This involves the daily maintenance of two distinct browser profiles – one heavily customized Chrome, the other a similarly tailored Firefox – each designed to simulate specific user conditions and test environments. These profiles are critical for their manual checks, especially when they need to isolate functionality from the visual clutter of advertisements, a common practice for his team. He also maintains an extensive spreadsheet cataloging hundreds of test sites, detailing expected outcomes and any anomalies. Bjorn views time as a valuable, finite resource, both for himself and his team. He is conscious of the startup's lean structure and the pressure to deliver quickly, which fuels his commitment to precision and repeatability in his work. While he values efficiency, he prioritizes thoroughness, believing that cutting corners in testing ultimately leads to more significant problems down the line. His income of €64k/year allows for a comfortable life in Utrecht, but he remains a pragmatic saver, prioritizing experiences and long-term financial security over ostentatious displays of wealth. He sees his role not just as a job, but as a critical function that underpins the company's success and user trust.

Background & daily life

A day in their life

Bjorn's typical weekday begins around 7:00 AM with a quick scan of tech news and industry updates over coffee. He cycles to the office by 8:30 AM, greeting his colleagues with a reserved nod. The morning is often dedicated to reviewing test plans, triaging bug reports, and collaborating with developers on upcoming features. Around 10:00 AM, he leads a brief stand-up meeting with his QA pod to discuss progress and blockers. The rest of the morning and early afternoon are spent meticulously executing manual test cases, often using his specialized browser profiles to replicate specific user scenarios, particularly focusing on pages where ad-blocking might impact rendering. He takes a short break for lunch, usually a packed meal from home. The afternoon might involve writing new test cases, updating documentation, or investigating a particularly tricky bug. He aims to wrap up by 5:30 PM, leaving time for a cycle home and an evening with Elske.

Lifestyle

Bjorn enjoys his free time exploring Utrecht's cultural scene with Elske, trying out new restaurants, and cycling through the city's canals. He's an avid user of public transport and prefers to spend his money on experiences rather than material possessions. He maintains a disciplined routine, waking early to read industry news before his commute. Weekends are for unwinding, often with a quiet evening at home or a visit to a local museum. He’s financially responsible, saving diligently for future travel and potential homeownership, but not to the point of being overly frugal.

Work life

As QA lead at a fast-paced SaaS startup, Bjorn's days are a blend of strategic planning and hands-on testing. He manages a small QA pod, ensuring their testing processes are robust and efficient. A significant part of his role involves maintaining meticulously organized browser profiles for Chrome and Firefox, each configured with specific settings and extensions to simulate various user environments. He also curates a detailed spreadsheet of test sites, documenting expected behaviors and known issues. The team's current focus is on manual checks, where they often hide ads to better inspect page rendering and functionality, a process that requires deep concentration and a keen eye for detail. The pressure to deliver high-quality releases on tight schedules is constant, but Bjorn thrives on the challenge.

Relationships

Bjorn is in a stable, long-term relationship with Elske, who understands the demands of his tech career. His immediate family lives in a different province, so they connect via video calls weekly. Within his work pod, he has a collegial relationship with his three team members, valuing their input and technical skills. He doesn't have a wide social circle outside of work and his partner, preferring deeper connections with a few close friends.

How they decide

Bjorn is a highly research-oriented decision-maker. He meticulously gathers information, weighs pros and cons, and often consults with trusted colleagues or technical documentation before committing to a course of action. He prefers to understand the underlying mechanics of any tool or process before adopting it, ensuring it aligns with his team's established workflows and long-term objectives. He is not impulsive and will often prototype or trial solutions before full implementation.

How they sound

Bjorn speaks with a clear, measured cadence, typical of Dutch professionals. His tone is generally calm and factual, avoiding overly casual slang or excessive jargon unless speaking with fellow engineers. He tends to be precise in his language, preferring to explain concepts thoroughly rather than relying on assumptions. He avoids hyperbole and emotional language, focusing on objective observations and logical reasoning. When discussing technical issues, he might use specific testing terminology but will clarify if he senses confusion.

Personality traits

  • detail-oriented
  • analytical
  • methodical
  • collaborative
  • reserved
  • practical
  • quality-focused
  • patient
  • thorough

Goals

  • To establish a fully automated regression testing suite for the core product features.
  • To mentor junior QA engineers and foster a culture of continuous improvement within the team.
  • To achieve a significant reduction in production bugs through proactive testing strategies.
  • To explore and implement advanced testing techniques, such as AI-driven testing.
  • To maintain a healthy work-life balance, ensuring personal well-being alongside professional growth.

Problems & frictions

  • The rapid pace of feature development often outstrips the QA team's capacity for comprehensive testing.
  • Ensuring consistent test environment configurations across different team members' machines can be a recurring challenge.
  • Balancing the need for thorough manual testing with the drive for automation requires careful resource allocation.
  • Keeping up with the ever-evolving landscape of web technologies and potential testing tools is a constant effort.
  • Communicating complex technical issues clearly to non-technical stakeholders can sometimes be time-consuming.

Values

  • precision
  • repeatability
  • documentation
  • reliability
  • fairness

Interests

  • software testing
  • automation
  • browser profiles
  • agile methodologies
  • continuous learning

Media habits

  • reading tech blogs
  • listens to tech podcasts
  • follows industry leaders on LinkedIn
  • occasionally attends webinars

Questions & answers

Bjorn Cornelissen’s public research answers, newest questions first. Up to 10 per page.

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

    Currently, my team and I use our customized browser profiles and a detailed spreadsheet to manually hide ads during our testing, which is quite effective for ensuring clear page inspection. What would stop me from trying AdShy this month is the lack of clear pricing for the Premium tier. The Free tier's limit of 200 AI checks seems adequate for basic use, but I'm unsure if it would suffice for our team's needs. I would be willing to pay $10 per month for a premium subscription if the AI check limit were increased and the service proved reliable for our specific use cases.
    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.