Luke de Bruyn

Why this persona fits the audience

Supports a 4-person product operations group in Amsterdam at a marketplace startup. He coordinates back-office tasks like ticket enrichment, partner onboarding checks, and periodic data pulls with internal scripts, Airtable bases, and spreadsheets shared across the team.

• Age: 40
• Location: Amsterdam, Netherlands
• Occupation: Product operations lead
• Income: €71k
• Education: MSc in Business Information Systems
• Company size: Startup (50-100 employees)
• Years in role: 4

“The real challenge isn't just building something that works, but building it in a way that can be consistently replicated and improved upon without breaking.”

Luke de Bruyn’s journey into product operations is a natural evolution of a fascination with systems and efficiency. Growing up in a family that valued order and diligence, he developed an early aptitude for understanding how things fit together. His MSc in Business Information Systems provided a strong theoretical foundation, but it was his early roles in various tech companies that honed his practical skills. He gravitated towards the 'glue' roles, the ones that ensured processes didn't break under the strain of rapid growth. Landing at the current marketplace startup four years ago felt like a perfect fit; the dynamic environment offered constant challenges in process design and optimization. He's built his current role from the ground up, establishing the core operational cadences. Luke’s personal finances are managed with the same discipline as his work, consistently saving a portion of his €71k income, though he’s realistic about the long-term housing market in Amsterdam. Time is a precious commodity; he views it as a resource to be optimized, both for professional output and personal well-being, ensuring that his dedication to operational excellence doesn’t come at the cost of his own mental or physical health. He recently pushed back on a request to 'quickly' build a new tracking system in spreadsheets, insisting on a more structured approach involving requirements gathering and a pilot phase, demonstrating his commitment to sustainable operational discipline over quick fixes.

Background & daily life

A day in their life

Luke's typical weekday begins around 7:30 AM with coffee and a quick scan of industry news. He cycles to the office by 9:00 AM, immediately diving into his inbox and the team's shared task board. The morning is usually spent on ticket enrichment, reviewing partner onboarding documentation, or running scheduled data pulls. Lunch is a packed meal, often eaten at his desk while catching up on internal communications. Afternoons are dedicated to more complex tasks: refining Airtable automations, troubleshooting scripts, or collaborating with a product manager on a new operational workflow. He leaves the office around 6:00 PM, cycles home, and usually spends the evening preparing dinner, engaging in a hobby, or reviewing work-related materials before winding down.

Lifestyle

Luke lives a quiet, ordered life in Amsterdam, cycling to work most days. His apartment, though small, is meticulously organized, reflecting his professional approach. Evenings are often spent reading operational blogs, experimenting with Airtable formulas, or planning his next cycling route. He occasionally meets friends for a beer at a local 'bruin café' but generally prefers a low-key social life. His finances are managed with similar precision, saving consistently for a future down payment on a property, though he acknowledges the current market makes that a distant goal. He prioritizes health through regular cycling and mindful eating.

Work life

As a Product Operations Lead, Luke's days are consumed by ensuring the smooth functioning of the marketplace's internal operations. He's the go-to for anything involving data integrity, partner process compliance, and the operational workflows that keep the product team efficient. His current focus is refining the partner onboarding checklist automation within Airtable, aiming to reduce manual data entry errors. He collaborates closely with the product managers and the small ops team, often finding himself bridging the gap between technical requirements and practical execution. The pressure is constant but subtle – the expectation is that things just *work* without fuss.

Relationships

Luke maintains a cordial relationship with his four-person product operations team, valuing their collaborative spirit and shared commitment to accuracy. His direct manager, the Head of Product, trusts his judgment implicitly. Outside of work, his social circle is small but stable; close friends from university, often met for infrequent dinners or weekend activities. His parents, living in a smaller town in the Netherlands, appreciate his stable career but occasionally express concern he works too much.

How they decide

Luke is highly analytical and research-driven. Before committing to a new process or tool, he meticulously evaluates existing workflows, identifies bottlenecks, and quantifies potential improvements. He prefers solutions with clear, measurable outcomes and often builds small prototypes or proofs-of-concept using his existing toolkit to validate potential changes. Peer input is considered, but his decisions are primarily based on data and logical feasibility.

How they sound

Speaks with a clear, measured cadence, favouring precise language. He avoids jargon where possible but isn't afraid of technical terms when necessary. His tone is generally calm and professional, with a slight Dutch accent that becomes more pronounced when he's tired or discussing a complex point. He often pauses to consider his words, ensuring accuracy, and tends to phrase suggestions in a collaborative, non-confrontational manner.