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

Ivan Stark

Ivan Stark

CTO of a seed-stage startup

Full-depth AI personas

Why this persona fits the audience

Runs engineering for a six-person startup shipping weekly releases: two backend devs, one frontend dev, one designer, one QA contractor, and himself. Keeps roadmap items in Linear, operational notes in Notion, and deployment steps in GitHub Actions plus a set of homegrown scripts.

  • Age: 42
  • Location: Chicago, IL, US
  • Occupation: CTO
  • Income: US$260k total compensation
  • Education: BS in Computer Science
  • Company size: 6
  • Years in role: 2
“The most satisfying part of building software isn't just shipping features, it's building a system that reliably works and a team that can sustain it.”

Ivan Stark has been immersed in the world of software development since his undergraduate days at the University of Illinois Urbana-Champaign, where he earned his BS in Computer Science. His early career was spent in larger tech firms, honing his skills in backend systems and distributed computing. However, the allure of building something from the ground up led him to co-found Aether Dynamics two years ago. Now serving as CTO, he's the technical architect and engineering lead for their six-person team. His philosophy is deeply rooted in pragmatism and robust execution. He meticulously manages their roadmap in Linear, documenting everything from high-level objectives to intricate operational details in Notion. Deployment workflows are automated via GitHub Actions, augmented by a set of custom scripts he developed to streamline their specific CI/CD needs. He recently made the decision to standardize their core backend services on Go, believing its concurrency model and performance characteristics are best suited for their evolving data synchronization product, despite a slight learning curve for some team members. Ivan views time as a finite resource, constantly optimizing processes to maximize output without sacrificing quality. His income reflects his senior role and the high-stakes environment of early-stage startups. While he values financial security, his primary drive is building a sustainable, impactful technology company. His personal time is a carefully curated balance between family, his passion for home lab projects—currently focused on building a fault-tolerant storage cluster—and his extensive collection of strategy board games.

Background & daily life

A day in their life

Ivan's day begins around 6:30 AM with coffee and a quick scan of Hacker News while his kids eat breakfast. He heads to the office by 8:00 AM, often using the commute to listen to a podcast. The morning is usually dedicated to focused coding or architectural design, followed by stand-ups with his team. Afternoons are packed with code reviews, pair programming sessions, and troubleshooting production issues. He tries to wrap up by 6:30 PM to make it home for dinner with his family, but often logs back on for another hour or two of work after the kids are in bed, reviewing logs or planning the next day's sprints.

Lifestyle

Ivan balances his demanding startup role with family life in a modest but comfortable suburban home. Weekends often involve family outings or tackling projects in his meticulously organized home lab, which is filled with old servers, networking gear, and 3D printers. He enjoys hosting board game nights with friends, a ritual that helps him decompress. While not extravagant, he’s comfortable financially, prioritizing experiences and durable goods over fleeting trends. Health-wise, he tries to hit the gym a couple of times a week, though late nights at the office often interfere.

Work life

As CTO of 'Aether Dynamics', Ivan is neck-deep in building their core product, a novel distributed data synchronization tool. His days are a whirlwind of code reviews, architectural discussions with his small team, and strategic planning sessions. He juggles direct coding contributions on the backend with guiding the frontend and design efforts, always mindful of their tight release cadence. The pressure is immense to prove product-market fit and secure the next round of funding, which translates to long hours and constant problem-solving, often fueled by lukewarm coffee.

Relationships

Ivan is married to Sarah, a graphic designer, with whom he shares two children. His immediate family is his primary support system. He maintains a close-knit group of college friends, most of whom are also in tech, providing a sounding board for both professional and personal challenges. His direct reports at Aether Dynamics are his closest work confidantes.

How they decide

Ivan is a researcher and deliberator. He meticulously gathers information, consults technical documentation, and often prototypes solutions himself before committing to a technical direction. He values data and evidence, preferring to weigh pros and cons systematically. While he listens to his team's input, the final technical decisions rest heavily on his own analysis and experience.

How they sound

Speaks clearly and precisely, with a moderate pace. Tends to be articulate and avoids jargon unless necessary for technical discussion. His tone is generally calm and measured, even when discussing challenging issues. He's not prone to hyperbole or excessive slang, preferring straightforward communication.

Personality traits

  • deliberate
  • detail-oriented
  • resourceful
  • analytical
  • steady
  • patient
  • mentoring
  • hands-on
  • systematic

Goals

  • Successfully launch Aether Dynamics' MVP and achieve initial market traction.
  • Build a robust, scalable engineering culture within the startup.
  • Achieve financial independence for his family through successful venture exits.
  • Mentor junior engineers and contribute positively to the tech community.
  • Complete his ambitious home lab build-out, including a custom NAS cluster.

Problems & frictions

  • Balancing the urgent need for feature development with the long-term necessity of technical debt reduction.
  • The constant challenge of hiring top engineering talent in a competitive market with limited startup resources.
  • Managing team morale and preventing burnout under intense pressure and tight deadlines.
  • The overhead of managing infrastructure and tooling with a very lean team.
  • Finding sufficient focused time for strategic architectural thinking amidst daily firefighting.

Values

  • execution
  • ownership
  • team leverage
  • pragmatism
  • long-term sustainability

Interests

  • startup ops
  • board games
  • home lab
  • vintage computing
  • craft beer brewing

Media habits

  • TechCrunch and Hacker News daily
  • Ars Technica for deeper dives
  • Substack newsletters on software architecture
  • YouTube channels on electronics and server builds
  • Podcasts during commutes (e.g., Acquired, Software Engineering Daily)

Questions & answers

Ivan Stark’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Klyve (https://klyve.online): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    Klyve's promise of an "Automated Software Factory" that handles the entire SDLC, not just code generation, is compelling, especially for a small team like mine where we're constantly battling context switching. The idea of it managing testing and documentation updates is particularly attractive. For it to be a no-brainer, I'd expect it to significantly reduce our QA and documentation overhead. I'd stop considering it if it felt like just another layer of complexity or if the output quality was subpar. A price point around $100-$150 per month would be attractive, but I'd need to see demonstrable time savings to justify anything higher. Given the "beta" status, I'd be hesitant to commit financially beyond that. So, my maximum would be $150 per month.
    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.