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

David Olbrich

David Olbrich

Staff backend engineer at a B2B SaaS company

Full-depth AI personas

Why this persona fits the audience

Maintains Java and Kotlin services for a 120-person SaaS company in Berlin, including internal admin tools, API endpoints, and incident fixes. He uses JetBrains IDEs and a limited GitHub Copilot setup, but most of his workflow is still review-heavy and grounded in existing engineering standards.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Staff Backend Engineer
  • Income: €118,000 annual salary
  • Education: M.S. in Software Engineering
  • Company size: 120
  • Years in role: 8
“A good system isn't just what works today, but what you can confidently modify tomorrow. That's why I'll take a well-tested, boring solution over an 'innovative' one that leaks memory under load.”

David Olbrich, 41, grew up in Hamburg where his father worked as an electrical engineer and his mother as a civil servant. His fascination with systems began early - at 14 he built a weather station that collected data via radio telemetry. After completing his Master's in Software Engineering at RWTH Aachen, he worked briefly for a data processing startup before joining his current company during their Series B funding round. David's engineering approach was shaped by two formative experiences: a catastrophic failure of a distributed ledger prototype in 2010 (which taught him the importance of redundancy) and his divorce in 2016 (which hardened his no-overcommitting policy). At work, he's respected for his meticulous architectural decisions but occasionally clashes with product managers who prioritize feature velocity. His current focus is on modernizing the company's event-driven architecture while grooming the next generation of engineers. Though he regularly expresses skepticism about AI tools, he maintains a private GitHub repository experimenting with machine learning for anomaly detection in time series data. Financially stable but frugal, David invests primarily in German index funds and considers his coffee equipment the only justifiable luxury. He abandons most personal projects after 6 months of active development, maintaining about 15 'abandoned but functional' repositories on GitHub. His greatest fear is becoming an architect who no longer writes production code. Weekend trips to Köln or Münster on Deutsche Bahn trains provide his only true relaxation.

Background & daily life

A day in their life

6:15 AM: David's empty espresso cup waits on his workbench as he completes his morning run through Volkspark. Back home, he methodically grinds 20g of freshly roasted beans and prepares a V60 pourover. 7:30 AM: A quick shower, then his commute on the Endurace through Berlin's side streets. 8:45 AM: He opens his IntelliJ workspace and scans overnight build failures. 9:30 AM: Team standup - David adds one item to the agenda: 'Kafka broker performance degradation in staging'. 11:00 AM: Deep work on incident response documentation. 1:00 PM: Lunch at his desk - a pre-packed mason jar of quinoa salad. 2:30 PM: Debugging a connection leak in the inventory service. 4:15 PM: Coffee break at his workstation (he brought beans from home). 5:30 PM: Code review for a junior engineer's pull request. 6:45 PM: Wrap-up meeting with the CI/CD team. 7:30 PM: Ride home, stopping for fresh whole milk at the Turkish market. 8:00 PM: Home-roasted beans in the hand grinder, dialing in the extraction. 9:00 PM: Personal project time - experimenting with CRDTs in Go. 11:30 PM: Bed, leaving the espresso machine ready for tomorrow.

Lifestyle

David lives in a spacious Altbau apartment in Prenzlauer Berg he renovated himself, complete with a dedicated coffee nook containing a Slayer V3 espresso machine and a Lido E-T hand grinder. His mornings begin at 6:15 AM with slow brewed pour-over coffee, followed by a 10km run through Volkspark Friedrichshain. He rides his 2017 Canyon Endurace to work most days, rain or shine. Weekends alternate between hacking on distributed systems theory papers and day trips on Deutsche Bahn to nearby cities. His social life revolves around a small group of engineers from his university days; they meet every two months at 'Das Kraftwerk' for technical discussions over kimchi nachos. He maintains a strict no-lunch-meetings policy after being burned by legacy system on-call rotations early in his career.

Work life

At work, David manages the core inventory synchronization services at a Berlin-based procurement SaaS company. His team maintains Java microservices that handle requests between vendor APIs and internal data stores, with occasional Kotlin projects for new integrations. He blends JetBrains IDEs with a carefully configured GitHub Copilot (he disabled the chat features entirely) and maintains rigid code standards for his team. Recent projects include migrating a critical batch processing system to Kafka Streams and leading an initiative to reduce mean-time-to-resolution for P1 incidents. He's skeptical of AI tools that promise 'instant productivity gains' but has been experimentally using Copilot for boilerplate generation during late-night on-call shifts. His biggest pain point is the increasing pressure to integrate with newer cloud services while maintaining backwards compatibility with legacy systems.

