Omar Jansen

Why this persona fits the audience

Splits time between release notes, bug reports, and UI documentation for a software team and frequently edits screenshots for those docs. Usually converts PNG, JPEG, and WebP files without installing extra software on a locked-down corporate laptop, leaning on free browser utilities and native OS tools.

• Age: 32
• Location: Amsterdam, Netherlands
• Occupation: Technical product manager
• Income: €72k/year
• Education: MSc Computer Science
• Company size: Mid-sized SaaS startup (150-300 employees)
• Years in role: 4

“Efficiency isn't about doing more things faster; it's about removing the friction so you can focus on what actually matters.”

Omar Jansen, 32, resides in the vibrant yet historic Oud-West district of Amsterdam, living a life defined by the intersection of technical rigor and practical necessity. With an MSc in Computer Science from Delft University of Technology, he transitioned from pure development to a hybrid role as a Technical Product Manager four years ago. This pivot was driven by a desire to bridge the communication gap between code and business requirements, a niche where his natural inclination for clarity and organization thrives. Currently earning €72,000 annually, Omar operates within a mid-sized SaaS startup where agility is prized but security protocols are ironclad. His daily reality is a unique paradox: he manages high-level product strategy while simultaneously performing low-level, repetitive tasks like image manipulation for documentation. Because his corporate laptop is locked down to prevent unauthorized software installations, he has developed a robust repertoire of browser-based solutions and native OS shortcuts to handle image conversions and edits on the fly. He frequently navigates the friction of converting PNGs, JPEGs, and WebP files without compromising data privacy, relying on his knowledge of web technologies to find temporary, secure fixes. Omar's approach to life and work is deeply pragmatic; he values self-sufficiency above all else, preferring to build his own workflows rather than wait for corporate procurement to approve a new tool. While he is open to new technologies that genuinely solve problems, he remains skeptical of solutions that introduce complexity or security risks. His recent decisions reflect this mindset: he chose to automate parts of his documentation pipeline using simple scripts rather than purchasing expensive enterprise suites. Despite the pressures of a fast-paced tech environment, Omar maintains a steady pace, prioritizing mental clarity and long-term career growth over short-term wins. He is a man who believes that the best tools are often the ones you already have, refined through experience and disciplined usage.

Background & daily life

A day in their life

Omar wakes up at 6:15 AM, brewing coffee while checking emails on his phone before getting out of bed. By 7:00 AM, he is cycling through the morning traffic to his office in Amsterdam Zuid, listening to a tech podcast. At work, his morning is consumed by a stand-up meeting followed by deep-focus time spent writing detailed release notes. Around 10:30 AM, he hits a recurring bottleneck: a stakeholder needs a cropped, resized, and format-converted version of a UI mockup immediately. Instead of asking for help or installing a heavy desktop app, he opens a private browser tab to use a lightweight online converter, ensuring no sensitive data leaves his machine. After lunch, he reviews bug reports from the QA team, annotating screenshots and formatting them for the Jira board. The afternoon is reserved for meetings with product designers to clarify feature specifications. He leaves the office at 6:00 PM sharp, cycling home to cook dinner, read a non-fiction book, and unwind with his partner, avoiding screens after 9:00 PM to ensure a good night's sleep.

Lifestyle

Omar lives in a renovated canal-side apartment in Oud-West, Amsterdam, characterized by high ceilings and minimalistic clutter. His routine is structured around cycling to work regardless of weather, a habit that keeps him physically active but exposes him to the elements. He is not a night owl; he prefers to finish work by 6 PM to manage his household chores and cook dinner from scratch using fresh market ingredients. Financially, he is conservative, prioritizing savings over luxury goods, often choosing second-hand furniture or repairing items rather than replacing them. Socially, he maintains a small circle of close friends, preferring one-on-one coffee chats or quiet dinners over large parties, valuing deep conversation over superficial networking.

Work life

As a Technical Product Manager bridging the gap between engineering and business, Omar spends roughly 40% of his week documenting features and managing release notes. A significant portion of his day involves creating visual evidence for bug reports, which requires constant screen capturing and editing. Due to strict IT policies preventing local software installation, he relies heavily on browser-based utilities and built-in OS tools to resize images or convert formats like WebP to PNG for internal wikis. He navigates a pressure cooker environment where clear communication is paramount, often mediating between frustrated developers and impatient stakeholders. His workspace is a dual-monitor setup with a mechanical keyboard, and he values tools that integrate seamlessly into his existing workflow without requiring context switching.

Relationships

Omar is married to Elise, a graphic designer who understands his need for visual precision but often finds his pragmatism overly rigid. They share responsibilities for home maintenance and occasional weekend trips to the countryside. His primary professional influence comes from his CTO, whose emphasis on 'move fast but don't break things' mirrors Omar's own management style. He has a few childhood friends he sees monthly for bike rides, providing a grounding connection outside the tech bubble. He rarely engages in community volunteering due to time constraints, focusing his energy instead on mentoring junior developers within his company.

How they decide

Omar is a cautious, research-heavy decision-maker who prioritizes security and compatibility over novelty. He typically validates any new tool against strict criteria: does it run locally? Is it open source? Does it have a transparent privacy policy? He avoids impulsive purchases, preferring to test a solution in a sandboxed environment or via a limited trial before committing. Peer recommendations from trusted technical colleagues carry more weight than advertising, and he is skeptical of tools that promise efficiency gains through complex integrations. He often defaults to 'if it ain't broke, don't fix it' unless a friction point becomes unmanageable.

How they sound

Omar speaks with a calm, measured cadence, using precise terminology without unnecessary jargon. His Dutch accent is present but softened by years of international collaboration; he switches effortlessly to English when discussing technical specs. He avoids hyperbole, emotional language, or sales-pitch phrasing, preferring direct statements like 'the latency is unacceptable' or 'this workflow is inefficient.' He rarely interrupts others but will firmly correct misinformation if it pertains to technical accuracy. In casual settings, he uses dry humor and tends to listen more than he speaks, only offering opinions when asked directly.