10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Justin Blanchard

Justin Blanchard

Product engineer at fintech

Full-depth AI personas

Why this persona fits the audience

Works on a 9-person fintech team in Paris where he ships customer-facing pages and support links; the team’s current stack includes a few internal scripts for generating metadata cards and QR codes used in onboarding.

  • Age: 33
  • Location: Paris, France
  • Occupation: Product engineer
  • Income: €72k
  • Education: MSc in Computer Science
  • Company size: 9 (startup)
  • Years in role: 4
“‘I’d rather fix a problem today that no one cares about than bandage a problem tomorrow that costs us customers.’”

Justin Blanchard grew up in Lyon, where his parents ran a small accounting firm. He taught himself Python by automating their client billing system—a project he now cringes at, though his father still prints the output. After earning his MSc in Paris, he joined a neobank startups’ early engineering team, where he learned to ‘ship fast’ and ‘ship broken’—until a $20K compliance fine from the AMF taught the team the hard way about edge cases. Now at a 9-person fintech, he’s the sole engineer who’s seen every line of their legacy onboarding scripts. His coworkers tease him for ‘solving problems no one knew we had,’ but when their metadata parser failed during a demo to a German partner bank, it was his year-old refactor that saved the day. Justin’s apartment is a study in intentional minimalism, save one corner dedicated to espresso gear (he imports Ethiopian beans monthly). He’s skeptical of fintech buzzwords but privately excited about ‘dumb, reliable’ tools. Recently, he quietly replaced the team’s outdated QR code library, citing better error handling—though he’s still waiting for anyone to notice. His latest side project is documenting their internal workflows in a private wiki, a habit born from being ‘tired of asking the same questions.’ He runs everywhere, even to the bakery, and once timed his morning route to avoid a coworker he found too chatty. When not debugging, he’s likely debugging his own coffee workflow—currently testing a new pressurestat.

Background & daily life

A day in their life

5:30 AM wake-up to *black coffee + 5km run*. 7:00 AM: cold shower, oatmeal, and a podcast while drafting Jira tickets. 8:30 AM task-zero: triage Slack messages—ignores non-urgent threads with 🔁 emoji. Lunch is a pre-portioned bowl from Sunday prep. Afternoon devoted to features (TypeScript + React), but derailed when the chief compliance officer asks him to 'fix the QR code thing.' 6:30 PM: stands in kitchen debating whether to try a new coffee grind while scrolling through GitHub notifications. Falls asleep to a finance podcast, but mostly just hears 'blockchain' and zzz.

Lifestyle

Rents a studio in the 11th arrondissement with a Murphy bed to maximize space. Runs 5km daily along the Canal Saint-Martin before work (rain or shine), fueling runs with *honey lavender* espresso he roasts himself. Cooks from scratch but only on weekends; weekday meals are rotationally repetitive (e.g., 3 types of grain bowls). Socioeconomically comfortable but avoids conspicuous spending; his 'splurge' is a €300 bike upgrade. Socializes selectively—monthly dinners with a tight-knit group of ex-engineering classmates and weekly chess with a neighbor who’s a retired mathematician. Negotiates his own health insurance for better dental coverage.

Work life

At his scrappy fintech, Justin’s team own customer documents, onboarding flows, and support plugins. He recently rewrote their QR code generator to handle dynamic expiry times after a compliance scare. Their stack leans heavily on custom scripts (e.g., a Perl monster from Series A for metadata parsing), which Justin tolerates but privately documents as 'technical debt time bombs.' He’s the de facto 'process champion'—introduced Jira epics for blocking issues and a Figma library for UI consistency. Coworkers joke he ‘sleeps with the linting rules’ after he fought to enforce pre-commit hooks. Spends 20% of his time firefighting legacy scripts and the rest shipping features like a new transaction history dashboard.

Relationships

Distant with family in Lyon (visits twice yearly); closest to his thesis advisor, who now runs a VC fund and occasionally warns him about ‘baseless fintech hype.’ Social circle is small but deeply trusted—his ex-partner, now a UX designer, still helps him test new UI patterns. Strokes the ego of his company’s lone TPM by explicitly tagging her in GitHub issues, but privately doubts her prioritization framework.

How they decide

Researches comprehensively but trusts gut calls when data points are gray (e.g., once rewrote an entire microservice because 'it smelled wrong'). Prefers to delay decisions until he can verify 2nd-order effects. Dislikes consensus-driven processes ('If we all agree, someone isn’t thinking critically').

How they sound

Speaks in clipped, precise sentences with a faint Lyonnas accent. Uses dry humor (e.g., 'That script is like a haiku—beautiful but meaningless'). Avoids hyperbole or emojis in workplace chat but sprinkles them in casual texts ('You’re telling me the *bank* isn’t using TypeScript?? 💀'). Secretly curses in French when his npm install fails.

Personality traits

  • prone to over-documenting decisions for posterity
  • prefers quiet collaboration (e.g., async PR reviews over meetings)
  • skeptical of hype cycles but quick to adopt battle-tested tools
  • meticulous about code naming conventions
  • secretly enjoys optimizing workflows others consider trivial
  • avoids small talk but openly debates technical trade-offs
  • hates context-switching—blocks focus time religiously
  • uses 3-letter abbreviations in notes that bewilder new colleagues
  • low tolerance for fluff in meeting agendas

Goals

  • Move to a 2-bedroom to host remote friends visiting
  • Complete a half-marathon without pausing for stride adjustments
  • Learn enough Rust to rewrite one internal tool as a hobby
  • Reduce work email to <20/day by enforcing async-first culture

Problems & frictions

  • Team’s metadata generator occasionally fails on cyrillic URLs, but no one complains—just workarounds
  • CEO insists on 'personalizing' support PDFs with handwritten-style fonts
  • Legacy onboarding scripts have no tests; Justin’s 3 attempts to add them caused cascading failures
  • Running out of vertical space in his apartment for espresso gear
  • Vises with big EU banks for compliance audits take priority over feature work

Values

  • security
  • accuracy
  • process
  • accountability
  • autonomy

Interests

  • fintech
  • TypeScript
  • internal tooling
  • running
  • minimalist design
  • espresso

Media habits

  • listens to tech podcasts (e.g., *Syntax*) during commutes
  • reads Hacker News and X/Twitter threads on dev tooling
  • avoids LinkedIn but checks GitHub trends weekly

Questions & answers

Justin Blanchard’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Pixsnap (https://pixsnap.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Pixsnap better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, we’re patching things together with a mix of internal scripts and manual workarounds. For dynamic OG images, we have a hacked-together Perl script from Series A that occasionally fails on Cyrillic URLs. QR codes are handled by a library I recently replaced, but it’s still basic. For metadata extraction, we scraping URLs manually when needed—inefficient but it works. PixSnap’s integration of these services into a single API would’ve been a huge time-saver. The ability to generate and manage these elements through a simple API call is appealing, especially given our team’s size. However, since our current workaround doesn’t actively block us, it’s hard to justify switching to a paid service. That said, if PixSnap had offered a free tier with basic functionalities, I’d have been more inclined to try it. As for pricing, I’d consider up to $20/month, but only if the value proposition was clear and the service fit seamlessly into our workflow without requiring significant refactoring.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.