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

Christie Gerlach

Christie Gerlach

Engineering manager at a small AI consultancy

Full-depth AI personas

Why this persona fits the audience

Manages a 6-person London team that builds custom AI chat and agent workflows for clients. She coordinates code review, dependency checks, and container scans using open-source tools plus a shared checklist; most work is done in Jira, Slack, and spreadsheets rather than a dedicated security workflow.

  • Age: 41
  • Location: London, UK
  • Occupation: Engineering Manager
  • Income: £95,000/year
  • Education: M.S. in Software Engineering
  • Company size: Small consultancy (25 employees total)
  • Years in role: 3
“You can move fast, but you cannot ship broken promises without paying for it later.”

Christie Gerlach, 41, is the bedrock of a six-person engineering team at a small but ambitious AI consultancy in London. With an M.S. in Software Engineering and over fifteen years of industry experience, she transitioned from hands-on coding to management five years ago, driven by a desire to build better systems rather than just write them. Currently earning £95,000 annually, she operates in a high-pressure environment where the pace of AI innovation often outstrips the maturity of security tooling. Her team specializes in building custom chat interfaces and autonomous agents for UK and European clients, navigating a landscape where trust is the primary currency. Unlike larger enterprises with dedicated DevSecOps teams, Christie manages the entire security lifecycle manually. She orchestrates code reviews, dependency checks, and container scans using a patchwork of free, open-source utilities. These findings are meticulously logged in a sprawling, color-coded Excel spreadsheet that serves as the team's single source of truth. This approach reflects her core value of process clarity; she believes that until a process is documented and repeatable, it cannot be trusted. However, this reliance on manual coordination and disparate tools is becoming a liability. As the complexity of the agents increases, the spreadsheet is prone to human error, and the lack of an integrated workflow slows down deployment cycles. Christie recently made the difficult decision to pause a major client project to refactor their CI/CD pipeline, a move that annoyed stakeholders but was necessary to prevent potential data leaks. She is deeply invested in the ethics of AI, often debating the nuances of model hallucinations and prompt injection risks with her team. Financially, she is conservative, having paid off her student loans early and maxing out her pension contributions, viewing money as a tool for security rather than status. Her professional life is defined by a constant tension between the client's demand for speed and her own imperative for quality. She is currently exploring ways to automate parts of her security checklist without breaking the bank, though she remains wary of solutions that promise ease of use at the cost of transparency. To her, the future of AI isn't just about intelligence; it's about reliability.

Background & daily life

A day in their life

Christie wakes at 5:30 AM for a run along the Thames, returning just in time to shower and prepare for the Tube ride to central London. Her workday begins with a stand-up meeting where she reviews the sprint progress and addresses a blocker regarding a dependency conflict in one of the client's containers. Mid-morning is spent reviewing pull requests and updating the master security spreadsheet, a task she dreads but knows is essential. After lunch, she has a client call to explain why a requested feature requires a week of additional hardening. The afternoon involves one-on-ones with her engineers, focusing on career growth and removing obstacles. She leaves the office by 6:30 PM to attend a local running club event, ensuring she disconnects from work emails until the next morning. Dinner is a quick affair with her partner, followed by an hour of reading about distributed systems or planning the next week's roadmap.

Lifestyle

Christie lives in a slightly cramped but characterful Victorian terrace in South London, sharing the space with her partner, a graphic designer. Her mornings are rigidly structured: a 5:30 AM alarm, a long run through the park to clear her head, and a quiet breakfast before the commute. She is financially prudent, prioritizing mortgage payments and retirement savings over luxury travel, though she splurges occasionally on high-end coffee gear or running shoes. Socially, she maintains a tight-knit circle of friends from university and running clubs, valuing deep conversation over large parties. Evenings are usually reserved for unwinding with a book or light tech reading, rarely working past 8 PM unless a critical deployment looms.

Work life

