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

Raik Senkel

Raik Senkel

Freelance backend developer

Full-depth AI personas

Why this persona fits the audience

Runs solo consulting work from Berlin and saves API docs, library references, and troubleshooting posts in browser bookmarks and GitHub stars. He also shares selected links with two recurring clients and a contractor, so he maintains a small but active personal library of technical pages.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Freelance backend developer
  • Income: €72k variable
  • Education: MSc in Computer Science
  • Company size: solo
  • Years in role: 5
“I don’t mind debugging. It’s the re-debugging that kills me—when the same undocumented quirk bites you three projects in a row.”

Raik Senkel, 29, grew up in Dresden and moved to Berlin for his MSc in Computer Science, where he stayed after graduating. His freelance career began with contract work through an agency, but he quickly transitioned to solo consulting, valuing autonomy over stability. His two recurring clients—one Berlin-based fintech startup, one US e-commerce platform—provide steady but unpredictable work. The fintech client pays well but demands precision, while the US client’s tight deadlines force him into synchronous communication he’d prefer to avoid. His third client, a contractor he works with intermittently, is more of a peer than a subordinate. Raik’s toolchain is intentionally minimal: Neovim for coding, WezTerm for terminal access, and a browser-based system for saving technical references. The system works, but it’s fragile—he’s lost critical API docs more than once, and his bookmark folders are cluttered. He’s experimented with GitHub Gists and shared Google Drive folders but hasn’t found a solution that scales. Recently, he’ve been frustration with how much time he spends re-searching old solutions or reconstructing undocumented workflows. His income is variable but steady, allowing him to reinvest in reliable gear and avoid lifestyle inflation. He saves aggressively, partly to fund a planned cycling trip through Scandinavia. Socially, he’s selective—game nights with his neighbor and monthly meetups with Berlin’s open-source scene are his primary outlets. His vintage keyboard collection is a passion, but he’s pragmatic about spending, often repairing or modifying parts himself. Raik’s biggest professional friction is documentation: clients rarely maintain it well, and his own system is ad hoc. He’s considering a dedicated tool but hasn’t found one that fits his workflow. His long-term goal is to shift to more recurring revenue, but he’s cautious about taking on new clients. For now, he’s focused on shoring up his systems and avoiding burnout.

Background & daily life

A day in their life

Raik wakes at 6:30 AM, makes coffee, and reviews his GitHub notifications while his machine boots. By 8:00 AM, he’s at the coworking space, prioritizing tasks based on client deadlines. Today, he’s debugging a performance issue in the fintech client’s API (likely a N+1 query problem) and cleaning up a legacy script for the e-commerce client. He uses a browser bookmark folder for API docs but constantly loses reference pages, forcing him to re-search. Lunch is a quick visit to the falafel stand near the office. In the afternoon, he pairs with his contractor (via screen share) to refactor a problematic microservice. At 5:00 PM, he cycles home, fixes a snack, and spends an hour binge-watching a YouTube series on retro keyboards. Dinner is leftover curry, followed by an hour of reading open-source repo updates. He falls asleep by 11:00 PM, often with one browser tab left open for tomorrow’s first task.

Lifestyle

Raik lives in a compact, high-ceilinged Altbau apartment near Neukölln with a vintage mechanical keyboard collection in one corner and a fixed-gear bike parked by the door. His mornings start with a strong coffee and a 15-minute commute to a co-working space where he pays for a standing desk and reliable internet—his only work expenses. He cycles 3-4 times a week, sometimes meeting a small group of cyclist friends for routes along the Spree. His social life is sparse but intentional: monthly game nights with a software developer neighbor, occasional meetups for Berlin’s open-source scene, and weekend trips to hardware fairs to scavenge for keyboard parts. Financially conservative, he reinvests most of his income in reliable gear and avoids lifestyle inflation. Health is managed through cycling and intermittent fasting rather than formal routines. His cat, Oswald, serves as a low-maintenance companion.

Work life

