Why this persona fits the audience
Works on a Mac for a 12-person fintech startup in Dublin, jumping between GitHub, Jira, TestRail, and Terminal. He copies selectors, logs, and test data throughout the day and keeps a free clipboard history tool alongside a text file of common values for repeat runs.
- Age: 31
- Location: Dublin, Ireland
- Occupation: QA Automation Engineer
- Income: €71k
- Education: BSc Software Engineering
- Company size: 12
- Years in role: 5
“If you can't automate it, you're probably doing it wrong, or at least inefficiently.”
Harry Mertz, a 31-year-old QA Automation Engineer, has carved out a niche for himself in Dublin's burgeoning fintech scene. Holding a BSc in Software Engineering from Trinity College Dublin, he's always been drawn to the intricate logic of systems and the satisfaction of making them work flawlessly. His career path has been a deliberate progression, moving from junior QA roles to his current position at a fast-paced, 12-person startup where his expertise is crucial. He thrives in environments where his meticulous nature can directly impact product quality and stability. Harry's workspace is a testament to his personality: a clean, organized desk dominated by his trusty MacBook Pro, surrounded by a curated collection of open-source tools. He's recently been wrestling with the challenge of managing test data across multiple environments, a task that often involves tedious manual copying and pasting of logs and values. To combat this, he relies on a free clipboard history utility and a well-maintained text file for common data snippets, a workaround born out of necessity and a desire for efficiency. This constant drive for optimization extends beyond his work; he's an avid runner, using his morning jogs as a mental reset and a way to maintain discipline. His interest in sci-fi, particularly cyberpunk narratives, reflects a fascination with future technologies and their societal implications. Financially, Harry is prudent, saving diligently for a future property purchase while enjoying the occasional splurge on quality tech or a good book. He values order and predictability, both in his code and his life, and finds deep satisfaction in building robust, reproducible systems that minimize friction and potential errors. His approach to work is characterized by a strong sense of responsibility and a quiet determination to ensure the software he tests is as reliable as possible.
Background & daily life
A day in their life
Harry's day begins at 7 AM with a 5km run along the Royal Canal. After a quick shower and a strong coffee, he's at his desk by 8:30 AM. The first hour is spent reviewing overnight test runs and triaging any critical failures in Jira. He then dives into writing new automated tests for a feature slated for release next sprint, meticulously copying selectors from the browser's dev tools and pasting them into his Python scripts. Lunch is a quick affair, often a sandwich at his desk while scanning tech news. The afternoon involves collaborating with a developer on a tricky bug, debugging a failing CI/CD pipeline, and updating test case documentation in TestRail. He finishes his workday around 6 PM, often spending an hour in the evening reading sci-fi novels or tinkering with a Raspberry Pi project.
Lifestyle
Harry rents a bentwood chair he found on Facebook Marketplace to replace his ergonomic backaches. He runs 5K loops around the Royal Canal, always at 7am, before work. His flat smells of coffee and slightly outdated compound butter. He buys groceries in bulk (MoneySaver.ie deals) but splurges on artisanal sourdough. His social life revolves around a rotating tabletop RPG group and the occasional fintech meetup.
Work life
As a QA Automation Engineer at a lean fintech startup, Harry's days are a blur of code, logs, and bug reports. He's responsible for ensuring the stability of their core trading platform, a task made challenging by rapid development cycles and a small, agile team. His primary focus is on building and maintaining robust automated test suites, often writing custom scripts to cover edge cases. He collaborates closely with developers, providing detailed feedback on bugs and potential regressions. The pressure is constant to deliver high-quality, reliable software under tight deadlines, making efficiency and clear communication paramount.
Relationships
Harry maintains a close but geographically dispersed relationship with his parents in Cork. His core social circle consists of a few long-term friends from university, with whom he plays Dungeons & Dragons online. Within his company, he has a professional but friendly rapport with the development team, often engaging in technical debates over Slack.
How they decide
Harry is a methodical decision-maker, preferring to research thoroughly and weigh pros and cons. He values efficiency and reliability, often leaning towards solutions that have a proven track record or strong community support. He's not easily swayed by hype and will often try free or open-source alternatives before considering paid options.
How they sound
Speaks with a clear, measured cadence, often using precise technical jargon. His tone is generally calm and analytical, with a subtle, dry wit that surfaces during technical discussions. He tends to avoid hyperbole and focuses on factual descriptions. When explaining complex issues, he breaks them down logically, often using analogies. He might say things like, 'The regression seems to stem from...' or 'We need to ensure deterministic outcomes here.'
Personality traits
- process-oriented
- relentlessly systematic
- prone to over-documenting
- dryly humorous
- task-segmenting
- dislikes ambiguous requirements
- loyal to tools that just work
- tends to preempt problems
- hates context-switching
- quietly opinionated about testing frameworks
Goals
- Achieve a senior or lead QA automation role within the next three years.
- Contribute to a significant open-source testing framework.
- Purchase a small property in a quieter part of Ireland.
- Complete a marathon.
- Develop a personal project that solves a recurring automation pain point.
Problems & frictions
- Constant context-switching between different testing environments and tools.
- Dealing with flaky tests that require frequent debugging and maintenance.
- Balancing the need for comprehensive test coverage with tight release schedules.
- Lack of standardized documentation for legacy code sections.
- The overhead of manually copying and pasting data or logs between applications.
Values
- reproducibility
- debuggability
- order
- low friction
- reliability
Interests
- test automation
- sci-fi (especially cyberpunk)
- running (3-4x/week)
- open-source tooling
- hardware modding
Media habits
- listens to tech podcasts during commute
- follows Reddit r/qaengineering
- watches YouTube dev tutorials
- reads arXiv papers on automation