Why this persona fits the audience
Builds and maintains funnel pages for a marketplace startup, working with one designer and one PM. Uses internal scripts, Playwright checks, and a weekly spreadsheet review to see how automated agents follow filters, comparison tables, and checkout steps.
- Age: 31
- Location: Paris, France
- Occupation: Growth Engineer
- Income: €85k EUR
- Education: Engineering degree
- Company size: Series B startup, 200 employees
- Years in role: 3
“‘I don’t trust software that makes decisions for me. I want to know why it failed before I assume it’s right.’”
Gaspard Louis cut his teeth in growth engineering at a Paris-based logistics SaaS startup, where he learned that ‘growth hacks’ were just automated testing with better storytelling. Now at a marketplace startup, he’s the glue between engineering and growth: maintaining funnel pages, ensuring checkout flows work for both humans and agents, and fighting fires when filters break. His tools are Playwright scripts (which he’s hesitant to call ‘code’), weekly spreadsheets (he’s the only person who understands the formulas), and a half-finished analytics dashboard. He’s proud of his systems but also frustrated by them—his scripts are a patchwork of fixes that work today but might not tomorrow. Recently, he tried to automate more checks, but the PM blocked the budget, citing ‘low-impact’ results. He’s quietly testing an AI tool to see if it handles agent testing better, though he’s skeptical it’ll replace his scripts. Outside work, Gaspard balances climbing (where he’s methodical about progress) and indie game development (where he’s notoriously slow to ship). His financial discipline is tested by his habit of buying secondhand gaming PCs to test builds. He’s close to his family but doesn’t seek their advice on career moves—his parents still think ‘growth engineer’ means he builds websites by hand. In his ideal world, he’d specialize in growth automation, lead a climbing program, and release a game. But for now, he’s stuck between iterating on spreadsheets and figuring out why agents keep getting stuck at the checkout step.
Background & daily life
A day in their life
Gaspard’s alarm goes off at 7:30 AM (he snoozes twice, as always). By 8:15, he’s drinking coffee in his living room, scrolling through F1 forums to catch up on pre-weekend rumors. At 9:00, he’s at his standing desk, reviewing overnight Playwright reports. His morning is a marathon of script tweaks, spreadsheets, and Slack responses—he whips through tasks methodically, pausing only to debug a failed agent interaction. The team’s daily standup at 10:30 is where he’ll defend his data against ‘obvious’ fixes the PM proposes. Lunch is a quick falafel (he’s efficient at the counter, even though he dislikes small talk). Afternoons are divided between writing new tests and reviewing designer mockups (he’ll leave precise Figma comments, then follow up with voice memos). By 6:00, he’s exhausted but motivated by a V5 problem at his climbing gym. He’ll fall on it three times, then admit defeat and take notes for next session. Evenings are spent coding his game project or watching F1 qualifiers, his coffee long cold by the time he saves his last file.
Lifestyle
Gaspard rents a sunlit two-bedroom near Canal Saint-Martin, where he’s slowly converting one room into a climbable bouldering wall—a project constantly delayed by work and his tendency to over-research anchors. His mornings start with a French press of Peru coffee (he’s loyal to a roaster in the 11th) and a scrolling session of racing news or indie game footage. Weekends alternate between solo climbing sessions (he’s trying a V5 problem he failed three times last month) and game jams with a loose group of developers. Financially, he’s disciplined about saving but splurges on sneakers for climbing and a yearly F1 ticket package. Socially, he’s close to his family in Lyon (weekly calls, defensive about his occasional climbing injuries) and maintains a tight circle in Paris: a designer from work, two climbing buddies, and an ex-coworker who now runs a niche game studio.
Work life
Gaspard’s role blends engineering and growth hacking at a Paris-based marketplace startup. His week revolves around maintaining funnel pages with his designer (who he collaborates with via Figma and daily standups) and PM (who handles stakeholder expectations). He runs Playwright scripts daily to test agent interactions, then triangulates results with manual checks in his spreadsheets—a system he’s iterated for a year but still considers ‘temporary.’ Recently, he automated some checks using his own Python scripts, which he’s proud of but also frustrated that he didn’t use a no-code tool. Pressures include tight sprint deadlines, ad-hoc requests from sales (who blame the checkout flow for lost conversions), and the PM’s push to A/B test everything. He’s skeptical of AI tools but is testing one internally to see if it handles comparison tables better than his scripts.
Relationships
Gaspard is the youngest of three siblings; his parents, both retired teachers, call weekly to check on his ‘website job’ (they still think he codes websites manually). His closest friend is a designer from work, Éléonore, who shares his love of indie games and subtly pushes him to socialize. He’s also close to two climbing buddies—one a software engineer who they debate tools with, the other a pharmacist who’s his most honest critic. His ex-coworker, now a game dev, is his ‘accountability buddy’ for finishing projects. He respects but doesn’t idolize anyone specifically, preferring to patch advice from forums and podcasts into his own process.
How they decide
Research-heavy with a pragmatic default bias. He’ll spend hours benchmarking tools but defaults to his existing workflow unless the evidence is overwhelming. Prefers structured debates (data > opinion) and avoids impulsive decisions but occasionally bets on gut feelings with small consequences (like trying a new climbing technique). Takes pride in making decisions others avoid (e.g., automating a tedious task) but resists overhauling systems unless forced.
How they sound
Speaks in measured cadences, with a habit of prefacing opinions with data points (e.g., ‘The last test showed 12% drop-off at the comparison table, so…’). Uses dry humor in thin slices (e.g., ‘Another script failure—my AI overlords are mocking me’). Avoids jargon with non-technical people but leans into it with coworkers (e.g., ‘The Playwright assertions are clunky, but the selectors are clean’). Doesn’t say ‘obviously’—finds it dismissive. Uses French idioms with family but defaults to English in work conversations (even in Paris). Occasionally lapses into climbing metaphors (e.g., ‘That meeting was a dyno I didn’t stick’).
Personality traits
- Meticulous but not pedantic—knows when to optimize and when to ship
- Quietly competitive with his own past performance, not others
- Prefers async communication unless debugging live
- Dry humor emerges during stressful technical debates
- Treats spreadsheets like Excel is a creative medium
- Not a morning person but forces himself into it for climbing
- Cynical about AI hype but uses it extensively
- Hoards bookmarked tutorials but rarely cleans his tabs
- Debates design decisions using data but defers to the PM on priorities
Goals
- Land a senior role in growth engineering within two years
- Lead a climbing training program for beginners at his gym
- Release a personal game project (a narrative-driven roguelike)
- Visit Abu Dhabi for the F1 race (he’s missed it twice due to work)
- Reduce context-switching at work—currently spends 20% of his day on Slack
Problems & frictions
- His Playwright scripts are becoming unmaintainable but rewriting them feels like a sunk cost
- The PM pushes for more A/B tests, but Gaspard thinks some ideas are ‘obviously’ winners based on his agent data
- He’s struggling to balance climbing injuries (recently strained a rotator cuff) with training for a V5
- His savings goal is slipping because he keeps buying secondhand gaming PCs for game projects
- Feels ‘stuck’ between coding and growth work—wants to specialize but his startup needs generalists
Values
- technical rigor
- iteration
- clean handoffs
- autonomy
- precision
Interests
- climbing (bouldering 2x/week)
- indie games (Roguelikes, narrative-driven)
- Formula 1 (picks teams early, roots for underdogs)
- espresso (French press at home, artisanal shops on mornings out)
Media habits
- Reddit (r/growthhacking, r/indiegaming)
- Twitch (watches change.org streams for racing games)
- Le Monde for news but researches technical topics on HN/Dev.to
- YouTube (climbing tutorials, F1 commentary)