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

Emily Sutschet

Emily Sutschet

Technical product designer at an agency

Full-depth AI personas

Why this persona fits the audience

At a seven-person digital agency in Berlin, she spins up local prototype sites and exposes them over SSH so account managers and clients can review them without deployment. She documents the temporary addresses in Notion and reuses a saved terminal alias for the same workflow across projects.

  • Age: 34
  • Location: Berlin, Germany
  • Occupation: Technical product designer
  • Income: €52k-€68k
  • Education: Master's degree in interaction design
  • Company size: 7
  • Years in role: 5
“The most satisfying part of my job is when a complex idea clicks into a simple, usable interface that just *works*.”

Emily Sutschet, 34, is a technical product designer at a compact digital agency nestled in the vibrant heart of Berlin. Holding a Master's degree in Interaction Design from a respected German university, she has cultivated a reputation for her ability to bridge the gap between conceptual design and functional implementation. Her professional journey began with a strong foundation in visual design principles, but a natural inclination towards problem-solving and a fascination with how things work under the hood led her to specialize in technical product design. She's been in this specific role for five years, honing her skills in creating tangible, interactive prototypes. Emily's current workflow often involves spinning up local prototype sites and exposing them over SSH, a method she’s refined to allow account managers and clients to review work without the need for full deployment. She meticulously documents these temporary addresses in Notion and has a saved terminal alias that streamlines this process across various projects, a testament to her focus on efficiency and repeatable workflows. This approach is born from a desire for independence and control over her work, allowing her to iterate quickly and present functional demos with minimal friction. She values collaboration, but on her own terms, preferring focused teamwork over constant interruptions. Her income places her comfortably within Berlin's middle class, allowing for a good quality of life without excessive luxury. Emily is driven by a deep appreciation for usability and craftsmanship, constantly seeking elegant solutions to complex design challenges. She sees her work not just as a job, but as a craft where continuous learning and refinement are paramount. Her decision to remain at a smaller agency stems from a desire to have a direct impact and maintain a close connection to the projects she works on, valuing the agility and direct communication it affords over the potential bureaucracy of larger firms.

Background & daily life

A day in their life

Emily's typical weekday begins around 7:30 AM with coffee and a quick check of her personal photography blog. She cycles to the agency by 9:00 AM, grabbing a pastry from her favorite bakery. The morning is often spent in focused design work, refining UI elements or building out a new feature in Figma. After lunch, she'll dedicate time to client-facing tasks: spinning up a prototype site via SSH, documenting the temporary URL in Notion, and coordinating with the account manager for client review. The afternoon might involve a team stand-up, a quick design critique session, or troubleshooting a tricky CSS issue. She usually leaves around 6:00 PM, often stopping at a local market before heading home to cook dinner and unwind.

Lifestyle

Emily lives in a bright, airy Altbau apartment in Prenzlauer Berg, shared with a cat named Pixel. Her mornings start with a strong coffee and a quick scan of design news before a brisk cycle to the agency. Weekends are for exploring Berlin's diverse neighborhoods on her bike, often with her vintage camera in tow, or meeting friends for brunch and discussing new projects. She's mindful of her budget, preferring to invest in quality tools and experiences over fleeting trends, and enjoys cooking simple, healthy meals. Independence is key; she values her autonomy both at work and in her personal life.

Work life

Emily thrives on the fast-paced, project-driven environment of her small agency. Her days are a blend of deep-focus design work and client-facing problem-solving. She's the go-to for bridging the gap between design and development, often building interactive prototypes that clients can immediately test. This involves a lot of terminal work, spinning up temporary servers via SSH, and meticulously documenting access details in Notion. She collaborates closely with account managers and developers, ensuring everyone is aligned. The pressure comes from tight deadlines and managing client expectations, but she finds satisfaction in delivering functional, user-friendly solutions efficiently.

Relationships

Emily maintains a close-knit circle of friends, mostly fellow creatives and tech professionals she met through university or work. Her parents, a retired teacher and an engineer, live in a smaller town in Bavaria and are supportive but don't fully grasp the nuances of her digital work. She has a few trusted colleagues at the agency she can rely on for technical advice or a quick sanity check.

How they decide

Emily is a pragmatic decision-maker. She researches thoroughly, weighing the pros and cons of different approaches, and often seeks input from a few trusted peers. She values efficiency and elegance in solutions, preferring tools and methods that streamline her workflow. While not overly impulsive, she's open to trying new things if they promise a significant improvement in her process or the quality of her output. Budget is a consideration, but she's willing to invest if the value proposition is clear and long-term benefits are evident.

How they sound

Speaks with a clear, measured cadence, often using precise technical terms when discussing her work. Her English is fluent but retains a slight German accent. She avoids overly casual slang or jargon when speaking with clients, opting for professional clarity. When talking with peers, she's more relaxed, occasionally using industry-specific shorthand. She tends to be direct and avoids hyperbole, preferring factual descriptions.

Personality traits

  • Detail-oriented
  • Pragmatic
  • Curious
  • Methodical
  • Resourceful
  • Calm under pressure
  • Independent thinker
  • Appreciates elegant solutions

Goals

  • Develop a personal design system for freelance projects
  • Master advanced CSS techniques for interactive elements
  • Travel to Japan to photograph its unique urban landscapes
  • Contribute to an open-source design tool
  • Achieve a better work-life balance by streamlining workflows

Problems & frictions

  • Constantly juggling multiple client projects with competing priorities
  • The overhead of setting up and tearing down temporary demo environments for clients
  • Ensuring consistent feedback loops with account managers and clients on prototypes
  • Finding time for personal creative projects amidst client work
  • Keeping up with the rapid pace of front-end development tools and frameworks

Values

  • usability
  • collaboration
  • independence
  • efficiency
  • craftsmanship

Interests

  • design systems
  • photography
  • urban cycling
  • experimental typography
  • local craft breweries

Media habits

  • Reads Smashing Magazine and CSS-Tricks daily
  • Listens to design podcasts during commutes
  • Follows design leaders on Twitter/X
  • Watches YouTube tutorials for new tools
  • Subscribes to newsletters on web development trends

Questions & answers

Emily Sutschet’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Expose local servers to the internet (https://airic.serveo.net/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    I already have a workflow for exposing local prototypes using SSH and documenting the temporary addresses in Notion. I've refined this over the years with a saved terminal alias, making it quite efficient. While the idea of using a dedicated service is interesting, I'd need to see a significant advantage over my current setup. The free plan with three tunnels seems too limited for the multiple projects I juggle. For the Pro plan, $6 per month is acceptable if it truly streamlines my process and reduces the overhead I currently manage, but I'm hesitant to pay for something that might not offer a substantial improvement.
    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.