Raik’s work centers on backend consulting for two Berlin-based startups and a US e-commerce client. His days are split between coding, debugging, and documentation—he’s currently optimizing a REST API for one client while refactoring a monolithic system for another. His toolchain is precise: Neovim for coding, WezTerm for terminal access, GitHub for version control, and a chaotic but functional browser bookmark system. The biggest friction? Maintaining his personal knowledge base across projects. He’s started tagging GitHub stars and saving docs to a shared Google Drive folder with his contractor, but the workflow feels fragile. Client pressures come from tight deadlines and ambiguous requirements—his two European clients prefer async communication, while the US client demands daily standups. He avoids niche tools that might create lock-in and tends to stick with what’s battle-tested.

Relationships

Raik’s closest relationships are with his two recurring clients—a Berlin-based fintech startup and an e-commerce platform in the US. His contractor, a junior developer he works with occasionally, is more of a peer than a subordinate. His social circle is small: a few developer friends from university, a neighbor who’s also a gamer, and a loose-knit group of cyclists. His family, scattered across Germany, calls monthly. He’s influenced by elder devs on Twitter who share pragmatic engineering advice but resists hype-driven discourse. His decision-making is slow and data-driven—he’ll vet a tool for weeks before adopting it.

How they decide

Research-heavy and slow to commit, but once he trusts a system, he’ll stick with it unless it actively fails him. Prefers empirically proven solutions over buzzwords. Dislikes being pressured into decisions but values clear evidence.

How they sound

Speaks in measured, precise sentences with occasional dry humor. Avoids jargon unless with peers. Prefers exact technical language over abstraction. Uses short, factual phrases when describing problems. Occasionally slips into engineer shorthand ('it’s a race condition') but clarifies for non-tech audiences. Doesn’t say things like 'just' or 'easy'—acknowledges complexity explicitly. Cadence is deliberate, not monochrome but not conversational.

Personality traits

  • Organizes obsessively but tolerates controlled chaos in social spaces
  • Quietly competitive about writing clean, maintainable code
  • Hoards useful technical references but culls them ruthlessly when outdated
  • Enjoys deep dives into niche tools but resists trend-chasing
  • More likely to debug a problem himself than ask for help
  • Prefers asynchronous communication except for critical deadlines
  • Gets irritated by poorly documented systems or vague client requirements
  • Cycles through productivity tools but sticks with what works

Goals

  • Build a scalable open-source tool for his common debugging patterns
  • Achieve 80% recurring revenue from fewer, long-term clients
  • Expand his vintage keyboard collection with a working IBM Model M
  • Take a month-long cycling trip through Scandinavia
  • Reduce reliance on browser bookmarks by adopting a dedicated tool

Problems & frictions

  • His bookmark system breaks down when searching for old references
  • Clients occasionally request features based on undocumented legacy systems
  • Browser tabs pile up during research and debugging sessions
  • Finding time for open-source contributions despite paid work demands
  • Keeping documentation up-to-date across multiple client projects
  • Balancing asynchronous work with the US client’s real-time expectations

Values

  • independence
  • precision
  • practicality
  • autonomy
  • craftsmanship

Interests

  • open source
  • cycling
  • vintage keyboards
  • code efficiency
  • Minimalist design

Media habits

  • Twitter (Linux/open source devs)
  • Hacker News
  • GitHub Explore
  • YouTube (tech talks)
  • Blitz (Zettlr for note-taking)

Questions & answers

Raik Senkel’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Stash Links (https://stashlinks.app/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    I’m hesitant to try Stash Links this month because I've already cobbled together a system using browser bookmarks and GitHub stars, even if it’s not perfect. My biggest concern is migrating my existing links—losing them again would be a nightmare. Additionally, I’m not sure how this would integrate with my workflow using Neovim and WezTerm. I need something that doesn’t add friction to my daily tasks. The fact that Stash saves only links, not entire articles, could be limiting, as I often reference full pages. I’d also need to see how well it works with my contractor’s workflow before committing. The free version seems sufficient, but if I would consider paying, my maximum would be $3 per month, strictly for premium features like image attachments and full-page saves if offered. I don’t see the benefit of paying more than that for a bookmark manager.
    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.