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

Jessy Bultmann

Jessy Bultmann

Platform engineer on a team that already pays for a sandbox

Full-depth AI personas

Why this persona fits the audience

She is on a 5-person platform team that pays for a cloud lab subscription to spin up Azure-like sandboxes for internal developers. She still keeps a local copy of service endpoints, runs reset scripts for sample data, and documents the environment in a Confluence table for repeatable use.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Platform engineer
  • Income: €74k
  • Education: M.Sc. Software Engineering
  • Company size: 1000+ employees
  • Years in role: 3
“The most elegant solutions are the ones that disappear, letting the work just happen.”

Jessy Bultmann's journey into platform engineering began with a fascination for how complex systems are built and maintained. Growing up in a family that valued practicality and self-sufficiency, she developed an early aptitude for problem-solving. Her M.Sc. in Software Engineering from Humboldt University of Berlin provided a strong theoretical foundation, but it was her internship at a mid-sized software company that ignited her passion for the operational side of technology. She thrived on the challenge of building reliable infrastructure that empowered development teams. After graduating, she joined her current company, a large enterprise with a global presence, drawn by its reputation for investing in its engineering talent and its commitment to modern cloud practices. Her current role on the 5-person platform team is central to her professional identity. The team is tasked with providing and managing development sandboxes, a critical but often resource-intensive service. Despite the company paying for a comprehensive cloud lab subscription, Jessy finds herself frequently augmenting it. She maintains local copies of service endpoints for quick testing, develops and runs custom reset scripts for sample data to ensure consistent developer experiences, and meticulously documents environment configurations in Confluence. This dual approach—leveraging the paid service while building custom solutions—stems from her drive for precision and efficiency. She believes that even with existing tools, there's always room for improvement and optimization. Her income of €74k allows for a comfortable life in Berlin, but she remains mindful of her spending, preferring to invest in quality and long-term value, whether it's for her home setup or her professional toolkit. She views her work not just as a job, but as a continuous learning process, constantly seeking ways to make the developer experience smoother and more robust.

Background & daily life

A day in their life

Jessy's typical weekday starts around 7:00 AM with a carefully brewed pour-over coffee. After a quick breakfast and checking personal emails, she heads to her home office. Her workday begins with a stand-up meeting with her platform team, discussing ongoing tasks and blockers. The rest of the morning is often spent writing or refining IaC scripts for the sandbox environment, troubleshooting a developer's reported issue, or updating Confluence documentation. Lunch is usually a simple, home-prepared meal. The afternoon might involve a cross-team sync, reviewing a colleague's pull request, or exploring new tooling that could improve their sandbox offering. She aims to log off by 6:00 PM, leaving her evenings free for personal pursuits.

Lifestyle

Jessy lives in a shared apartment in Berlin's Prenzlauer Berg with her partner, a graphic designer. Their living space is functional and minimalist, reflecting their shared appreciation for design and order. Weekends are a mix of exploring Berlin's diverse neighborhoods, visiting flea markets, and dedicating time to her passion for specialty coffee, meticulously dialing in her espresso machine. She enjoys quiet evenings with her partner, often playing strategy board games or reading. Financially, she's a saver, prioritizing long-term security and experiences like city breaks over impulsive purchases, though she'll splurge on high-quality tools for her hobbies.

Work life

As a platform engineer at a large tech company, Jessy's days are focused on enabling internal developers. Her team manages the cloud sandbox environment, a crucial but often complex system. She spends a significant portion of her time troubleshooting issues, refining deployment scripts, and ensuring the sandboxes are stable and performant. Collaboration with developers is key, but often involves translating their needs into platform capabilities. The pressure to maintain high uptime and reduce developer friction is constant, driving her to seek out more robust and automated solutions.

Relationships

Jessy has a close relationship with her partner, who provides a supportive and grounding influence. Her friendships are deep rather than wide, consisting of a few long-term friends from university and work. She values their intellectual discussions and shared interests. Her parents, who live in a smaller town in Lower Saxony, are proud of her career but don't fully grasp the technical details of her work.

How they decide

Jessy is a cautious and research-heavy decision-maker, especially concerning work-related tools or significant personal investments. She thoroughly evaluates options, reads documentation, and often seeks out peer reviews or case studies. For personal hobbies, she might be slightly more impulsive if a high-quality, well-reviewed item aligns perfectly with her needs, but still prioritizes value and longevity.

How they sound

Jessy speaks with a clear, measured cadence, often pausing to formulate her thoughts precisely. Her tone is generally calm and professional, even when discussing complex technical issues. She avoids overly casual slang or jargon when speaking with developers outside her immediate team, preferring clear, unambiguous language. When excited about a technical solution, her speech might quicken slightly, but she maintains a grounded, analytical delivery.

Personality traits

  • detail-oriented
  • resourceful
  • self-motivated
  • methodical
  • reserved
  • analytical
  • pragmatic
  • observant
  • patient

Goals

  • Achieve a senior platform engineering role within the next five years.
  • Contribute to open-source projects related to cloud infrastructure.
  • Develop a more sustainable and energy-efficient home environment.
  • Master advanced coffee roasting techniques.
  • Travel to Japan for a cultural and culinary exploration.

Problems & frictions

  • The current cloud sandbox environment, while paid for, still requires significant manual intervention for setup and data seeding.
  • Bridging the gap between developer needs and platform capabilities can be challenging due to differing technical perspectives.
  • Keeping up with the rapid pace of cloud technology evolution requires constant learning and adaptation.
  • Balancing the need for robust, secure infrastructure with the desire for developer agility.
  • Finding time for deep work amidst frequent meetings and urgent requests.

Values

  • independence
  • precision
  • low-friction collaboration
  • autonomy
  • continuous learning
  • efficiency

Interests

  • platform engineering
  • coffee brewing
  • city breaks
  • sustainable living
  • board games
  • DevOps tooling

Media habits

  • tech podcasts (e.g., Software Engineering Daily, The Changelog)
  • industry blogs (e.g., Martin Fowler, InfoQ)
  • e-books on cloud architecture and Kubernetes
  • streaming services for downtime
  • technical documentation sites

Questions & answers

Jessy Bultmann’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: the product is a single-binary Azure emulator. 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.

    A single-binary Azure emulator... that's an interesting concept. My biggest problem isn't with the sandboxes themselves, but the *data*. Developers need consistent, realistic data to test against, and seeding it manually or with custom scripts is time-consuming. It's not just about setup time; it's the potential for inconsistencies and the effort spent debugging data-related issues. We've tried various scripting approaches, but it's a constant battle to keep them updated and reliable.
    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.