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

Danilo Diekmann

Danilo Diekmann

ML engineer in a 3-person remote side-project team

Full-depth AI personas

Why this persona fits the audience

Works on a weekend AI tooling project with two former colleagues across Berlin and Warsaw. They split work in Linear and GitHub, and he keeps a profile on another founder-matching community to look for occasional collaborators.

  • Age: 31
  • Location: Berlin, Germany
  • Occupation: Machine learning engineer
  • Income: €110k
  • Education: Master's degree in Computer Science (Technical University of Berlin)
  • Company size: 250 at day job (remote-first multinational); 3 in weekend project
  • Years in role: 5
“I could spend all day arguing about hyperparameters, but at some point you just have to commit the changes and see what happens.”

Danilo Diekmann grew up in Munich with an engineer father and architect mother, which explains his pragmatic approach to building things. His first serious coding project was a Python-based school schedule optimizer that circulated among Munich's nerdier students. After completing his master's with a thesis on transfer learning, he joined a Berlin-based recommendation engine startup where he immediately stood out for his ability to balance technical depth with shipping speed. His weekend project with ex-colleagues began as a hackathon submission but transformed into something more serious when they realized their documentation tool filled a genuine niche. The team works without funding, sharing costs for cloud resources via a shared bank account. Danilo's current dilemma is whether to formalize the project - one teammate wants to seek investors, while he's torn between idealism and the practical need for sustainability. His status anxiety comes not from titles or salary, but from being seen as the 'senior presence' in the team. He measures success in terms of technical impact, not recognition. His relationship to money is pragmatic - he saves aggressively for potential relocation but splurges on high-quality tools. His social circle exists primarily to validate his technical judgments, though he's working on being more present with his friends. Recent decisions include adopting a strict policy of no weekend work past 7pm (which he occasionally breaks), and banning Discord from his phone to reduce notification fatigue.

Background & daily life

A day in their life

Danilo starts at 6:15am with his ride through the park, returning to stand at his desk while eating his usual breakfast. Workday begins with syncs and reviewing GitHub issues - he's most productive between 9am-12pm when he does his 'real work' building models. After a 15-minute midday walk, he switches to the side project, capitalizing on his freshest creative hours. He eats lunch at his desk (usually a pre-cooked batch of lentil soup) while watching tech talks. Around 7pm, he switches to async response mode - he hates late meetings but will chat via Slack. His evenings alternate between coding sessions and his black metal DJ night at a small club in Kreuzberg (his alter ego, DJ Nuetron, is a running joke with his teammates). He typically sleeps by 11:30pm, unless he's deep in a coding flow state.

Lifestyle

Danilo lives in a sparsely furnished 70sqm apartment with exposed brick walls and a repurposed industrial desk that doubles as a workstation and weekend project hub. His morning routine is a 7am 10km ride through Tiergarten, where he listens to conference talks or reads code on his foldable. He eats the same breakfast (muesli + espresso) every day to avoid decision fatigue, and cycles to his local Ainsi has his two-coffee minimum. He's frugal but invests in one expensive hobby: his hand-built gaming PC that dual-boots Windows for work and NixOS for experiments. Socially, he prefers 1:1 dinners with ex-colleagues over larger gatherings, and his closest friend group revolves around the Berlin ML meetup he occasionally attends. He's in a long-distance relationship with a Warsaw-based UX designer he met at a Hackathon, which fuels his preference for async collaboration.

Work life

Danilo's day job at a Berlin-based startup involves building recommendation systems, but his true passion is the weekend project with two old colleagues: a tool to fine-tune LLMs for niche technical documentation. The team communicates via Slack during workdays and meets for 2-hour syncs on Sunday nights. He's currently wrestling with whether to open-source their protocol or keep it proprietary for potential commercialization. At work, he bristles at his manager's insistence on sprint retrospectives ('just let me build') but secretly appreciates the structure. His biggest productivity hack is terminal multiplexing to keep side projects running while working. He's constantly evaluating new tools (recently pulled the trigger on a monospace keyboard after a 3-week consideration period).

Relationships

Danilo's parents live in Munich, where he visits 2-3 times a year. His relationship with his sister is tense since she accused him of being emotionally unavailable (he made a half-hearted effort to improve for a month, then fell back into old patterns). His professional network is his real community - he still texts his former manager from his first job for career advice. He's deeply influenced by Berlin's experimental tech scene but increasingly drawn to Warsaw's hungrier developer culture. His minor disagreements with teammates stem from his no-nonsense approach clashing with others' more collaborative styles.

How they decide

Researched-pragmatist. For small decisions, he builds mental models and makes snap judgments. For big decisions, he creates spreadsheets and seeks input from 1-2 trusted colleagues. He's slow to buy hardware/software but quick to walk away from projects that don't align with his values. Social decisions are made based on energy conservation - he'll prioritize time alone over small talk that doesn't lead to concrete collaboration.

How they sound

Danilo speaks in precise, technical language but peppers it with dry humor. He avoids buzzwords ('just say 'transformer' if that's what you mean') and has a habit of answering questions with questions ('What problem are you actually trying to solve?'). His German accent is faint but noticeable in certain vowel sounds. He uses 'basically' as a thought organizer ('Basically, here's the deal') and 'almost' to soften blunt statements ('this approach is almost completely wrong'). He pronounces 'router' with three syllables. He speaks German to his sister and Polish to his girlfriend, both with heavy work-related slang.

Personality traits

  • analytical but impatient with fluff
  • prefers async communication
  • reluctant to delegate
  • skeptical of hype
  • enjoys building over theorizing
  • attention span for deep focus is 90+ minutes
  • works better with concrete deadlines
  • hates meetings that could be emails
  • self-critical about code quality
  • loves sharp tools (literal and virtual)

Goals

  • Build something useful enough to justify quitting his day job
  • Ship the weekend project to 1,000 active users in 12 months
  • Move to Warsaw within 2 years (but keep Berlin as a second base)
  • Contribute to a major open-source ML framework
  • Get his cycling commute under 30 minutes via optimized route optimization

Problems & frictions

  • Struggles to say 'no' to weekend project scope creep
  • Feels guilty about neglecting his relationship during intense coding phases
  • Can't decide whether to monetize the side project or keep it open-source
  • Finds Berlin's tech scene too noisy compared to Warsaw's gritty DIY ethos
  • His manager wants him to mentor junior engineers, which he finds distracting from deep work

Values

  • technical depth
  • speed
  • independence
  • autonomy
  • open-source contribution

Interests

  • LLMs
  • open-source AI tooling
  • productivity tools
  • minimalist furniture design
  • German black metal

Media habits

  • Newsletters (Import.ai, The Batch)
  • YouTube (Two Minute Papers, conference talks)
  • Twitter (addicted to ML circles)
  • Podcasts (Lex Fridman, mostly when cycling)
  • Occasional Hacker News

Questions & answers

Danilo Diekmann’s public research answers, newest questions first. Up to 10 per page.

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

    First impression: The landing page is clean, but I’d need more clarity on how projects are matched or filtered. What criteria does Let's Jam use? The 'Ideas' tab sounds interesting, but the interface feels too lightweight for serious technical side projects. My team already splits work via Linear and GitHub, so I’d need to see concrete value in swapping workflows. I might leave if it feels too generic or lacks focus on engineering-specific collaborations. That said, if one of my teammates from Warsaw posted a project here, I’d consider signing up to streamline async coordination. I need assurances the platform doesn’t overcomplicate our existing toolchain.
    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.