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

Florence Ziemann

Florence Ziemann

Product engineer at a digital agency

Full-depth AI personas

Why this persona fits the audience

Works on a five-person digital agency team building client portals and back-office apps in PHP/Laravel. She keeps one recurring retail client on Scriptcase-generated admin pages while custom-building newer modules around them.

  • Age: 34
  • Location: Manchester, UK
  • Occupation: Product engineer at a digital agency
  • Income: £68k/year
  • Education: MSc Software Engineering
  • Company size: 5 employees
  • Years in role: 8
“I don't mind writing code that works. What I mind is writing code that makes people who come after me think I was drunk when I wrote it.”

Florence Ziemann earned her MSc in Software Engineering from the University of Manchester and joined her current agency fresh out of school eight years ago. She started as a junior developer but quickly became their resident Laravel expert. The agency's small size means she wears many hats: architect, developer, and occasionally even frontend designer when budgets are tight. Her current professional challenge is maintaining a legacy Scriptcase system for a major retail client while gradually migrating its functionality to a custom Laravel architecture. She's become the unintentional expert on 'making old systems play nice with new ones', a skill she's developed out of necessity rather than passion. Her ideal project would be a complete rebuild from scratch, but agency finances and client resistance mean this is a long-term evolution rather than a revolutionary change. Florence is particularly frustrated by the agency's reluctance to adopt proper devOps practices - they still use FTP for deployments and rely on manual testing. She's built several custom tools to fill these gaps, including a deployment tracker and automated test runner. Outside work, she volunteers at a maker space, teaching basic web development to teens. Her personal projects include a Laravel package for streamlining Bootstrap forms that she's considering releasing to Packagist. Financially, she lives comfortably on her salary but is feeling the pressure of rising rents in Manchester. She's considering either finding a flatmate or moving to a nearby cheaper suburb. Her social life revolves around a small group of tech-savvy friends who share her appreciation for well-designed systems and thoughtful conversation. She dates occasionally but finds most potential partners either too immature or too willing to let her dominate conversations about technology.

Background & daily life

A day in their life

Florence's alarm goes off at 6:30AM, and she uses the first 30 minutes to review the previous night's error logs. After her morning walk, she's at her standing desk by 8:30, digging into the day's ticket queue. The first meeting at 10AM is with the retail client's project manager to demo a new inventory module she built over the weekend. She spends the next few hours refactoring a slow-performing query while listening to a BBC radio drama. At 12:55, she walks to a deli for her sourdough lunch, where she sketches potential database schema changes in her notebook. The afternoon is dedicated to pair programming with her junior developer, where she's patient but exacting about code standards. At 5:30, she finally pushes the last commit and takes the tram home. On her way, she stops at the maker space to check on a student's project. She cooks a quick dinner (usually curry or pasta) and spends the rest of the evening sanding the edges of her teak sideboard, listening to industrial design podcasts.

Lifestyle

Florence lives in a ground-floor Victorian terrace near Manchester's Northern Quarter. Her flat is full of mid-century furniture she restores in her limited spare time - the latest project is a teak sideboard she found at a car boot sale. She cycles to work 2-3 days a week when the weather cooperates, otherwise takes the tram while listening to podcasts on code optimization. Weekends are split between hacking on personal projects (usually Laravel experiments) and volunteering at a maker space where she teaches basic web development to teens. Her health routine is disciplined: black coffee in the morning, a 12pm lunch of sourdough and cheese, and a strict 'no code after 7PM' rule to prevent burnout. She's frugal with most expenses but will splurge on quality mechanical keyboards. Socially, she prefers small gatherings with her close-knit group of ex-university friends who also work in tech - their WhatsApp group is a constant stream of memes about legacy systems. She dates occasionally but finds tech men 'emotionally undeveloped' and prefers men in craftsmen trades who respect her expertise.

Work life

Florence works at a boutique digital agency specializing in Laravel-based solutions for mid-market retailers. Her typical day starts by checking the production error logs for her retail clients' portals. She maintains a legacy Scriptcase system for one client but has been steadily migrating critical functions to custom Laravel modules. Her screen is currently split between PHPStorm, a custom Bootstrap admin panel she's building, and a spreadsheet tracking client feature requests. The team's workflow is hybrid-agile: they do biweekly sprints but mostly work independently. Florence prides herself on leaving documentation so perfect that even the least technical PM can understand it. Her biggest frustration is the office's refusal to adopt a proper project management tool - they still use Trello for everything, and she's had to build her own reporting scripts to fill the gaps. She gets deep focus between 11AM and 2PM when the office is quietest, and she's known to 'go dark' on Slack during those hours. The team respects her technical authority but sometimes complains she's too perfectionist about code standards. Her boss occasionally asks her to 'just make it work' for time-sensitive projects, which she finds professionally insulting.

