Why this persona fits the audience
Works in Dublin as the product designer for a 7-person SaaS team, helping define the app shell, forms, and onboarding flow in Figma while engineers translate those layouts into React and Chakra components. She is close enough to the codebase to review component states and variant coverage.
- Age: 28
- Location: Dublin, Ireland
- Occupation: Product Designer
- Income: €63k
- Education: B.A. in Product Design
- Company size: 7 employees (Series A startup)
- Years in role: 4 years total experience, 1 year in current role
“Design isn't just about making things look pretty; it's about removing the friction so people can actually do their work without thinking twice.”
Born in Cork and raised in a household that valued education and practical skills, Melba Hegmann moved to Dublin to pursue her B.A. in Product Design, drawn by the city's burgeoning tech scene. Now 28, she works as the sole product designer for a nimble seven-person SaaS startup, a role that forces her to wear many hats beyond the traditional scope of the profession. Her background in a rigorous academic program gave her a strong theoretical foundation, but her true expertise lies in the pragmatic application of design principles within a fast-moving engineering environment. She has become intimately familiar with the codebase, often reviewing pull requests to ensure that the visual intent of her Figma files translates accurately into React and Chakra components. This unique proximity to the code allows her to catch edge cases early, preventing the common disconnect between design and development. Melba is currently navigating the complexities of scaling a design system from scratch, a task that requires not only aesthetic judgment but also a deep understanding of component architecture. She is driven by a desire for clarity and usability, believing that good design should be invisible. Her income of €63k provides a comfortable life in Dublin, allowing her to save steadily for a future property purchase, though she remains acutely aware of the cost-of-living crisis. Professionally, she seeks to build a reputation as a bridge-builder who can harmonize the creative and technical sides of product development. Recently, she made the difficult decision to push back on a feature request from stakeholders because it compromised the onboarding flow, demonstrating her commitment to user experience over short-term gains. Despite the pressures of a lean team, she maintains a balanced lifestyle, finding solace in her cycling routine and the vibrant, albeit competitive, community of Dublin's design sector.
Background & daily life
A day in their life
Melba wakes at 6:30 AM, brewing strong tea and cycling to work through the morning drizzle. By 9:00 AM, she is already in a stand-up meeting, quickly shifting context to discuss a blocking issue with the login flow. The bulk of her morning is spent in Figma, meticulously refining the spacing and typography of the settings page, ensuring every pixel aligns with the design system rules. Lunch is usually a quick sandwich eaten at her desk while skimming a thread on Twitter about accessibility standards. Afternoon hours are reserved for engineering syncs, where she walks through the codebase, pointing out missing hover states and color contrast issues in the Chakra components. She spends the last hour documenting her changes and preparing for tomorrow's sprint planning. On her way home, she stops at a local market for fresh produce, using the walk to decompress from the intense mental focus of the day before cooking dinner and winding down.
Lifestyle
Melba lives in a renovated Victorian terrace in Rathmines, sharing rent with a fellow software engineer to keep costs manageable on her €63k salary. Her evenings are a mix of winding down with a glass of wine and scrolling through niche design communities or reading technical blogs. She is an avid cyclist, commuting 15 minutes to work regardless of the Irish rain, which keeps her fitness high but adds a layer of weather-dependent stress. Financially, she is budget-conscious, prioritizing savings for a potential first deposit on a flat over luxury travel. Socially, her circle is small but tight-knit, mostly consisting of other creatives and developers from the local Dublin scene who understand the specific pressures of the tech industry.
Work life
At her startup, Melba operates at the intersection of design and engineering, a rare position that demands fluency in both languages. Her day is dominated by building the foundational 'app shell' in Figma, ensuring every form field and onboarding step aligns with user needs before a single line of code is written. Unlike designers who hand off static mockups, she actively participates in code reviews, checking if the React implementation matches her intended states and variants within the Chakra UI system. The pressure comes from the lean team size; there are no dedicated QA or research roles, so she must advocate for usability while simultaneously managing the friction of translating complex designs into functional components. Alignment meetings are frequent, as the entire seven-person team relies on her vision to maintain consistency.
Relationships
Melba's professional network is heavily skewed toward Dublin's tech ecosystem, where she attends weekly coffee chats with fellow founders and engineers. She has a supportive relationship with her engineering lead, whom she trusts implicitly, allowing for blunt feedback sessions. Her family lives in Cork, visited monthly, though they often struggle to grasp the nuances of her job. She values her roommate, not just for rent splitting, but as a sounding board for the emotional weight of shipping products. Her primary influence comes from senior designers she follows online, whose case studies shape her approach to problem-solving.
How they decide
Melba is a methodical synthesizer who avoids impulsive choices. She gathers data from multiple sources—user feedback, engineering constraints, and competitor analysis—before committing to a direction. She values consensus and rarely makes unilateral decisions that could alienate the engineering team. While she is open to new tools, she requires a clear demonstration of how a solution improves workflow efficiency rather than adding novelty. Peer validation is crucial; she is more likely to adopt a practice if she sees it working effectively in a similar startup environment.
How they sound
Melba speaks with a calm, measured cadence, favoring precise vocabulary over slang. She tends to use collaborative phrasing like 'we might want to consider' or 'does this align with our goals?' rather than commanding statements. She avoids hyperbolic language or absolute guarantees, preferring to qualify her opinions with evidence. In casual conversation, she remains polite and engaging, often asking follow-up questions to ensure understanding. She rarely uses jargon without explaining it, even to peers, and generally avoids discussing salary or personal finances in mixed company.
Personality traits
- diplomatically direct
- visually obsessive
- collaborative skeptic
- process-oriented
- quietly confident
- detail-obsessed
- pragmatic idealist
- emotionally steady
- curious about code
- time-conscious
Goals
- Lead the creation of a fully documented, version-controlled design system from scratch
- Transition into a Senior Product Designer role within three years
- Reduce cognitive load for new users during the B2B onboarding process by 20%
- Build stronger collaborative bridges between design and engineering teams
- Save enough for a 20% down payment on a property in Dublin by age 32
- Mentor junior designers from non-design backgrounds
Problems & frictions
- Maintaining design consistency when engineers prioritize speed over perfect component parity
- Balancing deep focus time with constant context switching in a seven-person environment
- Lack of dedicated user research resources leading to assumptions about user behavior
- Managing stakeholder expectations regarding the timeline for complex interaction states
- Keeping up with rapidly evolving React patterns while maintaining legacy code stability
- Feeling isolated as the sole designer without a peer group for immediate critique
Values
- usability
- clarity
- team alignment
- technical integrity
- sustainable pace
- evidence-based design
Interests
- Figma advanced prototyping
- B2B onboarding flows
- design systems architecture
- React component state management
- Scandinavian minimalism
- urban cycling
Media habits
- Figma Community daily deep dives
- Indie Hackers podcast during commute
- Twitter/X threads on frontend engineering
- Awwwards for visual inspiration
- Local Dublin tech meetups (offline)
- Medium articles on UX psychology