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

Aymonde Bourgeois

Aymonde Bourgeois

Engineering manager at B2B fintech

Full-depth AI personas

Why this persona fits the audience

At a 28-person fintech SaaS company in Paris, she reviews the SSO/SAML work done by one backend engineer and keeps a lightweight checklist in Notion for enterprise-login requests. The team uses a mix of homegrown auth code, manual account provisioning, and email threads with support and sales.

  • Age: 38
  • Location: Paris, France
  • Occupation: Engineering Manager
  • Income: €85k salary
  • Education: Engineering degree
  • Company size: 28
  • Years in role: 4
“Every line of code, every process, is a small piece of the larger structure we're building; it needs to be sound, or the whole edifice risks a tremor.”

Born and raised in Lyon, Aymonde Bourgeois developed an early aptitude for logic and problem-solving, nurtured by a family that valued education and meticulousness. She pursued a degree in Computer Engineering at INSA Lyon, where she excelled in areas requiring rigorous analytical thinking. After graduating, she spent several years at a larger software firm in France, gaining experience in backend development and team leadership within established corporate structures. Seeking a more dynamic environment and greater impact, she moved to Paris five years ago and joined her current fintech SaaS company, initially as a senior engineer before being promoted to Engineering Manager two years later. She's married to Antoine, an academic, and they share a quiet life focused on intellectual pursuits and cultural enrichment. Aymonde is deeply invested in the stability and integrity of her team's work. She recently pushed back against a rushed request to implement a temporary workaround for enterprise SSO, advocating instead for a more robust, standardized solution, even if it meant delaying other feature work. This decision reflects her core belief in building for the long term, prioritizing technical debt reduction and compliance over short-term gains. She sees time as a resource to be managed with precision, much like code, and views financial stability as a prerequisite for personal and professional freedom. Her approach to work is characterized by a quiet determination to build reliable systems and foster a healthy, productive team environment, seeing her role as much about nurturing talent as it is about technical architecture.

Background & daily life

A day in their life

Aymonde's typical weekday begins around 7:00 AM with a quick scan of overnight alerts and urgent emails. After a shared breakfast with her husband, she commutes to the office by Vélib' bike, often listening to a podcast. Her workday is structured around stand-ups, code reviews – currently focused on a backend engineer's implementation of SAML assertion validation – and a series of one-on-one meetings with her direct reports. Mid-morning, she'll field requests from sales regarding a potential enterprise client's SSO requirements, updating a Notion checklist with specific points. Lunch is usually a quick affair at her desk or a brief walk. The afternoon might involve architectural discussions, planning the next sprint, or delving into support tickets related to account provisioning, before cycling home around 6:30 PM.

Lifestyle

Aymonde lives in a well-organized, light-filled apartment in the 15th arrondissement with her husband, a university researcher. Their routine is structured but not rigid; weekday evenings often involve a shared meal, perhaps followed by her practicing piano or them discussing current events. Weekends are for longer bike rides along the Seine or through Bois de Boulogne, visiting exhibitions at the Louvre or Musée d'Orsay, or exploring a new wine bar. She manages her finances carefully, prioritizing long-term security and occasional indulgences like a rare bottle of Burgundy. Social life is centered around a small group of close friends and occasional family gatherings.

Work life

As an Engineering Manager at a growing fintech SaaS company, Aymonde juggles technical oversight with team management. Her days are a blend of code reviews, one-on-ones, sprint planning, and addressing ad-hoc requests, particularly from sales and support regarding enterprise client needs. The current manual process for handling SSO/SAML integrations and account provisioning is a persistent, low-level stressor. She advocates for more robust, automated solutions, but balancing this with immediate feature delivery and the company's lean resources is a constant challenge. She relies heavily on Notion for tracking, Asana for task management, and Slack for communication, though she often finds herself buried in email threads for critical cross-departmental issues.

Relationships

Aymonde is married to Antoine, who shares her appreciation for quiet evenings and intellectual pursuits. Her immediate team of backend and frontend engineers relies on her for technical direction and support. She maintains a professional but cordial relationship with her sales and customer support counterparts, though she sometimes finds their urgent requests for custom authentication setups challenging to manage effectively.

How they decide

Aymonde is a deliberate and research-oriented decision-maker. She gathers data, weighs pros and cons carefully, and seeks input from trusted colleagues or subject matter experts. While she values team consensus, the final decision often rests on her assessment of long-term maintainability, security implications, and alignment with company goals. She is risk-averse when it comes to critical infrastructure changes and prefers incremental, well-tested improvements over radical overhauls.

How they sound

Speaks clearly and precisely, with a measured cadence. Her tone is generally calm and professional, even when discussing complex technical issues. She avoids overly casual slang or jargon, preferring clear, direct language. When explaining problems, she tends to focus on systemic issues and process improvements rather than blaming individuals. She uses French sentence structures naturally, occasionally employing slightly more formal vocabulary than might be common in a purely English-speaking tech environment.

Personality traits

  • methodical
  • detail-oriented
  • responsible
  • calm under pressure
  • analytical
  • patient
  • organized
  • slightly reserved
  • pragmatic
  • focused

Goals

  • To build a highly competent and cohesive engineering team.
  • To transition the company's authentication infrastructure from ad-hoc solutions to a scalable, secure, and maintainable system.
  • To achieve a better work-life balance by optimizing team processes and reducing reactive firefighting.
  • To contribute to the company's sustainable growth and market reputation.
  • To complete her collection of Chopin nocturnes on the piano.

Problems & frictions

  • The current patchwork of homegrown auth code and manual processes for enterprise clients is error-prone and time-consuming.
  • Lack of standardized procedures for onboarding enterprise customers leads to inconsistencies and potential security gaps.
  • Balancing the need for architectural improvements with the pressure to ship new features quickly.
  • Managing technical debt while ensuring team morale and preventing burnout.
  • Navigating internal stakeholder expectations (sales, support) that often don't align with technical realities.
  • The constant overhead of resolving support tickets related to user access and authentication.

Values

  • stability
  • compliance
  • precision
  • team health
  • efficiency
  • scalability

Interests

  • piano
  • urban cycling
  • museums
  • wine
  • French literature
  • cryptography theory

Media habits

  • Reads technical blogs (e.g., Hacker News, InfoQ)
  • Listens to podcasts on engineering leadership and economics during commute
  • Follows select French news outlets (Le Monde, Les Échos)
  • Subscribed to a few curated newsletters on SaaS growth and security
  • Occasional browsing of art history sites

Questions & answers

Aymonde Bourgeois’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Show HN launch (205 pts, 2020-03-17): the product – APIs for enterprise features like SSO/SAML. Site shows pricing/signup. 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 us is the manual effort and potential for error in provisioning enterprise SSO. Sales comes with requests, often with tight deadlines for potential clients. We have homegrown scripts and rely heavily on email threads with support and sales to manage it. It's time-consuming and introduces inconsistencies. I've tried to streamline it with a Notion checklist, but it doesn't address the core process. It feels like a recurring overhead that distracts from core product development, and I worry about the security implications of our current ad-hoc approach. I haven't even begun to quantify the exact hours lost, but it's significant.
    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.