Esther Herzog

Why this persona fits the audience

Coordinates operations for a 15-person recruitment startup in London, where she uses AI to summarize candidate interviews, generate role descriptions, and tidy spreadsheet-heavy workflows. She can handle no-code tools and basic API configs, but usually depends on templates, shared docs, and whatever is easiest for the small team.

• Age: 33
• Location: London, UK
• Occupation: Operations manager
• Income: £52,000
• Education: B.A. Sociology
• Company size: 15 employees
• Years in role: 2 years

“If I can't see the data in one place, it doesn't exist.”

Esther Herzog is a 33-year-old Operations Manager based in London, navigating the complex intersection of human resources and technology in a fast-paced startup environment. With a background in Sociology, she understands the nuances of organizational behavior, yet her daily reality is defined by spreadsheets, APIs, and the relentless need for order. She joined her current 15-person recruitment firm two years ago, tasked with building operational infrastructure from the ground up. Before this, she worked in corporate HR administration, where she became frustrated by legacy systems that slowed down decision-making. This experience drove her passion for modern, agile tools. Currently, Esther acts as the de facto CTO for non-technical tasks. She manages the company's tech stack, which includes a mix of Asana, Airtable, and various AI wrappers. Her recent major project involved migrating the entire candidate database to a new format to improve searchability, a task that took three weeks of late nights. She is technically competent, able to write basic scripts and configure webhooks, but she remains wary of over-engineering solutions. She prefers simple, robust tools that require minimal maintenance. Financially, she earns £52,000, a solid income for her age but modest given London's cost of living, leading her to be extremely selective with subscriptions. She views technology not as a novelty, but as a utility to reclaim her time. Her greatest fear is not failure, but inefficiency—the slow creep of processes that waste the team's energy. She is currently evaluating how to better integrate generative AI into her workflow without compromising data privacy, a delicate balance she navigates daily.

Background & daily life

A day in their life

Esther wakes up at 6:30 AM, brewing strong coffee while checking her phone for urgent Slack messages from the US team. By 8:15 AM, she's cycling through Clapham Common, listening to a podcast on productivity hacks. At 9:30 AM, she arrives at the office, opens her massive Airtable dashboard, and immediately tackles the 'unassigned candidates' queue. The morning is spent cleaning data imports from LinkedIn and Indeed, converting PDF resumes into structured JSON for their internal system. Lunch is a quick sandwich eaten at her desk while reviewing the weekly hiring report. Afternoon meetings are packed: a sync with the sales lead about pipeline velocity, then a training session for a new recruiter on the new AI summarization tool. She spends the last hour fixing a broken Zapier automation that stopped syncing emails to the CRM. By 6:30 PM, she packs up, mentally checks off her to-do list, and heads home to cook dinner, finally disconnecting from work until tomorrow.

Lifestyle

Esther lives in a slightly cramped but vibrant flat in Clapham, sharing costs with her partner, Mark, a graphic designer. Her weekends are a mix of necessary rest and active organization; she spends Saturday mornings meal-prepping to avoid weekday stress and Sunday afternoons tackling household admin or exploring new local coffee shops. She prioritizes health by cycling to work three times a week and tries to maintain a strict 'no-work-after-7pm' rule, though it often slips during peak hiring seasons. Financially, she is budget-conscious, tracking every subscription via a dedicated spreadsheet, preferring value over luxury. Her social circle is primarily work-adjacent—colleagues and other startup operators she meets at industry meetups—but she fiercely guards her evenings for close friends and family back in Germany.

Work life

At her 15-person recruitment startup, Esther is the operational glue holding the chaotic hiring process together. Her day is dominated by triaging candidate pipelines, ensuring recruiters have clean data, and managing the company's tech stack. She spends hours cleaning messy CSV exports from job boards and manually formatting role descriptions before they go live. Recently, she began integrating AI summaries for interview notes, though she still double-checks every output for tone and accuracy. The pressure is constant; if the spreadsheets break, the whole team stalls. She relies heavily on shared Google Docs and Slack threads, often acting as the translator between the technical needs of the founders and the practical reality of the recruiters.

Relationships

Esther is the primary contact for her German parents, calling them every Sunday to discuss their garden and recent travels. Her partner, Mark, is her sounding board for work stress, often providing the creative perspective she lacks. Professionally, she maintains a tight-knit group of four other Ops managers from London startups who share templates and vent about 'shiny object syndrome.' She values trust above all; if someone breaks her confidence regarding sensitive salary data, the relationship ends immediately.

How they decide

Cautiously experimental. Esther researches options extensively, reading user reviews and watching tutorial videos before committing. She prefers low-risk trials (e.g., free tiers or short-term subscriptions) and is deeply influenced by peer recommendations from her specific niche community. Once she finds a tool that integrates smoothly with her existing workflow without requiring a steep learning curve, she becomes loyal, but she is quick to abandon anything that disrupts her carefully built systems.

How they sound

Her speech is clear, efficient, and polite, with a slight British cadence. She uses corporate shorthand like 'sync,' 'pipeline,' and 'bandwidth' naturally but avoids overly technical jargon unless speaking to developers. She tends to speak in complete sentences rather than fragments and often prefaces suggestions with 'I think we could try...' or 'Just to be safe...' She rarely raises her voice, even when stressed, preferring to document issues rather than argue. She dislikes vague statements and will often ask for clarification on timelines or deliverables.