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

John Illing

John Illing

Analytics engineer at a product company with multiple database sources

Full-depth AI personas

Why this persona fits the audience

Works on a 4-person data team in Berlin supporting product and finance reporting. Switches between PostgreSQL for internal apps and ClickHouse for event data, then validates transformations and chart outputs. Uses DataGrip daily and spends time comparing query results across environments.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Analytics Engineer
  • Income: €80k
  • Education: M.S. in Information Systems
  • Company size: startup (50–100 employees)
  • Years in role: 3
“'I don’t care how fast your SQL client opens. What I care about is how many clicks it takes to get from ‘Hmm, that’s odd’ to ‘Ah, it was the user_id filter all along,’'”

John Illing grew up in Bonn, where his father’s work in IT exposed him to databases early. He studied Information Systems in Aachen, earning his M.S. while interning at a Berlin startup—that’s where the SaaS bug bit. At 26, he moved to Berlin permanently, part of the inflow of developers chasing Europe’s post-pandemic tech boom. His current role is his first full-time analytics engineering job, but he’s already outgrown the title. He’s built the APIs, written the DAGs, and debugged the dashboards that keep his company’s metrics reliable. His desk is a shrine to efficiency: a mechanical keyboard for fast typing, a trackball mouse to avoid wrist strain, and a second monitor just for terminal tabs. His biggest professional win was convincing engineering to allocate 20% of his time to ‘data reliability debt’—a term he coined, though it’s now used company-wide. Lately, he’s been frustrated by how much of his day is spent context-switching between PostgreSQL and ClickHouse. He’s tried every SQL client in the Berlin tech scene, and none satisfy his need for speed and precision. Personally, he’s comfortable alone but not lonely. His weekends are a mix of cycling, vinyl flipping, and tinkering with self-hosted tools (he recently replaced his smart light’s cloud service with open-source software). He’s saving aggressively for a trip to Japan, where he plans to rent a bike and map every kilometer of the Shimanami Kaidō. Status-wise, he’s content but unfulfilled—he knows he’s ready to lead, but the role hasn’t opened up. Until then, he’ll keep optimizing his own workflow, one query at a time.

Background & daily life

A day in their life

John’s weekday starts at 5:30 AM with a preset coffee maker and a pre-staged cycling route on his Garmin. By 8:30, he’s at his standing desk, reviewing yesterday’s failing data pulls. His morning ritual is a 10-minute ‘sanity check’ of stale queries—every database, every environment, to ensure nothing broke overnight. Around 10 AM, he meets with the product team to review a new dashboard design, where he points out three edge cases in their EventStream data. Lunch is usually at his desk, eaten in silence while he debugs a PostgreSQL join that’s running 20% slower than it did last month. Post-work, he cycles to a local bike shop to price replacement brake pads, then stops at a record store for a 90s ambient album he’s been eyeing. By 8 PM, he’s back at his apartment, knee-deep in a ClickHouse optimization project he’ll never finish.

Lifestyle

John lives in a compact Berlin apartment with a standing desk rigged with three monitors, a mechanical keyboard, and a bike frame hanging from the ceiling. His mornings start with a 15km road ride before work, then he cycles home past the Spree to shower and change. He eats mostly self-cooked meals but keeps a stash of instant ramen for late-night debugging sessions. On weekends, he occasionally attends underground synth nights or hosts a small group of friends for vinyl listening (his collection leans toward 80s Italian electronic). Financially, he’s stable but avoids unnecessary spending—his last big purchase was a used road bike with disc brakes. Socially, he’s more comfortable in niche tech circles than large gatherings, though he’s a regular at a local data engineering meetup where he’s known for his sharp but fair feedback on others’ setups.

Work life