Christie leads a six-person engineering squad at a boutique AI consultancy, where they build bespoke chatbots and autonomous agents for enterprise clients. Her day is a juggling act of technical oversight and people management. She relies heavily on Jira for task tracking, Slack for rapid communication, and a notoriously complex spreadsheet for managing security dependencies. While the team uses various open-source scanners, Christie personally curates a checklist to ensure every container scan and code review passes before shipping. The pressure comes from the speed of the AI sector; clients demand rapid iteration, yet she must enforce a quality gate that often feels manual and fragile. She spends significant mental energy translating vague client requirements into secure, deployable architecture while shielding her team from scope creep.

Relationships

Christie is married to David, whose calm demeanor balances her intensity. They have no children but frequently discuss starting a family in three years. Her professional network is strong; she actively mentors junior developers and sits on an advisory board for a local coding bootcamp. She trusts peer recommendations from other engineering leaders more than marketing material. Her immediate influence comes from the CTO of her firm and a former mentor who now works at a FAANG company, both of whom shape her views on scalability and ethical AI.

How they decide

Christie is a cautious, evidence-based decider who values process integrity above all else. She rarely makes impulsive choices, preferring to gather data, consult with her team, and analyze the long-term implications before committing. She is skeptical of flashy claims and looks for concrete proof points, such as case studies or transparent methodology. When evaluating new approaches, she weighs the friction against the value add, often defaulting to the status quo if the integration cost seems too high relative to the perceived benefit.

How they sound

Christie speaks with a crisp, clipped British accent, favoring directness over pleasantries. Her cadence is measured and deliberate, rarely rushing her sentences even when discussing urgent matters. She avoids hyperbole and corporate jargon like 'synergy' or 'disrupt,' preferring plain English and specific technical terms. In meetings, she asks clarifying questions frequently to ensure alignment. She tends to use phrases like 'Let's verify the data' or 'What's the risk here?' rather than making assumptions. Her tone is generally neutral but can become sharp if she perceives a lack of rigor in a plan.

Personality traits

  • Methodical
  • Pragmatic
  • Diplomatic
  • Detail-oriented
  • Calm under pressure
  • Protective of team time
  • Skeptical of hype
  • Systematic thinker
  • Direct communicator
  • Disciplined

Goals

  • Establish a repeatable, automated security pipeline that doesn't slow down development velocity
  • Promote two senior engineers to lead their own squads within the next year
  • Complete a full marathon without injury by autumn
  • Reduce weekend emergency on-call incidents to near zero
  • Achieve architectural certification in a major cloud provider's AI stack
  • Build a culture where 'shipping fast' never compromises 'shipping safe'

Problems & frictions

  • The manual nature of their current security checklist creates bottlenecks during peak sprints
  • Difficulty proving to clients exactly how their custom agents handle data privacy without third-party validation
  • Spreadsheets becoming increasingly error-prone as the number of dependencies grows
  • Tension between the desire for rapid prototyping and the need for rigorous testing
  • Limited budget to hire additional DevSecOps specialists
  • Keeping up with the exploding rate of new LLM vulnerabilities versus stable tooling

Values

  • quality delivery
  • process clarity
  • client trust
  • balanced workload
  • technical autonomy

Interests

  • LLM application design
  • team leadership
  • cloud infrastructure
  • vintage mechanical watches
  • marathon training

Media habits

  • Hacker News daily digest
  • The Changelog podcast
  • Substack newsletters on AI safety
  • Local running group WhatsApp
  • LinkedIn for industry trends

Questions & answers

Christie Gerlach’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on DevHunt: Find and fix vulnerabilities in code, dependencies and containers - Every AI-building team faces one question: can you trust what you're shipping? the product... What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest problem we face is the sheer manual effort involved in ensuring the security of our AI agents. We're patching together open-source tools and a frankly overloaded spreadsheet to track code, dependency, and container vulnerabilities. It's a time sink – I spend hours each week collating findings and chasing down issues. The risk of human error is significant, and honestly, it slows us down considerably when clients want rapid iteration. We've had to pause projects before to fix these gaps, which frustrates stakeholders and impacts our delivery timelines. I've tried creating more robust checklists and standardizing our scanning approach, but it's still a house of cards.
    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.