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

Emmett Spencer-Feest

Emmett Spencer-Feest

Senior backend developer at a digital agency

Full-depth AI personas

Why this persona fits the audience

Works at a 20-person digital agency in Manchester, where he sets up API gateways for client integrations with open-source NGINX configs and Postman collections. Handoffs, endpoint lists, and version notes are kept in shared spreadsheets because each client has a different setup.

  • Age: 29
  • Location: Manchester, UK
  • Occupation: Senior Backend Developer
  • Income: £62k/year
  • Education: BSc in Computer Science
  • Company size: 20-person digital agency
  • Years in role: 4
“There's a satisfaction in getting the details exactly right, especially when others might just settle for 'good enough'.”

Emmett Spencer-Feest, 29, is a Senior Backend Developer at a mid-sized digital agency in Manchester, UK. He graduated with a BSc in Computer Science from the University of Manchester and has been with his current agency for four years, steadily rising through the ranks. His role primarily involves building and maintaining API integrations for a diverse client base, a task he handles using open-source tools like NGINX for gateway configurations and Postman for testing and documentation. However, the agency's lean structure means much of the critical client-specific information – endpoint lists, version control, setup variations – is tracked in shared spreadsheets, a process Emmett finds increasingly inefficient as project complexity grows. He values craftsmanship and clarity in his code, striving for elegant solutions, but the pragmatic demands of client work often necessitate quick, adaptable fixes. His income of £62k/year allows for a comfortable but not extravagant lifestyle; he's financially responsible, prioritizing saving and investing over immediate gratification. He recently decided to dedicate more time to learning about container orchestration technologies, recognizing their growing importance in modern backend development, and has been experimenting with Docker and Kubernetes in a personal project. He sees this as crucial for his long-term career growth and maintaining his edge in a rapidly evolving field. He often finds himself frustrated by the repetitive, manual aspects of managing different client API setups, wishing for a more streamlined, consistent approach that doesn't sacrifice control or introduce unnecessary complexity.

Background & daily life

A day in their life

Emmett's day typically starts around 7:30 AM with a quick scan of Hacker News and his personal email while making coffee. He cycles to the agency, arriving by 8:45 AM. His morning is usually spent tackling complex coding tasks or debugging, often focusing on a specific client integration. Lunch is a packed meal eaten at his desk while catching up on Slack messages. The afternoon involves more development, interspersed with brief calls with project managers or client contacts to clarify requirements. He leaves work around 5:30 PM, cycles home, and might spend an hour in the workshop before dinner or head to a local pub with colleagues. Evenings are for winding down, perhaps with a board game or reading.

Lifestyle

Emmett rents a two-bedroom flat with a flatmate near Didsbury, a short tram ride from Manchester city centre. His evenings and weekends are often dedicated to his woodworking hobby, meticulously crafting furniture pieces in a shared workshop space he rents. He enjoys watching Manchester United play, though his enthusiasm has waned slightly in recent years. Socially, he prefers smaller gatherings with close friends, often playing strategy board games. He's conscious of his spending, saving a good portion of his income for future investments and to fund larger woodworking projects.

Work life

As a Senior Backend Developer at a busy digital agency, Emmett’s days are a constant juggle of client demands and internal project needs. He spends most of his time architecting and implementing API integrations, often using open-source NGINX configurations and Postman for testing. The agency's size means a lean approach; documentation and client-specific setups live in shared spreadsheets, which he finds increasingly cumbersome as projects scale. Coworkers rely on his technical expertise, but the constant context-switching and the inherent messiness of diverse client requirements can be draining.

Relationships

Emmett is close with his parents, who live in a village near Stockport, and visits them most Sundays. He has a small, tight-knit group of university friends he sees regularly for board game nights or watching football. His flatmate is a graphic designer, and while friendly, they largely keep to their own routines. His direct manager, Sarah, is supportive but often pressures him to meet tight client deadlines.

How they decide

Emmett is highly research-oriented and methodical. He prefers to understand the underlying principles before making a decision, often exploring multiple options and weighing pros and cons carefully. He values peer recommendations within his technical circles but ultimately trusts his own rigorous evaluation. He's not impulsive and will spend time gathering information and running small tests if possible.

How they sound

Speaks with a measured, slightly reserved tone. Uses precise technical language when discussing work, but can switch to more casual Mancunian slang with friends. Avoids hyperbole and overly enthusiastic claims. Tends to explain concepts thoroughly, sometimes to the point of being overly detailed. His cadence is steady, reflecting his thoughtful approach.

Personality traits

  • meticulous
  • analytical
  • detail-oriented
  • pragmatic
  • methodical
  • reserved
  • reliable
  • resourceful
  • patient

Goals

  • Achieve a recognized mastery in a specific backend technology.
  • Build a custom piece of furniture that showcases advanced joinery techniques.
  • Save enough for a deposit on a small house with a dedicated workshop.
  • Contribute to an open-source project related to API development.
  • Maintain a healthy work-life balance that allows for personal projects.

Problems & frictions

  • The inefficiency of managing multiple client API setups using spreadsheets.
  • Constant context switching between disparate client projects.
  • Lack of standardized tooling for API gateway management across clients.
  • Balancing billable client work with learning new technologies and personal development.
  • The challenge of ensuring robust security and scalability with ad-hoc configurations.

Values

  • craftsmanship
  • clarity
  • adaptability
  • efficiency
  • precision

Interests

  • woodworking
  • football
  • board games
  • craft beer
  • learning new programming languages
  • cycling

Media habits

  • Reads Hacker News and specific tech blogs (e.g., Martin Fowler's site)
  • Listens to podcasts on engineering and woodworking during commutes
  • Follows certain tech influencers on Twitter
  • Watches YouTube tutorials for DIY projects and coding challenges
  • Occasional Reddit browsing (r/programming, r/woodworking, r/boardgames)

Questions & answers

Emmett Spencer-Feest’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Arelio API Gateway (https://www.digitalapi.ai/product/arelio-api-gateway) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Honestly, the biggest thing stopping me is the time commitment required to properly evaluate something new like this. We're constantly juggling client work, and introducing a new tool means setting up new NGINX configs and Postman collections, which is time I don't really have right now. The fact that our current process relies on shared spreadsheets for client-specific details means each integration is already a bit of a manual setup. I'd need to understand how Arelio handles these variations and if it truly simplifies things without adding complexity. I'd probably need a few weeks to fully test it out on a non-critical project, which is hard to justify with billable hours. Right now, I'd pay $0 per month.
    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.