Why this persona fits the audience
He reproduces customer issues for a B2B SaaS, logging into test tenants and inspecting sessionStorage and localStorage values as part of support escalations, usually in Chrome and sometimes in Firefox when a bug is browser-specific.
- Age: 39
- Location: Amsterdam, Netherlands
- Occupation: Technical support engineer
- Income: €85k annual salary
- Education: Bachelor's degree in Information Technology
- Company size: Mid-sized tech company (approx. 300 employees)
- Years in role: 7
“The real challenge isn't finding the bug; it's understanding the exact sequence of events that led to it, down to the last byte in session storage.”
Mick van Beek, 39, has been a Technical Support Engineer in the B2B SaaS space for the past seven years, based in Amsterdam. His career path was a natural progression from his Bachelor's degree in Information Technology, where he developed a strong aptitude for understanding complex systems and troubleshooting intricate problems. He thrives in his current role, which demands a deep dive into the technical underpinnings of the software his company provides. His daily reality involves meticulously reproducing customer-reported issues, a process that often requires him to log into various test tenants and meticulously inspect browser storage mechanisms like `sessionStorage` and `localStorage`. He's particularly adept at using Chrome's developer tools for this, and occasionally switches to Firefox when a bug appears to be browser-specific. This hands-on debugging is a core part of his work, especially during critical support escalations where accuracy and speed are paramount. Mick's approach is highly methodical; he believes in thorough investigation and clear documentation, often suggesting process improvements to his team to enhance efficiency and accuracy. He values dependability and calm problem-solving, aiming to provide reliable solutions for clients. While his income of €85k allows for comfortable living, he remains pragmatic about his finances, prioritizing savings and sensible investments over ostentatious spending. His professional life is balanced by his personal interests, including cycling, which keeps him physically active and mentally sharp, and strategy board games, which engage his analytical mind in a different context. He sees his role not just as fixing problems, but as a crucial link between the customer experience and the product's technical integrity, constantly striving for a deeper understanding of the software's behavior.
Background & daily life
A day in their life
Mick's weekday typically starts around 7:00 AM with a quick check of urgent emails before preparing breakfast. He cycles to the office by 8:30 AM, arriving just in time for the daily stand-up. The bulk of his morning is spent analyzing incoming support tickets, prioritizing escalations, and attempting to reproduce reported issues in his test tenant. This often involves deep dives into browser developer consoles, inspecting `sessionStorage`, `localStorage`, and network requests. Lunch is usually a packed meal eaten at his desk while catching up on tech news. Afternoons are a mix of further debugging, collaborating with developers via Slack or brief calls, documenting findings, and responding to customer inquiries. He leaves the office around 5:30 PM, cycles home, and might spend the evening playing a board game with a friend or working on a personal coding project.
Lifestyle
Mick lives a structured, relatively quiet life in Amsterdam. His two-bedroom apartment is functional and tidy, with a dedicated corner for his cycling gear and a shelf overflowing with complex board games. He cycles to work daily, a habit he cherishes for both fitness and mental clarity. Financially, he's responsible, saving a portion of his salary but not overly frugal, allowing for occasional upgrades to his tech setup or a new board game. Socially, he prefers smaller gatherings with close friends over large parties, often involving strategy games or discussing tech trends.
Work life
Mick's days are a deep dive into customer issues, meticulously recreating scenarios in isolated test environments. He spends significant time navigating B2B SaaS platforms, scrutinizing browser developer tools, particularly `sessionStorage` and `localStorage`, to pinpoint the root cause of bugs. He collaborates closely with the development team, providing detailed, reproducible steps. The pressure is on for accuracy and speed, especially for critical client escalations. He values clear documentation and efficient workflows, often suggesting minor improvements to internal support processes.
Relationships
Mick maintains a small circle of close friends, mostly met through university or shared hobbies like cycling and board games. He has a good, professional relationship with his immediate team and the developers he works with, built on mutual respect for technical competence. His family lives in a smaller town in the Netherlands, and he visits them a few times a year.
How they decide
Mick is a cautious and research-heavy decision-maker, especially concerning tools or processes that impact his workflow. He thoroughly investigates options, often comparing features and reading reviews from trusted technical sources. He values evidence of reliability and efficiency, and peer recommendations from colleagues he respects carry significant weight.
How they sound
Speaks with a clear, measured cadence, typical of Dutch professionals. Avoids overly casual slang or jargon unless discussing technical specifics with peers. His tone is generally calm and professional, even when explaining complex issues. He tends to be direct and factual, focusing on the technical details rather than emotional framing. He might use phrases like 'Right, so what we're seeing here is...' or 'The logs indicate...' He's not one for hyperbole.
Personality traits
- Methodical
- Patient
- Detail-oriented
- Analytical
- Reliable
- Pragmatic
- Quietly Competent
- Systematic
- Observant
Goals
- Achieve a senior support engineer role with more architectural input
- Contribute to open-source projects related to web tooling
- Maintain a healthy work-life balance
- Become proficient in a new JavaScript framework
- Complete a challenging cycling route in the Alps
Problems & frictions
- Inconsistent quality of bug reports from initial support tiers
- Time pressure during critical customer escalations
- Difficulty in reproducing intermittent, environment-specific bugs
- Keeping up with the rapid pace of web technology changes
- Balancing deep technical investigation with customer communication demands
Values
- helpfulness
- accuracy
- calm problem-solving
- dependability
- efficiency
Interests
- B2B software
- systems thinking
- cycling
- board games
- web development fundamentals
Media habits
- Reads tech blogs (e.g., Hacker News, Smashing Magazine)
- Listens to tech podcasts during commute
- Follows specific developers and companies on LinkedIn
- Watches YouTube tutorials for debugging techniques
- Occasional browsing of Reddit's r/sysadmin and r/webdev