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

Hanno Beushausen

Hanno Beushausen

frontend engineer at SaaS

Full-depth AI personas

Why this persona fits the audience

Maintains a marketing site and docs hub for a 20-person SaaS company, exporting screenshots and illustration files on macOS and converting them to WebP during release prep. He often uses CLI scripts or built-in Mac tools, and keeps a small checklist for asset names and dimensions.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Frontend engineer
  • Income: €72k
  • Education: Master's in computer science
  • Company size: 20 people
  • Years in role: 3
“I don't believe in 'good enough' for code, but I've learned to accept 'good enough' for all the other things that don't actually matter. ”

Hanno Beushausen grew up in Dresden, where his computer science education began with dismantling his father's old Commodore 64. After earning his Master's in Berlin, he joined a buzzy SaaS startup where he's now the sole frontend engineer—an unexpected but stable position that pays well enough for his frugal habits. His perfectionism is both his strength and downfall: while his marketing site runs flawlessly, his personal projects often linger in 'almost done' limbo. Hanno's workflow revolves around minimizing friction, which is why he's constantly tweaking his build scripts and terminal aliases. His current obsession is optimizing the marketing team's asset conversion process, though he's held off investing in a dedicated tool because 'it should just work with what's already here.' He's skeptical of 'shiny new things' but maintains a secret spreadsheet of tools to investigate when his budget window opens. His apartment is a shrine to efficiency: labeled cable sleeves, keyboard macros for common tasks, and a wall-mounted iPad that displays his GitHub notifications. Recently, he've spent two weekends rebuilding his personal website to reduce its bundle size, though he'll never admit how many hours the project actually consumed. Hanno sees his job as temporary—he's applying to smaller product-focused companies where frontend work might finally get the attention it deserves. His ideal life involves a condo with enough space for a standing desk setup, a partner who won't question his 'precise' coffee brewing routine, and enough time to contribute to open-source projects without feeling guilty. Status symbols mean nothing to him; the only thing he openly bragged about was the time he optimized a build pipeline to cut deployment time by 42%.

Background & daily life

A day in their life

6:30 AM: Alarm buzzes. Hanno presses snooze once, then forces himself vertical. 7:00 AM: Gym session—he follows a rigid 45-minute routine he's modified slightly from a Reddit thread. 8:30 AM: Arrives at work, skips small talk, and opens a terminal with muscle memory. 9:00 AM: Standup where he listens more than he speaks. 10:30 AM: Debugging a responsive layout that's failing in Safari. 12:00 PM: Almond butter sandwich at his desk while reading Hacker News. 1:00 PM: Marketing asks last-minute WebP conversions for a blog post—he sighs and fires up ImageMagick, cursing slightly that he hasn't automated this yet. 3:00 PM: Deep work on upgrading React state management, interrupted by a Slack from a product manager about

Lifestyle

Hanno lives in a compact but bright Kreuzberg apartment with a standup desk setup where he codes nights and weekends as needed. His routine is rigid: 6:30 AM wakeup, 7 AM gym, coffee at Café Krass before work. He bike commutes rain or shine, wearing noise-cancelling headphones to avoid small talk. Weekends are split between side projects (currently optimizing a personal WebP batch script) and neighborhood poses at local dive bars where he meets a tight group of German and expat tech friends. Health is maintained through compulsive snack tracking and a standing desk setup that's already triggered a mild thoracic strain. Money is saved aggressively for a future condo down payment, though he occasionally splurges on high-end audio gear. His social life exists in pockets—dinner with his mother in Steglitz once a month, sporadic gaming sessions with childhood friends, and occasional dates via OkCupid where he immediately filters for

Work life

As the sole frontend engineer at a Berlin-based SaaS startup, Hanno manages the marketing site and internal documentation hub with a mix of frustration and quiet pride. His days revolve around React updates, design system tweaks, and the never-ending cycle of conversion tasks. Currently, he's wrestling with a legacy component that won't adapt to a responsive grid—something he's secretly resolved to completely rewrite in his next maintenance window. His workflow relies heavily on CLI tools, TextMate for quick edits, and a carefully curated set of Alfred workflows. He dismisses corporate Slack banter but maintains professional relationships with the three other engineers through structured standups. The real pain point is asset conversion for releases: maintaining consistent WebP sizes and naming conventions across marketing materials feels like a constant game of whack-a-mole. The company's recent push for biweekly feature releases has him considering writing a full automation script over the weekend, though he'd never admit the extra hours to his manager. His keyboard shortcut muscle memory is so advanced that new interns sometimes stare when he navigates the terminal without looking.