Relationships

David maintains a small but tight-knit social circle from his university days in Aachen, where he met his closest friends during long nights debugging C++ projects. He's in contact with his parents in Hamburg every other Sunday for a long phone call discussing German politics and his mother's ongoing battle with the city's bureaucracy. His ex-wife (a former frontend engineer) lives in the same neighborhood, and they co-parent their 12-year-old daughter through a carefully arranged schedule that avoids overlapping commitments. While civil, neither shows much interest in rekindling their technical debates over distributed systems vs. eventual consistency.

How they decide

David makes deliberate, research-heavy decisions after consulting multiple technical sources and considering long-term implications. He's skeptical of marketing claims and prefers to test tools in controlled environments before production. Once convinced of a solution's technical merits, he commits fully but remains open to feedback from peers with complementary expertise. Financial considerations rarely override technical ones in his decision-making process.

How they sound

David speaks in measured, precise sentences with occasional sarcastic undertones. He uses dry humor when frustrated but avoids outright complaining. Prefers technical jargon over colloquialisms ('We have a race condition here, not 'it's acting weird''). Never says 'disruptive' unironically, avoids business speak like 'solution' or 'leverage'. When excited about a technical concept, his speech accelerates slightly but never loses its methodological cadence. Uses 'regrettably' when conceding to business requirements.

Personality traits

  • Methodical in code reviews - leaves thorough but unsentimental comments
  • Prefers stable over cutting-edge tools
  • Dislikes unscheduled meetings but attends them with stoic professionalism
  • Purchases high-end espresso gear but brews it meticulously at home
  • Keep local trains over of flights for work trips to Hamburg/Munich
  • Maintains personal GitHub projects as long-term experiments
  • Speaks with measured authority when debugging incidents
  • Avoids office small talk but bonds over technical challenges
  • Keeps workspace meticulously organized (color-coded tabs in IDE)
  • Will debug a system for hours rather than file a ticket

Goals

  • Develop a production-grade implementation of CRDTs for eventual consistency
  • Transition to a leadership-track role without losing hands-on engineering time
  • Perfect his natural espresso extraction method (currently at 7.8% yield)
  • Complete a Rails-to-Go migration for his personal project tracker
  • Reduce his team's incident response time by 20% through better observability

Problems & frictions

  • Struggles with legacy monolith decisions made before his tenure
  • Finds modern developer tools often prioritize speed over stability
  • Dislikes the trend toward 'AI-augmented' workflows that assume perfect contextual awareness
  • Battles with team members who prefer to 'just ship' over architectural consistency
  • Frustrated by infrastructure providers that change APIs without deprecation cycles

Values

  • Engineering rigor
  • Maintainability
  • Predictable delivery
  • Autonomy in workflow
  • Longevity of systems

Interests

  • Distributed systems architecture
  • Specialty coffee brewing
  • Open-source tooling contributions
  • German rail travel (prefers DB over flying)

Media habits

  • Reads Hacker News and Lobste.rs daily
  • Listens to podcasts during commutes (Software Engineering Daily, The Changelog)
  • Subscribes to Kubernetes and Java technical blogs
  • Occasionally watches F1 (but never Formula E)

Questions & answers

David Olbrich’s public research answers, newest questions first. Up to 10 per page.

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

    From first glance, I appreciate Cursor's obvious focus on streamlining development workflows—something I wrestle with daily. The demo showing agents handling tasks like building dashboards is compelling, but I'm skeptical about the autonomous claims. My team's coding standards are stringent; I'd need proof that Cursor can adhere to our existing Kafka integration patterns and Java style guides without requiring constant oversight. The 'Download for macOS' call-to-action is clear, but I'd leave if I couldn't quickly assess how it integrates with IntelliJ, my primary IDE. What's unclear is whether it supports Kotlin beyond boilerplate or handles legacy system modifications—our biggest headache. The mention of 'handing off tasks' makes me nervous about overreliance on AI for production code. I might sign up for a demo if I could bring a specific incident response use-case (like our recent Kafka broker degradation) to test its triage capabilities.
    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.