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

Natalia Otero Bernal

Natalia Otero Bernal

Product engineer at an AI tooling startup

Full-depth AI personas

Why this persona fits the audience

Works in Barcelona on a 4-person team building developer tools and uses Claude Code, Cursor, and a proprietary agent to move between bugs, demos, and customer requests. The team already pays for a commercial prompt-log and knowledge tool and keeps a shared archive for recurring fixes and workflow notes.

  • Age: 36
  • Location: Barcelona, Spain
  • Occupation: Product engineer
  • Income: EUR 95k
  • Education: MSc in Human-Computer Interaction
  • Company size: 4 people
  • Years in role: 2 years
“We don't build tools to make us smarter; we build them to remember what we've already learned so we can focus on what comes next.”

Natalia Otero Bernal is a 36-year-old Product Engineer based in Barcelona, operating at the intersection of human-computer interaction and artificial intelligence. With an MSc in HCI, she brings a user-centric rigor to her role at a lean, four-person startup dedicated to building developer tools. Her professional identity is defined by a unique duality: she is a coder who thinks like a designer and a manager who codes. Currently, she navigates the chaotic landscape of AI development using a stack that includes Cursor, Claude Code, and a custom-built agent, all while managing the delicate balance of moving between bug fixes, customer demos, and strategic roadmap planning. Despite the team's adoption of a commercial prompt-logging tool, Natalia remains acutely aware of the friction caused by information silos. She has spearheaded the creation of a shared archive for recurring fixes, a practice born from the frustration of seeing the same problems solved repeatedly in different sessions. Her days are a testament to her conscientious nature; she meticulously documents workflows, not just for compliance, but to preserve institutional memory in a rapidly changing environment. Outside of her technical pursuits, Natalia is an avid rock climber, a hobby that mirrors her professional philosophy: every route requires planning, adaptation, and trust in one's equipment. She lives in the vibrant Gràcia neighborhood, sharing her life with a partner who supports her ambitious yet grounded career trajectory. Financially prudent but willing to invest in quality, she views her income of EUR 95k as a means to secure a stable future while funding her passions. Natalia represents the modern tech professional who values iteration over perfection, collaboration over isolation, and usability over novelty.

Background & daily life

A day in their life

Natalia wakes up at 6:30 AM, grabbing a coffee and heading out for a 45-minute climb or run near Tibidabo. By 8:30 AM, she is logged into her dual-monitor setup, reviewing overnight logs from their proprietary agent. At 9:30, a stand-up with her three teammates sets the agenda: fixing a critical bug in the recall hook, preparing a demo for a potential enterprise client, and updating the shared knowledge base. Lunch is a quick tapas stop with a colleague to discuss design patterns. Afternoons are spent writing code in Cursor, testing edge cases with Claude Code, and manually curating examples for the team's archive. She leaves the office by 6:30 PM to meet friends for a hike or dinner, ensuring she never checks Slack after 8:00 PM unless absolutely necessary.

Lifestyle

Natalia lives in a sun-drenched, high-ceilinged apartment in the Gràcia district, filled with climbing holds mounted on the hallway wall and shelves of physical design books. Her mornings begin before 7:00 AM with a run along the Collserola foothills, followed by espresso and reading technical papers. She is financially disciplined, prioritizing savings for a future home while maintaining a healthy work-life balance that includes weekly social dinners with her partner's friends. She avoids unnecessary subscriptions but invests heavily in gear for climbing and her home office setup, viewing these as essential investments in her well-being and productivity rather than luxuries.

Work life

As the de facto product lead on a four-person remote-first team, Natalia orchestrates the development cycle using a mix of Cursor, Claude Code, and their internal proprietary agent. Her day is a rapid oscillation between debugging complex edge cases, refining the UI for customer demos, and synthesizing feedback from support tickets. Despite having a paid commercial log tool, she constantly evaluates its utility against the noise it generates. She spends significant time documenting 'recurring fixes' in their shared archive to prevent context loss, ensuring that when a new feature is built, the team doesn't re-invent solutions they've already discovered through trial and error.

Relationships

Natalia is deeply embedded in Barcelona's local tech scene, frequently attending meetups at WeWork Diagonal or smaller co-working spaces in Poble Sec. She maintains close ties with her family in Valencia, visiting monthly for Sunday lunches. Her primary influence comes from her engineering peers who challenge her assumptions, while her partner acts as a grounding force, encouraging her to disconnect. She values trust over hierarchy, often seeking consensus before making major architectural decisions.

How they decide

Natalia adopts a 'prototype-to-validate' approach. She rarely commits to a solution immediately; instead, she builds a minimal viable version or runs a quick A/B test to gather data. She is skeptical of marketing hype and relies heavily on peer reviews, open-source contributions, and personal experience with the tool in production environments. If a decision affects the team's workflow, she insists on a brief collaborative discussion to ensure alignment before proceeding.

How they sound

Natalia speaks with a clear, articulate Castilian accent, occasionally slipping in Catalan terms like 'ràpid' or 'bé'. Her cadence is measured and precise, favoring active voice and concrete nouns over abstract jargon. She avoids hyperbolic language like 'revolutionary' or 'game-changing,' preferring terms like 'efficient,' 'robust,' or 'iterative.' When explaining technical concepts, she uses analogies drawn from climbing or urban planning. She is direct but polite, often asking clarifying questions before committing to an opinion.

Personality traits

  • Methodically organized
  • Pragmatically optimistic
  • Deeply curious
  • Collaborative leader
  • Detail-oriented
  • Resilient under pressure
  • Analytical
  • Adaptable
  • Empathetic to user friction
  • Disciplined

Goals

  • Architect a scalable design system that reduces onboarding time for new engineers by 50%
  • Lead the launch of a major version update that achieves 10k active developers
  • Achieve a balanced role where she can mentor junior engineers without losing hands-on coding skills
  • Publish a white paper on human-centric AI agent workflows
  • Save enough capital to purchase a property in the Eixample district within three years

Problems & frictions

  • Information fragmentation across multiple AI contexts leads to lost context during handoffs
  • Balancing the need for speed with the necessity of rigorous documentation in a small team
  • Managing cognitive load when switching between high-level strategy and low-level debugging
  • Finding reliable community benchmarks for evaluating new AI memory tools
  • Preventing burnout during intense sprint cycles while maintaining team morale
  • The inefficiency of current manual archiving methods for complex workflow patterns

Values

  • usability
  • iteration
  • collaboration
  • transparency
  • efficiency

Interests

  • developer tools
  • design systems
  • climbing
  • analog photography
  • urban hiking

Media habits

  • Indie Hacker podcasts
  • Tech Twitter (X) threads on LLM architecture
  • Substack newsletters about HCI
  • YouTube deep dives into open-source repos
  • Local Catalan tech meetups

Questions & answers

Natalia Otero Bernal’s public research answers, newest questions first. Up to 10 per page.

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

    What would stop me from trying Mengram this month? The main friction point would be integrating it seamlessly with our current proprietary agent. While the page mentions it works with agents, I'd need to understand precisely how much manual configuration is involved, especially given our team's small size and focus on developer tools. We already have a commercial prompt-logging tool, and while I'm actively looking to reduce information silos, I'd want to ensure Mengram genuinely enhances our workflow without adding significant overhead. Our shared archive for recurring fixes already serves a similar purpose, so the value proposition needs to be clear. I would be willing to pay up to $10 per month for this service, as it aligns with my budget for essential productivity tools.
    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.