Kjeld de Vries

Why this persona fits the audience

Leads a five-person web agency in Amsterdam. He often jumps into client-ticket pair programming with another developer or a designer-turned-QA, and their team already uses JetBrains Code With Me for some shared coding sessions.

• Age: 31
• Location: Amsterdam, Netherlands
• Occupation: Agency technical lead
• Income: €78k salary + profit share
• Education: B.Sc. Information Technology
• Company size: 5 employees (his own agency)
• Years in role: 6

“I'd rather over-communicate early than have to fix misunderstandings later. And yes, before you say it, I know I'm the worst about it sometimes.”

Kjeld de Vries grew up in a small town outside Utrecht, where his interest in computing started with tinkering with his father's old PC. After earning his B.Sc. in Information Technology at the University of Amsterdam, he worked at a few different agencies before starting his own in 2017. His agency started as just himself and one junior developer, but has steadily grown to five full-time employees. Kjeld prides himself on building a team where everyone can code, but also values soft skills like communication and client management. His approach to work is pragmatic—he prefers battle-tested solutions over bleeding-edge tech unless there's a clear advantage. The agency's current tools are a mix of industry standards and niche solutions that work well for their specific workflow. Lately, Kjeld has been frustrated with the limitations of JetBrains Code With Me, especially during international calls where lag makes collaboration painful. He's considering alternatives but hasn't found one that integrates as seamlessly with their existing stack. Despite the frustrations, he's proud of the work his team does and the relationships they maintain with clients. His biggest challenge is maintaining their craftsmanship standards while scaling the business. On a personal level, he's trying to find better balance between work and hobbies, with mixed success. He's seen other agencies burn out from growth, and he's determined to avoid that fate while still expanding. His next big push will be improving their developer experience—better tooling, clearer documentation, and more efficient workflows to reduce the mental load on his team. For now, though, he's focused on shipping quality work for clients and keeping his team happy.

Background & daily life

A day in their life

Kjeld's alarm goes off at 6:30, and he forces himself out of bed with a cold shower. He cycles to the office by 8:00, stopping for fresh oat milk for his espresso. The first hour is sacred: he does deep work on code or documentation while his brain is fresh. By 9:30, he's reviewing a junior developer's pull request with pointed but constructive comments. At 10:00, there's a client call about a feature backlog—he's prepared the project status in advance. Between 11:00 and 1:00, he does hands-on coding with a designer (who does QA) using Code With Me, but they all notice the lag and resort to Google Docs for notes. After lunch, he responds to agency emails and then pairs with another developer on a tricky API integration. At 4:00, he reviews the team's progress for the day and assigns tomorrow's priorities. He leaves by 5:30, often grabbing groceries on the way home. Evenings are for cooking, reading, and if he's feeling social, organizing a meetup. By 10:30, he's in bed with a technical book or a history podcast.

Lifestyle

Kjeld rents a compact but well-organized apartment in De Pijp, within biking distance of his agency. His mornings follow a strict routine: cold shower, oatmeal with honey, and a quick scan of tech news while waiting for his espresso to brew. He rides an old but well-maintained Gazelle bike to work, rain or shine, and always carries a waterproof laptop sleeve. His weekends alternate between coding pet projects (usually JavaScript experiments) and organizing small tech meetups at local coworking spaces. He's been trying to get back into guitar playing but keeps getting sidetracked by the latest npm package. Socially, his circle is mostly other agency founders and developers, with a few friends from his university days who work in unrelated fields. He's fiscally conservative with his personal finances but reinvests aggressively in agency upgrades. His health is mostly good, though he's noticed his back tense up after long coding sessions, which he treats with ice packs and stretching routines.

Work life

Kjeld's agency specializes in smaller, high-impact web projects for Dutch startups and EU-focused businesses. His days are a mix of client communications, technical leadership, and hands-on coding. He prefers to start his mornings with code reviews and then transition to client calls. The team uses GitHub Projects for task tracking and Slack for internal communication, though Kjeld often finds himself frustrated by Slack's limitations for technical discussions. His current frustration is with Code With Me's lag during international collaborative sessions—they've considered alternatives but haven't found one that integrates as seamlessly with their workflow. He's currently mentoring a junior developer who's eager but prone to overcomplicating solutions, which Kjeld handles with a mix of patience and dry humor. Client deadlines are always tight, and Kjeld's biggest pressure is maintaining quality while meeting them. He's been considering implementing better onboarding documentation but hasn't found the time to make it happen.

Relationships

Kjeld's family is spread across the Netherlands, and he visits his parents in Rotterdam every other weekend for dinner. His younger sister is studying architecture and he enjoys debating the future of cities with her. His closest friend is a fellow agency founder from university days—They meet monthly for bitterballen and to vent about client frustrations. In the tech community, he's known for his pragmatic approach to tooling debates, though he's careful not to burn bridges. His team sees him as approachable but serious about quality, and his clients appreciate his straightforward communication. He's occasionally asked to speak at meetups but turns most invitations down, preferring to reserve his energy for client work.

How they decide

Kjeld researches thoroughly but trusts his intuition when the data is ambiguous. He values his team's input heavily, especially when it challenges his assumptions. He's cautious with tools that might disrupt workflows but will take calculated risks if the potential upside is significant. He dislikes making decisions under pressure and will often say 'I need to think about it' to buy time. Once decided, he commits fully and expects the same from his team. He's more likely to adopt a tool if it's recommended by someone he respects than if it has impressive marketing.

How they sound

Kjeld speaks in measured, precise sentences with occasional dry humor. He avoids jargon when talking to clients but won't dumb down technical discussions with his team. His Dutch accent is subtle but noticeable, especially when he's frustrated. He uses filler words like 'well' or 'basically' when thinking aloud, and often ends sentences with a rhetorical question. He's prone to understatement ('This'll be fine') when hiding stress. He avoids startup buzzwords and marketing speak, preferring straight talk about problems and solutions. His voice gets quieter when he's deep in thought and louder when making a point he cares about.