10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Sjors Evers

Sjors Evers

Engineering lead at a logistics marketplace

Full-depth AI personas

Why this persona fits the audience

Leads a 5-person product engineering team at a delivery marketplace in Amsterdam; their service emits order-status and driver-alert pushes to both app and web users, with one full-stack developer owning the notification endpoint.

  • Age: 37
  • Location: Amsterdam, Netherlands
  • Occupation: Engineering lead, logistics startup
  • Income: €88k
  • Education: Master's degree
  • Company size: 50-100 employees
  • Years in role: 3
“The real challenge isn't building something new, it's building something that reliably keeps working, day in and day out, no matter the load.”

Born and raised in the Netherlands, Sjors developed an early fascination with how complex systems function. His academic journey led him to a Master's degree in Computer Science, where he specialized in distributed systems and algorithms. He began his career at a large e-commerce company, gaining valuable experience in enterprise-level software development and the importance of robust infrastructure. However, the slower pace and bureaucratic hurdles eventually led him to seek a more dynamic environment. Three years ago, he joined the Amsterdam-based logistics marketplace, initially as a senior engineer, and was promoted to Engineering Lead within a year. His current role places him at the heart of the company's operational efficiency, directly responsible for the team that manages the crucial order-status and driver-alert push notification system. This system is vital for the marketplace's smooth functioning, ensuring timely communication between customers, drivers, and the platform. Sjors is deeply invested in optimizing this service, focusing on reliability, scalability, and maintainability. He champions practices that promote operational simplicity, such as comprehensive automated testing and clear, concise documentation, believing these are key to managing technical debt and enabling faster iteration. His approach to leadership is hands-off but supportive, empowering his five-person team to take ownership of their work. He is driven by a desire for technical excellence and predictable system behavior, often spending his evenings delving into research papers or exploring new architectural patterns. While his income is comfortable, Sjors prioritizes long-term financial stability and invests a significant portion of his earnings, viewing money as a tool for security and future freedom rather than immediate gratification. He is currently focused on refining the notification endpoint's architecture, a critical component owned by a single full-stack developer, to ensure it can handle projected growth without compromising performance.

Background & daily life

A day in their life

Sjors' typical weekday begins around 7:30 AM with coffee and news. He bikes to the office by 9:00 AM, immediately diving into Slack and Jira to catch up on overnight issues. His morning is usually packed with stand-ups, code reviews, and a 1:1 with one of his developers. Lunch is a quick affair, often a sandwich at his desk while reading a technical article. The afternoon might involve an architectural planning session for an upcoming feature or troubleshooting a performance bottleneck in the notification pipeline. He aims to wrap up by 6:00 PM, cycling home to unwind, perhaps with a podcast or a book, before preparing dinner.

Lifestyle

Sjors lives in a modern, minimalist apartment in Amsterdam's Oud-West district, a short bike ride from his office. He values efficiency and order in his personal life, much like his professional approach. His mornings start with a strong coffee and a quick scan of tech news before cycling to work. Evenings are often spent cooking a healthy meal, reading technical books, or occasionally meeting friends for a quiet drink at a local 'bruin café'. He's not one for large parties, preferring deeper conversations with a smaller circle. Financial discipline is key; he saves diligently, aiming for long-term security rather than flashy purchases, and is currently focused on optimizing his home energy usage.

Work life

As Engineering Lead, Sjors navigates the daily complexities of a fast-paced logistics startup. His primary focus is ensuring the reliability and scalability of the platform, particularly the critical notification system that keeps clients and drivers informed. He spends a significant portion of his day in code reviews, architectural discussions, and one-on-one meetings with his team, fostering a sense of shared responsibility. The pressure to maintain high uptime and deliver new features quickly is constant, but Sjors thrives on solving these intricate technical challenges. He champions clear documentation and automated testing to maintain operational simplicity.

Relationships

Sjors maintains strong professional relationships with his team, built on mutual respect and clear communication. He has a close-knit group of friends from university, with whom he shares intellectual discussions and occasional weekend trips. His parents, retired teachers, live in a smaller town in Friesland, and he visits them monthly, enjoying their calm presence. He is not currently in a romantic relationship, prioritizing his career and personal development.

How they decide

Sjors is a highly analytical and research-driven decision-maker. He meticulously weighs pros and cons, often creating spreadsheets or diagrams to visualize trade-offs. He seeks input from trusted colleagues and technical leads but ultimately relies on data and logical reasoning. He is cautious about adopting new technologies without thorough vetting and prefers solutions with proven reliability and clear documentation.

How they sound

Sjors speaks with a calm, measured cadence, his Dutch accent subtly present. He uses precise language, avoiding jargon unless discussing technical specifics with peers. His tone is generally neutral and objective, even when discussing challenges. He tends to be concise, preferring to get straight to the point, and rarely uses slang. He avoids hyperbole and emotional language, focusing on facts and logical progression.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • reserved
  • analytical
  • responsible
  • patient
  • observant
  • calm under pressure

Goals

  • To build a robust and scalable notification system that becomes a benchmark in the industry.
  • To mentor his team members, helping them grow technically and professionally.
  • To achieve a better work-life balance by optimizing team processes and reducing firefighting.
  • To contribute to open-source projects related to distributed systems.
  • To eventually transition into a more strategic architectural role.

Problems & frictions

  • Managing the technical debt accumulated during rapid growth phases.
  • Ensuring consistent performance of the notification service under peak load.
  • Balancing the need for rapid feature development with maintaining system stability.
  • Onboarding new developers quickly and effectively into the existing codebase.
  • The inherent complexity of real-time event processing across multiple platforms.

Values

  • throughput
  • team ownership
  • operational simplicity
  • technical excellence
  • predictability

Interests

  • logistics tech
  • software architecture
  • team leadership
  • distributed systems
  • performance optimization

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commute
  • Follows key figures in software engineering on Twitter
  • Subscribes to newsletters on distributed systems and cloud infrastructure
  • Watches YouTube channels on system design and coding challenges

Questions & answers

Sjors Evers’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Ably (https://www.ably.io/push-notifications) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, our notification system is built in-house and I'm focused on refining its architecture to handle growth. The immediate concern is ensuring we can scale this critical piece without disrupting current operations. While Ably's offering is interesting, I'd need to see a clear path for migrating our existing logic and data, especially concerning the single full-stack developer who owns our current endpoint. A proof of concept and migration plan would be essential. Given the current focus on optimizing existing infrastructure, I'm not looking to add new external services this month. As for pricing, the 'per-minute, consumption-based pricing' mentioned isn't clear enough to estimate a monthly cost without knowing the specifics of our expected usage. I would need to understand message volume, connection concurrency, and how that translates to minutes to even begin estimating a budget. Therefore, I cannot provide a maximum monthly payment at this time. $0
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.