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

Jay Rosenbaum

Jay Rosenbaum

Technical co-founder at a seed-stage SaaS

Full-depth AI personas

Why this persona fits the audience

He co-runs a 3-person SaaS in Austin and is the main person touching the PlanetScale database. He drafts and tests queries with ChatGPT, then copies them into the PlanetScale console while tracking schema changes and rollback notes in Notion for the other two teammates.

  • Age: 31
  • Location: Austin, TX, USA
  • Occupation: Co-founder / full-stack engineer
  • Income: USD 130k salary equivalent plus equity
  • Education: Bachelor's degree in computer science
  • Company size: 3
  • Years in role: 2
“The real magic happens when you can build fast without breaking everything.”

Jay Rosenbaum, 31, is a driven technical co-founder in Austin, Texas, co-leading a nascent SaaS company with two partners. Holding a Bachelor's degree in Computer Science, he has gravitated towards roles where he can build and optimize from the ground up. His current venture, a lean operation of three people, places him squarely in the trenches of early-stage startup development. He is the primary architect and steward of their PlanetScale database, a critical component of their product. This responsibility means he spends a significant portion of his workday drafting, testing, and refining SQL queries, increasingly leveraging tools like ChatGPT to accelerate the process and ensure accuracy. He meticulously documents schema changes and rollback strategies in Notion, a practice born from a desire for clarity and control amidst the chaos of rapid iteration. Jay's income of USD 130k, supplemented by equity, reflects his demanding role and the high-stakes environment of seed-stage startups. He lives alone in a rented apartment, his lifestyle characterized by discipline and a singular focus on the company's success. His decision to co-found this SaaS stems from a deep-seated belief in ownership and the power of small, autonomous teams to innovate rapidly. He's constantly weighing the need for speed against the imperative of maintaining robust systems, embodying his core value of 'speed with guardrails.' His recent technical decisions have centered on optimizing database performance and ensuring data integrity, even as feature pressure mounts, reflecting a pragmatic approach to innovation that doesn't sacrifice foundational stability. He views time as a precious commodity, meticulously allocating it between coding, strategic planning, and essential personal upkeep, always with an eye toward maximizing output for the company.

Background & daily life

A day in their life

Jay's typical weekday begins around 7:00 AM with coffee and a quick scan of Hacker News and his company's monitoring dashboards. He dedicates the morning to deep work, often tackling complex database tasks or core feature development. After a quick, healthy lunch, he might have a brief sync with his co-founders to align on priorities. The afternoon is a mix of coding, responding to urgent issues, and perhaps testing new query optimizations using ChatGPT. He usually wraps up around 7:00 PM, followed by a run or some light reading on AI in development, before a simple dinner. Evenings might involve a brief check of the production environment before winding down.

Lifestyle

Jay lives a focused, somewhat solitary life in Austin, prioritizing his startup. He rents a modest 1-bedroom apartment, keeping it clean and functional rather than decorative. His daily routine is structured around work, with evenings often spent catching up on industry news or tinkering with personal projects. He's health-conscious, opting for home-cooked meals and regular runs at Zilker Park. Social life revolves around occasional meetups with fellow founders or casual drinks with his co-founders. Finances are managed tightly, with most discretionary income reinvested into the business or saved.

Work life

As the technical co-founder, Jay shoulders significant responsibility for the company's core infrastructure. His days are a blend of coding, database management, and strategic technical decision-making. He's deeply involved with PlanetScale, meticulously crafting and testing SQL queries, often leveraging AI tools to accelerate this process. The pressure is constant, stemming from the need for rapid development and stability in a lean, three-person operation. He values clear documentation and processes, using Notion to maintain order for the team.

Relationships

Jay maintains close, professional relationships with his two co-founders, Sarah (CEO) and Mark (Product). Their dynamic is built on mutual respect and shared ambition. Outside of work, his social circle is smaller, consisting of a few college friends and a handful of contacts from the Austin tech scene. He has a good but somewhat distant relationship with his parents, who live in Ohio.

How they decide

Jay is a methodical decision-maker, heavily reliant on data and prior research. He’ll explore multiple options, weigh pros and cons, and often prototype solutions before committing. Peer recommendations and established best practices from reputable sources also influence his choices, but the final call is based on a thorough, analytical assessment of technical feasibility and long-term impact.

How they sound

Jay speaks clearly and deliberately, with a precise vocabulary. He tends to avoid overly casual slang or hyperbole, preferring factual descriptions. His cadence is steady, reflecting his analytical nature, and he often pauses to gather his thoughts before answering complex questions. He's not afraid to admit when he doesn't know something but will usually follow up with how he'd find out.

Personality traits

  • meticulous
  • driven
  • analytical
  • resourceful
  • detail-oriented
  • self-disciplined
  • curious
  • calm under pressure

Goals

  • Achieve product-market fit and secure Series A funding.
  • Build a robust, scalable, and performant SaaS product.
  • Establish a strong engineering culture within the company.
  • Become a recognized expert in scalable database architectures.
  • Maintain a healthy work-life balance, even as the company grows.

Problems & frictions

  • Balancing speed of development with robust database integrity.
  • Limited bandwidth for proactive infrastructure improvements due to urgent feature requests.
  • Onboarding new engineers to the existing database architecture and best practices.
  • Managing cloud infrastructure costs effectively as usage scales.
  • Finding time for deep technical research amidst daily operational demands.

Values

  • speed with guardrails
  • ownership
  • small-team autonomy
  • pragmatic innovation
  • data integrity

Interests

  • SaaS building
  • SQL
  • developer tools
  • startup operations
  • performance optimization
  • AI in development

Media habits

  • Reads Hacker News daily
  • Subscribes to several tech newsletters (e.g., TLDR, Cooper Press)
  • Listens to tech podcasts during commutes (e.g., Syntax, Acquired)
  • Follows key developers and VCs on Twitter/X
  • Watches technical deep dives on YouTube

Questions & answers

Jay Rosenbaum’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Show HN launch (11 pts, 2023-04-20): We built a PlanetScale plugin for ChatGPT. Site shows pricing/signup. 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.

    We're laser-focused on getting our core product stable and hitting product-market fit, which means every engineering hour is precious. Right now, the biggest problem is the sheer bandwidth required to maintain our PlanetScale database alongside feature development. We're constantly juggling schema changes, query optimization, and ensuring data integrity under pressure. Anything that slows down our iteration loop or introduces complexity without a clear ROI is a significant concern. I'm curious how this plugin handles schema migrations and rollback scenarios – that's a critical piece for us to avoid costly downtime.
    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.