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

Côme Mathieu

Côme Mathieu

Backend engineer

Full-depth AI personas

Why this persona fits the audience

Works on backend services from a MacBook Pro at home and in a small office rotation, has external monitors on both desks, and still uses the built-in display menus rather than a paid brightness tool.

  • Age: 35
  • Location: Paris, France
  • Occupation: Backend engineer
  • Income: €78k salary
  • Education: MSc in Computer Science
  • Company size: Series B fintech startup (approx. 120 employees)
  • Years in role: 6
“A system should work so smoothly that you forget it exists until it doesn't, and then you spend all night wondering why the lights went out.”

Côme Mathieu, 35, is a seasoned backend engineer navigating the complexities of modern fintech infrastructure in Paris. Born in Lyon and educated with an MSc in Computer Science from ENSIMAG, he spent his early career in traditional banking before pivoting to the agile world of startups six years ago. His current role involves maintaining critical payment processing services, a responsibility that demands unwavering attention to detail and a deep understanding of distributed systems. Côme's professional philosophy is rooted in stability and efficiency; he believes that software should be a reliable engine rather than a source of constant anxiety. This mindset extends to his hardware choices. While he possesses a powerful MacBook Pro, he remains steadfast in his preference for the native macOS display menus over third-party utilities like MacGlow, viewing them as potential points of failure in an otherwise streamlined workflow. He has tried various manual brightness adjustments across his dual-monitor setups but finds the inconsistency frustrating, yet he hesitates to adopt new tools without a proven track record of non-disruptive integration. At home, his workspace is a testament to his ergonomic interests, featuring a custom-built standing desk and a carefully curated keyboard, yet he admits that the transition between his home and office lighting conditions often requires tedious manual recalibration. Financially, Côme is prudent, earning a solid €78k which allows him to live comfortably but not extravagantly. He views money as a tool for security and freedom, allocating resources toward health, education, and high-quality equipment that lasts. His life is a carefully balanced equation of intense intellectual labor and deliberate rest, driven by a desire to build well-structured systems in both code and daily living.

Background & daily life

A day in their life

Côme wakes up at 6:30 AM, immediately checking the weather and his calendar before moving to the kitchen to brew a single-origin pour-over coffee. After a quick shower and dressing in a pre-selected outfit of dark trousers and a merino wool sweater, he cycles to the RER station, listening to a podcast on system design patterns. By 9:15 AM, he is logged into his workstation at the office, syncing his local environment and reviewing overnight CI/CD logs. The morning is dedicated to deep work on the payment gateway refactoring, where he writes unit tests and optimizes database queries. Lunch is a sandwich eaten while standing, followed by a brief walk around the block to clear his head. Afternoon meetings are kept to a minimum, focusing on architectural reviews with the DevOps team. Around 5:30 PM, he packs up, cycling back home as the light shifts. Dinner preparation begins promptly at 7:00 PM, involving chopping vegetables and managing a slow-cooked stew. Evenings are reserved for reading technical blogs or tinkering with his home server, winding down with a glass of wine and a documentary before bed by 11:00 PM.

Lifestyle

Côme lives in a functional, uncluttered apartment in Paris's 11th arrondissement, where every object has a designated place. His mornings begin before 7:00 AM with a precise espresso routine using a V60 dripper, a ritual he guards fiercely against interruption. He commutes via bike or RER depending on the weather, valuing the predictability of public transit over driving. In the evenings, he disconnects completely to cook elaborate meals for his partner, often experimenting with fermentation or slow-cooking techniques that require hours of unattended time. Financially, he is conservative; he maxes out his employer's retirement plan and avoids impulse buys, preferring to invest in high-quality, long-lasting gear like ergonomic chairs or mechanical keyboards rather than trendy gadgets. Socially, he maintains a tight circle of three close friends, meeting monthly for board games or hiking, preferring deep conversation over large networking events.

Work life

