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

Klaas Janssen

Klaas Janssen

freelance full-stack developer

Full-depth AI personas

Why this persona fits the audience

He is a freelance full-stack developer in Amsterdam juggling three client repos, mostly on free tiers of coding assistants and occasional local models. He keeps context in Obsidian and copies file trees into a spreadsheet before long sessions.

  • Age: 27
  • Location: Amsterdam, Netherlands
  • Occupation: Freelance full-stack developer
  • Income: €70k-€110k variable
  • Education: Bootcamp plus self-taught full stack
“The best tool isn't always the most expensive one; it's the one that lets you solve the problem most elegantly and efficiently.”

Klaas Janssen, 27, is a freelance full-stack developer based in Amsterdam, carving out a niche in the competitive tech landscape through sheer resourcefulness and a pragmatic approach. His journey into development wasn't a traditional one; after a brief stint exploring other fields, he discovered a passion for coding through an intensive bootcamp, quickly supplementing it with relentless self-teaching. This hands-on, problem-solving ethos defines his career. He thrives on the independence freelancing offers, relishing the autonomy to structure his work and choose projects that align with his technical interests. His current setup involves juggling three client repositories simultaneously, a testament to his ability to manage complexity. Klaas is deeply invested in optimizing his workflow, particularly concerning AI coding assistants. He relies heavily on the free tiers of these tools, augmented by local models for tasks requiring enhanced privacy or customization. His context management is meticulous: he meticulously organizes project information within Obsidian, creating detailed file tree snapshots in spreadsheets before embarking on intensive coding sessions to maximize the efficiency of his AI interactions. This approach reflects his core values of frugality and practical problem-solving; he seeks the most effective solutions without unnecessary expenditure. Beyond coding, Klaas is an avid climber, finding both physical and mental release in the sport, and is constantly exploring ways to automate repetitive tasks in his life and work. His financial habits are disciplined, driven by a desire for long-term stability and the freedom to pursue projects he finds genuinely engaging, rather than chasing the highest immediate payout. He views technology, especially AI, not just as a tool for clients, but as a personal lever for efficiency and continuous improvement in his own craft.

Background & daily life

A day in their life

Klaas's typical weekday begins around 7:00 AM with a brisk cycle through Vondelpark. Back home by 8:00 AM, he makes coffee and reviews his Obsidian vault, outlining the day's priorities for his three client projects. From 9:00 AM to 1:00 PM, he's deep in code, tackling bugs or implementing new features, often using AI assistants for boilerplate code or debugging suggestions. Lunch is a quick, home-prepared meal around 1:00 PM. The afternoon, from 2:00 PM to 6:00 PM, might involve client calls, code reviews, or focusing on a different project's architecture. He dedicates an hour each evening, usually around 7:00 PM, to personal learning or optimizing his workflow, perhaps exploring a new automation script or reading about the latest LLM advancements. He winds down by 10:00 PM, often reading or listening to a podcast.

Lifestyle

Klaas lives in a functional, well-organized studio apartment in Amsterdam West, prioritizing proximity to public transport and green spaces. His routine is self-imposed but structured: early mornings often involve a quick run or cycling session, followed by a strong coffee and a review of his Obsidian notes for the day's tasks. He cooks most of his meals, valuing both health and cost-effectiveness. Socially, he's selective, preferring deep conversations with a small circle of close friends over large gatherings. Weekends might involve a trip to a climbing gym or exploring a new neighborhood, but he's equally content spending an afternoon optimizing a personal script. Financial discipline is key; he tracks expenses meticulously and avoids unnecessary subscriptions.

Work life

As a freelance full-stack developer, Klaas's workdays are a dynamic mix of client demands and self-directed problem-solving. He's currently managing three distinct client projects, each with its own codebase and set of challenges. His primary focus is on backend development using Node.js and Python, with a solid grasp of frontend frameworks like React. He leverages free tiers of AI coding assistants extensively, supplemented by local models for sensitive tasks, meticulously managing context through Obsidian and file tree spreadsheets to maintain session efficiency. The pressure comes from balancing deadlines across multiple clients while ensuring code quality and managing his own administrative overhead. Coworkers are typically remote client teams or other freelancers he collaborates with occasionally.

Relationships

Klaas maintains a close relationship with his parents, who live in a smaller town in the Netherlands, and communicates with them weekly. His core social circle consists of a few university friends and fellow freelancers he met through online communities or coworking spaces. These friends often serve as informal sounding boards for technical challenges and career decisions. He doesn't have a romantic partner currently, prioritizing his career and personal development.

How they decide

Klaas approaches decisions with a blend of analytical research and pragmatic testing. He'll thoroughly investigate options, compare features and potential benefits, often creating spreadsheets or detailed notes. However, he's not afraid to experiment with free trials or open-source alternatives to see what works best in practice. Cost-effectiveness is a significant factor, and he'll often choose a slightly less polished but free or low-cost solution if it meets his core needs. Peer recommendations from trusted developer communities carry weight, but he ultimately relies on his own assessment of utility and efficiency.

How they sound

Speaks with a clear, measured cadence, often using precise technical terminology. His Dutch accent is subtle but present. He tends to be direct and avoids overly casual slang, preferring straightforward communication. When discussing technical challenges, he might use analogies related to optimization or efficiency. He's not one for hyperbole and tends to downplay potential risks or difficulties, focusing instead on solutions. He avoids expressing strong opinions on non-technical matters unless directly relevant to his work or values.

Personality traits

  • methodical
  • resourceful
  • persistent
  • analytical
  • self-reliant
  • detail-oriented
  • optimizing
  • curious
  • pragmatic

Goals

  • Achieve a stable income stream allowing for more strategic project selection.
  • Develop a personal framework for evaluating and integrating new AI development tools.
  • Contribute meaningfully to an open-source project related to developer productivity.
  • Maintain a healthy work-life balance that supports his physical and mental well-being.
  • Build a small, automated passive income stream through a side project.

Problems & frictions

  • Managing context switching between three disparate client projects efficiently.
  • The constant need to stay updated with rapidly evolving AI and development technologies.
  • Balancing the cost of development tools and services against project budgets.
  • Ensuring consistent project scope and avoiding scope creep from clients.
  • The isolation inherent in solo freelancing, despite occasional remote collaboration.
  • Optimizing AI assistant usage to maximize output without incurring significant costs.

Values

  • independence
  • frugality
  • practical problem-solving
  • efficiency
  • continuous learning

Interests

  • solo freelancing
  • Obsidian note-taking
  • climbing
  • automations
  • open-source development
  • AI tooling

Media habits

  • YouTube tech tutorials (especially for new frameworks)
  • Stack Overflow for specific issues
  • Developer podcasts during commutes or chores
  • Reading documentation thoroughly
  • Following key figures in AI development on Twitter/X
  • Subscribing to niche coding newsletters

Questions & answers

Klaas Janssen’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.paritok.com/ (Paritok) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core concept of compressing AI agent context for longer sessions and reduced bills is immediately appealing. I appreciate the focus on "non-destructively compressing" because I'm always worried about losing crucial information when using free tiers. What's unclear is how exactly the "compression gateway" handles different types of files and tool outputs without sacrificing fidelity; the diagram shows a `read_original` function, which is reassuring, but I'd need to see more detail there. The "Self-host free" option is especially interesting given my reliance on local models for privacy. However, the "Hosted GPU" pricing, $0.30 per 1M billable file tokens, feels a bit nebulous. I'd want to understand what constitutes a "billable file token" more clearly before committing.
    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.