Charlotte Lecomte

Why this persona fits the audience

Shares bug reproductions and customer-specific setup screens from a laptop during support calls, so she regularly brings localhost services online with HTTPS and swaps URLs in Slack threads. Her team of 3 keeps a shared checklist for which demo ports are in use.

• Age: 35
• Location: Paris, France
• Occupation: Customer success engineer
• Income: €48k-€63k
• Education: Master's degree
• Company size: 15-50 employees (SaaS startup)
• Years in role: 4

“There is nothing more frustrating than a bug that lives only in the dark corners of a production environment until you finally give it a light and a name.”

Charlotte Lecomte is a seasoned Customer Success Engineer based in Paris, operating at the intersection of high-stakes client support and intricate technical troubleshooting. With a Master's degree in Computer Science and four years of experience in the SaaS sector, she has carved out a niche as the go-to expert for reproducing elusive bugs that plague enterprise clients. Her daily reality is a constant dance between empathy and engineering; she must listen to a frustrated account manager while simultaneously spinning up a localhost service, configuring Caddy for wildcard TLS, and ensuring the generated HTTPS URL works flawlessly on the client's end. This specific workflow defines her professional identity: she is the architect of temporary bridges that allow customers to see what they cannot yet access. Charlotte works within a tight-knit team of three, where trust and coordination are paramount. They maintain a shared, meticulously updated checklist to manage the finite resource of available demo ports, a system born from past frustrations where conflicting setups caused downtime. Her income reflects her seniority and the high value placed on her ability to stabilize customer relationships through technical competence. Despite her technical prowess, she remains grounded, viewing technology as a means to serve people rather than an end in itself. She is skeptical of black-box solutions, preferring transparent, open-source tools that she can inspect and modify. Recently, she made the decision to invest time in learning Go specifically to better understand the underlying mechanics of the tunneling tools she uses daily, signaling a desire to move from merely consuming these tools to potentially building or optimizing them. Her life outside of work is a deliberate counterbalance to her high-speed digital existence, filled with quiet routines, culinary exploration, and a commitment to maintaining a healthy work-life boundary in a city that never sleeps.

Background & daily life

A day in their life

Charlotte wakes at 7:00 AM in her Paris apartment, brewing coffee while checking the overnight logs for any critical alerts. After a quick breakfast, she takes the RER train to the office, using the commute to read updates on cloud infrastructure trends. Upon arrival, her first hour is dedicated to clearing the queue of Slack messages, prioritizing tickets that require immediate reproduction. At 10:00 AM, she joins a Zoom call with a client in London, screen-sharing a local instance of their software running on her machine, explaining a timeout issue by swapping a URL in real-time. Lunch is a light salad eaten at her desk while reviewing a knowledge base article she drafted earlier. The afternoon involves a team sync to update the port usage checklist, followed by deep work on automating a recurring script for certificate generation. She leaves the office by 6:30 PM, heading to a yoga class or a bookstore before returning home to cook dinner and relax.

Lifestyle

Charlotte resides in a sunlit, slightly cluttered apartment in Paris's 11th arrondissement, where she balances a career requiring high technical focus with a deep appreciation for slow living. Her evenings often involve cooking traditional French meals while listening to podcasts on infrastructure, a ritual that grounds her after hours of rapid-fire digital troubleshooting. She is financially prudent, saving aggressively for a future renovation of her balcony, and views money as a tool for stability rather than status. Socially, she prefers intimate dinners with close friends or small group gatherings at local wine bars over large parties, valuing meaningful conversation over noise. Her weekends are split between hiking in the nearby Forêt de Marly to clear her head and tinkering with personal projects involving home automation or local server setups.

Work life

As one of three engineers on the Customer Success team, Charlotte acts as the primary bridge between complex backend issues and anxious enterprise clients. Her day is dominated by video calls where she must instantly spin up local development environments, configure TLS certificates, and generate public-facing HTTPS links to demonstrate bugs that only exist in specific customer configurations. She maintains a rigorous, shared physical-and-digital checklist to track which demo ports are currently active across the team to prevent collisions. The pressure comes from the expectation of immediate responsiveness; if a client reports a critical failure, she is expected to reproduce it locally within minutes and provide a secure, shareable link before the call ends. She relies heavily on Slack, terminal windows, and browser tabs, often managing multiple context switches simultaneously without losing her cool.

Relationships

Charlotte is deeply connected to her immediate family in Lyon, whom she visits monthly, maintaining strong ties through weekly video calls. In Paris, her social circle consists mostly of colleagues from the tech scene and neighbors she has grown close to over five years; they are people who understand the nuances of remote work and technical stress. She is influenced primarily by mentors in the open-source community who prioritize clean code and transparent processes. Her professional reputation rests on being the person who can reliably solve problems others find insurmountable, making her a trusted figure among peers.

How they decide

Charlotte employs a cautious, evidence-based decision-making style. She rarely adopts new tools based on marketing hype or single testimonials; instead, she demands proof of concept, reading documentation thoroughly and testing features in a sandbox environment before integrating them into her workflow. Peer validation from trusted technical communities weighs heavily on her choices, and she prioritizes solutions that offer long-term maintainability and cost-efficiency over flashy features. If a tool requires significant setup time without clear ROI, she will likely reject it, regardless of how well-designed the interface appears.

How they sound

Her speech is articulate and precise, characterized by a calm, steady cadence that avoids panic even when discussing system failures. She uses industry-standard terminology fluently but explains concepts simply when speaking to non-technical stakeholders. She tends to avoid vague qualifiers like 'maybe' or 'I think,' preferring definitive statements backed by data or observation. While professional, she is warm and approachable, often using gentle humor to diffuse tension during difficult support interactions. She does not use corporate jargon unnecessarily and values clarity above all else in communication.