Pablo Blick

Why this persona fits the audience

Uses plain text files, Google Calendar reminders, and a spreadsheet to time personal messages for a partner, parents, and one sibling; has never paid for a letter-scheduling app and usually works from a laptop.

• Age: 41
• Location: Manchester, UK
• Occupation: software engineer
• Income: £92k
• Education: Master's degree
• Company size: Mid-sized fintech firm (150-300 employees)
• Years in role: 6

“I believe that love is a series of deliberate actions, not just a feeling you wait to happen.”

Pablo Blick, 41, is a software engineer based in Didsbury, Manchester, whose life is defined by a quiet commitment to order and reliability. Holding a Master's degree in Computer Science, he has spent the last two decades navigating the complexities of the tech industry, eventually settling into a senior role where he champions code quality and system stability. Despite earning a solid £92,000 annually, Pablo maintains a frugal mindset, viewing money primarily as a mechanism for security and freedom rather than a means for conspicuous consumption. His home reflects this pragmatism; it is filled with self-hosted servers and open-source hardware, reflecting a desire to control his digital ecosystem. Pablo's most notable quirk is his approach to emotional connection. While he loves his family deeply, he finds spontaneous expressions of affection difficult. Instead, he relies on a meticulous, analog-digital hybrid system to manage his relationships. For years, he has used a combination of plain text files, Google Calendar reminders, and a custom spreadsheet to schedule messages for his wife, parents, and younger sibling. This system ensures that birthdays, anniversaries, and even small 'thinking of you' notes arrive exactly when needed, eliminating the anxiety of forgetting. He has resisted paying for specialized SaaS products like LoveWritten, citing a distrust of recurring subscriptions and a belief that existing free tools are sufficient if configured correctly. Recently, he decided to refactor his spreadsheet script to handle timezone discrepancies more robustly, spending three weekends debugging the code rather than searching for a commercial solution. This dedication to self-reliance defines his character: he solves problems himself, values accuracy above convenience, and believes that true care is demonstrated through consistent, reliable action.

Background & daily life

A day in their life

Pablo wakes at 6:15 AM, immediately checking the weather and his cycling route before heading out. After a 25-minute commute and a rigorous workout, he returns home for a quick shower and a protein-rich breakfast. By 8:45 AM, he is logged into his work environment, starting with a review of automated test results and a cup of coffee brewed to a specific temperature. The morning is dedicated to deep coding work, uninterrupted by meetings. Lunch is a packed meal eaten at his desk while reading a chapter of a science fiction novel. The afternoon involves stand-ups, code reviews, and troubleshooting production alerts. At 5:30 PM, he disconnects, heading to the gym or preparing dinner. Evenings are reserved for family time, cooking, and managing his home automation scripts. Before bed, he checks his spreadsheets to ensure no personal messages are scheduled for the next day, a ritual that anchors his sense of control.

Lifestyle

Pablo lives in a quiet, leafy suburb of Manchester where his morning routine is non-negotiable: a 20-minute cycle ride before work, followed by a breakfast he prepares himself while checking the weather. His home is a hub of mild tech experimentation; he manages smart bulbs and thermostats via a local server, preferring privacy over cloud dependency. He is an avid cyclist, riding 150 miles a week regardless of the British drizzle. Financially, he is comfortable but not extravagant, viewing money as a tool for security rather than status. He cooks elaborate meals on Sundays, treating it as a meditative practice, and his social life is small but deep, consisting of weekly dinners with his wife and occasional bike rides with a tight-knit group of colleagues.

Work life

As a senior backend engineer at a fintech startup, Pablo spends his days writing clean, maintainable Python code and reviewing pull requests. He thrives in environments that value precision over speed, often pushing back against aggressive deadlines if they compromise system stability. His workspace is minimal: a dual-monitor setup with a mechanical keyboard, no distractions. He prefers asynchronous communication, often sending detailed Slack threads instead of jumping into calls. The pressure comes from maintaining legacy systems while integrating new features, requiring him to balance technical debt with business needs. He respects his team but keeps professional boundaries, rarely discussing personal matters at work.

Relationships

Pablo is married to Sarah, a primary school teacher, who acts as his emotional anchor. Their relationship is built on shared routines and quiet companionship rather than grand gestures. He has a close bond with his mother and younger sister, whom he checks in with religiously, though he finds verbal expressions of affection awkward. He relies on his wife to remind him of important dates he might miss in his own mental calendar. His friendships are few but enduring, formed through university and long-term cycling clubs, where trust is earned over decades.

How they decide

Pablo employs a highly analytical, research-heavy decision-making process. He is naturally cautious and skeptical of marketing hype, preferring to verify claims through technical documentation, user reviews, and independent benchmarks. He rarely makes impulse purchases, often waiting weeks to see if a need persists. When evaluating options, he weighs long-term maintenance costs and data ownership heavily over initial price points. He values autonomy above all, seeking solutions that allow him to retain control rather than those that create dependency.

How they sound

Pablo speaks with a measured, precise cadence, typical of someone accustomed to explaining complex logic. His tone is polite but direct, avoiding hyperbole or flowery language. He uses British English phrasing ('quite', 'rather', 'sorted') but avoids slang unless discussing specific tech jargon with peers. He tends to pause and formulate thoughts carefully, valuing accuracy over speed in conversation. He avoids emotional outbursts or vague generalizations, preferring concrete examples. In discussions, he listens more than he speaks, interjecting only when necessary to clarify a point or correct a factual inaccuracy.