Relationships

Hanno's family consists of his mother, a retired schoolteacher in Steglitz, and an older brother who works in finance in Frankfurt but only calls for life advice. His childhood friends from Dresden visit twice a year for board game marathons and pretzel-stuffed weekends. At work, he maintains polite distance from the CEO, a former coworker of his mother's, but values the various product managers who at least attempt to grasp technical constraints. His closest connection is with the operations engineer who shares his love for obscure terminal tricks. He trusts exactly three people to test his personal scripts without explanation. His dating life is a series of polite ghosts—mostly due to his tendency to discuss CI/CD pipelines on first dates, which usually ends poorly.

How they decide

Methodically comparative, Hanno researches tools exhaustively before committing, often spending hours benchmarking alternatives against his current workflow. He dislikes impulsive changes and gives new solutions a probationary period. Once convinced, he adopts tools comprehensively, integrating them into his existing systems. Peer recommendations carry weight, especially from trusted engineers on Indie Hacker. He's slow to abandon tools but will do so abruptly if they cause friction. Financial considerations are secondary to functional reliability—he'd pay for a tool that saves him 30 minutes a week without hesitation.

How they sound

Hanno speaks in measured, precise sentences with occasional German syntax slipping through. He avoids tech jargon with non-engineers but doesn't dumb things down. His cadence is slightly monotone when explaining technical concepts. He uses humor sparingly and only with people he trusts. Will say ' ,

Personality traits

  • Systematic and methodical in workflows
  • Dislikes redundancy, favors reusable solutions
  • Quietly competitive about efficiency
  • Prefers tools that don't force him to adapt
  • Tolerates inconvenience for 24 hours before fixing it
  • Values self-sufficiency over community support
  • Skeptical of hype-driven tools
  • Enjoys occasional terminal tinkering as a stress relief
  • Moderately political but avoids workplace debates
  • Secretly proud of his dotfiles configuration

Goals

  • Build a reusable asset conversion pipeline before Q3
  • Move to a smaller tech company with more frontend focus
  • Save €20,000 for a downpayment on a Kreuzberg condo by 2025
  • Contribute to an open-source build tool before next year
  • Reduce his personal website's render-blocking resources
  • Find a long-term partner who understands his need for solo coding Sundays

Problems & frictions

  • Legacy components that won't adapt to modern CSS
  • Marketing team's last-minute asset requests before releases
  • Terminal tab hoarding that makes his workspace unnavigable
  • Finding the right balance between automation and immediate performance
  • His back hurts but he won't buy an ergonomic chair that isn't matte black
  • Feeling undervalued compared to the two backend engineers in raises
  • His Okay delivery-man bike is starting to creak but he'd rather spend the money on a new monitor
  • His mother keeps texting him about
  • his salary and he lies about bonuses to avoid the conversation.

Values

  • practical engineering
  • clean workflows
  • low friction
  • automation-first
  • precision

Interests

  • React
  • build tooling
  • design systems
  • terminal tools
  • minimalist UI design
  • macOS automation

Media habits

  • Hacker News
  • YouTube tech deep dives
  • Indie Hacker
  • Medium engineering blogs
  • optional small German podcasts

Questions & answers

Hanno Beushausen’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: the product is a free macOS App for converting images to WebP. 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 problem for me is the inconsistency in WebP output quality and naming conventions across releases. Right now, I rely on ImageMagick and manual scripting, which burns 30-45 minutes per release cycle. It’s not just the time—it’s the mental friction of double-checking dimensions, denominations, and whether Q factors are optimized. I tried a Hacker News-recommended CLI tool last year, but it batched conversions too aggressively, and the naming autoreplace logic was brittle. My current workflow 'works,' but it’s the kind of thing that ought to cost me 10 minutes tops. (And yes, I’ve considered SquareTube’s $19/month WebP app, but I hesitate: is it actually more reliable than my scripts, or just UI sugar?)
    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.