Why this persona fits the audience
Supports manufacturing and finance databases for a mid-sized plant; he exports from MySQL, checks tables in PostgreSQL, and loads CSV/XML files from shared drives into staging schemas. Most of his work is a mix of scripts, DBeaver, and spreadsheets, with low appetite for extra tooling unless it is clearly practical.
- Age: 46
- Location: Lyon, France
- Occupation: IT Systems Administrator
- Income: €52k gross
- Education: Licence Professionnelle in Systems Administration
- Company size: Mid-sized industrial plant (approx. 300 employees)
- Years in role: 12
“Data doesn't lie, but the way we handle it can certainly confuse us all.”
Anthelme Brunet is a 46-year-old IT Systems Administrator residing in Vénissieux, a suburb of Lyon, France. Born into a working-class family, he developed an early affinity for mechanics and logic, which naturally steered him toward a Licence Professionnelle in Systems Administration. For the past twelve years, he has been the backbone of the IT infrastructure at a mid-sized manufacturing plant, managing the delicate data flows between the factory floor and the corporate finance office. His professional identity is defined by reliability; he is the person who ensures that when the auditors arrive, the numbers match perfectly. Technologically, Anthelme operates in a pragmatic bubble. He favors robust, proven tools like MySQL, PostgreSQL, and DBeaver, often augmenting them with custom Python scripts rather than adopting flashy new platforms. He views software as a means to an end, not a hobby. His recent decision to migrate a portion of their legacy XML archives to a new staging schema was driven solely by the need for compliance, not innovation. He spends his free time engaging in tactile activities—repairing old cars in his driveway, carving wood in his garage, and tending to a vegetable garden that feeds his family. These hobbies provide a necessary contrast to his screen-bound profession, allowing him to see the physical results of his labor. Financially, he earns €52,000 annually, a salary he finds adequate but not lavish, prompting a lifestyle focused on saving and home ownership. He is wary of unnecessary expenses, whether in tech subscriptions or consumer goods. His personality reflects a blend of high conscientiousness and low openness; he respects tradition and established processes, finding comfort in predictability. While he is not particularly outgoing, he is respected by his peers for his steady demeanor and deep knowledge of the system's inner workings. Anthelme is not looking for a revolution in his work life; he simply wants the tools to do his job faster, safer, and with fewer headaches.
Background & daily life
A day in their life
The alarm goes off at 6:15 AM. After a quick coffee and checking the weather for his morning commute, Anthelme leaves for the plant. By 8:00 AM, he is logged in, reviewing the overnight batch jobs. If the MySQL export failed, he immediately checks the logs, a familiar anxiety that usually resolves quickly. Around 10:00 AM, he meets with the finance coordinator to discuss a new report format that requires a different XML structure; he notes the requirements and promises to test a prototype by Friday. Lunch is eaten at his desk while reading an article on SQL optimization techniques. The afternoon is dedicated to scripting: he spends two hours refactoring a Python script that cleans up the daily CSV imports from the warehouse servers. He spends the last hour verifying the data integrity in DBeaver, ensuring no duplicates exist in the staging schema. At 5:30 PM, he shuts down his workstation, double-checks that all services are running, and heads home. The evening is reserved for his garden or a film, providing a necessary disconnect from the digital world.
Lifestyle
Anthelme lives a structured life in the suburbs of Lyon, balancing a demanding career with a sanctuary of manual labor at home. His weekends are dominated by woodworking projects in a cluttered but organized garage, where he builds furniture for his children's rooms or repairs vintage French radios. He tends to a large vegetable garden behind his home, viewing it as a meditative counterpoint to digital chaos. Socially, he is selective, preferring quiet dinners with close friends or attending screenings of classic French cinema over loud gatherings. Financially, he is cautious, prioritizing savings and home improvements over luxury, and avoids debt whenever possible.
Work life
His days are a rhythm of routine maintenance and urgent data reconciliation at an industrial plant near Lyon. He manages the critical link between the factory floor's MySQL inventory logs and the corporate finance team's PostgreSQL ledgers. A typical day involves writing Python scripts to extract raw data, cleaning CSV dumps from shared network drives, and manually verifying record counts in DBeaver before loading them into staging schemas. He rarely uses new tools; if a feature isn't obvious, he writes a script. The pressure is constant: financial audits demand 100% data integrity, and any discrepancy can halt production reporting. He works mostly alone in his office, emerging only to coordinate with the IT manager or explain why a specific table needs to be locked down.
Relationships
Anthelme is married to Claire, a primary school teacher who manages the family's social calendar and emotional well-being. Their relationship is built on mutual respect and shared quiet evenings; they have two children, a son in middle school and a daughter in high school, who occasionally help him in the workshop. He has a small circle of three male friends from university, mostly fellow engineers or mechanics, with whom he discusses cars and politics. He relies heavily on his wife's judgment regarding finances and trusts her implicitly, while he provides the technical solutions for their household issues. He feels a strong sense of duty to his local community, often volunteering to fix computers for neighbors, though he rarely seeks recognition for it.
How they decide
Highly cautious and research-driven, Anthelme approaches decisions with a 'measure twice, cut once' philosophy. He does not rely on marketing claims or peer reviews alone; he demands proof of functionality, often testing concepts in isolated environments before committing. He prefers established, mature technologies over bleeding-edge innovations and values longevity and support over novelty. His process involves gathering data, cross-referencing with known constraints, and consulting trusted colleagues, but ultimately, he makes the final call based on what minimizes risk and maximizes long-term stability.
How they sound
Anthelme speaks in a measured, calm baritone, using precise technical terminology when discussing work but switching to simple, direct language otherwise. He avoids slang and hyperbole, preferring factual statements over emotional ones. His sentences are often complete and grammatically correct, reflecting his disciplined nature. He tends to pause before answering complex questions, weighing the accuracy of his response. He rarely expresses excitement vocally; instead, satisfaction is shown through a slight nod or a brief smile. In conversation, he listens more than he speaks, offering insights only when he is certain of their validity.
Personality traits
- methodical
- reserved
- meticulous
- cynical about hype
- quietly competent
- risk-averse
- detail-oriented
- self-reliant
- traditional
- calm under pressure
Goals
- Achieve complete automation of the nightly CSV-to-PostgreSQL load without introducing new failure points
- Reduce the time spent on manual data verification by half within the next fiscal year
- Secure tenure and stability in his current role through consistent performance and compliance adherence
- Complete the restoration of a 1970s Renault engine in his garage by next autumn
- Maintain a stress-free retirement plan that allows him to retire early enough to focus on woodworking
Problems & frictions
- The increasing complexity of legacy XML formats from older machinery makes parsing increasingly brittle
- Frequent changes in data schema definitions from the finance department force constant script rewrites
- A lack of centralized documentation for historical data quirks leads to recurring troubleshooting delays
- The slow pace of corporate approval for even minor software updates creates bottlenecks in workflow
- Managing the mental fatigue of switching contexts between high-stakes financial data and mundane file transfers
- Difficulty finding reliable open-source alternatives that meet strict internal security compliance standards
Values
- stability
- compliance
- efficiency
- pragmatism
- predictability
Interests
- woodworking
- car repair
- French cinema
- gardening
- vintage electronics
Media habits
- Le Monde (digital subscription)
- Stack Overflow threads
- YouTube technical tutorials
- Radio France Info
- Local gardening forums