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

Jimmy Prinsen

Jimmy Prinsen

Product engineer at a small multilingual startup

Full-depth AI personas

Why this persona fits the audience

He works in Amsterdam on a 3-person team shipping a SvelteKit app with Dutch and English routes, and the navigation map lives in a mix of README files and a shared spreadsheet. He is comfortable with code but still checks route helpers manually because the team changes pages frequently.

  • Age: 27
  • Location: Amsterdam, Netherlands
  • Occupation: Product Engineer
  • Income: €74k base
  • Education: MSc Informatics
  • Company size: 3-person startup
  • Years in role: 1.5
“I never trust a routing system I didn't build myself to be perfectly predictable. And I'm always wrong.”

Jimmy Prinsen earned his MSc in Informatics from Utrecht University, where he first discovered Svelte and became enamored with its simplicity. After a brief stint at a larger tech firm, he joined a three-person startup in Amsterdam building multilingual tools for small businesses. His current role as product engineer means he touches everything from API design to UI components, though his favorite work involves making systems more maintainable. The team's rapid iteration pace means he's constantly balancing ship-ready code with architectural improvements, a conflict he finds simultaneously frustrating and rewarding. Jimmy's apartment, near Amsterdam Centraal, reflects his preferences for clean surfaces and functional design. His workspace features a large whiteboard for routing diagrams and a wall of sticky notes marking his ongoing experiments with different coffee brewing methods. His SvelteKit knowledge is deep but self-taught, with his confidence earned through solving real problems rather than formal credentials. He often volunteers his time answering SvelteKit questions on forums, deriving satisfaction from helping others avoid his own past mistakes. A recent travel weekend to Belgium confirmed his desire to become fluent in Dutch, a goal he's pursuing through language apps and local social events. Jimmy's attention is currently focused on reducing the friction in his team's development workflow, particularly around their ad-hoc routing system. He's considering proposing a more rigorous solution but wants to gather more evidence that the pain points justify the investment of time. His ideal tool would automate the boring parts while still giving him full control when needed. Despite his technical depth, Jimmy remains approachable and enjoys explaining concepts to less experienced developers. His colleagues appreciate that he always has a working prototype to demonstrate new ideas, even if it's just mocked data.

Background & daily life

A day in their life

Jimmy's day starts at 7:15am with a quick protein shake and cycling to work. He'll usually swing by a different coffee shop each morning, judging today's based on whether they have properly roasted Ethiopian beans. The first hour of work is spent triaging PRs and checking last night's deploy. Around 10am he realizes they need to add a new route for a client feature, triggering the familiar 20-minute spreadsheet update and manual helper file check. He grabs lunch (usually smoked Gouda and rye bread) at his desk while reading Svelte GitHub discussions. Afternoon brings a particularly frustrating bug in their locale handling, which he solves by 4:30pm. On the ride home, he mentally rehearses his pitch for better routing tooling during tomorrow's standup. Dinner is likely a pre-cooked meal from the Albert Heijn, eaten on his couch while watching Formula 1. He'll wind down by reading technical blogs and occasionally contributing to SvelteKit discussions on Discord.

Lifestyle

Jimmy rents a small but airy ground-floor apartment near Amsterdam Centraal, its large windows letting in light that dances off the canal just outside. His mornings start with a 30-minute bike ride to work, often taking different routes to discover new shortcuts or coffee spots. He's perpetually trying to perfect his home workspace: currently experimenting with a standing desk made from an old Dutch drawer unit and IKEA parts. His weekend ritual is cycling into the Netherlands' countryside with a thermos of koffiemelk. Jimmy's social life revolves around a small group of fellow tech builders and board game enthusiasts, with monthly meetups at a café that doubles as a strategy game night. He's budget-conscious but invests in small luxuries like high-quality cycling gear and local specialty coffee.

Work life

