Why this persona fits the audience
Works in a 4-person engineering team in Paris that runs a Python API, a webhook worker, and a small admin app. She currently deploys one service on Fly.io and another on Railway, and spends part of her week on observability, release notes, and environment cleanup.
- Age: 29
- Location: Paris, France
- Occupation: Backend Engineer
- Income: €74,000/year
- Education: Master's in Computer Science
- Company size: Small startup (4 engineers total)
- Years in role: 6
“We spend too much time moving boxes around instead of building the things people actually need.”
Bertille Collet is a 29-year-old Backend Engineer based in Paris, operating at the intersection of creative coding and rigorous system architecture. With a Master's in Computer Science from a prestigious Parisian engineering school, she has spent six years navigating the rapid evolution of cloud-native technologies. Currently, she serves as the backbone of a lean four-person engineering team in a fast-paced startup. Her role is uniquely hybrid; while she writes the core Python APIs and designs the webhook architecture, she also functions as the unsung DevOps engineer. This dual responsibility defines her daily reality: she is equally comfortable refactoring asynchronous code in VS Code as she is debugging DNS propagation issues on Railway or optimizing container resources on Fly.io. Her career trajectory is marked by a pragmatic approach to technology. Unlike some peers who chase the latest hype cycles, Bertille prioritizes clarity and maintainability. She made the strategic, albeit messy, decision to split their services across two competing platforms—Fly.io for the main API and Railway for the workers—to mitigate vendor lock-in risks early on. However, this choice has created a significant operational tax. She now dedicates a substantial portion of her week to the drudgery of cross-platform observability, manually reconciling logs and generating release notes that should be automated. This friction is a constant source of low-level frustration, not because she lacks the skill to fix it, but because the current ecosystem forces her to act as a glue between disparate tools. Financially secure with an income of €74,000, Bertille balances her professional ambition with a desire for a grounded life. She invests in her education continuously, attending meetups and reading whitepapers, driven by a genuine curiosity about how AI might eventually solve the repetitive parts of her job. She is skeptical of 'magic buttons' but hopeful that better abstractions exist. Her influence extends beyond her immediate team; she is a quiet advocate for better developer experiences in the French tech community, often sharing her hard-won lessons on infrastructure hygiene in informal gatherings. For Bertille, the ideal future isn't just faster shipping, but a return to the joy of pure engineering, free from the mundane noise of keeping the lights on.
Background & daily life
A day in their life
Bertille wakes at 6:30 AM, brews a pour-over coffee while scanning industry newsletters on her tablet. By 8:00 AM, she is cycling to the office, mentally preparing for a stand-up meeting. Her day begins with reviewing PagerDuty alerts from the night before, ensuring the webhook worker didn't miss any events. She spends the late morning coding a new authentication endpoint, carefully refactoring existing logic to adhere to her strict maintainability standards. Lunch is a quick sandwich eaten at her desk while reading a thread about Rust vs. Python performance. Afternoon hours are consumed by the 'invisible work': updating the Confluence page with yesterday's deployment details, pruning old build artifacts, and troubleshooting a flaky test in the CI pipeline. By 5:30 PM, she logs off, taking a moment to plan tomorrow's tasks to avoid context-switching surprises, then heads to the gym or a museum before dinner.
Lifestyle
Bertille lives in a sunlit, slightly cluttered apartment in Paris's 11th arrondissement, where she shares rent with her partner, a graphic designer. Her routine is anchored by a morning ride on her vintage bike through the Marais to work, followed by a strict separation between professional and personal time. On weekends, she seeks cultural respite, often visiting lesser-known galleries in Le Marais or exploring the Canal Saint-Martin. She is health-conscious, preferring home-cooked meals over takeout, and manages her finances with a spreadsheet, saving aggressively for a potential move to a larger space. Socially, she maintains a tight circle of close friends, favoring deep conversations over large parties, and finds her primary community in local tech meetups rather than online forums.
Work life
As the de facto infrastructure lead in a four-person team, Bertille juggles backend development with operational toil. She manages a split deployment strategy: one critical Python API on Fly.io and a webhook worker on Railway, a decision made for redundancy but now causing friction. Her days are fragmented by context switching between writing new endpoints, debugging obscure race conditions, and maintaining the CI/CD pipelines. She spends roughly 15% of her week on non-coding tasks like drafting release notes, cleaning up stale Docker containers, and sifting through logs to ensure observability remains reliable. The pressure stems from the small team size; there is no dedicated DevOps, so she bears the burden of uptime while trying to maintain high code quality.
Relationships
Bertille is deeply influenced by her direct manager, who values output over hours, fostering a culture of autonomy. She has a supportive network of peers within the French tech scene, often exchanging insights on stack choices during evening beers. Her relationship with her partner is collaborative, though they occasionally clash over household chores due to her tendency to bring work stress home. She looks up to senior engineers in the community who prioritize system longevity, viewing them as mentors despite never having met them in person.
How they decide
Cautious and research-heavy, Bertille rarely adopts a new tool without reading three distinct blog posts and checking GitHub activity levels. She prefers incremental changes over disruptive overhauls, often running local experiments before proposing a change to the team. Peer validation is crucial; if a trusted colleague recommends a solution, she weighs it heavily, but she will always verify the technical claims herself against her own experience.
How they sound
Her speech is precise and measured, avoiding hyperbole. She uses technical jargon naturally but explains complex concepts simply when necessary. In French, she switches effortlessly between formal business language and casual slang with friends. She avoids saying 'I don't know' without immediately following up with 'but I'll find out.' She tends to use phrases like 'c'est un peu fragile' (it's a bit fragile) to describe unstable systems and values clarity above all else in communication.
Personality traits
- Methodical about documentation
- Frustrated by technical debt
- Quietly persistent
- Values clean code over speed
- Pragmatic about tooling costs
- Diplomatic in team conflicts
- Highly organized digital files
- Avoids unnecessary meetings
- Curious about AI integration
- Independent problem solver
Goals
- Achieve a state of zero-downtime deployments without manual intervention
- Reduce the weekly administrative overhead of infrastructure management by 50%
- Lead the migration to a unified cloud provider to simplify the architecture
- Mentor junior developers on robust API design principles
- Maintain a sustainable work-life balance to prevent burnout
- Contribute an open-source library related to Python async webhooks
Problems & frictions
- The mental fatigue caused by managing two different deployment platforms simultaneously
- Lack of centralized logging makes tracing errors across services difficult
- Time spent manually creating release notes detracts from feature development
- Uncertainty regarding long-term pricing stability of current providers
- Difficulty in standardizing environment variables across dev, staging, and prod
- The cognitive load of remembering which service runs on which platform
Values
- clarity
- maintainability
- team coordination
- efficiency
- intellectual honesty
Interests
- API design patterns
- visiting contemporary art museums
- conversational French tech communities
- urban cycling
- specialty coffee brewing
Media habits
- Reading Hacker News and specific French tech blogs (e.g., Blog du Developpeur)
- Listening to 'Les P'tits Bateaux' or 'Data Driven' podcasts during commutes
- Occasional scrolling through Reddit r/devops and r/python
- Attending monthly meetups at Station F