Paula Kowal

Why this persona fits the audience

Runs visual regression and accessibility spot checks for a 15-person software team in Kraków, including color-contrast verification for new screens and theme updates. Uses spreadsheets, browser devtools, and hand calculations when reviewing HEX values during sprint testing.

• Age: 27
• Location: Kraków, Poland
• Occupation: QA Analyst
• Income: 180k PLN
• Education: Bachelor's in Information Systems
• Company size: 15 employees
• Years in role: 4

“If you can't prove the numbers support the design, the design doesn't exist for everyone.”

Paula Kowal is a 27-year-old QA Analyst based in the heart of Kraków, Poland, working for a rapidly growing 15-person software firm. With a Bachelor's degree in Information Systems, she has spent the last four years refining her craft into a discipline of exacting precision. Earning 180,000 PLN annually, she represents a rare demographic in the Polish tech sector: a highly paid specialist in quality assurance who prioritizes ethical design over speed. Her role is pivotal yet often thankless; she is the final barrier preventing inaccessible interfaces from reaching users, a responsibility she wears with quiet pride. Her workflow is a hybrid of modern automation and archaic rigor. Despite having access to various browser extensions, Paula insists on manual verification for complex theme updates. She keeps a dedicated spreadsheet where she logs every HEX value, calculates luminance ratios by hand to double-check automated reports, and documents deviations with photographic evidence. This methodical approach stems from a fundamental belief that software must serve all humans, regardless of visual ability. Recently, she faced a significant friction point when a senior developer pushed a 'brand refresh' that inadvertently lowered contrast ratios below WCAG 2.2 AA standards. Instead of accepting the trade-off, Paula halted the release, presented a data-backed report, and negotiated a redesign that preserved both aesthetics and compliance. Outside of work, Paula's life is structured around order and sensory appreciation. She is a devoted amateur chef who approaches recipes with the same logic as code, meticulously tracking variables like temperature and time. Her love for indie games often centers on titles with distinct, high-contrast art styles that do not rely on color alone for gameplay mechanics. Financially, she is secure but not ostentatious; she directs surplus income into savings and personal development rather than luxury consumption. Paula's personality is defined by high conscientiousness and moderate introversion; she finds energy in solitary focus and deep dives into problems rather than social networking. She is currently navigating the transition from a pure executor to a strategic leader, aiming to implement a more robust, automated accessibility framework that reduces the burden of manual calculation while maintaining her signature level of scrutiny.

Background & daily life

A day in their life

Paula wakes at 6:30 AM, brews a precise pour-over coffee, and walks to the office near Rynek Główny. By 9:00 AM, she is in the daily standup, listening intently while taking notes on potential visual regressions discussed. Her morning is spent running browser DevTools scripts and cross-referencing the output against her master spreadsheet. Around noon, she joins a design review where she points out that a proposed blue button fails AAA standards on white backgrounds, forcing a revision. After lunch, she spends two hours manually calculating contrast ratios for a new dark mode theme, writing down the math in her notebook to verify the tool's accuracy. Late afternoon involves updating Jira tickets with detailed screenshots and HEX value corrections. She leaves by 5:30 PM, attends a cooking class or grocery shopping, and ends the evening reading about new WCAG updates before bed.

Lifestyle

Paula lives in a renovated pre-war apartment in Kazimierz, surrounded by historic brickwork and narrow cobblestone streets. Her mornings are ritualistic: strong coffee, a 20-minute walk to work through Planty Park, and checking emails before the commute. She is an avid home cook who treats recipes like code—precise measurements and strict adherence to timing are non-negotiable, often experimenting with fermentation or sous-vide on weekends. Financially prudent, she maximizes her high income through a mix of savings and investing in technology upgrades rather than luxury goods. Socially, she prefers small gatherings with close friends over large parties, often meeting for board game nights or quiet dinners where conversation flows naturally without forced chatter.

Work life

At her startup, Paula is the gatekeeper for visual integrity and accessibility compliance. Her day is dominated by manual visual regression tests, where she inspects every pixel change across different themes. She frequently finds herself calculating contrast ratios manually using spreadsheets because automated tools miss subtle edge cases in their specific UI framework. The pressure comes from tight sprint cycles; if a developer pushes a 'light mode' update that fails WCAG AA standards, she must flag it immediately, even late in the week. She works closely with a small design team, acting as the bridge between creative intent and technical reality. While she enjoys the intellectual challenge, the repetitive nature of verifying thousands of HEX codes can be mentally draining.

Relationships

Paula is the youngest sibling in a close-knit family of engineers; her parents instilled a deep respect for rules and precision early on. She maintains a tight circle of four childhood friends from university, mostly fellow developers or designers, whom she meets bi-weekly. In her professional life, she has a mentorship relationship with the CTO, who values her unflinching adherence to standards. She is not heavily active in broad community groups but is a regular fixture at niche accessibility workshops in Warsaw and Kraków, where she feels most understood.

How they decide

Highly analytical and risk-averse. Paula rarely makes decisions based on hype or marketing flair. She requires empirical evidence, peer reviews, and clear documentation before committing to any new process or tool. If a solution lacks transparency in how it achieves results, she will reject it regardless of cost. She tends to research thoroughly, often creating comparison matrices of pros and cons before moving forward, preferring a slower decision path that guarantees long-term reliability over quick fixes.

How they sound

Her speech is measured, articulate, and devoid of filler words. She uses technical terminology naturally (e.g., 'luminance,' 'ratio,' 'compliance') but avoids jargon when speaking to non-technical colleagues, preferring clear analogies. She speaks with a slight Kraków accent, softening consonants, and maintains a calm, steady cadence even when correcting errors. She rarely uses hyperbole or emotional language, sticking to facts and observations. In meetings, she pauses frequently to ensure clarity, often asking, 'Can we verify that number?' before proceeding.