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

Alcide Petit

Alcide Petit

freelance software engineer

Full-depth AI personas

Why this persona fits the audience

Splits his week between contract work and a side project that sells a Sheets add-on to marketing teams. He maintains the add-on as a standalone codebase and handles auth, billing, release notes, and versioning himself.

  • Age: 30
  • Location: Paris, France
  • Occupation: Freelance software engineer
  • Income: €78k
  • Education: MSc Computer Science
  • Company size: 1 (self-employed)
  • Years in role: 7
“The elegance of a solution isn't just in its functionality, but in how cleanly it integrates and how little maintenance it requires down the line.”

Alcide Petit, a 30-year-old freelance software engineer based in Paris, embodies a modern iteration of the independent developer. After completing his MSc in Computer Science, he eschewed traditional corporate paths, drawn instead to the autonomy and intellectual stimulation of freelancing. His professional life is bifurcated: a significant portion of his week is dedicated to contract roles, primarily building web applications and internal tools for French businesses using a stack of React, Node.js, and PostgreSQL. This provides a stable income stream and exposes him to diverse business problems. However, his true passion lies in his side project, a Google Sheets add-on tailored for marketing teams. He meticulously built it from the ground up, handling every aspect – from user authentication and Stripe billing integration to release notes and version control – as a standalone codebase. This venture, driven by his value of compounding code reuse and a desire for simplicity in user experience, represents his entrepreneurial spirit. He recently decided to implement a more robust testing suite for his add-on after a minor bug caused unexpected data issues for a few users, reinforcing his commitment to quality and reliability. Alcide views time as his most valuable asset, meticulously allocating it between client demands and his own ambitious projects. He’s not driven by status, but by the satisfaction of building robust, efficient solutions and the freedom to choose his own path.

Background & daily life

A day in their life

Alcide's day typically begins at 7:00 AM. After a quick breakfast and a strong coffee, he dedicates two to three hours to his Sheets add-on project, often tackling the most complex coding challenges first. By 10:00 AM, he switches gears to his freelance contract work, which usually involves attending virtual meetings with clients, writing code, and responding to project-related emails. Lunch is a simple affair, often eaten at his desk while scanning tech news. The late afternoon is a continuation of contract work, wrapping up around 6:00 PM. Evenings are for personal learning, reading industry blogs, or sometimes experimenting with a new library, usually followed by a light dinner and an early bedtime.

Lifestyle

Alcide lives a structured, albeit somewhat solitary, life in Paris. He rents a compact apartment that doubles as his workspace, prioritizing functionality over space. His income allows for comfortable living, but he's frugal, preferring to invest in his side project or save rather than splurge on luxuries. His routine is clockwork: early mornings for focused coding on his add-on, followed by contract work, and evenings dedicated to learning or unwinding with a tech podcast. Socially, he's not one for large gatherings, preferring deep conversations with a few close friends over casual networking.

Work life

His workdays are a carefully managed balancing act. Mornings are sacred, dedicated to his Sheets add-on – debugging a tricky authentication flow or sketching out a new feature. Afternoons are for client-facing contract work, often involving full-stack development for small to medium-sized French startups, using technologies like React and Node.js. The pressure comes from juggling these two demanding streams, ensuring client deadlines are met while still making progress on his passion project. He works alone, relying on his own expertise for everything from development to deployment and customer support, which can be time-consuming.

Relationships

Alcide maintains a small circle of close friends, mostly fellow developers he met during university or through online communities. They occasionally discuss technical challenges and share insights, but rarely collaborate directly. His family lives in a smaller town in the Loire Valley, and he visits them a few times a year. He doesn't have a romantic partner currently, dedicating most of his free time to his work and personal development.

How they decide

Alcide is a research-heavy and pragmatic decision-maker. He meticulously evaluates options, weighing pros and cons based on technical feasibility, long-term maintainability, and efficiency. He's not easily swayed by hype and prefers to rely on his own judgment and well-documented solutions. When facing a significant choice, he'll often prototype a solution or read through extensive documentation before committing.

How they sound

Speaks with a precise, slightly formal tone, reflecting his analytical nature. His cadence is measured, and he rarely uses slang. He tends to articulate technical concepts clearly and avoids overly emotional language. When discussing his work, he's pragmatic and focused on the technical aspects, often using phrases like 'from an architectural standpoint' or 'the core challenge here is.'

Personality traits

  • analytical
  • meticulous
  • self-disciplined
  • resourceful
  • introverted
  • pragmatic
  • independent
  • detail-oriented

Goals

  • Achieve recurring revenue of €5k/month from his Sheets add-on within two years.
  • Refactor the core logic of his add-on for even greater reusability.
  • Become fluent in Rust for potential future backend projects.
  • Maintain a healthy work-life balance without sacrificing progress on his goals.
  • Potentially hire a freelance VA to handle customer support for the add-on within three years.

Problems & frictions

  • The overhead of managing all aspects of his add-on (auth, billing, releases) is becoming increasingly burdensome.
  • Finding time for deep, uninterrupted work on his side project amidst contract demands.
  • Dealing with edge cases and user support requests for a product he built alone.
  • The inherent unpredictability of freelance client work impacting his planning.
  • Occasional imposter syndrome when facing complex technical challenges outside his immediate expertise.

Values

  • autonomy
  • intellectual curiosity
  • efficiency
  • elegance in code
  • financial independence

Interests

  • side projects
  • Apps Script
  • startup newsletters
  • competitive programming
  • exploring new JS frameworks
  • minimalist design

Media habits

  • Reads Hacker News daily
  • Subscribes to several developer newsletters (e.g., TLDR, Software Lead Weekly)
  • Listens to tech podcasts during his commute (e.g., Syntax, Lex Fridman)
  • Watches YouTube tutorials on specific tech topics
  • Occasionally browses Reddit's r/programming

Questions & answers

Alcide Petit’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of ShipAddons (https://shipaddons.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make ShipAddons 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).

    Currently, I manage all the authentication, billing, and release aspects of my Sheets add-on myself. It's a significant overhead, but it gives me complete control. ShipAddons appears to automate much of this, which is appealing given the time I spend on these tasks. The idea of a pre-built system for auth and Stripe is certainly tempting. However, my current setup is a standalone codebase; I would need to understand how integrating a boilerplate like ShipAddons would affect that structure and my existing logic. The one-time purchase model is interesting, but I'd need to see if the feature set truly justifies the cost over continuing to build and maintain it myself, especially considering potential future modifications. I don't have a fixed budget for this kind of tool, but I would consider up to $50 per month if it significantly reduced my current workload and offered long-term value.
    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.