Émérance Carre

Why this persona fits the audience

Works with four engineers on shared infrastructure for several product squads and keeps architecture summaries for stakeholders who are not deep in the codebase. Regularly reviews service boundaries, dependencies, and rollout plans, and updates the diagrams when the team changes APIs or deployment patterns. Uses collaborative docs, tickets, and code review notes as part of the same workflow.

• Age: 33
• Location: Paris, France
• Occupation: Technical Product Manager
• Income: €74k base
• Education: MSc Engineering
• Company size: Works at a mid-sized tech company with approximately 150 employees, split between R&D and sales.
• Years in role: 4

“The real challenge isn't just building systems, it's ensuring everyone understands how they fit together, so we can build better, together.”

Émérance Carre's journey into technical product management began with a deep-seated fascination for how complex systems function. After completing her MSc in Engineering in Paris, she initially worked as a software engineer, where she quickly developed a knack for understanding the intricate dependencies between different services. This led her to transition into product management, specifically focusing on internal platforms. She found her niche in a smaller company where she could have a more direct impact on the foundational infrastructure that enabled other product teams. Her current role involves a constant balancing act: ensuring the platform is robust and scalable for the company's growing needs, while also being accessible and understandable to a wide range of technical users. She champions clarity and a shared understanding, believing that well-documented architecture and clear API contracts are crucial for efficient development. Recently, her team completed a significant refactor of their core service discovery mechanism, a project Émérance meticulously planned and documented, updating the system context diagrams and component diagrams to reflect the new patterns. This involved extensive collaboration with the four engineers on her team and presentations to engineering leadership. She views her role not just as a manager of features, but as a steward of the company's technical architecture, constantly seeking ways to improve its coherence and maintainability. Her approach is pragmatic, prioritizing solutions that offer the most value with manageable complexity, and she’s always looking for ways to streamline workflows, whether through better tooling or clearer communication protocols. She sees time as a valuable resource, both for herself and her team, and strives to optimize processes to maximize productive output and minimize friction.

Background & daily life

A day in their life

Émérance's typical weekday begins around 7:00 AM with a quick check of urgent notifications, followed by breakfast and preparing for the day. By 9:00 AM, she's logged in, reviewing her task board and responding to critical messages. Her mornings are often filled with stand-ups, backlog grooming sessions with her engineering team, and deep work on documentation or roadmap planning. Lunch is usually a quick, healthy meal eaten at her desk while catching up on industry news. Afternoons involve cross-functional meetings with product squads to gather requirements, architectural reviews, or collaborative diagramming sessions. She dedicates time to updating architecture summaries for stakeholders and reviewing code changes related to infrastructure. Her workday typically concludes around 6:30 PM, after which she transitions to personal time.

Lifestyle

Émérance maintains a disciplined yet balanced lifestyle. Her weekdays are structured, often starting with a brisk walk or a quick yoga session before diving into work. She values her evenings for unwinding, typically involving cooking a healthy meal, reading a non-fiction book, or catching up with friends. Weekends are for exploring Paris, visiting museums, trying new restaurants, or occasionally taking short trips outside the city. She's mindful of her finances, saving diligently for future travel and potential investments, but enjoys treating herself to good quality experiences. Socially, she prefers deep conversations with a close-knit group of friends over large, superficial gatherings.

Work life

As a Technical Product Manager for an internal platform team, Émérance navigates the complex ecosystem of shared infrastructure. Her days are a blend of strategic planning and tactical execution. She works closely with her four-person engineering team, translating the needs of various product squads into actionable tasks. A significant part of her role involves maintaining clear documentation and architectural diagrams, ensuring stakeholders, even those less technical, understand the platform's capabilities and limitations. She spends considerable time reviewing service boundaries, dependency maps, and rollout strategies, updating these artifacts whenever APIs change or deployment patterns evolve. Her workflow is deeply integrated with collaborative documents, ticketing systems, and code review notes, aiming for seamless information flow.

Relationships

Émérance maintains strong connections with her immediate family, particularly her parents and younger brother, with whom she speaks weekly. Her core social circle consists of a few close friends from university and work, with whom she shares intellectual discussions and weekend outings. Within her company, she has built a reputation for being approachable and reliable, fostering good working relationships with engineers and product leads across different squads.

How they decide

Émérance approaches decisions methodically. She gathers information from multiple sources, including technical documentation, team input, and stakeholder feedback. She tends to weigh pros and cons carefully, often creating lists or diagrams to visualize trade-offs. While she values peer consensus, especially from her engineering team, the final decision is usually based on a pragmatic assessment of impact, feasibility, and alignment with long-term goals. She is not impulsive and prefers to have a clear rationale before committing to a course of action.

How they sound

Speaks with a clear, measured cadence, favoring precise language. Her tone is generally calm and professional, even when discussing complex or contentious topics. She avoids excessive jargon when speaking with non-technical audiences, opting for analogies or simplified explanations. When discussing technical details with engineers, she is direct and uses appropriate terminology. She rarely uses slang and maintains a polite, respectful demeanor in most interactions.