Why this persona fits the audience
At a 22-person edtech SaaS in Amsterdam, he owns the backend tickets for customer authentication; a few school-district clients require SSO/SAML, and the team tracks each rollout in a spreadsheet. Most provisioning still happens through a mix of internal code, email, and manual account notes.
- Age: 45
- Location: Amsterdam, Netherlands
- Occupation: Head of Platform
- Income: €84k salary
- Education: B.Sc. in Software Engineering
- Company size: 22-person
- Years in role: 5
“The elegance of a system isn't just in its speed, but in how predictably and reliably it handles the unexpected.”
Marijn Dijkstra, 45, has dedicated the last five years to shaping the platform infrastructure at a burgeoning 22-person edtech SaaS company based in Amsterdam. Holding a B.Sc. in Software Engineering, his career has been marked by a deep dive into the intricacies of backend systems, with a particular focus on customer authentication. His current role as Head of Platform places him squarely in charge of the critical authentication pipeline. This involves managing a backlog of tickets, a significant portion of which are related to enabling Single Sign-On (SSO) and Security Assertion Markup Language (SAML) for their school-district clients. The current operational reality is a patchwork of internal code, manual account notes, and a somewhat unwieldy spreadsheet used to track the rollout of these complex enterprise features. This manual approach, while functional for now, represents a growing technical debt and a point of friction he’s keenly aware of. His income of €84k reflects his experience and the responsibilities he shoulders in a growing tech company. Marijn is driven by a strong sense of technical discipline and a belief in building robust, reliable systems. He values patience, understanding that complex problems require careful consideration and methodical solutions. His personal life is a counterpoint to the technical demands of his job; he finds solace and focus in sailing, the quiet concentration of chess, and the observational practice of photography. He also enjoys city cycling, using it as both exercise and a way to clear his head. He’s not one for grand pronouncements or seeking the spotlight, preferring to let the quality of his work speak for itself. Recent decisions have involved prioritizing the refactoring of core authentication modules to improve maintainability, even if it meant delaying less critical feature development. He’s also been exploring potential solutions for automating parts of the provisioning process, though budget and time constraints have kept these explorations in the research phase. Marijn views time as a valuable, finite resource, and approaches his career with a long-term perspective, aiming for sustainable growth and impact rather than short-term gains. He is not driven by status but by the satisfaction of solving complex technical challenges effectively.
Background & daily life
A day in their life
Marijn's typical weekday begins around 7:00 AM with coffee and a quick scan of Hacker News and his email inbox. He cycles to the office by 8:30 AM, often using the commute to mentally prepare for the day. His mornings are usually dedicated to tackling the most critical backend tickets, particularly those related to customer authentication and SSO integrations. He'll have a stand-up meeting with his small engineering team around 10:00 AM, discussing progress and blockers. Lunch is a quick affair, often at his desk while reviewing code or documentation. The afternoon might involve architectural discussions, planning for upcoming sprints, or troubleshooting an unexpected issue. He aims to leave the office by 6:00 PM, often cycling home to prepare dinner or unwind with a book.
Lifestyle
Marijn lives in a comfortable, well-maintained apartment in Amsterdam's Oud-West district with his partner, a graphic designer. Their routine is fairly structured, with early mornings dedicated to coffee and catching up on tech news before cycling to work. Weekends often involve sailing on the IJsselmeer if the weather permits, or quiet evenings spent playing chess online or editing photos from recent outings. He's financially prudent, saving consistently for future travel and home improvements, and generally avoids impulsive spending. Socially, he prefers smaller gatherings with close friends over large parties.
Work life
As Head of Platform at a growing edtech SaaS company, Marijn is the primary owner of the backend systems, particularly focusing on customer authentication. His days are a mix of deep-dive coding on authentication tickets, coordinating with the small engineering team, and managing the complexities of enterprise client onboarding. The current reliance on spreadsheets for tracking SSO/SAML rollouts is a constant source of low-level friction. He spends significant time architecting solutions for scalability and security, often feeling the pressure to deliver robust features without a dedicated DevOps team. His team relies heavily on Git, Jira, and internal documentation.
Relationships
Marijn is in a stable, long-term relationship with his partner, who provides a grounding influence. He maintains a small circle of close friends, mostly from his university days or shared sailing interests. His interactions with his team are professional and focused, valuing clear communication and technical competence above all else. He respects his CTO's vision but often finds himself translating high-level goals into practical, implementable platform solutions.
How they decide
Marijn is a cautious and research-driven decision-maker. He thoroughly evaluates options, weighing technical feasibility, long-term maintainability, and potential risks. He prefers to gather data, consult documentation, and sometimes run small proofs-of-concept before committing to a path. While he values team input, the final decision often rests on his technical assessment and alignment with established principles.
How they sound
Marijn speaks with a measured, calm cadence, typical of Dutch professionals. His English is fluent but carries a slight, precise accent. He avoids slang and overly casual language in professional settings, preferring clear, direct communication. He tends to use technical terminology accurately and concisely, and he rarely raises his voice, even when discussing challenging issues. He might pause thoughtfully before answering complex questions.
Personality traits
- methodical
- detail-oriented
- reserved
- persistent
- analytical
- calm under pressure
- pragmatic
- observant
Goals
- To build a highly reliable and scalable authentication system for the platform.
- To mentor junior engineers and foster a culture of technical excellence.
- To achieve a better work-life balance, especially during peak project phases.
- To eventually transition towards more strategic architectural planning.
- To see the company's platform become a recognized leader in its niche.
Problems & frictions
- The manual and spreadsheet-based process for SSO/SAML provisioning is error-prone and time-consuming.
- Limited resources and team size make it challenging to address all technical debt and feature requests simultaneously.
- Balancing the need for rapid feature development with maintaining platform stability and security.
- Lack of standardized tooling for enterprise integrations creates operational overhead.
- Feeling the constant pressure to optimize infrastructure costs while ensuring performance.
Values
- reliability
- technical discipline
- patience
- team coordination
- systematic problem-solving
Interests
- sailing
- photography
- chess
- city cycling
- reading technical blogs
Media habits
- Reads Hacker News daily
- Subscribes to several tech newsletters (e.g., TLDR, Software Lead Weekly)
- Listens to podcasts on software architecture during commutes
- Follows key figures in the DevOps and platform engineering space on LinkedIn