Jimmy's startup builds a SvelteKit app for small business owners needing multilingual tools. His typical day starts with a standup on Jitsi, then dives into rearranging route helpers in their Google Sheets diagram. He prefers the rare days when he can work in focused silence, but his team's rapid iteration means he's frequently context-switching. He's currently frustratingly aware of how much time they waste maintaining their hand-rolled routing system, but hasn't convincingly pitched reworking it. The team's recently adopted a more structured PR template after Jimmy got tired of incomplete migrations. He's secretly proud of the micro-optimizations he sneakily implements in their CI pipeline. His biggest current frustration is that their mix of READMEs and spreadsheets for route mapping leads to inconsistencies when localizing content.

Relationships

Jimmy's closest friends are colleagues from his university days and fellow tech enthusiasts from Amsterdam meetups. He's in regular contact with his parents in Utrecht, who still haven't fully understood what he does for a living. His social circle has expanded since moving to Amsterdam, particularly through board game nights and cycling activities. He respects one particular coworker's ability to navigate corporate politics, something he's still learning. His decisions about work tools are most influenced by online technical communities and direct peer recommendations.

How they decide

Research-heavy but with a bias toward action. He'll spend 2-3 hours evaluating options but will commit to a solution and move forward once convinced. Prefers solutions that give him quick results and reduce future maintenance. Tends to distrust overly hyped products but will experiment with promising tools in personal projects first.

How they sound

Speaks in complete sentences with deliberate pacing, occasionally using Dutch words when explaining technical concepts. Avoids jargon in favor of concrete analogies. Has a dry, understated sense of humor that comes out in workplace chat. Prone to saying 'It works, but...' when critiquing solutions. Uses 'we' when referring to his team's work, even for things he did solo. Avoids hyperbolic praise or criticism. His Dutch accent shows when he's deep in thought.

Personality traits

  • Subtly competitive about clean code architecture
  • Favors systems that prevent mistakes over those that detect them
  • Tends to automate repetitive tasks as soon as they appear twice
  • Prefers to prototype solutions before discussing them
  • Deliberately avoids over-engineering but hates technical debt
  • Mildly pedantic about correct terminology in code comments
  • Enjoys explaining technical concepts in simple terms
  • Takes pride in documenting things others might skip
  • Will spend 20 minutes debugging a colorscheme to be perfect
  • Subtly prefers unleaded coffee to espresso

Goals

  • Grow his ability to architect systems that scale with team growth
  • Improve his Dutch to native fluency in the next year
  • Build a personal project that demonstrates clean multilingual routing
  • Advance to a lead engineer role within 3 years
  • Master Dutch cycling infrastructure history enough to give tours
  • Perfect his pour-over coffee technique at home

Problems & frictions

  • Their ad-hoc routing system becomes increasingly brittle as content grows
  • Finding time to refactor technical debt while maintaining speed
  • Balancing his own architectural preferences with small team practicality
  • Keeping track of route changes across both Dutch and English versions
  • Frequently having to mentally map their spreadsheet to actual code
  • The ever-present tension between
  • Just ship it
  • Do it right

Values

  • experimentation
  • clean interfaces
  • team speed
  • good defaults
  • pragmatic minimalism
  • autonomy in systems

Interests

  • Svelte
  • design systems
  • canal cycling
  • board games
  • Dutch cycling infrastructure history
  • minimalist web design

Media habits

  • RSS reader for niche tech blogs
  • Listens to Svelte Radio and Dutch tech podcasts
  • Bookmarks tweet threads about frontend patterns
  • Occasional Reddit for SvelteKit tips
  • Uses Notion for personal project tracking

Questions & answers

Jimmy Prinsen’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: Type-safe routing, zero guesswork, seamless navigation.. Generate typed URL helpers from the pages your framework already routes. Discover routes… What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest problem is our inconsistent routing causing localization headaches. When we add a new route, it’s a 20-minute ritual of updating the spreadsheet, cross-checking the helpers, and praying we didn’t miss a translation. Last month, we shipped a broken Dutch page because the URL helper wasn’t synced. We’ve tried READMEs, spreadsheets, and manual checks, but the overhead adds up—especially when we’re shipping features twice a week. Type-safe routing would save us hours, but I’d want to see how it handles our NL/EN splits. We’re small, so any tool needs to be low-maintenance.
    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.