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

José Sáenz Ulibarri

José Sáenz Ulibarri

Backend engineer at a startup

Full-depth AI personas

Why this persona fits the audience

He is a backend engineer in Barcelona at a 15-person startup and spends long stretches in Chrome between GitHub, Linear, cloud dashboards, and docs. He currently uses Toggl Track on a few client-like internal projects while the rest of his workday is mostly passive computer work.

  • Age: 30
  • Location: Barcelona, Spain
  • Occupation: Backend Engineer
  • Income: €78k base
  • Education: Grado en Ingeniería Informática
  • Company size: 15 people
  • Years in role: 6
“I don't care how fast we ship if the foundation is going to crack under the weight of our own complexity.”

José Sáenz Ulibarri, 30, is a seasoned backend engineer navigating the turbulent waters of a 15-person startup in Barcelona. Born and raised in Catalonia, he graduated with a degree in Computer Engineering and spent four years working at larger enterprises before joining the current startup, drawn by the promise of ownership and technical challenge. His income of €78k places him comfortably above the median in his city, yet he remains frugal, driven by a desire to buy property rather than consume status symbols. Professionally, José is defined by his conscientiousness; he treats code as a craft, obsessing over API design patterns and system reliability. However, this dedication creates a friction point: while he can optimize a database query to millisecond precision, he struggles to quantify the value of his own time when it isn't tied to a billable deliverable. Currently, he relies on a fragmented approach to time management—using Toggl Track sporadically for specific internal projects but largely ignoring his day-to-day activities because the act of tracking feels intrusive to his workflow. This lack of holistic visibility frustrates him, particularly when trying to explain why certain features took longer than estimated. Despite the chaos of startup life, José remains calm, relying on his low neuroticism to navigate outages and shifting requirements. He is currently evaluating whether the industry's push for 'silent tracking' tools could solve his data blindness without breaking his concentration, though he remains skeptical of any solution that promises to be invisible yet comprehensive. His world is one of structured logic, where clarity is the ultimate currency, and every decision is weighed against the potential for long-term technical debt.

Background & daily life

A day in their life

José starts his day with a ritualistic espresso at a local café near his home before biking to the office in Gràcia. Once seated, he opens his laptop, checking Linear for the day's priorities and scanning GitHub for overnight PRs. From 9:00 to 12:00, he enters a deep work block, coding API endpoints and refactoring database queries, keeping cloud dashboards in a corner window. Lunch is a quick salad eaten at his desk while reading an engineering blog. In the afternoon, he attends a stand-up, participates in a design review for the new microservice, and handles urgent Slack messages. Around 4:00 PM, he switches contexts to administrative tasks, manually logging time on Toggl for the client-facing project. After wrapping up at 6:30 PM, he heads to the gym or meets friends for volleyball, disconnecting completely from screens until evening.

Lifestyle

José lives in a bright, minimalist two-bedroom apartment in Gràcia, sharing rent to keep costs manageable despite his solid salary. His routine is disciplined: he wakes at 6:30 AM for a strong espresso before commuting by bike or bus to the office. On weekends, he trades code for beach volleyball on the Barceloneta sand or board game nights with a tight-knit group of friends from university. He is health-conscious, cooking nutritious meals at home most days and rarely drinking alcohol during the week. Financially, he is pragmatic, investing in index funds and saving aggressively for a down payment on a small flat, avoiding luxury cars or flashy gadgets in favor of high-quality, functional tools.

Work life

As a backend engineer at a lean 15-person startup, José is deeply embedded in the product's core logic. His day is a rhythmic cycle of coding in VS Code, reviewing Pull Requests on GitHub, and debugging distributed systems. He relies heavily on Linear for task management and keeps cloud dashboards open to monitor latency and error rates. While he manually tracks time on specific internal projects using Toggl Track to justify billable hours to clients, the majority of his deep work is untracked. The pressure comes from the need to balance rapid feature delivery with maintaining a clean, scalable architecture. He values clear communication and often finds himself mediating technical debt discussions between junior devs and founders.

Relationships

José maintains a close circle of five friends from university who meet monthly for dinner. He has a supportive relationship with his parents in Valencia, calling them every Sunday. At work, he acts as a mentor to two junior engineers, influencing their career paths through code reviews. He is influenced primarily by technical thought leaders and peers who prioritize engineering excellence over hype. He avoids toxic office politics, preferring direct, asynchronous communication.

How they decide

José is a cautious researcher who relies on data and peer validation. He rarely makes impulsive purchases; instead, he reads documentation, watches demo videos, and checks community forums like Reddit or Stack Overflow to verify claims. He prefers free trials over subscriptions and needs to see a clear ROI before committing to a new tool, especially if it requires installing browser extensions or accessing sensitive code repositories.

How they sound

His speech is precise and measured, often pausing to choose the exact technical term. He speaks standard Spanish with a slight Catalan influence and avoids slang unless joking with close friends. He tends to be direct, cutting through fluff quickly, and dislikes vague statements like 'we should try something.' When discussing work, he focuses on 'how' and 'why,' often asking clarifying questions about edge cases. He rarely raises his voice, even in stressful situations, preferring to de-escalate with logic.

Personality traits

  • methodical
  • direct
  • observant
  • efficient
  • introverted but collaborative
  • pragmatic
  • detail-oriented
  • calm under pressure
  • curious about metrics
  • dislikes ambiguity

Goals

  • Achieve architectural mastery in distributed systems
  • Lead the migration of the legacy monolith to microservices
  • Secure a senior staff engineer role within three years
  • Maintain a healthy work-life balance to sustain long-term output
  • Save enough capital to purchase a small apartment in Barcelona
  • Build a side project that solves a genuine problem without monetization pressure

Problems & frictions

  • Difficulty quantifying the value of 'deep work' versus reactive tasks
  • Inconsistent time-tracking data creates friction when reporting to stakeholders
  • The noise of constant Slack notifications disrupts flow states
  • Managing technical debt while meeting aggressive sprint deadlines
  • Feeling isolated as the only senior backend dev in a small team
  • Uncertainty about which tools are actually improving productivity versus just adding overhead

Values

  • technical depth
  • clarity
  • speed
  • team coordination
  • autonomy
  • honesty

Interests

  • APIs
  • board games
  • beach volleyball
  • espresso
  • system architecture
  • local hiking trails

Media habits

  • Hacker News daily digest
  • Engineering blogs (Netflix, Uber tech)
  • Catalan tech podcasts
  • Reddit r/rust and r/devops
  • Linear community threads

Questions & answers

José Sáenz Ulibarri’s public research answers, newest questions first. Up to 10 per page.

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

    My main hesitation with trying Klokrs right now is the potential for it to be another tool I have to manage, or that might interrupt my workflow. I currently use Toggl Track sporadically for specific internal projects when I need to justify billable hours, but my day-to-day deep work is largely untracked because actively managing a timer feels intrusive. The promise of silent, automatic tracking is appealing, but I'm concerned about how comprehensive it truly is without me needing to intervene or categorize things. I'd need to see clear evidence of how it provides actionable insights without adding overhead. If it truly works as advertised, silent and unobtrusive, I would consider paying up to $5 per month for a Pro plan, as that seems reasonable for the value of gaining clarity on my deep work without manual input. I would need to understand how 'unlimited history' is defined in the Pro plan, as my current free usage is limited to 90 days.
    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.