Why this persona fits the audience
He is a product engineer at a 60-person fintech in Amsterdam and uses Graphite to organize stacked changes, then does final pull-request review in GitHub on a Mac. He regularly works across two company orgs and one personal project, so his review context is spread across multiple accounts.
- Age: 30
- Location: Amsterdam, Netherlands
- Occupation: Product Engineer
- Income: EUR 88k-118k/year
- Education: MSc Software Engineering
- Company size: 60-person
- Years in role: 5
“The real challenge isn't writing the code, it's ensuring it stays maintainable and understandable for everyone who has to touch it later.”
Tobias van Dongen grew up in a small town in North Holland, developing an early fascination with how things work. This curiosity led him to pursue a Master's degree in Software Engineering at TU Delft. After graduating, he joined a burgeoning fintech startup in Amsterdam, drawn by the sector's innovation and the opportunity to build systems from the ground up. He's been a Product Engineer there for five years, steadily rising in responsibility. He lives alone in a rented apartment, a space he meticulously organizes to reflect his appreciation for order. His income allows for comfortable living, with a significant portion allocated to savings and quality investments in his hobbies, like his prized collection of mechanical keyboard parts and his high-performance road bike. Tobias is currently focused on architecting a new microservice for his company's core lending platform, a task that demands careful consideration of scalability, security, and regulatory compliance. He recently decided to invest more time into optimizing his personal development workflow after realizing the overhead from managing multiple Git accounts was becoming a significant drag on his personal project's progress. He uses Graphite daily to keep his work organized, but finds the final review process in GitHub, when spread across different contexts, to be clunky and time-consuming. He values his autonomy and the intellectual challenge his work provides, but is increasingly aware of the time commitment required to stay at the forefront of fintech engineering.
Background & daily life
A day in their life
Tobias's weekday typically starts around 7:30 AM with a carefully brewed coffee and a quick scan of Hacker News and his primary work communication channels. He bikes to the office by 9 AM, grabbing another coffee on the way. His morning is usually dedicated to focused coding, tackling tickets from the backlog or working on assigned features. After a healthy lunch, often with colleagues discussing tech or weekend plans, the afternoon is a mix of code reviews, planning meetings with product, and sometimes pair programming. He uses Graphite to manage his stacked changes throughout the day, preparing them for submission. He leaves the office around 6 PM, bikes home, and might spend an hour on his personal project or reading tech articles before dinner. He tries to disconnect by 9 PM.
Lifestyle
Tobias lives in a modern, well-organized apartment in Amsterdam's Jordaan district. He bikes everywhere, even for groceries, and his weekends often involve longer cycling trips outside the city. He takes his coffee ritual seriously, grinding beans daily and experimenting with pour-over methods. Socially, he's selective, preferring small gatherings with close friends over large parties. He's financially responsible, saving diligently for future investments and travel, but enjoys investing in quality tools that enhance his work or hobbies, like his custom mechanical keyboard or high-end coffee maker. He prioritizes health through regular exercise and a balanced diet.
Work life
As a Product Engineer at a fast-growing fintech, Tobias navigates a dynamic environment. His days are a blend of coding, code reviews, and cross-functional meetings. He's deeply involved in refining the platform's core features, often working with product managers and designers. The pressure to deliver reliable, scalable solutions is constant. He collaborates closely with a small, talented engineering team, fostering a culture of mutual respect and constructive feedback. His primary challenge is context-switching between his main company's codebase, a related internal project, and his personal open-source contributions, all requiring different Git accounts and review processes.
Relationships
Tobias maintains strong relationships with his immediate family, who live in the Netherlands. His core social circle consists of about five close friends, many from university, with whom he shares interests like cycling and tech. He has a good rapport with his engineering team, built on shared technical challenges and mutual respect, but he tends to keep work relationships professional. He values candid feedback from peers he trusts.
How they decide
Tobias approaches decisions methodically. He gathers information, considers the pros and cons, and often seeks out objective data or benchmarks. He's influenced by proven solutions and peer recommendations within his trusted network, but ultimately relies on his own analysis. He's willing to try new things if the rationale is sound, but he's not impulsive and dislikes unnecessary complexity.
How they sound
Speaks with a measured, clear cadence. Uses precise technical language when discussing work, but can switch to more casual Dutch phrasing with friends. Avoids hyperbole and buzzwords. His tone is generally calm and rational, even when discussing challenges. He might use 'well' or 'actually' to preface a point he's clarified. Prefers direct, unambiguous communication.
Personality traits
- detail-oriented
- methodical
- resourceful
- analytical
- patient
- skeptical of hype
- independent
- observant
Goals
- Achieve senior engineering leadership within his company
- Contribute significantly to a popular open-source project
- Maintain a healthy work-life balance
- Become a recognized expert in distributed systems
- Complete a challenging multi-day cycling tour
Problems & frictions
- Managing fragmented code review contexts across multiple Git accounts and projects.
- Information overload from various communication channels and task queues.
- Balancing feature development velocity with the need for robust, long-term architectural decisions.
- Onboarding new team members effectively in a complex technical environment.
- The constant need to stay updated with rapidly evolving fintech regulations and technologies.
Values
- efficiency
- clean systems
- team trust
- continuous improvement
- pragmatism
Interests
- cycling
- fintech
- mechanical keyboards
- specialty coffee
- open-source contributions
Media habits
- Hacker News
- Twitter for tech news and opinions
- YouTube for technical deep dives and reviews
- Substack newsletters on software architecture
- Developer podcasts during commutes