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

Abdon Leclercq

Abdon Leclercq

Technical product manager coordinating schema changes

Full-depth AI personas

Why this persona fits the audience

Technical product manager at a 3-engineer marketplace startup in Paris; tracks database entities, reviews proposed schema edits with the backend lead, and keeps a shared ER sketch so support and analytics use the same terms.

  • Age: 34
  • Location: Paris, France
  • Occupation: Technical Product Manager
  • Income: €78k
  • Education: Master's in Information Systems
  • Company size: Startup (approx. 15 employees total)
  • Years in role: 4
“Every piece of data has a story, and our job is to make sure we understand that story correctly before we start writing new chapters.”

Abdon Leclercq grew up in a quiet suburb of Lyon, the son of a librarian and an accountant. His early fascination with how systems worked, from intricate clockwork mechanisms to early computer programs he encountered through school, led him to pursue a Master's in Information Systems at Université Claude Bernard Lyon 1. He was always the student who asked 'why' and 'how,' meticulously dissecting problems. After graduating, he spent two years at a large IT consultancy in Paris, where he learned the importance of structured processes and documentation, but found the corporate environment stifling. Seeking more direct impact, he joined his current marketplace startup three years ago. His role as Technical Product Manager is a natural fit, allowing him to leverage his analytical skills and passion for elegant data design. He sees the company's database as the core of its being, and his work ensuring its integrity and evolution is paramount. He views his salary of €78k as comfortable, allowing for his modest lifestyle and frequent, well-planned European travels, but he's always mindful of financial prudence. He doesn't chase status but values recognition for his technical expertise and his ability to foster clear communication within the team. His current focus is on refining the schema to support the rapid onboarding of new service providers, a task requiring careful negotiation between speed and long-term maintainability.

Background & daily life

A day in their life

Abdon's typical weekday begins with a review of overnight system logs and key performance indicators at home, followed by a brisk metro ride to the startup's office in Le Marais. His morning is usually dedicated to sync meetings with the engineering team and refining user stories for upcoming sprints. Post-lunch, he dives into reviewing schema change proposals from Sylvie, meticulously updating the ER diagram and documenting any implications. He spends a significant portion of his afternoon in cross-functional alignment sessions, clarifying data points for the support team or defining metrics with the analytics specialist. He aims to wrap up by 7 PM, often grabbing a quick bite from a boulangerie on his way home.

Lifestyle

Abdon enjoys a structured yet vibrant Parisian life. He typically wakes around 7 AM, making a strong espresso before checking tech news. His apartment, while small, is meticulously organized, reflecting his professional habits. Evenings are often spent cooking simple, healthy meals or exploring different neighborhoods on his bicycle. Weekends might involve visiting a museum, meeting friends for a casual apéro, or planning his next budget-conscious trip abroad, often to lesser-known European cities. He prioritizes experiences over material possessions, finding satisfaction in continuous learning and efficient living.

Work life

As the sole technical product manager at his startup, Abdon is the linchpin for data architecture. His days are a constant juggle between strategic planning, feature definition, and the nitty-gritty of database schema management. He works closely with the backend engineering lead, a seasoned developer named Sylvie, to vet every proposed change, ensuring it aligns with the product roadmap and doesn't introduce technical debt. His primary tool for collaboration is a shared, cloud-based ER diagram tool, which he diligently updates, making it the single source of truth for everyone from customer support to data analysts. The pressure is on to maintain data integrity while enabling rapid feature development for their growing marketplace.

Relationships

Abdon maintains strong professional relationships with Sylvie, the backend lead, and the two junior engineers, valuing their technical insights. His closest friendships are with a small group of university friends, often meeting for dinners or weekend excursions. His family, who live in Lyon, are supportive but often express concern about the demanding startup world. He tends to trust Sylvie's technical judgment implicitly and values candid feedback from his colleagues.

How they decide

Abdon is a research-heavy decision-maker, especially concerning technical matters. He gathers information from multiple sources, consults with relevant stakeholders (particularly Sylvie), and weighs pros and cons methodically. While he values efficiency, he's not impulsive and will advocate for a well-considered approach, often creating documentation or diagrams to solidify his understanding and present his findings.

How they sound

Speaks with a clear, measured cadence, favoring precise language. His tone is generally professional and earnest, often employing technical terms naturally within conversation. He avoids overly casual slang but might use subtle French idioms. When explaining technical concepts, he aims for clarity and thoroughness, sometimes using analogies. He rarely raises his voice, preferring calm, reasoned arguments.

Personality traits

  • Analytical
  • Organized
  • Communicative
  • Detail-oriented
  • Proactive
  • Collaborative
  • Methodical
  • Enthusiastic about technology
  • Slightly perfectionistic
  • Resourceful

Goals

  • Achieve a senior product leadership role within the next five years
  • Contribute to building a robust, scalable data infrastructure for the company
  • Travel to at least two new countries each year
  • Maintain a healthy work-life balance
  • Become proficient in a new programming language for personal projects

Problems & frictions

  • Balancing the immediate needs of feature requests with long-term data maintainability
  • Ensuring consistent data terminology and understanding across non-technical teams (support, marketing)
  • The limited bandwidth of a small engineering team means architectural decisions have long-lasting impact
  • Finding time for deep technical research amidst daily operational demands
  • The challenge of communicating complex data concepts to stakeholders with varying technical backgrounds

Values

  • shared understanding
  • cross-functional alignment
  • pragmatic execution
  • data integrity
  • scalability

Interests

  • product strategy
  • database design
  • travel
  • open-source software
  • photography
  • French cinema

Media habits

  • Reads Hacker News and technical blogs daily
  • Listens to podcasts on product management and technology during commutes
  • Follows industry leaders on LinkedIn and X (formerly Twitter)
  • Watches documentary films on streaming services
  • Occasional perusal of travel magazines

Questions & answers

Abdon Leclercq’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Navicat Data Modeler (https://www.navicat.com/en/products/navicat-data-modeler): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The pricing model is presented as a monthly subscription, which is a bit unusual for a tool like this. I'd expect a perpetual license to be an option. For a 'no-brainer' price, I'd look for something in the range of €10-€15 per month, considering our startup's budget. If it were significantly more, say €30-€40 monthly, I'd have to evaluate if the advanced AI features or the collaboration tools justify the cost. Ultimately, for my role, managing the ER sketch and reviewing schema edits is key, so I'd need to see a clear ROI against my current manual process. The maximum I would pay per month is $20.
    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.