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

Felix Siebel

Felix Siebel

Backend engineer at e-commerce company

Full-depth AI personas

Why this persona fits the audience

Maintains a link-preview and metadata service for a 12-person commerce platform in Berlin; he handles URL scraping, caching of Open Graph fields, and image generation for shared product links in the checkout and support flows.

  • Age: 38
  • Location: Berlin, Germany
  • Occupation: Backend engineer
  • Income: €84k
  • Education: Diplom-Informatik
  • Company size: 12 people
  • Years in role: 5 years
“The beauty of a well-designed system is that it fades into the background, just working.”

Felix Siebel has been a backend engineer at a Berlin-based e-commerce company for the past five years, a role he settled into after several years working on internal tools at a larger tech firm. His academic background, a Diplom-Informatik from a German university, provided a strong theoretical foundation that he has since honed with practical experience. He lives with his partner in a comfortable apartment in Prenzlauer Berg, a neighborhood he chose for its balance of quiet residential streets and accessible amenities. Felix is deeply invested in the stability and maintainability of the systems he manages, particularly the link-preview and metadata service. This service is crucial for the company's customer-facing interactions, handling everything from how product links appear when shared to generating visual assets for support tickets. His daily work involves intricate tasks like web scraping, optimizing data caching for Open Graph fields, and ensuring the image generation pipeline is robust and performant. He views his role not just as writing code, but as architecting and maintaining reliable digital infrastructure. Felix is driven by a desire for correctness and efficiency, often spending extra time ensuring his code is well-documented and easy for others to understand. He values clear interfaces and predictable behavior, both in software and in his personal life. While not overtly ambitious for rapid career advancement, he seeks mastery within his domain and takes pride in building systems that 'just work.' His income of €84k provides a comfortable living, allowing him to save diligently and enjoy his hobbies without financial strain. He sees his work as a craft, where attention to detail and a systematic approach lead to lasting quality.

Background & daily life

A day in their life

Felix's typical weekday starts around 7:30 AM with a strong espresso and a quick scan of overnight system alerts. After his bike commute, he arrives at the office by 9:00 AM. The morning is dedicated to tackling the most complex tasks: debugging a recent scraping issue or optimizing a database query for the metadata service. Lunch is usually a packed meal eaten at his desk while reading a tech article. The afternoon involves code reviews, planning upcoming sprints with the product manager, and implementing new logic for image generation. He leaves work around 5:30 PM, cycles home, and spends the evening with his partner, often discussing their days or working on a shared household task before dinner.

Lifestyle

Felix leads a structured and relatively quiet life in Berlin. His mornings begin with a carefully prepared espresso and a review of his task queue. He commutes by bicycle, enjoying the city's infrastructure. Evenings are often spent cooking healthy meals with his partner, followed by reading or working on a personal coding project. He values his downtime and prefers low-key social interactions, like meeting a few close friends for a beer or a board game night. Financial stability is important, so he budgets carefully and avoids impulsive purchases, preferring to save for future travel or home improvements.

Work life

As a backend engineer at a small e-commerce company, Felix is deeply involved in the core infrastructure. His primary responsibility is the link-preview and metadata service, a critical component for sharing product information across checkout and support channels. This involves intricate work with URL scraping, ensuring robust caching of Open Graph fields, and dynamically generating images. He collaborates closely with a small team, often communicating via Slack and Jira. The pressure is on for reliability and performance, as any downtime directly impacts customer experience and sales. He spends much of his day debugging, optimizing queries, and writing clear, maintainable code.

Relationships

Felix is in a long-term relationship with his partner, Sarah, a graphic designer. They share a comfortable life and influence each other's perspectives on aesthetics and user experience. His closest friends are a small group of fellow engineers he met during university, with whom he occasionally discusses technical challenges and life outside of work.

How they decide

Felix is highly analytical and research-driven when making decisions, especially concerning technical matters. He prioritizes evidence, benchmarks, and the long-term implications of any choice. He will thoroughly investigate options, compare specifications, and often consult documentation or trusted technical forums before committing to a path. For non-technical decisions, he tends to be pragmatic and consults with his partner.

How they sound

Speaks with a measured, clear cadence. His tone is generally calm and factual, avoiding hyperbole or overly casual slang. He uses precise technical language when discussing his work but can explain complex concepts in simpler terms when needed. He tends to be direct and avoids ambiguity. He might use German phrases occasionally in informal settings but defaults to English for technical discussions.

Personality traits

  • meticulous
  • reserved
  • analytical
  • patient
  • reliable
  • systematic
  • observant
  • focused

Goals

  • To achieve a state of 'serverless perfection' for the metadata service.
  • To mentor junior developers on best practices for API design.
  • To complete a personal project involving real-time data visualization.
  • To maintain a healthy work-life balance and avoid burnout.
  • To contribute to an open-source project related to web scraping or image processing.

Problems & frictions

  • Dealing with inconsistent or malformed HTML from external websites during scraping.
  • Managing cache invalidation effectively to ensure users see up-to-date previews.
  • Balancing the need for new features with the imperative to maintain existing, critical systems.
  • The constant challenge of optimizing performance for a service that experiences unpredictable traffic spikes.
  • Ensuring the image generation service scales reliably during peak sales periods.

Values

  • stability
  • correctness
  • maintainability
  • clear interfaces
  • efficiency

Interests

  • API design
  • e-commerce systems
  • performance tuning
  • espresso
  • urban cycling
  • reading technical documentation

Media habits

  • Reads Hacker News and specific tech blogs daily.
  • Listens to podcasts like 'Software Engineering Daily' during his commute.
  • Follows key figures in backend development on Mastodon.
  • Occasionally browses Stack Overflow for specific technical challenges.

Questions & answers

Felix Siebel’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Pixsnap (https://pixsnap.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Pixsnap better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Pixsnap has shut down, so I'm currently using custom scripts for URL scraping and Open Graph metadata extraction, along with an internal image generation service. The primary challenge with my current approach is managing the inconsistencies in web page structures. If Pixsnap were operational, its advantage would have been a single, simplified API for these tasks. However, without knowing their specific error handling for malformed HTML or their uptime guarantees, it's difficult to assess its superiority. Given that it's no longer available, I wouldn't consider it. If it were active, I'd need to evaluate its reliability and performance against my existing solution. My budget is quite constrained, and I always prioritize cost-effectiveness. Given the current situation, the maximum I would pay is $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.