Why this persona fits the audience
She currently works as the QA engineer at a five-person startup in Warsaw, with one founder plus four non-founders. She writes test cases, checks new builds before release, and reproduces bugs reported by the founders or first users.
- Age: 29
- Location: Warsaw, Poland
- Occupation: QA engineer at a five-person startup
- Income: 18k PLN/month
- Education: MSc in Computer Science
- Company size: 5
- Years in role: 3
“Every line of code has the potential for a hidden snag; my job is to find it before it trips anyone else up.”
Lea Gaweł grew up in a modest household in a smaller city near Warsaw, where her aptitude for logic and problem-solving was evident early on. Her parents, a teacher and an accountant, encouraged her academic pursuits, particularly in mathematics and science. She excelled in school, finding a particular fascination with how systems worked and how they could be optimized. This led her to pursue a Master's degree in Computer Science at the University of Warsaw. During her studies, she developed a keen interest in software quality assurance, appreciating the meticulous nature of testing and the satisfaction of ensuring a product's reliability. Upon graduation, she was drawn to the dynamic environment of startups, seeing it as an opportunity to have a more direct impact. She joined her current company, a five-person tech startup, three years ago as their first dedicated QA engineer. Her role involves a broad spectrum of responsibilities, from writing detailed test cases and executing manual testing on new builds to meticulously reproducing and documenting bugs reported by the founders or early users. She works closely with the development team, providing crucial feedback that shapes the product's stability. Lea is highly conscientious, driven by a deep-seated value for thoroughness and precision. She finds satisfaction in uncovering edge cases and ensuring that the software released is robust. While she enjoys the collaborative spirit of her small team, she sometimes feels the pressure of being the sole gatekeeper of quality, especially when development timelines are aggressive. She lives frugally, saving diligently towards the goal of owning her own apartment, a symbol of stability she deeply values. Her free time is spent engaging in activities that mirror her analytical mind, like complex puzzles and strategy board games, or escaping into the imaginative worlds of fiction podcasts and novels. She is currently advocating for the adoption of more automated testing tools within the startup to improve efficiency and coverage, a project she believes is crucial for the company's long-term success.
Background & daily life
A day in their life
Lea's typical weekday starts around 7:30 AM. After a quick breakfast and checking personal messages, she heads to the office, usually arriving by 9:00 AM. Her morning is dedicated to executing test cases for the latest build, meticulously documenting any discrepancies found in Jira. Around lunchtime, she might grab a quick pierogi from a nearby 'bar mleczny' or eat a packed lunch at her desk while reviewing bug reports. The afternoon often involves collaborating with a developer to reproduce a tricky bug, writing new test cases for upcoming features, or attending a brief stand-up meeting. She aims to leave by 5:30 PM, but sometimes stays later if a critical issue arises. Evenings are for unwinding with a podcast or a book.
Lifestyle
Lea lives in a shared apartment in the Ochota district of Warsaw with two roommates, both young professionals. She values her quiet evenings, often spent reading science fiction novels or listening to narrative podcasts. Weekends are for recharging, which might involve a long hike in the Kampinos National Park or a strategic board game session with friends. She's a careful spender, prioritizing saving for a down payment on her own apartment, and enjoys cooking simple, healthy meals rather than eating out frequently. Her social circle is small but close-knit.
Work life
As the sole QA engineer at a lean startup, Lea's role is critical and demanding. She meticulously crafts test plans and executes them for every new feature and bug fix. Her days are a cycle of testing builds, documenting defects with precise steps to reproduce, and collaborating closely with the two developers and two founders. The small team size means direct communication is constant, and she often finds herself explaining the impact of bugs to the founders who are more focused on rapid development. She uses Jira for bug tracking and Confluence for documentation, and is pushing for more automated testing.
Relationships
Lea maintains close ties with her parents and a younger brother who live in a smaller town outside of Warsaw. Her closest friends are from her university computer science program, with whom she still meets for board games. At work, she has a professional but friendly rapport with the two developers and respects the founders' vision, though she sometimes wishes for more clarity on long-term technical direction.
How they decide
Lea is a cautious and research-oriented decision-maker. She prefers to gather all available information, weigh the pros and cons systematically, and consider potential long-term implications before committing to a course of action. She values data and evidence, and will often consult with trusted peers or seek out expert opinions if unsure.
How they sound
Lea speaks with a clear, measured cadence. Her tone is generally calm and professional, even when discussing frustrating bugs. She avoids overly casual slang, preferring precise language. When explaining technical issues, she's patient and thorough, ensuring her points are understood. She might occasionally use Polish interjections like 'no cóż' (well) or 'dokładnie' (exactly) in informal moments.
Personality traits
- detail-oriented
- organized
- analytical
- reserved
- dependable
- curious
- methodical
- patient
Goals
- Achieve greater test automation coverage for the company's core product.
- Save enough for a down payment on a small apartment in Warsaw.
- Develop a deeper understanding of backend systems to improve bug detection.
- Maintain a healthy work-life balance despite startup pressures.
- Contribute to building a stable and reliable product that users trust.
Problems & frictions
- Limited resources and time for comprehensive test automation.
- Balancing the founders' desire for speed with the need for thorough quality assurance.
- Reproducing intermittent or environment-specific bugs can be frustrating.
- Feeling the pressure to catch every critical issue before release.
- The constant need to adapt to rapidly changing product requirements.
Values
- thoroughness
- stability
- team accountability
- precision
- reliability
Interests
- puzzles
- automation
- fiction podcasts
- hiking
- board games
Media habits
- technical blogs
- science fiction novels
- news podcasts
- streaming services