Rick Conn

Why this persona fits the audience

Leads a four-person QA team for a B2B SaaS company. He keeps offline mirrors of marketing pages and product docs from staging and live environments so the team can test link integrity, layout changes, and cached assets without depending on the network. He already uses Cyotek WebCopy on a Windows workstation.

• Age: 41
• Location: Leeds, UK
• Occupation: QA lead
• Income: £68k
• Education: Master's degree in software engineering
• Company size: 120 employees
• Years in role: 3

“If you can't reproduce it in a controlled environment, it doesn't exist until someone else breaks it.”

Rick Conn is a 41-year-old QA Lead based in Leeds, United Kingdom, operating at the intersection of rigorous engineering standards and practical software delivery. Holding a Master's degree in Software Engineering, he transitioned from a pure development role to quality assurance leadership six years ago, driven by a fascination with how systems fail when scaled. Currently, he leads a four-person team at a B2B SaaS company, where his primary mandate is ensuring the integrity of both the product and its accompanying documentation. Rick has developed a specific workflow relying on offline mirrors of marketing pages and product documentation, captured from both staging and live environments. He utilizes Cyotek WebCopy on his Windows workstation to maintain these local archives, a decision born from frustration with intermittent network outages that previously halted his team's ability to test link integrity and layout consistency. This proactive approach allows his team to work independently of external connectivity, significantly reducing downtime during critical release cycles. Personality-wise, Rick scores high on conscientiousness and low on neuroticism, traits that define his professional demeanor. He is the steady anchor in his team, valuing repeatability and accountability above all else. While he is open to new ideas, his default stance is one of cautious verification; he believes that a tool is only as good as its reliability record. His income of £68k supports a comfortable, middle-class lifestyle in Roundhay, where he balances his demanding job with a passion for analog photography and family life. Recently, Rick made the strategic decision to refactor his team's testing protocols to rely less on cloud-dependent services and more on locally cached assets, a move that required significant upfront scripting effort but has paid off in stability. He views technology not as a magic wand, but as a set of tools that must be mastered to prevent chaos. With two young children and a supportive spouse, Rick navigates his world with a deliberate pace, prioritizing long-term stability over short-term gains.

Background & daily life

A day in their life

Rick wakes at 5:45 AM for a thirty-minute jog along the River Aire, listening to a podcast on system architecture. By 7:30 AM, he's at the kitchen table with his family, packing lunches and checking emails. He arrives at the Leeds office by 8:45 AM, brewing coffee and running a quick status check on the overnight build pipelines. At 10:00 AM, he leads a stand-up, focusing on blockers for the team's regression tests. Mid-morning is reserved for deep work: updating the local mirror of the product docs and writing a PowerShell script to handle edge cases in asset caching. Lunch is a solitary affair at his desk while reading technical blogs. Afternoon meetings involve cross-departmental syncs with product managers, where he gently pushes back on unrealistic deadlines. He leaves by 5:30 PM sharp to pick up his kids, followed by homework help and dinner. Evenings are for film development or reading, ensuring a strict boundary between work and life.

Lifestyle

Rick lives in a semi-detached house in Roundhay, Leeds, a quiet suburb known for its green spaces. His routine is rigid; he wakes at 5:45 AM to run before his family stirs, a non-negotiable habit that grounds him. He and his wife, Sarah, share domestic duties equally, though Rick handles all home IT maintenance. They are financially conservative, maximizing their mortgage over savings, but have no debt aside from the car loan. On weekends, he trades code for film photography, developing black-and-white prints in a dedicated spare room. He values low-key social gatherings with close friends over large parties, often preferring board games or pub quizzes where strategy matters more than noise.

Work life

As QA Lead, Rick manages a tight-knit team of four testers at a mid-sized B2B SaaS firm in Leeds. His day is a blend of high-level strategy and granular debugging. He spends mornings reviewing automated regression suites and afternoons in deep work sessions, often configuring local mirrors of the company's documentation and staging environments using Cyotek WebCopy. This allows his team to verify link integrity and layout shifts without flaky internet dependencies. He shields his team from management pressure by ensuring data accuracy is never compromised. His workspace is a clean, dual-monitor Windows setup, heavily customized with PowerShell scripts to automate the mirroring process. He takes pride in the predictability of his output, viewing any deviation as a systemic failure rather than bad luck.

Relationships

Rick is deeply embedded in the Leeds tech community but remains introverted outside it. He and his wife share a strong, supportive partnership built on mutual respect for each other's careers. He has a small circle of three friends, mostly former university peers, with whom he meets monthly for dinner. He is influenced by his mentors from his early career days who emphasized 'measure twice, cut once.' He acts as the technical advisor for his extended family, though he prefers they call him only when necessary. He values privacy and rarely discusses work frustrations outside the office.

How they decide

Rick is a methodical researcher who relies on empirical evidence and peer validation. He does not make impulsive decisions, preferring to simulate outcomes or test hypotheses before committing resources. He values open-source transparency and community reputation over flashy marketing claims. When evaluating new tools, he reads documentation thoroughly, checks GitHub activity history, and consults with trusted colleagues. He is risk-averse regarding data integrity and will stick with a known, stable solution even if a newer alternative promises minor efficiencies, unless the current tool demonstrably fails.

How they sound

Rick speaks with a clear, measured Yorkshire accent, avoiding slang but maintaining a warm, approachable tone. He uses precise technical terminology but explains complex concepts simply when speaking to non-technical stakeholders. He avoids hyperbole, preferring phrases like 'that seems plausible' over 'this is amazing.' He rarely raises his voice, even under pressure, and tends to pause thoughtfully before answering difficult questions. In casual conversation, he asks probing questions about people's interests rather than dominating the discussion.