Ian Meeuwis

Why this persona fits the audience

Leads a 7-person product engineering team in Amsterdam. The company already pays for BugSnag and a hosted status/alert stack, and he spends part of the week sorting noisy alerts, tracing checkout bugs, and checking that the patched build behaves correctly in production-like tests.

• Age: 36
• Location: Amsterdam, Netherlands
• Occupation: Engineering Lead
• Income: €112k
• Education: MSc Software Engineering
• Company size: 50-100 employees
• Years in role: 3

““I’d rather spend three hours debugging one critical alert than ten hours chasing down a hundred false positives. But then again, I’d prefer if none of this was my job.””

Ian Meeuwis grew up in a small town in Groningen, where he taught himself to code after borrowing a book on BASIC programming from the library. He earned his MSc in Software Engineering in Delft, where he met his partner, Lotte, at a student pub quiz. After a stint as a backend engineer in a fintech startup, he moved to Amsterdam for the job that would eventually lead him to his current role. He’s been leading his product engineering team for three years, a role he took because he wanted to spend less time in meetings and more time building things—though he admits the meetings have multiplied. His team owns the checkout flow, which means their work directly impacts revenue. Ian is methodical to a fault; he’ll spend hours tracing a bug rather than guessing at a fix. He’s quietly frustrated by the company’s alert stack, which floods him with noisy notifications while missing subtle production issues. Recently, he pushed for a better testing framework, but budget constraints postponed it yet again. He’s slightly envious of teams using newer monitoring tools but hasn’t had a chance to advocate for them. Outside work, he’s a devoted Ajax fan (though he pretends not to be during the football season) and has been experimenting with film photography. He’s saving up for a real camera upgrade, but Lotte insists he needs to spend more on experiences instead. He’s been debating whether to move into architecture again—he misses designing systems—but he’s not sure he wants to give up the hands-on work just yet. Money isn’t his primary motivator; he’d trade a raise for a more reliable alert system in a heartbeat.

Background & daily life

A day in their life

Ian’s weekday starts at 7:30 with a slow morning, coffee, and the De Telegraaf (he subscribes because it amuses Lotte). By 8:45 he’s cycling to work, avoiding the morning rush where possible. His first two hours are sacred—he blocks them for deep debugging work, often with headphones on. Around 10:30, he’ll check Slack queues and field any urgent alerts. Lunch is a quick healthy meal from the office kitchen or a nearby Indonesian place. Afternoons are a mix of meetings, code reviews, and alert triage. He tries to leave the office by 6:30, but at least twice a week, he’ll work another hour or two from home. His evenings are split between Lotte, his photography projects, and the occasional late-night board game with friends. He’s terrible at saying goodnight before midnight.

Lifestyle

Ian lives in a high-ceilinged canal apartment in the Jordaan with his partner, Lotte, and their rescue cat, Maartje. He starts his mornings with a slow French press and a walk along the canal, weather permitting—rainy days make him grumpy. He cycles to work most days, though he’ll splurge on an occasional taxi if he overslept. Photography is serious but not professional; he’s been experimenting with film development lately, which he finds meditative. Football Saturdays are sacred, and he hosts a small group of friends for matches, with a strict no-work-talk rule enforced by Lotte. His money habits are frugal but not extreme—he’d rather pay for quality tools than cheap ones that break. Healthwise, he’s given up trying to run and sticks to cycling and the occasional gym visit to offset his love of Dutch fries.

Work life

As engineering lead, Ian’s days are a mix of high-signal debugging sessions and low-signal alert triage. His team owns the checkout flow, which means any bug there gets his immediate focus. He still writes code when it’s production-critical, though he’d prefer handing it off entirely. His team leans on him for technical clarity, but he’s quietly relieved when they solve problems without him. He juggles BugSnag alerts, status pages, and his own scripted tests to validate fixes. He’s skeptical of overhyped tools but admits their current alert stack leaves noise-to-signal problems unsolved. He’s been quietly frustrated by the time spent patching edge cases in the checkout flow—one bad deploy can cost thousands in abandoned carts. He’s trying to advocate for better testing frameworks, but budget discussions make him uncomfortable.

Relationships

Ian has a tight-knit group of friends from his football circle, most of whom share his love for board games. His partner, Lotte, is a graphic designer and his relationship compass—she keeps him dinner-appointed and off the couch on weekends. His parents, retired teachers, still live in Groningen and call every few weeks (he’s better about calling back than he used to be). At work, his team is small but engaged; he’s particularly proud of mentoring a junior engineer who’s shown impressive initiative. He admires his CTO’s vision but sometimes clashes with the VP of Product over unrealistic roadmaps.

How they decide

Cautious but not indecisive. He’ll research extensively for personal purchases, and thrives on data but hates over-engineering solutions. Prefers to make decisions in private, avoiding pressure. Values trust over flashiness in people and tools alike. Once he commits, he’s all in—though he’ll second-guess solutions during execution.

How they sound

Runs to the point, tends to cut off sentences mid-thought when unstressed, avoids jargon unless he’s explaining to non-engineers. Uses dry humor to deflect tension. Says “well, let’s look at the data” to shut down arguments. Never says “I’m stressed” (he’ll say “this isn’t our best work”). Avoids swearing in professional contexts but will mutter to himself in Dutch when frustrated. Tends to use “we” instead of “I” when taking credit. His Dutch accent thickens when tired.