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

Felix Metz

Felix Metz

Engineering manager at a B2B SaaS company

Full-depth AI personas

Why this persona fits the audience

Oversees a 5-engineer team shipping a 9,000-page customer portal and docs site. Keeps accessibility and HTML checks in the release workflow using axe-core CI jobs, browser validations, and a shared spreadsheet for exceptions and follow-ups.

  • Age: 45
  • Location: Austin, US
  • Occupation: Engineering manager
  • Income: $180k
  • Education: Bachelor's degree in software engineering
  • Company size: Mid-sized (approx. 250 employees)
  • Years in role: 5
“The real challenge isn't just building it, it's building it right, consistently, and sustainably.”

Felix Metz has been steeped in software development since his undergraduate days at the University of Texas at Austin. His early career was marked by hands-on coding in various startups, where he developed a deep appreciation for robust engineering practices and the long-term consequences of technical shortcuts. Around 15 years ago, he transitioned into management, finding he had a knack for guiding teams and fostering a productive work environment. He joined his current B2B SaaS company eight years ago, drawn by its stable growth and the opportunity to work on complex, user-facing products. Over the past five years as an Engineering Manager, he's taken ownership of the customer portal and its accompanying documentation site, a massive undertaking that now spans 9,000 pages. Felix is driven by a strong sense of responsibility and a need for order. He sees his role as a guardian of quality and a facilitator of his team's growth. He implemented the current accessibility and HTML checks in the CI pipeline two years ago, after a particularly painful production incident involving non-compliant forms. He meticulously maintains a shared spreadsheet for tracking exceptions and follow-ups, a process he finds both essential and frustratingly manual. He invests his personal time and income into his home and family, prioritizing stability and predictable returns on his investments, both financial and personal. He views time as a finite, precious resource, and his decisions are often guided by how they will impact his ability to maintain control and predictability in his work and personal life.

Background & daily life

A day in their life

Felix's day typically starts around 7:00 AM, helping his kids get ready for school before diving into emails and reviewing overnight CI reports. His mornings are often packed with team stand-ups and one-on-one meetings. After lunch, which he usually eats at his desk while catching up on industry news, he dedicates time to reviewing code, planning upcoming sprints, or troubleshooting issues that arose from the latest checks. He might spend an hour analyzing the spreadsheet of accessibility exceptions or coordinating with the product team on upcoming feature requirements. His workday usually wraps up around 5:30 PM, though he's known to occasionally log back in if a critical issue arises.

Lifestyle

Felix lives in a comfortable, slightly sprawling house in a suburban neighborhood of Austin with his wife and two teenagers. His evenings and weekends are often a blend of family time, tending to his increasingly sophisticated home automation setup (think smart lighting, temperature control, and security systems that he's meticulously programmed), and firing up the smoker for a weekend BBQ with friends. He's financially responsible, with a focus on long-term security, and generally avoids unnecessary risks. His social life is steady, built around a core group of long-time friends and colleagues.

Work life

As an engineering manager, Felix's days are a careful balancing act between strategic oversight and tactical execution. He spends a significant portion of his time in meetings – stand-ups, planning sessions, one-on-ones with his team of five engineers, and cross-functional syncs. His current focus is on stabilizing the release process for their massive customer portal and documentation site, ensuring that accessibility and HTML standards are consistently met. This involves reviewing CI job outputs, managing the exception spreadsheet, and advocating for technical debt reduction. The pressure to ship features while maintaining quality is a constant undercurrent.

Relationships

Felix is married to Sarah, a graphic designer, and they navigate raising two teenagers, Liam and Chloe, together. His relationship with his team is one of supportive leadership; he trusts their technical abilities but insists on process and quality. He has a small, close-knit circle of friends, many of whom he met in college or at previous jobs, and they often connect over shared hobbies or occasional weekend get-togethers.

How they decide

Felix is a deliberate and research-oriented decision-maker. He weighs pros and cons carefully, often seeking out data, best practices, and the opinions of trusted colleagues before committing. He prefers solutions that offer long-term stability and predictability over quick fixes. When evaluating new processes or tools, he'll consider scalability, maintainability, and how well it integrates with existing workflows.

How they sound

Speaks with a clear, measured cadence. Generally avoids jargon when speaking to non-technical stakeholders but uses precise technical terms with his team. His tone is calm and reassuring, even when discussing challenging problems. He's not prone to hyperbole or strong emotional outbursts, preferring direct and factual communication. He might use phrases like 'Let's look at the data,' 'My primary concern here is...', or 'We need to ensure this is robust.'

Personality traits

  • meticulous
  • organized
  • reliable
  • detail-oriented
  • supportive
  • calm under pressure
  • methodical
  • averse to chaos
  • pragmatic

Goals

  • Achieve a more predictable and less error-prone release cycle for the customer portal.
  • Mentor junior engineers on his team to develop stronger technical and problem-solving skills.
  • Deepen his understanding of product strategy to better align engineering efforts with business goals.
  • Maintain a healthy work-life balance and be present for his family.
  • Contribute to open-source projects in his spare time.

Problems & frictions

  • The sheer scale and complexity of the 9,000-page portal make comprehensive quality assurance challenging.
  • Balancing the demand for new features with the need to address technical debt and accessibility issues.
  • The manual tracking of exceptions in the shared spreadsheet is time-consuming and prone to oversight.
  • Ensuring consistent adherence to accessibility and HTML standards across a large, evolving codebase.
  • Finding time for deep technical work amidst managerial responsibilities.

Values

  • predictability
  • ownership
  • efficiency
  • mentoring
  • quality
  • stability

Interests

  • home automation
  • product management
  • classic rock
  • BBQ
  • strategy board games
  • golang

Media habits

  • Listens to tech podcasts during his commute
  • Reads industry blogs (e.g., Hacker News, specific SaaS tech sites)
  • Watches YouTube channels on home automation and DIY projects
  • Follows curated newsletters on software engineering best practices
  • Occasional use of LinkedIn for professional networking

Questions & answers

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

  1. What would stop you from trying Rocket Validator (https://rocketvalidator.com) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    This sounds promising for tackling our 9,000-page portal's accessibility and HTML checks. My main hesitation is understanding how 'credits' work in practice for a site of our scale. We currently rely on our CI jobs and a manual spreadsheet for tracking exceptions, which is time-consuming. I'd need to see how Rocket Validator streamlines that process, particularly if it can integrate with our existing workflow without adding significant overhead. A $50/month price point might be workable if it demonstrably reduces the manual effort and improves our release predictability.
    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.