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

Tomas Windler

Tomas Windler

Technical cofounder building internal tools

Full-depth AI personas

Why this persona fits the audience

Runs engineering for a 2-person startup that builds internal workflow software, so he still codes most features himself in TypeScript and Go. He uses the editor’s free suggestions and hand-written scaffolding, then compares package choices and rollout steps in a spreadsheet before merging.

  • Age: 38
  • Location: San Francisco, CA, USA
  • Occupation: Technical cofounder
  • Income: $210k/year plus equity
  • Education: BS Computer Engineering
  • Company size: 2
  • Years in role: 4
“The best solution is the one that works reliably, scales predictably, and doesn't create more problems than it solves.”

Tomas Windler, 38, is a technical co-founder based in San Francisco, CA, where he runs the engineering side of a two-person startup focused on building internal workflow software. Holding a BS in Computer Engineering, his career has been a steady progression through software development roles, culminating in the entrepreneurial leap four years ago. His current income of $210k, supplemented by equity, reflects his expertise and the high-stakes environment of early-stage tech. Tomas is deeply pragmatic, driven by a core value of efficiency and a strong belief in self-reliance, underpinned by a commitment to evidence-based decision-making. He still codes extensively, primarily using TypeScript for frontend components and Go for backend services, reflecting his hands-on approach to building the company's product. His development process is meticulous; he leverages editor suggestions and writes custom scaffolding, but critically, he dedicates significant time to comparing package choices and planning rollout strategies, often documenting these comparisons in spreadsheets before merging code. This methodical approach stems from his high conscientiousness (0.88) and a desire to minimize technical debt and future friction. His openness score (0.49) suggests he's not a radical innovator but is receptive to well-reasoned improvements. He’s not overly extraverted (0.43) or neurotic (0.27), preferring focused work and controlled environments. His recent decisions have centered on optimizing the core architecture of their workflow tool, specifically refactoring a data ingestion module to improve performance and reduce memory usage, a process that involved evaluating three different queuing mechanisms and benchmarking their throughput under simulated load. He also recently decided against adopting a bleeding-edge framework for their next major feature, opting instead for a more stable, well-supported library after a detailed risk-benefit analysis documented in a shared company wiki. Tomas views time as a critical, finite resource, meticulously allocating it between product development, strategic planning, and essential personal upkeep like his trail running routine. Money is a tool for achieving stability and enabling the startup's growth, not an end in itself. Status is derived from technical competence and the successful delivery of reliable software, not from external validation or accolades.

Background & daily life

A day in their life

Tomas's weekday typically begins around 7:00 AM with a strong coffee and a quick scan of Hacker News and his company's monitoring dashboards. He'll then head out for a 45-minute trail run, using the time to mentally organize his priorities. Back home, he showers and is at his desk by 9:00 AM. The morning is dedicated to focused coding, tackling the most complex features or critical bug fixes. Lunch is usually a quick, healthy meal prepared at home. The afternoon might involve a sync with his co-founder, reviewing pull requests, or researching a specific technical challenge. He aims to wrap up by 6:30 PM, though late nights happen when a critical deadline looms. Evenings are for winding down, perhaps reading a technical article or a chapter of a sci-fi novel.

Lifestyle

Tomas lives a focused, somewhat solitary life in San Francisco, prioritizing his startup and personal well-being. His apartment is functional, minimalist, and serves as both living space and workspace. He's disciplined with his finances, saving aggressively for future company milestones and personal security, viewing his income as a means to an end rather than an end in itself. His primary escape is trail running in the Marin Headlands, a physical and mental reset that clears his head. Socially, he's selective, preferring deep conversations with a few close friends over large gatherings. He values his independence and autonomy above most things.

Work life

As a technical co-founder of a two-person startup building internal workflow software, Tomas is deeply hands-on. He writes the majority of the code himself, primarily in TypeScript for the frontend and Go for the backend services. His days are a blend of deep coding sessions, architectural discussions with his co-founder, and the constant evaluation of new libraries or tools. He meticulously documents decisions, often using spreadsheets to compare package choices, performance implications, and rollout strategies before committing code. The pressure is constant, driven by the need to deliver value to their early customers and the inherent risks of a startup. He feels the weight of responsibility for the technical direction and execution.

Relationships

Tomas's closest relationship is with his co-founder, with whom he shares a deep professional respect and a similar pragmatic outlook. He has a small circle of long-time friends from university, mostly engineers, with whom he discusses technical challenges and life in general. His family lives out of state, and while he maintains contact, his startup demands most of his attention. He's not particularly influenced by external opinions unless they are backed by solid data or demonstrable expertise.

How they decide

Tomas is highly analytical and evidence-based in his decision-making. He researches thoroughly, comparing options systematically, often using spreadsheets or detailed notes to weigh pros and cons. He trusts data and empirical results over hype or anecdotal evidence. He's cautious, preferring to understand the implications of a choice before committing, and values solutions that are robust and maintainable in the long run.

How they sound

Speaks with a measured, deliberate cadence. His vocabulary is precise, often technical, but he avoids overly casual slang or jargon unless discussing with peers. He tends to be direct and to the point, valuing clarity and accuracy. He's not prone to hyperbole or emotional outbursts, preferring a calm, rational tone. He might pause to formulate his thoughts carefully before answering complex questions.

Personality traits

  • meticulous
  • analytical
  • resourceful
  • independent
  • detail-oriented
  • driven
  • skeptical
  • methodical
  • reserved

Goals

  • Achieve product-market fit and sustainable revenue for his startup.
  • Build a robust, scalable, and maintainable codebase.
  • Become a recognized expert in developer productivity tools.
  • Maintain a healthy work-life balance, avoiding burnout.
  • Contribute meaningfully to the open-source community.

Problems & frictions

  • Limited time and resources for feature development and bug fixing.
  • The constant need to evaluate and integrate new technologies without derailing progress.
  • Balancing the desire for elegant technical solutions with the urgency of shipping product.
  • The inherent uncertainty and financial precarity of a startup environment.
  • Finding reliable, efficient tools that genuinely improve his workflow without adding complexity.

Values

  • efficiency
  • self-reliance
  • evidence
  • pragmatism
  • continuous improvement

Interests

  • TypeScript
  • internal tooling
  • trail running
  • distributed systems
  • developer productivity
  • open-source contributions

Media habits

  • Hacker News
  • Lobste.rs
  • Ars Technica
  • Technical blogs (e.g., Martin Fowler, InfoQ)
  • Podcasts (e.g., Syntax.fm, Software Engineering Daily)
  • YouTube (coding tutorials, tech talks)

Questions & answers

Tomas Windler’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 (163 pts, 2024-02-22): the product, the first code completion tool with 300k token context. 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.

    The core problem for us right now is always resource allocation. We're a two-person team, and every hour spent evaluating new tools or potential integrations is an hour not spent building our core workflow product. While 300k tokens is impressive, my immediate concern is understanding the integration effort and ongoing maintenance overhead. We've already invested heavily in our current TypeScript/Go stack, and introducing something entirely new, even if powerful, requires significant justification. I'd need to see clear benchmarks against our current capabilities and a very low barrier to entry to consider it.
    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.