John works at a Berlin-based SaaS startup where his tiny data team juggles PostgreSQL for internal reporting and ClickHouse for event data. His days rotate between writing transformations, validating outputs, and debugging discrepancies between staging and production. Recently, he automated his team’s dullest task—a monthly finance report—by scripting a ClickHouse-to-Grafana pipeline that reduced his workload by 10 hours. He’s frustrated by how often he has to manually compare query results between environments, a ritual he performs 3–4 times daily. His coworkers respect his rigor but tease him for muttering ‘This should be a button’ whenever he spots inefficiency. He’s currently lobbying for a better SQL client (his team’s DataGrip licenses are a pain to manage), but the engineering team vetoed budget for it last quarter.

Relationships

John’s closest friend is his college roommate, a backend engineer in Munich who they pair up with over Discord to vent about work. His family in Bonn visits twice a year, usually coinciding with his birthday. He’s distant from his younger sister, who studies environmental science and texts him angry threads about data privacy violations. At work, he’s known as the ‘glue’ for his team—quiet but reliable, the person who remembers past queries and fixes others’ broken pipelines. His romantic life is sparse; his last relationship foundered over his preference for evenings spent optimizing SQL over spontaneous dates.

How they decide

John researches meticulously but trusts his gut for quick fixes. He’ll spend hours comparing tools before committing, but if a query breaks, he’ll hack a solution in 30 seconds. He’s skeptical of marketing claims and prefers to infer a product’s quality from its changelog. Peer recommendations carry weight, but he’s more likely to adopt a tool because ‘it feels right’ after a 10-minute trial than because someone tweeted about it.

How they sound

John speaks in clipped sentences, often pausing to rephrase for precision. He avoids jargon in favor of concrete terms (e.g., ‘That’s not a bottleneck, that’s a missing index’) and has a dry sense of humor about his own perfectionism (‘I spent 2 hours making my WHERE clauses prettier. Worth it.’). He hates empty corporate phrasing (e.g., ‘That’s not scalable, it just works’). His accent is unplaceably German, with the occasional English verb he mispronounces without realizing it.

Personality traits

  • detail-obsessed
  • hates manual repetition
  • prefers keyboard shortcuts to clicking
  • skeptical of vendor buzzwords
  • self-critical about code
  • enjoys tinkering
  • avoids small talk
  • dislikes ambiguity
  • loyal to tools that save time
  • secretly enjoys optimizing SQL queries for fun

Goals

  • Move into a leadership role without sacrificing technical depth
  • Build a personal data dashboard for his cycling metrics (currently tracking pace, heart rate, and route efficiency manually)
  • Save enough to take a 4-week solo trip to Japan next year (planned down to the train passes)
  • Contribute to an open-source data tool in his spare time (currently blocked on choosing between two projects)

Problems & frictions

  • His team’s database access is siloed, forcing him to switch contexts constantly
  • Lacks time to explore new tools—has a backlog of five SQL editors he wants to test
  • Struggles to say ‘no’ when asked to take on ad-hoc reporting for non-data teams
  • His apartment’s outlets are poorly placed, forcing a rat’s nest of cables to power all his gear
  • Invariably runs out of coffee during long debugging sessions

Values

  • precision
  • automation
  • shared context
  • efficiency
  • learning

Interests

  • data modeling
  • cycling
  • synth music
  • DIY home automation
  • tech meetups

Media habits

  • Tech Twitter (X)
  • Remote work blogs
  • Spotify playlists (ambient synth, post-rock)
  • Data engineering newsletters
  • YouTube coding tutorials

Questions & answers

John Illing’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Data Peek (https://www.datapeek.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 try Data Peek, but two things hold me back. First, the ClickHouse beta label makes me nervous—I can’t have my event-data workflows unstable. Second, the Command Palette (⌘K) shortcut overlaps with a critical function in DataGrip, which would disrupt my flow. I save 10 hours monthly with ClickHouse optimizations, so switching tools needs to be risk-free. I rely on stability more than AI or speed. At €80k, I’d consider $5/month for a pilot, but zero for unproven features in my workload.
    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.