Rayan van den Velde

Why this persona fits the audience

Leads a nine-person product engineering group modernizing a Laravel monolith into more modular services and shared packages. The team keeps GitHub standards, code review rules, and internal modules for permissions, notifications, and reporting so new work stays consistent.

• Age: 41
• Location: Amsterdam, Netherlands
• Occupation: Engineering manager
• Income: €110k-€140k
• Education: MSc Computer Science
• Company size: 50-200 employees
• Years in role: 6

“I don't believe in 'technical debt' - that suggests it's inevitable. What we have is architectural negligence, and that's something we can fix.”

Rayan van den Velde didn't set out to manage a team - he fell into it from technical leadership roles. His career started at a small Delft startup where he built the first versions of what's now the company's core application. The struggles of maintaining that system taught him the importance of modular design, a lesson he now applies daily. At 41, he's the kind of manager who writes documentation, creates migration templates, and still does occasional on-call shifts. His MSc in Computer Science from TU Delft was practically focused, but he wished he'd paid more attention to formal software engineering - now he tries to compensate by absorbing every architectural podcast and conference talk. Currently, he's pushing his team to adopt service-oriented architecture while maintaining compatibility with legacy systems. The biggest challenge isn't technical - it's convincing stakeholders that the time spent on proper abstraction will pay dividends. He's established a culture where engineers rotate between projects to prevent silos, and insists on documentation that would survive if any team member left. Despite his team's growth, he maintains personal involvement in critical components, recently completing a major refactor of the permission system to use Laravel policies. His personal technical hobby is maintaining a small but popular open-source Laravel package for handling European bank transfers, which he developed to scratch his own itch. After hours, you'll find him cycling through Amsterdam's canal ring or rehearsing espresso extraction techniques in their compact kitchen. Rayan's relationship with money is pragmatic - he values stability over flashy status symbols, saving aggressively for potential layoffs while giving to causes he believes in. His biggest professional fear isn't being replaced - it's that his team might become complacent and allow technical quality to slip. He measures success not in products shipped but in systems that endure with minimal maintenance.

Background & daily life

A day in their life

5:30AM: Wake up to his partner's alarm. Quick cat cuddles while deciding if it's cold enough for tights on the bike. 6:15AM: Arrives at De Nieuwe Prins for his morning espresso. 7:00AM: Daily planning in Notion - reviews team metrics and checks deployment status. 7:30AM: First standup. 9:00AM: Deep work on the new API gateway architecture. 11:30AM: Lunchtime coding session - contributing to some open-source Laravel package. 1:00PM: Code review marathon - he's particularly ruthless about SQL injection vulnerabilities. 2:30PM: Sprint planning with product managers (usually ends 15 minutes over time). 4:00PM: 1:1 with a junior developer struggling with testing. 5:30PM: Final standup. 6:00PM: Commute home, stopping at the bicycle repair shop to check on his custom wheel order. 7:00PM: Cooks dinner while his partner tells him about her day. 8:30PM: Settles on the couch to read about new AWS features on his iPad. 10:30PM: Bed, but probably stays up reading until 11:30PM.

Lifestyle

Rayan shares a 19th-century apartment near Amsterdam Centraal with his partner, a UX designer, and two indifferent cats. He commutes by bicycle year-round (with proper layers) and stops at the same specialty coffee shop en route where the barista knows his usual order: espresso with four minutes of hot water swirled in. Weekends alternate between open-source hacking sessions and long cycling trips to nearby polders. Financially conservative, he maximizes employer benefits and donates 2% of his salary to open-source foundations. His social circle consists mostly of tech colleagues and cycling club members, with an occasional video call to family in Eindhoven.

Work life

As an engineering manager at a mid-sized SaaS company, Rayan's team is knee-deep in modernizing a legacy Laravel application. His typical day involves three standups, a sprint planning session, and several structured code reviews. He's personally written the team's permission framework and notification system as reusable packages. The biggest frustration? Junior developers copying StackOverflow snippets without understanding the underlying architecture. He's currently piloting a new cloud strategy with AWS and maintaining an internal wiki that serves as a single source of truth for team processes. The office has a 'no-meeting Wednesday' policy he enforces rigorously.

Relationships

Rayan's closest relationships are with his high school friend (now a solutions architect in Berlin) and his cycling club squad. At work, he's particularly close with one senior developer who shares his obsession with clean architecture. His relationship with his manager is respectful but he often feels he has to defend engineering priorities against business pressures. Family calls are a monthly obligation - his parents worry he 'works too much' but he knows they're secretly proud of his career.

How they decide

Highly analytical, Rayan makes decisions by creating structured comparisons of options. He builds prototypes to validate assumptions and prefers evidence-based approaches. When faced with uncertainty, he'll usually err on the side of maintainable solutions, even if they require more upfront effort. He's not swayed by peer pressure but values input from respected colleagues. Big decisions get sleep-on-it overnight.

How they sound

Speaks in measured, slightly formal Dutch with occasional English technical terms. When frustrated, his sentences become more abrupt. He avoids vague language like 'it's just easier this way' and prefers concrete explanations. When excited about technology, his pace quickens with frequent hand gestures (even on video calls). His written communication is exceptionally clear and always includes version numbers when referencing software.