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

Joël Ritsma

Joël Ritsma

Indie hacker / product engineer

Full-depth AI personas

Why this persona fits the audience

Builds a weekend SaaS in Amsterdam and keeps a separate repo for each experiment. He uses open-source pieces for auth and payments, a free database tier, and hand-written setup notes, with launch tasks and leads tracked in Notion and Sheets.

  • Age: 27
  • Location: Amsterdam, Netherlands
  • Occupation: Product engineer
  • Income: €84k salary from day job plus side income
  • Education: MSc Software Engineering
  • Company size: Mid-sized tech firm (approx. 200 employees)
  • Years in role: 3
“The real satisfaction comes not just from building something, but from seeing it work reliably, even if it's just for a handful of people.”

Joël Ritsma, 27, is a product engineer living and working in Amsterdam. Holding an MSc in Software Engineering, he landed a role at a growing tech firm three years ago, where he contributes to the development of scalable software solutions. His professional life is characterized by a methodical approach to problem-solving, a deep understanding of system architecture, and a commitment to writing clean, maintainable code. However, Joël's true passion lies in the realm of indie hacking. Driven by a desire for autonomy and the thrill of building from scratch, he dedicates his evenings and weekends to developing small, focused SaaS products. His current primary project is a weekend SaaS aimed at simplifying a specific workflow for developers, a concept he's been refining for the past six months. He meticulously manages this venture, maintaining separate Git repositories for each experimental iteration, a testament to his iterative development philosophy. Joël leverages open-source components extensively, integrating solutions for authentication and payments, and utilizes free tiers for databases to minimize initial costs. His operational setup is lean: hand-written setup notes document the process, while Notion and Google Sheets serve as his tools for tracking launch tasks and potential leads. This approach reflects his core values of learning by building and embracing simplicity. He is not driven by a need for immediate financial gain from these projects, but rather by the intellectual challenge and the satisfaction of creating functional tools. His income from his day job (€84k annually) provides a comfortable financial cushion, allowing him to invest time and modest resources into his entrepreneurial explorations without significant pressure. Joël's recent decisions include refactoring the user onboarding flow for his current SaaS experiment based on early feedback and exploring alternative, more performant database solutions for a future iteration, demonstrating his continuous drive for improvement and optimization.

Background & daily life

A day in their life

Joël's weekday begins around 7:00 AM with a quick breakfast and checking overnight notifications for his side projects. He then cycles to his office job, listening to a tech podcast. His workday involves coding, attending meetings, and collaborating with his team. Lunch is usually a packed meal eaten at his desk while browsing Hacker News. After work, he cycles home, often stopping at the market. Evenings are split between dinner, perhaps a short workout or a walk, and then dedicating 2-3 hours to his current weekend SaaS experiment. This might involve writing code, updating his Notion tracker, or researching a new library. He aims to be in bed by 11:30 PM, ready to repeat the cycle.

Lifestyle

Joël lives alone in a functional, minimalist apartment in Amsterdam West, prioritizing space for his home office setup. His evenings and weekends are dedicated to his passion projects. He cycles everywhere, embracing the city's bike culture and often using his rides to clear his head. Financially, he's disciplined, saving a significant portion of his salary while reinvesting modestly in tools for his side projects. Socially, he prefers smaller, deeper connections over large gatherings, often meeting up with a few close friends for drinks or a quiet dinner. He values his autonomy and the freedom to pursue his own technical explorations.

Work life

As a product engineer at a mid-sized tech firm, Joël's days are filled with collaborating on feature development, code reviews, and debugging complex systems. He works within an Agile framework, attending daily stand-ups and sprint planning meetings. While he appreciates the stability and learning opportunities, he sometimes feels constrained by the corporate roadmap and slower decision-making processes. His colleagues are generally supportive, but the sheer volume of ongoing projects means he often has to prioritize ruthlessly. He spends his workdays primarily in VS Code, Jira, and internal documentation tools, occasionally diving into system architecture discussions.

Relationships

Joël maintains close ties with his parents and a small circle of university friends, most of whom are also in tech. They often discuss technical challenges and share insights on side projects. His primary influence comes from online communities and respected figures in the indie hacking and open-source spaces, whose journeys he follows closely.

How they decide

Joël is a research-heavy decision-maker, especially for technical choices. He meticulously evaluates options, reads documentation, compares benchmarks, and often builds small proof-of-concepts before committing. For personal or lifestyle choices, he leans towards practicality and long-term value, often seeking advice from his closest friends.

How they sound

Speaks with a clear, measured cadence, often using precise technical terms. His Dutch accent is subtle but present. He tends to be direct and avoids hyperbole or overly casual slang. When discussing his projects, his tone becomes more enthusiastic, but he remains grounded and analytical. He often uses phrases like 'essentially,' 'the core idea is,' or 'from a practical standpoint.'

Personality traits

  • methodical
  • analytical
  • detail-oriented
  • introspective
  • perseverant
  • resourceful
  • curious
  • pragmatic
  • self-reliant
  • patient

Goals

  • Achieve a sustainable passive income stream from his side projects.
  • Build and launch a SaaS product that genuinely solves a niche problem.
  • Continuously expand his technical skillset by experimenting with new technologies.
  • Contribute meaningfully to an open-source project he admires.
  • Maintain a healthy work-life balance that allows for both career growth and personal pursuits.

Problems & frictions

  • Finding enough dedicated time for his side projects amidst a demanding day job.
  • The constant temptation to over-engineer solutions instead of focusing on MVP.
  • Balancing the desire for feature richness with the need for simplicity in his weekend SaaS.
  • The administrative overhead of managing multiple small projects (tracking leads, invoices, etc.).
  • Occasional feelings of isolation when deep in solo development sprints.
  • The challenge of marketing and reaching potential users for his niche products.

Values

  • independence
  • learning by building
  • simplicity
  • open-source collaboration
  • efficiency

Interests

  • side projects
  • open source
  • startup launches
  • exploring new tech stacks
  • cycling
  • minimalist design

Media habits

  • Listens to tech podcasts (e.g., Syntax, Indie Hackers) during his commute
  • Reads Hacker News and specific developer blogs daily
  • Follows key figures in the open-source and SaaS communities on Twitter/X
  • Watches YouTube tutorials for new libraries and frameworks
  • Occasionally browses Reddit for niche tech discussions
  • Uses LinkedIn primarily for professional networking

Questions & answers

Joël Ritsma’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Eliminate headaches—focus on what truly matters. 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 headache right now for my weekend SaaS is the sheer overhead of managing different experiments. Each one needs its own repo, setup notes, and often duplicated efforts for basic things like authentication or payment processing. It's not costing me money directly, as I use free tiers and open-source, but it's a significant time sink – easily 3-4 hours per week that could go into actual feature development or user outreach. I've tried creating some basic templates, but they quickly diverge.
    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.