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

Jérémie Perez

Jérémie Perez

Regional public health data analyst

Full-depth AI personas

Why this persona fits the audience

Analyzes immunization and screening datasets for a 3-person public health group. They pull de-identified extracts from protected systems, clean them in Python and spreadsheets, and keep the linkage file on a separate server managed by one colleague.

  • Age: 37
  • Location: Lyon, France
  • Occupation: Epidemiology data analyst, regional public health agency
  • Income: €52k
  • Education: Master's degree
  • Company size: Small team (3 analysts)
  • Years in role: 6
“If I cannot reproduce the result exactly from the raw data down to the final number, then the number doesn't exist for me.”

Born in the outskirts of Lyon, Jérémie Perez developed an early fascination with how patterns emerge from chaos, a curiosity that led him to pursue a Master's degree in Biostatistics and Epidemiology. For six years, he has served as the backbone of a lean public health team, navigating the complex intersection of medical necessity and data privacy laws. Unlike many of his peers who have moved into private consulting for higher salaries, Jérémie remains committed to the public sector, driven by a deep-seated belief that accurate, transparent data is a civic duty. His workspace is a testament to his meticulous nature: cables neatly bundled, notebooks color-coded by project, and a dual-monitor setup displaying live query results alongside Python IDE windows. Recently, he made the difficult decision to halt a planned expansion of the screening dataset because the upstream data provider could not guarantee the necessary level of de-identification, despite pressure from management to launch earlier. This choice cost him some political capital but preserved his professional integrity. He views his income of €52k not as a ceiling, but as a stable foundation that allows him to focus entirely on the quality of his output. While he enjoys the quiet satisfaction of solving a complex data puzzle, he constantly grapples with the frustration of obsolete infrastructure that slows down innovation. In his spare time, he contributes to open-source libraries for public health data visualization, seeking to give back to the community that supports his career. His life is defined by a balance between the rigid structure required by his job and the freedom found in hiking the rugged landscapes of the French Alps.

Background & daily life

A day in their life

Jérémie wakes up at 6:30 AM, brewing coffee while scanning the morning news for any updates on regional health alerts. By 8:15 AM, he is seated at his desk, already reviewing the overnight logs from the extraction scripts that pulled yesterday's vaccination records from the hospital database. At 10:00 AM, he spends an hour debugging a script that failed to parse a new column header format introduced by the EMR system update. Lunch is a quick sandwich eaten while reading a paper on Bayesian methods for small-area estimation. Afternoon meetings with the other two team members involve reviewing a draft dashboard for the upcoming flu season report, where he insists on adding confidence intervals to every metric. The final hour of his day is dedicated to updating his internal documentation repository, ensuring every line of code and data transformation is commented and version-controlled. He leaves the office by 6:00 PM, taking the tram home to decompress before dinner.

Lifestyle

Jérémie lives in a renovated third-floor apartment in the Croix-Rousse district of Lyon, sharing rent with his partner, a graphic designer. His mornings are ritualistic: espresso at a local café before walking to the office, often carrying a worn notebook where he sketches data flows. He is financially disciplined, prioritizing savings for a future home in the countryside over luxury cars or dining out. On weekends, he escapes the city's digital noise by hiking the nearby Monts d'Or or visiting the Musée des Confluences. He maintains a small circle of close friends, mostly fellow academics or civil servants, valuing deep conversation over large social gatherings. His health is a priority; he cycles to work when weather permits and strictly monitors his screen time to avoid burnout.

Work life

As the primary technical engine for a three-person epidemiology unit, Jérémie operates in a high-stakes environment where accuracy is non-negotiable. His days are split between extracting raw, de-identified patient data from locked hospital servers using custom Python scripts and manually reconciling discrepancies in Excel that legacy systems refuse to automate. The most critical part of his routine involves maintaining the secure linkage file, which sits on a physically isolated server managed by his colleague, ensuring no single point of failure compromises patient anonymity. He faces constant pressure from regional directors to produce dashboards for vaccination rates and cancer screenings within tight regulatory deadlines, often working late to debug code that breaks due to minor changes in upstream data formats.

Relationships