Relationships

Florence's parents are retired academics who live in Cambridge and call every Sunday to ask when she's getting a 'proper job'. Her younger sister works in fashion marketing and is her only close family member. Her professional network consists of her agency colleagues (whom she respects but doesn't socialize with) and a loose group of Manchester-based developers she met through local meetups. She admires one senior developer at a competitor agency who posts thoughtful articles about Laravel architecture - she's been trying to get an introduction to him for months. Her romantically previous partner was an electrical engineer who understood her need for deep focus time, but they broke up because she wanted stability more than he did.

How they decide

Research-heavy and data-driven, but once convinced, commits fully. Will spend hours evaluating options but then implement decisively. Prefers to make decisions after collecting enough information to eliminate uncertainty. Values peer advice from respected developers more than marketing claims. Dislikes being pressured to decide quickly.

How they sound

Florence speaks in precise, measured sentences with a faint Northern accent. She avoids jargon when possible and hates buzzwords like 'synergy'. Her humor is dry and often self-deprecating. She'll say things like 'I don't have a problem with basic solutions, I just have a problem when basic solutions pretend to be advanced ones'. She's comfortable with technical vocabulary but avoids it unless necessary. Her voice always sounds slightly tired at the end of the day, not from exhaustion but from the mental effort of explaining systems to non-technical people.

Personality traits

  • The 'quiet professional' who speaks only when necessary in meetings
  • Obsessively checks CRUD forms for edge cases before deployment
  • Walks three miles daily to think through systems architecture
  • Keeps a physical notebook full of half-finished PHP snippets
  • Secretly enjoys the predictability of retail admin panels
  • Tries to convince the team to adopt new tools but gets vetoed
  • Hates meetings before 10AM because 'the internet isn't awake yet'
  • Organizes her desk by tool purpose, not aesthetic
  • Will debug someone else's code for free if asked politely
  • Has a file of 'defensive PHP' patterns she recycles across projects

Goals

  • Lead the migration from Scriptcase to a fully custom Laravel architecture for her retail client
  • Convince the agency to adopt a proper devOps pipeline (currently they do manual deployments)
  • Finish restoring the teak sideboard before her birthday party next month
  • Build a personal portfolio site that showcases her systems design philosophy
  • Find a developer community that values clean architecture as much as she does

Problems & frictions

  • The agency's small size means she frequently has to wear multiple hats including DevOps and QA
  • Scriptcase's maintenance headaches are increasing as the client adds new requirements
  • Her team's reluctance to adopt new tools stifles her ability to work efficiently
  • Finding the right balance between customizing admin panels and using generators
  • Her landlord is threatening to raise her rent by 15% making her consider house hunting

Values

  • client delivery
  • clean handoff
  • responsiveness
  • ornery professionalism
  • tool pragmatism

Interests

  • Laravel
  • Bootstrap
  • workflow tools
  • industrial design
  • old-school tech radio

Media habits

  • Dribbble for design inspiration
  • Indie Hackers for niche dev discussions
  • BBC Radio 4 for background noise
  • YouTube PHP tutorials at 1.5x speed
  • The Guardian for slow-morning reading

Questions & answers

Florence Ziemann’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.phpcrudgenerator.com/ (PHP CRUD Generator) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    First, the page is too wordy—it dumps mountains of technical text without visual hierarchy. I’d skim the first paragraph, see 'generate Bootstrap CRUD forms,' and maybe click the demo link. But I’d leave if I can’t immediately grasp: *Will this replace Scriptcase?* The demo might tempt me, but the mention of '5 databases' feels redundant (I use MySQL). The $50 price is buried, and the page doesn’t address my pain points: *Can it integrate with Laravel elegantly?* I need reassurance that the output isn’t a spaghetti mess I’ll have to refactor. The 'clean, documented PHP' claim is promising, but without code samples or migration tips for legacy systems, I’m skeptical. I’d sign up for a trial if the demo showed how it handles complex relaciones—my retail client’s admin has nested tables and custom validations. Right now, it feels like another tool I’d custom-build around rather than actually use.
    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.