Prokop Urbanowicz

Why this persona fits the audience

Works as a QA automation engineer on a 4-person test automation group in Warsaw. He keeps test ideas, bug patterns, and learning notes in Obsidian and spreadsheets, and uses them alongside CI dashboards and manual checklists for the systems he validates.

• Age: 30
• Location: Warsaw, Poland
• Occupation: QA automation engineer
• Income: PLN 260k annual income
• Education: Master's degree in Computer Science
• Company size: Mid-sized tech company (approx. 300 employees)
• Years in role: 5

“The most reliable systems are built not just on code, but on a deep understanding of potential failure points, meticulously documented.”

Born and raised in a smaller city in Poland, Prokop Urbanowicz developed an early fascination with how things work, which naturally led him to computer science. His academic journey culminated in a Master's degree, where he honed his analytical skills and developed a strong foundation in software engineering principles. He gravitated towards quality assurance, finding a particular satisfaction in the meticulous process of uncovering defects and ensuring system integrity. His career path led him to his current role as a QA automation engineer in Warsaw, where he's been for the past five years, steadily climbing the ranks within his team. Prokop’s approach to his work is deeply influenced by his values of precision and calm; he believes that thoroughness and a systematic mindset are paramount in building robust software. He meticulously documents his findings, test ideas, and bug patterns in Obsidian, creating a personal knowledge base that informs his daily work. This system, combined with CI dashboards and manual checklists, forms the bedrock of his validation process. He sees his role not just as finding bugs, but as contributing to the overall quality and reliability of the product. His income allows for a comfortable, albeit not extravagant, lifestyle, which he prioritizes maintaining through careful financial planning and saving. He views money as a tool for security and future opportunities, rather than a means for immediate indulgence. Prokop is currently focused on enhancing the stability of his team's automated test suites, a task that requires significant analytical effort and a deep dive into the application's architecture. He recently decided to invest more time in learning advanced Cypress techniques to tackle persistent flakiness issues, reflecting his commitment to continuous learning and problem-solving. His reserved nature means he often works through challenges independently before presenting solutions, a trait that, while effective, sometimes requires conscious effort to ensure collaborative alignment within his small team.

Background & daily life

A day in their life

Prokop's typical weekday starts around 6:30 AM with coffee and a review of his Obsidian notes or a quick scan of tech news. By 8:00 AM, he's logged in, checking CI build statuses and any urgent alerts. The morning is often dedicated to coding – writing new automation scripts, debugging failures, or refactoring existing code. He takes a short break for lunch, usually a simple meal prepared at home. The afternoon might involve a team sync-up, code reviews, or deeper analysis of a complex bug pattern he's identified. He finishes his workday around 5:00 PM, often spending the evening with a quiet hobby like chess or reading, ensuring he winds down before bed.

Lifestyle

Prokop lives a structured, relatively quiet life in Warsaw. His one-bedroom apartment is functional and tidy, reflecting his preference for order. He wakes early, often before 6 AM, to have a quiet coffee and review his Obsidian notes before his workday begins. Evenings are typically spent either reading technical articles, playing chess online against players from around the globe, or occasionally working on a small personal open-source contribution. He prioritizes health through regular, moderate exercise, usually a brisk walk or a session at the local gym a few times a week. His finances are managed carefully, with a focus on saving for future stability rather than immediate gratification.

Work life

As a QA automation engineer in a compact team of four, Prokop's days are a blend of coding, analysis, and collaboration. He's deeply involved in maintaining and expanding the automated test suites for their company's core SaaS product. His current focus is on refactoring a brittle end-to-end test suite using Cypress, aiming to improve its stability and reduce false positives. He relies heavily on his meticulously organized Obsidian vault for tracking bug patterns and test ideas, cross-referencing them with CI dashboard metrics and manual checklists. While he appreciates his colleagues, he often finds himself preferring to dive deep into a problem independently before seeking input.

Relationships

Prokop maintains a small circle of close friends, mostly met during university, with whom he shares intellectual interests. His relationship with his parents is cordial but somewhat distant due to geographical separation. Within his team, he has a professional, respectful rapport with his colleagues, though he tends to keep his deeper thoughts and analyses to himself until he's fully formed them.

How they decide

Prokop is highly analytical and research-driven. He prefers to gather information, weigh pros and cons systematically, and often consults documentation or technical reviews before making a decision. He is not easily swayed by trends or peer pressure, valuing evidence and logic above all else. He tends to be cautious, especially when it involves significant changes or investments of time and resources.

How they sound

Speaks with a measured cadence, often pausing to formulate his thoughts precisely. His language is generally formal and technical, avoiding slang or overly casual expressions. He tends to be direct and factual, preferring to explain the 'why' and 'how' behind his statements. He avoids hyperbole and emotional language, focusing on logic and observable data. When discussing technical topics, he uses specific terminology accurately.