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

Aubrey Koch

Aubrey Koch

In-house platform engineer supporting a content team

Full-depth AI personas

Why this persona fits the audience

He works at a mid-sized ecommerce company in Chicago and owns several internal WordPress sites and plugins used by marketing and customer support. His day-to-day includes maintaining a custom plugin codebase, coordinating with nontechnical stakeholders, and handling releases through CI and a staging environment. He is one of two engineers who touch the plugin layer.

  • Age: 41
  • Location: Chicago, Illinois, USA
  • Occupation: Platform engineer
  • Income: $135k-$175k
  • Education: Master's degree in information systems
  • Company size: mid-sized
  • Years in role: 7
“The best system is the one that just works, reliably, without needing constant attention.”

Aubrey Koch has spent the last seven years as an in-house platform engineer at a mid-sized Chicago-based ecommerce company, a role that has solidified his reputation for meticulousness and reliability. His journey into platform engineering wasn't a direct path; he initially pursued a Master's degree in Information Systems with a broader focus on database management and system administration. However, during an internship, he found himself drawn to the practical challenges of building and maintaining the tools that empower content creators and support teams. This led him to his current position, where he is one of two engineers responsible for the company's internal WordPress ecosystem. His days are consumed by the intricacies of custom plugin codebases, ensuring seamless integration with various marketing and customer support workflows. Aubrey thrives on the challenge of maintaining stability while also driving incremental improvements. He recently spearheaded the migration of a critical customer support plugin to a more modular architecture, a project that involved extensive refactoring and close collaboration with the support team lead to define requirements. This initiative, while time-consuming, significantly improved the plugin's maintainability and performance, aligning perfectly with his core value of building robust, long-lasting solutions. He views his work not just as writing code, but as engineering a stable foundation for the business's digital presence. His approach is deeply rooted in a belief in clear ownership and predictable outcomes, often leading him to meticulously document every change and thoroughly test releases through a dedicated CI and staging environment before pushing to production. This methodical approach, while sometimes perceived as slow by those seeking rapid iteration, has earned him the trust of his non-technical colleagues, who rely on his expertise to keep their digital tools running smoothly. He sees his role as a steward of internal technology, ensuring its longevity and efficiency.

Background & daily life

A day in their life

Aubrey's typical weekday starts around 6:30 AM with getting his kids ready for school. After dropping them off, he heads to the office, grabbing a coffee on the way. His morning is often dedicated to focused coding, tackling bug fixes or developing new features for an internal plugin. Around lunchtime, he might have a brief sync with a marketing manager to discuss an upcoming campaign's technical needs. The afternoon involves code reviews, deploying updates to the staging environment, and documenting recent changes. He aims to leave by 5:30 PM to make it home for family dinner, often spending the evening helping with homework or unwinding by reading tech blogs.

Lifestyle

Aubrey lives in a comfortable, two-story home in a quiet Chicago suburb with his wife and two school-aged children. Weekends are often a blend of family activities, like soccer games or trips to the Museum of Science and Industry, and personal projects. He enjoys brewing his own craft beer, meticulously following recipes and experimenting with new hops. Financially, he's focused on long-term security, diligently contributing to retirement accounts and college funds, viewing his income as a means to provide stability rather than a tool for ostentatious display.

Work life

Aubrey's role as an in-house platform engineer is centered on supporting the content and marketing teams at his mid-sized ecommerce company. He's one of only two engineers who manage the company's suite of internal WordPress sites and custom plugins. His days are a mix of deep-focus coding on plugin maintenance, collaborating with non-technical stakeholders to understand their needs, and managing the release pipeline through CI/CD and staging environments. The pressure is on to ensure platform stability and smooth deployments, as any disruption directly impacts content creation and customer engagement.

Relationships

Aubrey is married to Sarah, a graphic designer, and they have two children, ages 8 and 11. His primary social circle consists of his immediate family and a few close friends from his university days. At work, he has a collegial but somewhat distant relationship with his fellow plugin engineer and relies on clear, direct communication with the marketing and customer support leads.

How they decide

Aubrey is a highly cautious and research-driven decision-maker. He prefers to thoroughly evaluate options, weigh pros and cons, and understand the long-term implications before committing to a course of action. He values data, established best practices, and peer validation (within trusted technical circles) when making technical choices.

How they sound

Aubrey speaks in a measured, clear, and slightly formal tone. He avoids slang and hyperbole, preferring precise language. His cadence is steady, and he often pauses to consider his words carefully, especially when explaining technical details. He's not one for small talk but is polite and professional in all interactions.

Personality traits

  • methodical
  • detail-oriented
  • reserved
  • responsible
  • analytical
  • patient
  • pragmatic
  • thorough

Goals

  • Achieve a more streamlined and automated release process for internal tools.
  • Mentor junior engineers on best practices for plugin development.
  • Develop a more robust internal documentation system for the platform.
  • Maintain a healthy work-life balance to be present for his family.
  • Contribute to open-source WordPress projects in his spare time.

Problems & frictions

  • Balancing the urgent requests from non-technical teams with long-term platform improvements.
  • Managing technical debt within legacy plugin codebases.
  • Ensuring consistent development and deployment practices with the other plugin engineer.
  • Keeping up with the rapid pace of WordPress core and plugin updates without introducing regressions.
  • Communicating complex technical concepts to stakeholders with limited technical understanding.

Values

  • stability
  • clear ownership
  • maintainability
  • efficiency
  • predictability

Interests

  • release engineering
  • internal tools
  • WordPress admin workflows
  • system architecture
  • craft beer brewing

Media habits

  • TechCrunch
  • Ars Technica
  • The Changelog podcast
  • local Chicago news
  • YouTube tutorials

Questions & answers

Aubrey Koch’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at WP Bones (https://wpbones.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This WP Bones framework appears to offer a structured approach to building WordPress plugins, which could be beneficial for maintaining our internal codebases. The idea of having Laravel-like features such as Eloquent models and migrations is intriguing. However, I don't see any pricing information on this page, which makes it impossible to assess value. If it were a one-time purchase for a perpetual license, I might consider up to $150. As a monthly subscription, I would need to see significant ongoing value, perhaps around $20-$30 per month, to justify it. Without clear pricing and details on support, it's difficult to commit.
    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.