As a backend engineer at a growing fintech startup, Côme spends his days architecting microservices and debugging race conditions in distributed systems. He rotates between his home office in Paris and the company's small hybrid workspace twice a week. At both locations, he utilizes a dual-monitor setup: a MacBook Pro paired with two large Dell UltraSharp displays. He is deeply invested in maintaining a stable environment, spending significant time configuring his dotfiles and ensuring his shell environments are identical across machines. His workdays are characterized by long stretches of deep focus interrupted only by stand-ups and code reviews. He prefers asynchronous communication via Slack and Jira over unnecessary meetings, often blocking out 'focus hours' where he disables notifications entirely. The pressure comes from the need to maintain zero-downtime during transaction spikes, requiring him to be constantly vigilant about system reliability.

Relationships

Côme shares a domestic life with his partner, Sophie, an elementary school teacher who balances his structured nature with spontaneity. They rely on each other for emotional stability, though they have distinct social circles. His professional influence comes primarily from his engineering manager and a few peers from university, with whom he exchanges technical insights weekly. He is not active in broad online communities, preferring niche forums where discussions remain focused and substantive. Family ties are strong but distant; he calls his parents in Lyon once a week, adhering to a strict schedule he finds comforting.

How they decide

Côme employs a highly analytical and cautious decision-making process. He rarely acts on impulse, instead gathering data, reading documentation, and consulting trusted peers before committing to a change. He values evidence over marketing claims and is skeptical of 'new and improved' features unless they solve a specific, documented inefficiency. Once he identifies a solution that meets his criteria for stability and utility, he moves quickly to implement it, but the vetting phase can be lengthy. He dislikes making decisions based on peer pressure or trends, preferring to trust his own assessment of the system's needs.

How they sound

Côme speaks in a measured, calm baritone, favoring precise vocabulary over slang. His cadence is steady, rarely rushing his sentences even when explaining complex logic. He tends to use conditional phrasing ('It might be possible that...') rather than absolute statements, reflecting his low neuroticism and high conscientiousness. He avoids hyperbole and emotional exaggeration, keeping conversations grounded in facts and practical outcomes. When discussing technology, he defaults to French but seamlessly integrates English terminology common in the industry, such as 'latency', 'throughput', and 'deployment pipeline'. He does not use filler words like 'um' or 'like' frequently, as he plans his thoughts before speaking.

Personality traits

  • methodical
  • quietly persistent
  • pragmatic
  • detail-oriented
  • stoic under pressure
  • minimalist
  • solitary but collaborative when needed
  • systematic thinker
  • value-conscious
  • disciplined

Goals

  • Achieve senior engineer status within the next two years without sacrificing personal time
  • Reduce technical debt in the payment processing service to improve deployment frequency
  • Build a fully automated home lab for learning Kubernetes and edge computing
  • Maintain a consistent fitness routine despite a sedentary job
  • Save enough capital to purchase a vacation property in Provence by age 40

Problems & frictions

  • Frustration with inconsistent monitor brightness settings when switching between macOS and Linux VMs
  • Difficulty finding quiet spaces in the open-plan office during peak coding hours
  • The physical strain of adjusting display angles manually multiple times a day due to lighting changes
  • Managing context switching between legacy Java services and new Go implementations
  • Occasional latency issues when accessing internal tools from home networks outside Paris
  • Balancing the desire to optimize workflows with the risk of over-engineering simple solutions

Values

  • stability
  • well-structured systems
  • low friction
  • technical elegance
  • work-life boundaries

Interests

  • distributed systems
  • home office ergonomics
  • specialty coffee
  • mechanical keyboards
  • urban cycling

Media habits

  • French tech newsletters (Les Echos Tech, FrenchWeb)
  • Hacker News and Reddit r/programming
  • Spotify coding playlists (Lo-fi / Jazz)
  • YouTube deep dives on system architecture
  • Local meetup groups for Rust and Go developers

Questions & answers

Côme Mathieu’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at MacGlow (https://lovi.sh/macglow): 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 fact that this tool offers lifetime access for $9 is very appealing. It solves a real annoyance I face daily, switching between my home and office setups, and manually adjusting brightness. If it works reliably and integrates seamlessly without causing any system instability, that price would be a no-brainer for me. I wouldn't consider paying more than $9 for lifetime access, as it's a utility, not a core part of my development workflow. Monthly subscriptions for such tools don't make sense to me.
    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.