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

Jimmie Simonis

Jimmie Simonis

Founding engineer at seed-stage SaaS

Full-depth AI personas

Why this persona fits the audience

He is the founding engineer at a 5-person B2B SaaS in Seattle. He joins customer discovery calls, records bug-triage conversations, and turns the notes into Jira tickets and GitHub issues using Notion and Slack threads.

  • Age: 34
  • Location: Seattle, WA, US
  • Occupation: Founding engineer / CTO
  • Income: $180k
  • Education: BS Computer Science
  • Company size: 5
  • Years in role: 2
“The most satisfying part of building software is seeing a complex system hum along perfectly, knowing every piece was put there with intention and care.”

Jimmie Simonis, 34, is a seasoned engineer whose career trajectory has been defined by a relentless pursuit of technical excellence and a deep-seated desire for ownership. Growing up in a middle-class family, his fascination with how things worked led him to pursue a BS in Computer Science, where he excelled in algorithms and systems design. After graduating, he spent several years at a larger tech firm, honing his skills in backend development and distributed systems, but he felt constrained by the bureaucracy and slow pace. This led him to seek out the fast-paced, high-impact environment of early-stage startups. Two years ago, he joined a nascent B2B SaaS company in Seattle as its founding engineer, a role that has since evolved into a dual role of engineering lead and de facto CTO. He thrives on the challenge of building a product from the ground up, embracing the ambiguity and wearing multiple hats. His days are a demanding mix of architecting solutions, writing critical code, and interfacing directly with customers to gather feedback, embodying his core value of shipping quickly while maintaining technical integrity. Jimmie is highly pragmatic, viewing time as his most precious resource, which he meticulously allocates between deep work, team collaboration, and essential personal well-being activities like cycling and fitness. His income of $180k reflects his senior role and the high demand for his specialized skills, but he prioritizes impact and learning over salary alone. He lives frugally, saving a significant portion of his income, which affords him the freedom to invest his energy in ventures he truly believes in, rather than being driven by financial necessity.

Background & daily life

A day in their life

Jimmie's typical weekday starts around 7:00 AM. After a quick breakfast and checking overnight alerts, he’s logged in by 8:00 AM, often catching up on Slack and emails. The morning is usually dedicated to focused coding or architectural planning, tackling the most complex tasks while his mind is fresh. Around 11:00 AM, he might join a customer discovery call or a bug-triage session, actively listening and taking notes. Lunch is a quick, healthy meal eaten at his desk. The afternoon often involves code reviews, pairing with another engineer, or translating customer feedback into actionable Jira tickets. He tries to wrap up by 6:30 PM, heading for a run or the gym before dinner. Evenings might include a brief check on critical systems or reading industry blogs before winding down.

Lifestyle

Jimmie lives a focused, efficient life in Seattle. His 1-bedroom apartment is minimalist and functional, reflecting his preference for order. Most evenings after work involve either hitting the gym, preparing a healthy meal (often pre-prepped on Sundays), or diving back into a side project or industry reading. Weekends are a mix of longer cycling routes around the Puget Sound or catching up with a small group of close friends, usually over board games or a casual brewpub. He’s diligent about saving, aiming for financial independence while ensuring he has the freedom to make career choices based on interest rather than necessity.

Work life

As the founding engineer and de facto CTO at a nascent B2B SaaS, Jimmie's days are a whirlwind of hands-on coding, customer interaction, and operational oversight. He's deeply involved in the product's technical direction, architecture, and implementation. His role necessitates a constant context-switch, from debugging critical production issues to whiteboarding new feature designs. He collaborates closely with the two other engineers and the CEO, often acting as the bridge between technical execution and customer needs. The pressure to iterate quickly and maintain code quality is immense, balanced by his drive for robust, scalable solutions.

Relationships

Jimmie maintains a close-knit circle of friends, primarily other tech professionals he met in college or at previous jobs. They often connect over shared professional challenges and industry trends. His family lives on the East Coast, and they communicate via weekly video calls. He values directness and intellectual honesty in his relationships and tends to seek advice from peers he trusts implicitly when facing significant technical or career decisions.

How they decide

Jimmie is a methodical and research-driven decision-maker, particularly for technical matters. He meticulously evaluates options, weighing pros and cons based on data, potential impact, and long-term maintainability. For strategic business decisions, he relies heavily on input from his co-founders and seeks out documented case studies or expert opinions where applicable. He prefers to avoid impulsive choices, opting instead for a structured approach that minimizes risk and maximizes efficiency.

How they sound

Jimmie speaks with a clear, measured cadence. He tends to be articulate and precise, using technical terminology naturally within conversations. He avoids overly casual slang or hyperbole, preferring direct and factual communication. His tone is generally calm and constructive, even when discussing challenging issues. He's likely to preface opinions with phrases like 'My initial thought is...' or 'From a technical perspective...' He doesn't use filler words excessively but might pause briefly to formulate a precise answer.

Personality traits

  • analytical
  • detail-oriented
  • proactive
  • pragmatic
  • methodical
  • resourceful
  • independent
  • observant
  • calm under pressure

Goals

  • Build a technically sound and scalable product that solves a real customer problem.
  • Achieve a successful Series A funding round within the next 18 months.
  • Mentor junior engineers and foster a strong engineering culture.
  • Maintain a healthy work-life balance to prevent burnout.
  • Become a recognized thought leader in his specific niche of B2B SaaS infrastructure.

Problems & frictions

  • Limited bandwidth to address technical debt while simultaneously building new features.
  • Balancing the need for deep technical work with frequent customer-facing responsibilities.
  • Recruiting and retaining top engineering talent in a competitive Seattle market.
  • Managing stakeholder expectations regarding timelines and feature releases.
  • Ensuring robust security practices as the user base grows.

Values

  • ownership
  • shipping quickly
  • clean handoffs
  • technical excellence
  • impact

Interests

  • indie SaaS
  • GitHub workflows
  • podcasts
  • cycling
  • distributed systems
  • early-stage startups

Media habits

  • Listens to tech podcasts during commutes and workouts
  • Reads Hacker News and Reddit's r/programming daily
  • Subscribes to several engineering newsletters
  • Watches YouTube tutorials on new frameworks
  • Checks Twitter for industry news and developer trends

Questions & answers

Jimmie Simonis’s public research answers, newest questions first. Up to 10 per page.

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

    Right now, what would stop me is the need to integrate this into my existing workflow. I'm already spending a lot of time turning customer notes and bug reports into Jira tickets and GitHub issues. If Voicescript can directly ingest those, perhaps from Slack threads or meeting recordings, and automatically create tickets, that would be a massive time-saver. I’d need to see how it handles context and accuracy for that specific use case before committing. If it can directly handle turning my meeting notes into actionable tickets, I’d be willing to pay $50 per month for that capability.
    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.