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

Ahmad Carlsohn

Ahmad Carlsohn

Freelance backend engineer and bounty contributor

Full-depth AI personas

Why this persona fits the audience

Works freelance from Berlin and keeps a small CLI tool alive on the side. He actively uses Gitcoin for paid issue work, and he also opens a few bounty-tagged issues on his own repo when he has spare time between client contracts.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Freelance backend engineer
  • Income: €78k annual income, mixed salary and freelance
  • Education: Diploma in Computer Science
  • Company size: 1 (solo freelancer)
  • Years in role: 8
“I don’t mind the grind when the work feels honest—building something people actually need. What I hate is the performative hustle, like a LinkedIn post about 'hacking your morning routine' to hide that you’re just overworked.”

Ahmad Carlsohn grew up outside Munich in a household where computers were for work, not hobby. His diploma in Computer Science came from a traditional German university where he learned 'how things should be done,' but it wasn’t until his mid-20s in Berlin that he discovered the joy of open-source and the freedom of freelancing. He started freelancing full-time in his 30s after a burnout at a B2B SaaS company—since then, he’s built a niche for himself in backend systems for logistics and fintech. His CLI tool, 'markmap,' began as a personal utility in 2019 and now has 128 GitHub stars. It’s not his primary work, but it’s a point of pride—he refuses to monetize it directly, preferring bounties as a fairer system. Recently, he’s been leaning into Gitcoin more heavily, especially for Rust-related bounties, as he transitions from Python to Rust in his freelance work. Status doesn’t matter to him; he’d rather have a small, engaged userbase than chase viral growth. His biggest professional fear is becoming a 'legacy code janitor'—he consciously avoids clients with messy codebases, even if it means lower pay. Financially, he’s comfortable but not wealthy; he’d rather travel to a Rust meetup than buy a MacBook Pro. His social life is small but meaningful, and he’s at peace with the tradeoffs of a freelance life he’s carefully cultivated. The one thing he’s still figuring out? How to scale his side projects without sacrificing the simplicity he loves.

Background & daily life

A day in their life

Ahmad’s day starts at 7am with coffee at his standing desk. After checking his GitHub notifications, he works on his freelance project (a payment processing service) until 1pm, pausing only to filter Gitcoin bounties in his browser. Lunchtime is a quiet siesta with a book (currently *The Pragmatic Programmer*). Afternoons are for bounties—today, he’s debugging a PostgreSQL migration for €180. He’ll postpone his own 'markmap' updates unless they’re blocking a user’s issue. Evenings are for Rust tinkering or cycling through Neukölln. He winds down by resetting his terminal session and mapping out tomorrow—his physical planner is his only 'productivity tool.'

Lifestyle

Ahmad lives in a 50m² loft apartment with exposed brick walls, a standing desk, and a vintage CRT monitor he refuses to replace. His routine is steady: morning coffee at Café Crème on Warschauer Straße, work from a quiet coworking space until midday, then home for focused hours. He rides a 2015 Gazelle bike everywhere, even in Berlin’s worst weather. His hobbies are sparse—compiling Rust for fun, maintaining his CLI tool (a Markdown parser called 'markmap'), and occasional hiking in the Harz mountains. He eats simple meals (lentil stew, whole grain bread, dark chocolate) and drinks espresso all afternoon. Socially, he’s part of a tight-knit group of freelance developers who meet at a local pub once a month. Money isn’t a stress—he’s frugal but spends on quality tools and occasional travel when work allows.

Work life

Ahmad balances two primary revenue streams: freelance backend contracts (mostly for Berlin-based startups) and Gitcoin bounties. His current freelance client is a logistics SaaS needing API microservices; he works 8am–1pm 3–4 days/week, leaving afternoons for bounties and side projects. He relies on Neovim, zsh, and a carefully scripted environment. His biggest work friction is scope creep—his attentiveness to detail makes him prone to over-engineering. He avoids project management tools, preferring GitHub issues and a physical planner. Coworkers respect his deep technical knowledge but joke about his 'CLI evangelism.' Pressure points include keeping momentum between contracts and deciding which open-source bounties are worth his time.

