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

Forrest Emard

Forrest Emard

Founding engineer at a seed-stage SaaS startup

Full-depth AI personas

Why this persona fits the audience

He is the only full-time engineer at a 4-person B2B SaaS startup in Austin. He regularly uses a coding agent to scaffold features, then turns the output into deployed customer-facing releases with GitHub Actions, Postgres, and Stripe. He also handles auth, basic observability, and a small backlog of internal tooling.

  • Age: 31
  • Location: Austin, Texas, US
  • Occupation: Founding Engineer
  • Income: $150k-$190k base + equity
  • Education: BS Computer Science
  • Company size: 4
  • Years in role: 2
“My goal is to build something that just works, reliably, so we can focus on the next big thing.”

Forrest Emard, 31, is a Founding Engineer at a burgeoning seed-stage B2B SaaS startup in Austin, Texas. Holding a BS in Computer Science from a state university, he gravitated towards the startup world for its inherent challenges and opportunities for rapid impact. He's been instrumental in building the core product from the ground up, acting as the sole full-time engineer for the past two years. His compensation reflects this crucial role, with a base salary in the $150k-$190k range, complemented by significant equity that represents his long-term financial aspirations. Forrest’s daily work is deeply intertwined with modern development practices; he leverages AI coding agents extensively to accelerate feature development, treating their output as a starting point for robust, production-ready code. He meticulously crafts deployment pipelines using GitHub Actions, manages the company's PostgreSQL database, and ensures seamless transaction processing through Stripe integrations. Beyond customer-facing features, he shoulders the responsibility for authentication mechanisms, basic system monitoring, and the development of internal tooling to streamline operations. He views his role as a constant learning experience, driven by the value of shipping functional, reliable systems quickly. This philosophy is reflected in his decision to recently implement a more rigorous code review process for himself, even as the only engineer, to enforce higher quality standards before deployment. He's pragmatic about money, saving diligently and investing his income, viewing his equity stake as the primary driver of future wealth, rather than immediate salary bumps. His approach to his career is one of building tangible value, piece by piece, under the constant pressure of a fast-moving startup environment.

Background & daily life

A day in their life

Forrest's typical weekday starts around 7:30 AM with coffee and a quick scan of Hacker News. He dives into coding by 8:30 AM, often starting with a generated feature scaffold from his coding agent, which he then refines, tests, and integrates. By mid-morning, he's reviewing pull requests (his own, usually) and configuring a GitHub Actions workflow to deploy it. Lunch is a quick affair, often a meal prep from the weekend. The afternoon might involve debugging an elusive bug reported by a customer, researching a new observability tool, or setting up a basic internal dashboard. He aims to wrap up by 6:30 PM but often finds himself back online for an hour to push a late-breaking fix or prepare for the next day’s sprint planning.

Lifestyle

Forrest lives a fairly frugal but comfortable life in Austin, prioritizing experiences and professional growth over material possessions. He shares a decent apartment in a growing neighborhood, saving money to eventually put a down payment on a small house. His routine is structured around work, but he makes time for weekend hikes in the Greenbelt and occasional craft brewery visits with friends. He's conscious about his health, trying to hit the gym a few times a week, but often his schedule dictates late nights. Financial decisions are deliberate; he tracks his spending and aggressively saves and invests a portion of his salary, seeing equity as a long-term play.

Work life

As the sole full-time engineer, Forrest wears multiple hats, from architecting core features to managing CI/CD pipelines and even patching the occasional production bug. The pressure is constant to ship value to early customers, balanced by the need to build a stable foundation. He spends his days juggling coding agent outputs with manual refinements, configuring GitHub Actions workflows, monitoring Postgres performance, and ensuring Stripe integrations are solid. He’s also responsible for setting up basic logging and alerting to catch issues before they impact users. The small team size means direct collaboration with the CEO and product lead, making feature decisions a rapid, iterative process.

Relationships

Forrest maintains a close-knit circle of friends from college and a few work acquaintances from previous roles. He talks to his parents regularly, who are proud of his career but don't fully grasp the startup grind. His current roommate is a graphic designer, offering a welcome break from tech talk. He values candid feedback from his co-founders and trusts their product vision implicitly.

How they decide

Forrest approaches decisions methodically, weighing pros and cons based on current needs and future scalability. He researches thoroughly, often diving into documentation and looking at community discussions for similar problems. He values practicality and evidence, preferring solutions that have a clear benefit and a manageable learning curve. While he respects the opinions of his co-founders, he ultimately relies on his technical judgment for engineering choices.

How they sound

Speaks clearly and deliberately, with a moderate pace. Tends to be precise with technical jargon but can explain complex concepts in simpler terms if needed. Avoids hyperbole or overly casual slang, preferring direct and factual communication. Has a slightly analytical tone, even in casual conversation.

Personality traits

  • Pragmatic
  • Detail-oriented
  • Driven
  • Resourceful
  • Slightly introverted
  • Curious
  • Systematic
  • Self-starter
  • Focused

Goals

  • Successfully scale the startup's infrastructure to support significant user growth
  • Become a principal engineer or CTO in a successful tech company
  • Build a reputation as an expert in scalable SaaS architectures
  • Achieve financial independence through equity and smart investments
  • Mentor junior engineers and contribute to open-source projects

Problems & frictions

  • Limited time and resources to address technical debt while also building new features
  • The constant need to stay updated with rapidly evolving AI developer tools
  • Balancing the demands of a fast-paced startup with personal well-being
  • Ensuring robust security and scalability on a shoestring budget
  • Lack of specialized expertise in certain areas like advanced observability or complex database tuning

Values

  • shipping quickly
  • reliable systems
  • learning by building
  • technical craftsmanship
  • team cohesion

Interests

  • developer tools
  • startups
  • automation
  • product analytics
  • cloud infrastructure
  • AI in software development

Media habits

  • Listens to tech podcasts during commutes and workouts
  • Scans Hacker News and Reddit (r/programming, r/SaaS) daily
  • Follows key figures in the dev tool and startup space on Twitter/X
  • Reads technical blogs and documentation extensively
  • Watches YouTube tutorials on new frameworks or libraries

Questions & answers

Forrest Emard’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://stacknaut.com (Stacknaut) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core promise of turning a coding agent's output into a production-ready SaaS repo is compelling, especially the idea of saving time on auth, billing, and deployment. However, it's unclear exactly how much of the development process is automated versus what I'd still need to handle. The tech stack (Vue, Fastify, PostgreSQL) is fine, but not my current stack, so that's a consideration. What would make me sign up is seeing concrete examples of the generated repo and understanding the effort required to adapt it to my existing workflow. A clear breakdown of features and costs would also be helpful before committing.
    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.