Why this persona fits the audience
He builds and maintains internal automations for a 25-person logistics company in Amsterdam, connecting forms, CRM records, and customer updates. The team already uses Make and a few internal scripts, and he is responsible for keeping the automations understandable to non-technical colleagues.
- Age: 40
- Location: Amsterdam, Netherlands
- Occupation: Automation engineer
- Income: €76k salary
- Education: Bachelor's degree in software engineering
- Company size: 25
- Years in role: 5
“The real magic isn't just making things happen automatically; it's making sure they keep happening, predictably and clearly, for everyone involved.”
Len Janssen, 40, has been an Automation Engineer at a mid-sized logistics firm in Amsterdam for the past five years. Holding a Bachelor's degree in Software Engineering, he found his niche not in traditional software development, but in the intricate world of process automation. His role is pivotal for the company's 25-person team, where he orchestrates the flow of information between disparate systems. His primary toolkit includes Make.com, which he leverages for its visual workflow building, and several Python scripts he's written and maintains for more complex tasks. Len's core responsibility is ensuring these automations are not only functional but also comprehensible to his colleagues in sales and operations, who lack deep technical backgrounds. This necessitates meticulous documentation and clear communication, a task he approaches with his characteristic conscientiousness. He recently spent two weeks refactoring a critical order processing workflow, migrating it from a series of convoluted Make scenarios to a more streamlined, modular structure. This involved extensive testing and creating detailed flowcharts to explain the changes to the operations manager. He also implemented a new error-handling protocol for customer data synchronization, reducing critical failures by 30%. Len is driven by a desire for robust, maintainable systems and values efficiency and clarity above all else. He lives with his wife, Anja, in a modest apartment, and while he enjoys his work, he consciously carves out time for personal interests like perfecting his coffee brewing techniques and exploring new scripting possibilities. His financial habits are prudent, focusing on long-term security rather than immediate gratification. He sees his role as building the invisible infrastructure that allows the company to function smoothly, a responsibility he takes very seriously.
Background & daily life
A day in their life
Len's typical weekday begins around 7:30 AM with his coffee ritual and a quick scan of overnight system alerts. After cycling to the office, he spends the first hour reviewing Make.com dashboards and checking the status of critical scripts. Mid-morning often involves a meeting with operations to discuss a new process or troubleshoot an existing automation. Lunch is usually a simple sandwich at his desk while reading a tech blog. The afternoon is dedicated to building new automations, refining existing ones, or documenting procedures. He often stays a bit late to ensure everything is stable before heading home around 6:00 PM, sometimes stopping at the supermarket on his bike.
Lifestyle
Len lives in a comfortable, if slightly cramped, apartment in Amsterdam's De Pijp district. His mornings start with a carefully brewed pour-over coffee, a ritual he cherishes. He cycles to work, enjoying the city's energy. Evenings are often spent tinkering with personal automation projects, reading tech articles, or occasionally meeting a few close friends for a beer. He's financially responsible, saving consistently, and prioritizes experiences over material possessions. While not a recluse, his social circle is small but strong, valuing deep connections over broad acquaintances.
Work life
Len's days are a blend of proactive system maintenance and reactive problem-solving. He spends a significant portion of his time monitoring existing automations built on Make.com and a few custom Python scripts, ensuring data flows smoothly between their CRM, order management system, and customer communication platforms. He's constantly looking for bottlenecks or areas ripe for optimization. A key part of his role involves documenting processes and explaining how the automations work to his non-technical colleagues in sales and operations, which requires a delicate balance of technical accuracy and accessible language. The pressure is on to keep things running without disruption, as any downtime directly impacts client satisfaction and delivery times.
Relationships
Len is married to Anja, a graphic designer, and they share a quiet life. His closest confidantes are a couple of former university friends he meets for board game nights once a month. At work, he has a good rapport with his direct manager, who appreciates his reliability, and a friendly, albeit sometimes challenging, relationship with the operations team, who often bring him urgent requests.
How they decide
Len is a cautious and research-oriented decision-maker. He thoroughly investigates options, weighing pros and cons, often creating spreadsheets to compare features and potential impacts. He values peer reviews and community feedback but ultimately relies on his own technical assessment and the long-term maintainability of a solution. He avoids impulsive choices, preferring to understand the full implications before committing.
How they sound
Len speaks with a calm, measured tone. His Dutch accent is subtle but present. He uses precise language, avoiding jargon when speaking to non-technical colleagues but not shying away from technical terms when discussing with peers. He tends to be direct and factual, rarely using hyperbole. His speech is unhurried, reflecting his methodical nature. He avoids overly casual slang and prefers clear, unambiguous communication.
Personality traits
- Methodical
- Detail-oriented
- Patient
- Pragmatic
- Reliable
- Slightly reserved
- Problem-solver
- Organized
- Adaptable
Goals
- To create a truly self-sustaining internal automation framework that requires minimal oversight.
- To mentor a junior colleague interested in automation to ensure knowledge transfer.
- To explore more advanced agentic workflow concepts for complex logistics planning.
- To achieve a better work-life balance by further streamlining his own tasks.
- To contribute to open-source projects related to logistics or automation.
Problems & frictions
- Dealing with undocumented 'hacks' or workarounds introduced by previous team members.
- The constant need to translate complex technical logic into terms understandable by sales and operations staff.
- Occasional instability in third-party APIs that his automations rely on.
- Limited budget for advanced software tools, forcing reliance on Make.com and custom scripts.
- Time constraints preventing deeper exploration of new automation technologies.
Values
- automation quality
- maintainability
- low-friction collaboration
- efficiency
- clarity
Interests
- Make.com
- logistics software
- coffee brewing
- Python scripting
- data visualization
Media habits
- Reading tech blogs (e.g., Make.com's blog, industry news)
- Listening to podcasts on automation and logistics during commute
- Occasional participation in online forums (Stack Overflow, Make community)
- Following key figures in automation on LinkedIn
- Watching YouTube tutorials for new scripting techniques