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

Umut Riediger

Umut Riediger

QA automation engineer at a software company

Full-depth AI personas

Why this persona fits the audience

He works in a 3-person QA group and spends part of most days opening local JSON fixtures, CSV test exports, screenshots and PDF reports on a work laptop. He moves between VS Code, terminal tools and browser previews when checking test data before it goes into tickets.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: QA automation engineer
  • Income: €78k/year
  • Education: Master's degree in Computer Science
  • Company size: mid-sized SaaS company (150-200 employees)
  • Years in role: 5
“I don't mind fixing other people's tests, but I draw the line at fixing their bad habits. The system should prevent the mistakes, not just catch them after the fact.”

Umut Riediger earned his Master's in Computer Science from the Technical University of Berlin, specializing in software testing and quality assurance. After three years at a startup that emphasized 'move fast and break things' (which he hated), he joined his current SaaS company five years ago specifically because of their stated commitment to quality. As the most experienced member of his small QA team, he's become the de facto expert on their test infrastructure - a role he enjoys but finds increasingly isolating as the company pushes for faster releases. His meticulous approach makes him the team's error catcher, but also their bottleneck when management wants to adopt new tools. Recently, he's been spending evenings teaching himself Playwright after realizing their current Selenium tests were becoming unwieldy, though he's careful not to overcommit to the new framework until he's certain it solves their specific pain points. Financially, he lives comfortably but prioritizes experiences over possessions - his monthly budget includes a climbing gym membership, high-quality coffee beans, and a small GitHub sponsorship fund for open-source testing tools. Socially, he maintains a small but meaningful circle, preferring deep technical conversations over small talk. His biggest professional frustration is watching the company's test coverage erode in pursuit of metric-driven velocity, but he's too prideful to complain directly and instead channels his efforts into creating self-documenting test scripts. A recent highlight was helping onboard a junior QA engineer, where he discovered teaching the fundamentals was far more satisfying than he expected. He's currently evaluating whether to specialize further in test automation or transition toward a staff engineer role, though the latter would require developing more political skills he's deliberately cultivated to avoid.

Background & daily life

A day in their life

Umut's workday starts at 8:15 AM with coffee made from yesterday's roast, then a 15-minute commute via e-bike. By 9:00 AM, he's already debugging yesterday's failed test cases in VS Code while eating a protein bar. The morning blurts into standup (where he carefully words his updates to avoid triggering their velocity-obsessed PM), then two hours of writing new Selenium tests for a new API endpoint. Lunch is a salad from the corner shop eaten at his desk while reviewing CI/CD pipeline logs. Afternoons are spent analyzing test failures - today it's inconsistent JSON responses between environments, which he documents in a shared Notion page. At 5:30 PM, he cycles past Alexanderplatz to Boulders gym, where he focuses on his 'project' climb - a 6B+ he's been working on for three weeks. Evenings are for roasting coffee beans (noticing subtle flavor differences is a kind of work for him) and kicking back with a board game like Terraforming Mars or Root with his flatmate.

Lifestyle

Umut lives in a compact but well-organized apartment in Prenzlauer Berg, where he's converted a corner of his living room into a small climbing wall for practice. His schedule alternates between focused home days (where he roasts small batches of coffee beans) and social outings limited to board game nights with a tight-knit group or climbing sessions at the Boulders gym. Financially prudent but not frugal, he splurges on high-quality tools and hobbies but meticulously tracks expenses. Health-wise, he's disciplined about movement but occasionally skips breakfast in the mornings where he codes. His social circle is small but deep – mostly colleagues from tech meetups and climbing partners who share his quiet intensity.

Work life

As the most senior QA engineer in his 3-person team, Umut spends mornings writing and debugging test scripts in Python, then afternoons reviewing rapid test executions. His laptop is always a mess of open tabs: JSON viewers for API responses, diff tools comparing logs, and terminal windows running CI/CD pipelines. His biggest daily friction is hunting through CSV exports where data fails to align properly – a weekly occurrence he's stopped trying to escalate. The team's agile standups feel performative, but he's developed a system of annotated PDF reports and color-coded Jira tickets to keep track of reality. Recently pushed back against management's push to transition from Selenium to Playwright, citing unproven stability in their specific workflow.

Relationships

Single and happy with the arrangement, Umut's closest relationships are with his climbing partners (who also share his board game obsession) and a small group of former university classmates now scattered across Berlin tech jobs. His mother in Hamburg keeps trying to set him up with engineers who 'understand his lifestyle', which he politely declines. Most of his professional mentorship comes from reading the work of senior engineers on GitHub and experimenting with their approaches in personal projects. His strongest influence is a mid-career QA lead he met at a Berlin meetup, whose pragmatic approach to testing still guides his work.

How they decide

Deliberate and research-heavy, Umut tests potential solutions in isolated environments before considering adoption. He values documentation over demos and prefers making decisions at his own pace. Once convinced, he commits fully but isn't afraid to reverse course if evidence changes. Skeptical of vendor claims, he'll often prefer building his own small tool over adopting a new product unless the time savings are demonstrably significant.

How they sound

Speaks in precise, measured phrases with occasional dry humor. Uses vivid technical analogies when frustrated ('This CSV is like a spaghetti script with extra steps'). Avoids filler words and disdains corporate jargon. Voice tends to flatten during technical discussions but gains energy when talking about climbing or open-source projects. German accent faintly present when tired or excited, specifically noticeable on the words 'problem' and 'solution'.

Personality traits

  • quietly analytical
  • predictably meticulous
  • skeptical of buzzwords
  • patient with systems
  • impatient with chaos
  • enjoys quiet expertise
  • dislikes performative meetings
  • tolerates ambiguity but hates messy data
  • involuntary problem solver
  • tactfully assertive when standards slip

Goals

  • Transition into a staff engineer role within 2 years
  • Contribute significantly to an open-source testing framework
  • Climb 6C without falling
  • Build a reliable home espresso rig that doesn't break the 300€ mark
  • Write a technical blog series about underrated QA patterns

Problems & frictions

  • Struggles with data consistency across different environments when testing
  • Finds some team members cut corners on test coverage for velocity
  • Dislikes how management prioritizes flashy new tools over stable systems
  • Wants better visualization tools for comparing large CSV datasets
  • Occasional burn out from being the team's de facto documentation keeper

Values

  • correctness
  • clean systems
  • independence
  • learning
  • efficiency

Interests

  • open source projects
  • board games (eurogames specifically)
  • bouldering
  • coffee roasting
  • urban cycling

Media habits

  • Hacker News
  • GitHub trending
  • Berlin tech meetups
  • Notion for personal knowledge management
  • Spotify playlists for deep work

Questions & answers

Umut Riediger’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying FileWink (https://filewink.com/) 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, I'm juggling CSV exports, JSON fixtures, and PDF reports on my laptop, and if I'm honest, it’s messy. I usually open JSON in VS Code, CSVs in some terminal tool—I’ve got a half-dozen tabs open just to track test data before tickets go out. FileWink sounds convenient, but I’d need to see if it handles our JSON and PDF formats reliably, especially since I’m dealing with inconsistent API responses daily. Also, I don’t want to introduce another tool that complicates our workflow. For something like this, I’d only commit if it genuinely sped things up. As for cost, I wouldn’t pay more than $5/month, but I’d prefer a free option if it works without sacrificing performance.
    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.