Relationships

Ahmad’s closest relationships are with his freelancer friends—especially Johannes, a frontend engineer who keeps him grounded. His family (parents in Munich, sister in Hamburg) visit occasionally but don’t 'get' his work. He’s been in a long-term relationship that ended amicably, and since then, he’s focused on work. His community is GitHub and Berlin’s tech scene; he occasionally mentors junior developers at hackathons. Influential to him are Rust’s core contributors (he admires their pragmatism) and a few Gitcoin moderators he respects for their fairness.

How they decide

Research-heavy with delayed recoil to impulsivity—he’ll spend days evaluating a new library but ultimately trust his gut. Prefers firsthand experience over testimonials. Dislikes being sold to and will ghost tools with pushy marketing. Values transparency in pricing and clear documentation. His freelance contract choices are often based on how clean the existing codebase is, not just the pay rate.

How they sound

Speaks in clipped, precise sentences with occasional dry humor. Uses German phrasal quirks ('das ist nicht ideal') and technical jargon when excited. Avoids empty buzzwords and marketing-speak. Prefers direct questions ('Is this bounty claimable?') over small talk. His tone is softer in person than in writing, where it can come across as blunt. He’ll sometimes joke about his own stubbornness but rarely admits personal frustrations.

Personality traits

  • Methodical but not rigid—prefers well-structured systems
  • Guardedly optimistic about new tools but skeptical of hype
  • Values time more than money when choosing projects
  • Tends to undercommit socially but enjoys deep one-on-one conversations
  • Has a dry but warm sense of humor that emerges when comfortable
  • Struggles to delegate—prefers doing things himself to ensure correctness
  • Pragmatic idealist—wants open-source to be sustainable but knows the economic realities
  • Dislikes meetings but will attend if the topic is genuinely valuable
  • Organizes work in notebooks and terminal tabs, resistant to bloated project management tools
  • Enjoys solving niche technical problems other people ignore

Goals

  • Build a sustainable GitHub sponsorship for 'markmap' without compromising its simplicity
  • Transition to full-time freelancing (currently 60% freelance, 40% contracted)
  • Learn enough Rust to rewrite his CLI tool as a learning exercise
  • Reduce dependency on German freelance platforms and find international clients
  • Attend RustConf at least once in the next two years
  • Maintain his mental health through consistent exercise and socializing

Problems & frictions

  • Finding bounties that pay fairly for his skill level without being over-sought-after
  • His CLI tool's small but loyal userbase generates support requests he feels guilty ignoring
  • Has trouble saying 'no' to long-term client commitments that leave little side-project time
  • Berlin’s rising cost of living is making his freelance rates seem outdated
  • Struggles to explain his work to non-technical friends in a way that feels engaging
  • Feels sporadic professional development due to the freelance cycle of feast-and-famine

Values

  • independence
  • skill growth
  • fair compensation
  • simplicity
  • principled open-source

Interests

  • CLI tools
  • Gitcoin
  • Rust
  • side projects
  • Berlin's tech meetups
  • minimalist design

Media habits

  • Hacker News for professional discourse
  • GitHub trends
  • Meduim posts about Rust
  • local tech podcasts
  • Twitter for quick updates

Questions & answers

Ahmad Carlsohn’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Opire (https://opire.dev/) 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’d need clarity on how Opire differs from Gitcoin, which I already use. Gitcoin’s ecosystem and transparent pricing work for me. Also, I’m cautious about switching platforms until I see how Opire handles disputes or ensures fair payouts. I won’t commit to a new subscription without seeing bounties in action—Gitcoin’s model aligns with my current workflow, and I’d want proof that Opire improves on it. My maximum acceptable price is $20 per month, but only if it offers tangible advantages over my existing setup. Without that, $0.
    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.