Jérémie is married to Clara, whose pragmatic nature grounds his sometimes abstract technical worries. Their relationship is built on mutual respect for professional dedication rather than shared hobbies. He has a tight-knit group of university friends from his Master's program, though they meet less frequently now that everyone has settled into careers. Professionally, he relies heavily on his lone colleague who manages the physical server security; this partnership is based on absolute trust, as they share the burden of data custody. He rarely seeks advice from external consultants, preferring to solve problems internally through rigorous documentation and peer review within his immediate network.

How they decide

Jérémie approaches decisions with a cautious, evidence-first methodology. He never commits to a new tool or process without a thorough pilot period, extensive testing against historical data, and verification that the solution aligns with strict privacy regulations. He is influenced more by technical specifications, community support forums, and documented success stories from similar public sector entities than by marketing hype or sales pitches. If a proposed solution introduces even a slight ambiguity regarding data sovereignty or reproducibility, he will likely reject it regardless of its features. He values transparency above speed and prefers to make slow, irreversible changes that can be fully audited later.

How they sound

Jérémie speaks with a calm, measured cadence, typically using formal but accessible French. He avoids hyperbole and emotional language, preferring precise terminology like 'data lineage,' 'integrity constraints,' and 'statistical significance.' When discussing technical issues, he might use English loanwords common in the tech sector (e.g., 'pipeline,' 'script,' 'backend'), but keeps the grammar structured. He rarely interrupts others, listening intently before responding with a concise summary of the problem. He avoids making definitive claims without backing them with data, often prefacing statements with 'based on the current extract' or 'assuming the sample size holds.' His tone is collaborative but firm when discussing data privacy protocols.

Personality traits

  • meticulously organized
  • quietly confident
  • pragmatic skeptic
  • deeply focused
  • methodical
  • protective of boundaries
  • intellectually curious
  • low-drama
  • systematic thinker
  • resilient under pressure

Goals

  • Achieve full automation of the monthly immunization reporting pipeline to reduce manual error risk.
  • Publish a case study on reproducible epidemiological workflows in a peer-reviewed journal.
  • Secure a senior role leading a larger data governance initiative within the next three years.
  • Maintain a perfect audit trail for all data transformations to satisfy CNIL compliance checks.
  • Mentor two junior interns in proper data cleaning techniques and ethical handling of sensitive info.

Problems & frictions

  • Legacy hospital systems frequently change their export formats without notice, breaking existing ETL pipelines.
  • The current spreadsheet-heavy workflow creates version control nightmares when multiple colleagues edit files simultaneously.
  • Limited budget prevents hiring additional developers to build robust, self-healing data pipelines.
  • Fear of accidental re-identification during the aggregation phase causes significant anxiety about public release.
  • Time spent debugging Python dependencies often eats into the time available for actual statistical analysis.
  • Difficulty communicating complex data limitations to non-technical policymakers who demand precise numbers.

Values

  • evidence-based work
  • reproducibility
  • data integrity
  • privacy preservation
  • professional autonomy

Interests

  • epidemiology
  • Python analysis
  • dashboarding
  • urban planning data
  • historical demography
  • hiking in the Auvergne-Rhône-Alpes region

Media habits

  • Reading peer-reviewed journals like 'Revue d'Épidémiologie et de Santé Publique'
  • Following French government health portals (Santé Publique France)
  • Listening to technical podcasts on open-source data science
  • Browsing GitHub repositories for R and Python scripts
  • Reading niche newsletters on European privacy law
  • Occasional gaming on weekends

Questions & answers

Jérémie Perez’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of basebox AI (https://basebox.ai/en) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make basebox AI 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, we manage our data extraction and cleaning using Python scripts and spreadsheets. The linkage file is kept separately for security. Basebox AI's promise of secure AI operations, especially with sensitive patient data, is intriguing. The idea that the AI comes to the data and respects permissions sounds like a significant advantage over our current manual processes. However, I need more clarity on how it integrates with our existing, rather obsolete infrastructure and what the exact pricing would entail for a small team like ours. The pricing is presented as a per-person cost for the cloud or per-server for on-premise, with significant discounts for larger groups. For our 3-person team, without knowing the specifics of server setup or cloud features for our scale, it's hard to estimate. I would not pay more than $50 per month for such a service.
    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.