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

Emilia Hendriks

Emilia Hendriks

frontend engineer in a small team, self-directed prep

Full-depth AI personas

Why this persona fits the audience

She is a frontend engineer at a five-person healthtech startup in Amsterdam and prepares for interviews alongside one coworker who is also exploring new roles. They share a spreadsheet of React and TypeScript prompts, swap mock questions after lunch, and rely on free community resources.

  • Age: 31
  • Location: Amsterdam, Netherlands
  • Occupation: Frontend Engineer at a healthtech startup
  • Income: €78,000
  • Education: HBO in Software Development
  • Company size: 5
  • Years in role: 4
“It's about building things that are not just functional, but also elegant and maintainable – that's where the real satisfaction lies.”

Emilia Hendriks, 31, is a dedicated Frontend Engineer at a burgeoning healthtech startup in Amsterdam, a role she's held for four years. Her journey into software development began with an HBO in Software Development, where she developed a strong foundation in programming principles. She thrives in collaborative environments, valuing the synergy of a small team where her contributions feel impactful. Her current role involves crafting user-centric interfaces using React and TypeScript, with a keen eye for clean code and performance optimization. Emilia is driven by a desire for stability and continuous learning, constantly seeking to deepen her understanding of frontend technologies. She lives a relatively frugal but comfortable life, prioritizing experiences and long-term security over ostentatious displays of wealth. Her income of €78,000 allows for a comfortable existence in Amsterdam, but she's diligent about saving and budgeting. Recently, she and a coworker, Mark, have begun a concerted effort to prepare for future career opportunities. This self-directed preparation involves meticulously sharing and dissecting React and TypeScript interview prompts via a shared spreadsheet, engaging in daily mock interview sessions during their lunch breaks, and leveraging a wealth of free online community resources. This proactive approach stems from a desire to explore new challenges and ensure she's well-equipped for the next step in her career, reflecting her conscientious nature and forward-thinking mindset. She’s deeply invested in the quality of her work, believing that well-crafted code is a testament to professional integrity and a key factor in long-term project success.

Background & daily life

A day in their life

Emilia's typical weekday starts around 7:00 AM with a quick breakfast and a glance at tech news. She cycles to the office, arriving by 8:30 AM. The morning is dedicated to focused coding, tackling tickets from their agile board, and attending the daily stand-up. Lunch is usually a packed meal, often shared with Mark, where they'll discuss a React hook or a tricky TypeScript problem, sometimes running through mock interview questions. The afternoon involves more development, code reviews, and perhaps a brief sync with the product owner. She leaves the office around 5:30 PM, cycles home, and might spend an hour in the evening on interview practice or learning a new concept before dinner and winding down. She aims to disconnect by 9:30 PM.

Lifestyle

Emilia lives in a compact but well-organized apartment in Amsterdam Noord, sharing it with a cat named Pixel. Her income allows for comfortable living, though she's mindful of saving for future travel and potential homeownership. Weekday evenings often involve cooking a healthy meal, followed by coding practice or reading tech blogs. Weekends are a mix of exploring the city's canals, visiting local markets, and occasional meetups with friends. She prioritizes a balanced routine, incorporating cycling to work and yoga for stress relief. Money is managed carefully, with a budget for discretionary spending and a growing emergency fund.

Work life

As a frontend engineer at a small healthtech startup, Emilia's role is multifaceted. She's responsible for building user interfaces, collaborating closely with the backend team and the product owner, and ensuring code quality. The team's small size means everyone wears multiple hats, and decisions are made collaboratively. Lately, the pressure to deliver new features while also preparing for potential job changes has increased. She spends her days writing React components, debugging, participating in code reviews, and attending daily stand-ups. The startup environment is dynamic, with a focus on rapid iteration and problem-solving.

Relationships

Emilia maintains close ties with her family back in Friesland, speaking to her parents weekly. Her core social circle consists of a few long-term friends from university, with whom she shares life updates and occasional outings. Her closest work relationship is with her coworker, Mark, who is also job hunting, making their interview prep sessions a shared, supportive endeavor. She values genuine connection and mutual respect in her relationships.

How they decide

Emilia approaches decisions methodically. She gathers information from multiple sources, weighs pros and cons carefully, and often seeks input from trusted peers or online communities before committing. For significant decisions, she prefers to have a clear understanding of the long-term implications and potential risks. She is not impulsive and values thorough research.

How they sound

Emilia speaks with a clear, measured cadence, her Dutch accent subtly present. She uses precise language, avoiding excessive slang or jargon unless discussing technical specifics. Her tone is generally calm and thoughtful, but can become more animated when discussing a challenging problem or a new technology she's excited about. She tends to be direct but polite, and often qualifies her statements with phrases like 'I think' or 'It seems to me'.

Personality traits

  • methodical
  • detail-oriented
  • proactive
  • analytical
  • supportive
  • reserved
  • diligent
  • curious

Goals

  • Secure a senior frontend engineering role with more complex challenges
  • Contribute to open-source projects
  • Achieve financial independence
  • Travel to Japan and experience its culture
  • Maintain a healthy work-life balance

Problems & frictions

  • Feeling overwhelmed by the sheer volume of interview preparation material
  • Balancing current job responsibilities with interview practice
  • Navigating the uncertainty of the job market
  • Finding reliable, high-quality free resources for interview prep
  • The pressure to constantly upskill in a rapidly evolving tech landscape

Values

  • collaboration
  • stability
  • clean code
  • continuous learning
  • impactful work

Interests

  • React
  • TypeScript
  • community resources
  • web performance optimization
  • accessibility in frontend

Media habits

  • Following key figures on Twitter/X for tech news
  • Reading articles on dev.to and Medium
  • Listening to tech podcasts during commutes
  • Participating in Discord tech communities
  • Watching YouTube tutorials for specific libraries

Questions & answers

Emilia Hendriks’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maximize your chances of success in frontend interviews with our expert-driven preparation platform. 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.

    Honestly, the single biggest problem is the sheer volume of material to cover. Mark and I have this shared spreadsheet, but it's growing so fast, it feels like drinking from a firehose. It's costing us hours of our personal time each week, time that could be spent on actual rest or other learning. We've tried focusing on specific areas, like React hooks, but there's always more to consider – algorithms, system design... I'm not even sure what the 'expert-driven' part of your platform would cost, or if it's even relevant to my current situation.
    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.