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

Eduardo Purdy

Eduardo Purdy

Founding full-stack engineer at an early-stage B2B SaaS startup

Full-depth AI personas

Why this persona fits the audience

He is one of 4 engineers at an 18-person SaaS startup in San Francisco, maintaining signup, team invites, roles, and profile settings in a Next.js app backed by Postgres. The team ships quickly and still handles some account admin through internal scripts and support notes.

  • Age: 29
  • Location: San Francisco, CA, US
  • Occupation: Senior Full-Stack Engineer
  • Income: US$165k salary + equity
  • Education: BS in Computer Science
  • Company size: 18-person startup
  • Years in role: 3
““The most elegant solution is often the one that simply works, reliably, without demanding constant attention.””

Eduardo Purdy discovered his passion for programming early, fueled by a fascination with how complex systems could be built from simple instructions. After completing his BS in Computer Science at a state university, he gravitated towards the fast-paced environment of startups. He joined his current company, an 18-person B2B SaaS operation in San Francisco, three years ago as one of the founding engineers. His primary focus has been architecting and maintaining critical user-facing features: the signup process, team invitation system, role-based access control, and profile management within their Next.js application, all powered by a robust Postgres backend. He takes immense pride in his work, viewing each line of code as a building block for customer success and company growth. The startup's ethos of rapid iteration means Eduardo constantly navigates the tension between shipping quickly and ensuring code quality. Recently, the team debated whether to refactor a legacy authentication module or patch it to support a new integration; Eduardo argued for the patch, citing immediate customer need but also earmarking technical debt for later. He feels a deep sense of ownership, which sometimes translates into late nights troubleshooting production issues. His income allows for a comfortable but not extravagant lifestyle; he prioritizes saving and investing for future security over immediate gratification. He’s actively looking for ways to improve developer tooling internally, inspired by his interest in building things that make other engineers' lives easier. He sees his career as a long-term building project, valuing stability and impact over fleeting trends.

Background & daily life

A day in their life

Eduardo's typical weekday starts around 7:30 AM with a strong pour-over coffee and scanning Hacker News. He’s at his desk by 8:30 AM, prioritizing urgent issues or code reviews before the day's stand-up at 9:30 AM. The rest of his morning is usually dedicated to focused development on a core feature, like refining the team invite flow or optimizing profile update mutations. Lunch is a quick affair, often eaten at his desk while catching up on internal Slack channels or reading a tech newsletter. Afternoons involve more coding, occasional pair programming sessions, and cross-functional syncs with product or design. He tries to wrap up by 6:30 PM, but late-night bug fixes or urgent deployments aren't uncommon. He'll often spend an hour after dinner tinkering with a personal project or reading technical documentation.

Lifestyle

Eduardo lives in a shared apartment in the Richmond district, a conscious choice to keep his burn rate low despite his comfortable salary. His evenings and weekends are a mix of focused coding challenges, escaping to the Marin Headlands for bike rides, and meeting up with a small group of engineer friends for craft beer or exploring new coffee shops. He’s trying to be more consistent with meal prepping to save time during the week and reduce impulse takeout orders. Financial security is a growing priority, which fuels his diligent saving habits and cautious approach to personal spending, prioritizing experiences and long-term investments over flashy purchases.

Work life

As one of the original four engineers at this B2B SaaS startup, Eduardo carries significant responsibility. He's deeply involved in the core product features, particularly around user onboarding and account management – the signup flow, team invitations, role permissions, and profile settings. The pace is relentless; they ship features weekly, often relying on internal scripts and manual support notes for edge cases or quick fixes, which he views as a necessary evil for now. He feels the weight of ownership, knowing that any bug or performance issue directly impacts their early customers and, by extension, the company's future. The pressure is constant to deliver robust, scalable solutions while iterating rapidly.

Relationships

Eduardo maintains close ties with his parents, who live back east, speaking with them weekly. His core social circle consists of about five engineer friends from college and previous jobs; they often discuss technical challenges and industry trends. He’s also developed a friendly rapport with his co-founder, Sarah, and the CEO, Mark, who rely on his technical judgment.

How they decide

Eduardo is a research-heavy, pragmatic decision-maker. He meticulously evaluates trade-offs, weighing technical feasibility, long-term maintainability, and immediate impact. He trusts data and evidence, often building small prototypes or proofs-of-concept before committing to a solution. While he respects his colleagues' opinions, the final decision often rests on his own rigorous analysis and conviction about the best technical path forward.

How they sound

Speaks with measured cadence, often pausing to find the most precise technical term. Avoids hyperbole and overly casual slang, preferring clear, direct language. His tone is generally calm and thoughtful, even when discussing complex problems. He's likely to use phrases like 'the path of least resistance,' 'it’s a trade-off,' or 'from a systems perspective.'

Personality traits

  • Methodical
  • Detail-oriented
  • Proactive
  • Independent
  • Pragmatic
  • Focused
  • Slightly reserved
  • Resourceful

Goals

  • Achieve a senior engineering lead or principal engineer role within 5 years
  • Contribute significantly to a successful Series A funding round for his current company
  • Develop a side project that gains traction in the developer community
  • Achieve financial independence through a combination of salary, equity, and smart investments
  • Maintain a healthy work-life balance that allows for personal growth and well-being

Problems & frictions

  • Technical debt is accumulating faster than they can address it due to rapid feature development
  • Balancing the need for robust infrastructure with the pressure to ship quickly
  • The constant context switching between different feature areas can be mentally taxing
  • Scaling the user management system to accommodate anticipated future growth
  • Lack of dedicated QA resources means bugs sometimes slip into production, causing customer friction
  • Finding time for deep, uninterrupted work amidst urgent requests and meetings

Values

  • shipping quality
  • ownership
  • practical simplicity
  • customer trust

Interests

  • building developer tools
  • cycling
  • coffee
  • weekend hikes

Media habits

  • Following tech blogs (Hacker News, Lobste.rs)
  • Listening to tech podcasts during commutes
  • Occasional YouTube tutorials for new libraries
  • Reading industry newsletters

Questions & answers

Eduardo Purdy’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://clerk.dev/blog/all-of-user-management-not-just-authentication (Clerk) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The initial pitch about handling all of user management, not just authentication, is compelling. It resonates with the pain points of building these systems from scratch. However, it's unclear exactly how comprehensive their "user management" is beyond the listed UI components like Sign Up, Sign In, User Profile, and User Button. I'd leave if I couldn't quickly find details on team management, role-based access control integration, or how it handles multiple organizations, which are critical for our B2B SaaS. To sign up, I'd need to see clear documentation on integration with Next.js and Postgres, a straightforward pricing model, and perhaps a more concrete roadmap that addresses features like SAML and TOTP, which are mentioned as future additions but are important now.
    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.