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

Emilio Beatty

Emilio Beatty

Frontend engineer at a digital agency

Full-depth AI personas

Why this persona fits the audience

Builds user-flow and component interaction diagrams for client work across several accounts; uses Figma, issue trackers, and Markdown notes, then converts rough sketches into Mermaid when handing work to backend and QA teammates.

  • Age: 27
  • Location: New York, NY, USA
  • Occupation: Frontend engineer
  • Income: $132,000
  • Education: Bachelor's degree in interaction design
  • Company size: 50-100 employees
  • Years in role: 4
“Every line of code, every pixel, and every interaction should serve a purpose. If it's not clear, it's not done.”

Emilio Beatty, 27, is a frontend engineer at a New York City-based digital agency, specializing in crafting user experiences for a diverse clientele. Graduating with a Bachelor's in Interaction Design from a respected university, he quickly found his niche in translating complex client requirements into elegant, functional web interfaces. His current role demands a high degree of organization and precision, as he’s responsible for building user-flow and component interaction diagrams for multiple accounts. Emilio meticulously uses Figma for visual design and prototyping, leverages issue trackers like Jira for task management, and relies on Markdown for internal notes. A key part of his workflow involves converting these intricate sketches and wireframes into Mermaid diagrams, a crucial step for efficient handoffs to his backend and QA colleagues. This process ensures that the visual logic and interactive components are clearly understood before implementation. He's developed a strong sense of craftsmanship, believing that even the documentation and handoff artifacts should reflect a high standard of quality. He recently pushed back on a client request to simplify a complex onboarding flow too drastically, advocating for a more nuanced approach that preserved user guidance, demonstrating his commitment to good UX over expediency. His income of $132,000 allows for comfortable city living and moderate saving, but he's conscious of the financial demands of New York and is diligently building his savings for a future property investment. He sees his career as a continuous learning process, striving to stay ahead of evolving frontend technologies and design paradigms, while also valuing the tangible output of his work and the collaborative spirit of his team.

Background & daily life

A day in their life

Emilio's weekday typically begins around 7:00 AM with a quick bike ride through Prospect Park or a home workout. After a carefully prepared breakfast, he’s at his desk by 8:30 AM, catching up on Slack messages and emails. Most of his morning is dedicated to coding a new feature for a fintech client, followed by a design review session in Figma. Lunch is usually a quick affair, often a sandwich eaten at his desk while reviewing issue tracker tickets. The afternoon involves collaborating with a backend developer to clarify API requirements, meticulously updating user flow diagrams in Mermaid, and then diving into another coding sprint for a different client account. He aims to log off by 6:30 PM, often followed by a quick spin on his bike to clear his head before dinner.

Lifestyle

Emilio lives in a modest but well-organized one-bedroom apartment in Brooklyn, a deliberate choice to be close to his agency and favorite cycling routes. He's disciplined about his fitness, typically starting his day with a quick workout or a meticulously brewed pour-over coffee before heading to the office. His weekends often involve exploring new neighborhoods on his bike, catching an off-Broadway show, or meeting friends for dinner. He's mindful of his spending, prioritizing experiences and quality over fleeting trends, and is saving for a down payment on a condo. He enjoys the energy of the city but values quiet evenings for focused work or unwinding.

Work life

As a frontend engineer at a fast-paced digital agency, Emilio juggles multiple client projects simultaneously. His days are a blur of coding responsive interfaces, refining component libraries, and, crucially, translating complex user interactions into clear diagrams. He spends significant time in Figma, meticulously crafting user flows and state diagrams for new features, often translating these into Mermaid syntax for the backend and QA teams. The pressure to deliver polished, functional UIs on tight deadlines is constant, but Emilio thrives on the challenge of bringing abstract concepts to tangible, user-friendly realities. He values clear communication and efficient handoffs, seeing well-documented diagrams as key to team success.

Relationships

Emilio is close with his parents, who live upstate, and maintains a core group of about five close friends from college, mostly in tech or creative fields. His agency team is a significant part of his social circle, often grabbing drinks after work. He's influenced by his lead designer at the agency, who champions user-centered design principles, and he occasionally seeks advice from senior engineers on complex technical challenges.

How they decide

Emilio tends to be analytical and research-oriented when making significant decisions. He gathers information from multiple sources, compares options systematically, and often seeks input from trusted colleagues or peers before committing. For more routine decisions, he prioritizes efficiency and clarity, opting for the path that seems most straightforward and effective based on past experience.

How they sound

Emilio speaks clearly and deliberately, with a moderate pace. He uses precise language, especially when discussing technical concepts, and avoids excessive slang. He sounds informed and thoughtful, often pausing briefly to formulate his thoughts. When excited about a project or design detail, his cadence might quicken slightly, but he generally maintains a composed and professional tone.

Personality traits

  • Meticulous
  • Organized
  • Articulate
  • Proactive
  • Detail-oriented
  • Adaptable
  • Slightly perfectionistic
  • Curious

Goals

  • Become a senior frontend architect with more design influence
  • Contribute to an open-source UI component library
  • Purchase a small condo in a vibrant NYC neighborhood
  • Achieve a better work-life balance without sacrificing project quality
  • Master advanced animation techniques for web interfaces

Problems & frictions

  • Client scope creep that disrupts planned workflows
  • Inconsistent documentation standards across different project teams
  • The overhead of manually updating diagrams when designs change rapidly
  • Balancing the desire for perfect pixel implementation with project timelines
  • Finding time for deep learning and skill development amidst demanding client work

Values

  • craftsmanship
  • responsiveness
  • collaboration
  • clarity
  • efficiency

Interests

  • interface design
  • urban cycling
  • live theatre
  • independent film
  • craft coffee

Media habits

  • Follows design and tech blogs (Smashing Magazine, UX Collective)
  • Listens to podcasts during commutes (This American Life, Syntax)
  • Active on LinkedIn for industry news, occasionally Twitter for niche design discussions
  • Reads online tech journals and architecture reviews

Questions & answers

Emilio Beatty’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Mermaidonline (https://www.mermaidonline.live/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The main thing that would stop me from trying Mermaidonline this month is the sheer volume of client work I have. I'm currently converting a lot of rough sketches into Mermaid diagrams for backend and QA, which takes a significant chunk of time. My current process involves using Figma for the initial design, then Markdown notes, and finally manually translating that into Mermaid syntax. It can get tedious, especially when designs change rapidly. I'd be willing to pay up to $9.9 per month, assuming the AI features for generating diagrams from text or screenshots are efficient and save me considerable time. I'd need to see how quickly and accurately it handles complex flows before committing long-term.
    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.