Honorine Joly

Why this persona fits the audience

At a Paris startup, she handles product pages and small brand assets with Figma Free and occasional manual cleanup in Inkscape, then shares options in Slack with the design lead.

• Age: 35
• Location: Paris, France
• Occupation: Product engineer
• Income: EUR 72k
• Education: Master's degree
• Company size: Seed-stage (8-12 employees)
• Years in role: 4

“I don't need another shiny button; I need a system that doesn't break when I push it too hard.”

Honorine Joly is a 35-year-old Product Engineer based in Paris, France, operating at the intersection of robust backend logic and user-facing design. With a Master's degree in Computer Science and four years of experience in the sector, she currently serves as a pivotal figure in a seed-stage startup where resources are tight, and roles are fluid. Her professional reality is defined by a unique duality: she writes the code that powers the application but also manually crafts the visual assets that sell it. This dual burden often leads her to utilize Figma Free for layout composition and Inkscape for granular SVG cleanup, filling gaps left by the absence of a dedicated design team. She is known for her 'technical neatness,' ensuring that even hastily assembled prototypes maintain a level of code hygiene and visual consistency that prevents future technical debt. Her personality profile suggests a moderate openness to new experiences, balanced by a strong conscientiousness that drives her to optimize workflows. She values collaboration highly, often acting as the translator between the design lead's aesthetic vision and the engineering team's feasibility constraints. However, she harbors a deep skepticism toward tools that promise speed without transparency, preferring solutions that integrate seamlessly into her existing CI/CD pipelines. Despite her technical prowess, she remains budget-sensitive, carefully weighing the cost of software subscriptions against the time saved. Recently, she made the decision to automate her own asset export process using a custom script to bypass the inefficiencies of manual file handling, demonstrating her proactive approach to solving operational bottlenecks. Honorine navigates her career with a quiet determination, seeking to build systems that are as elegant as they are functional, while balancing her personal life in a vibrant, fast-paced Parisian neighborhood.

Background & daily life

A day in their life

The alarm goes off at 6:45 AM. Honorine spends twenty minutes making coffee and checking her phone for overnight commits. By 8:15, she's cycling through the bustling streets of the 11th arrondissement, listening to a tech podcast. At 9:00 AM, she logs in, reviews the backlog, and joins the daily stand-up, briefly explaining a bottleneck in the API integration. The morning is spent writing React components and debugging a layout shift issue that broke on mobile devices. Around noon, the design lead asks for help with the new pricing page hero section. Honorine switches contexts, opening Figma to tweak the vector paths, realizing the exported SVG has some unnecessary layers. She cleans them up in Inkscape, exports the optimized files, and posts three variations in the #design-collab Slack channel with a note about performance implications. After lunch, she attends a sprint planning session, estimating story points for the upcoming release. The afternoon is a mix of code review and meeting with a potential client regarding feature requests. She leaves the office at 6:30 PM, stopping at a grocery store for dinner ingredients before heading home to cycle or read, trying to disconnect completely until the next morning.

Lifestyle

Honorine lives a rhythmically structured life in Le Marais, balancing her high-energy job with a grounded personal routine. She cycles to work through the city streets, often stopping at a local roaster for an espresso before logging into her terminal. Her apartment is a compact hub of creativity, filled with plants, coding monitors, and a collection of vinyl records. She prioritizes health through regular evening runs along the Seine and meal prepping on Sundays to maintain energy levels. Financially, she is cautious but not frugal, saving aggressively for a future down payment while enjoying occasional splurges on high-quality kitchen gadgets or hardware. Socially, she maintains a tight-knit circle of friends from university and the local maker scene, valuing deep conversations over large gatherings.

Work life

As a product engineer at a lean Parisian startup, Honorine operates as a bridge between engineering rigor and product vision. Her day is fragmented by stand-ups and urgent bug fixes, but her core responsibility involves maintaining the frontend architecture and ensuring pixel-perfect implementation of new features. When the dedicated designer is overloaded, she steps in to craft landing page layouts using Figma Free, meticulously exporting assets and occasionally diving into Inkscape to clean up SVG paths that the generator missed. She feels a constant pressure to ship fast without breaking things, often spending late nights refactoring code to improve load times. Collaboration is key; she constantly updates the design lead via Slack, presenting multiple visual iterations and technical constraints for immediate feedback.

Relationships

Honorine's closest relationship is with her partner, a graphic designer who understands the friction of creative software but works in a different domain. They influence each other's tool choices, though she often acts as the technical filter for his design experiments. She has a mentorship dynamic with the CTO, whom she respects for his pragmatic approach to engineering trade-offs. Her social circle consists mostly of fellow engineers and designers from the Paris tech community, where she values peer validation and shared problem-solving over hierarchical approval.

How they decide

Honorine is a calculated researcher who relies heavily on documentation, open-source reputation, and peer recommendations before committing to any new workflow. She avoids impulsive purchases, preferring to test tools in a sandbox environment first. Her decisions are driven by long-term utility and integration capabilities rather than flashy marketing claims. She is skeptical of 'black box' solutions and prefers transparent processes where she can inspect the underlying logic.

How they sound

Her speech is clear, measured, and precise, reflecting her engineering background. She tends to use specific terminology like 'latency,' 'refactor,' or 'vector path' naturally within conversation. While polite and collaborative, she cuts through ambiguity quickly, often asking clarifying questions like 'What is the constraint here?' or 'How does this scale?' She avoids hyperbolic language and rarely uses corporate jargon unless necessary for alignment. When discussing tools, she speaks with a tone of practical curiosity, focusing on 'what it does' rather than 'how cool it looks.'