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

Marcos Howe

Marcos Howe

ML engineer on a media monitoring product

Full-depth AI personas

Why this persona fits the audience

Builds retrieval and ranking features for an 11-person monitoring product in San Francisco that summarizes breaking news and public web mentions. He already pays for a competing search API on a usage-based plan and benchmarks it against hand-curated searches and scraped result sets in notebooks. His day-to-day work includes evaluating freshness, coverage, and snippet quality.

  • Age: 34
  • Location: San Francisco, CA, US
  • Occupation: Machine Learning Engineer
  • Income: $205k base + equity
  • Education: MS Computer Science
  • Company size: 11
  • Years in role: 4
““If you can’t measure it, you’re just guessing, and guessing is how you build products nobody needs.””

Marcos Howe grew up in a suburban environment, developing an early aptitude for problem-solving and a fascination with how complex systems worked. His academic journey led him to pursue a Master's degree in Computer Science, where he specialized in machine learning and algorithms, solidifying his passion for quantitative analysis and data-driven approaches. After graduating, he spent a few years at a larger tech company, gaining experience in building scalable backend systems, but found the environment too bureaucratic and detached from tangible product impact. Seeking a more agile and hands-on role, he joined his current startup, attracted by the challenge of building a media monitoring product from the ground up. He chose San Francisco for its concentration of tech talent and opportunities, accepting the high cost of living as a trade-off for career advancement. His income allows for comfortable living and investment, but he remains frugal, prioritizing long-term financial security and experiences over conspicuous consumption. Marcos is driven by a deep-seated need to understand and optimize complex processes, viewing his work not just as a job, but as a continuous intellectual pursuit. He recently made a significant decision to refactor a critical data ingestion pipeline to improve its resilience, a project that consumed weeks of his focused effort and involved extensive benchmarking against older versions and potential alternatives. He sees time as a valuable, non-renewable resource, which he allocates carefully between work, personal growth, and maintaining his physical health through rigorous outdoor activities.

Background & daily life

A day in their life

Marcos’s typical weekday begins around 7:00 AM with a quick scan of overnight news and tech headlines while he makes coffee. He’s usually at his desk by 8:00 AM, diving into code for the retrieval pipeline, analyzing recent benchmark results, or refining parameters for an LLM experiment. He has a stand-up meeting at 10:00 AM to discuss progress and blockers with his team. Lunch is usually a quick affair, often eaten at his desk while reading a research paper or a technical blog. The afternoon might involve debugging a tricky ranking issue, collaborating on a design document, or exploring new data sources. He aims to wrap up by 6:00 PM, often heading out for a short mountain bike ride if the weather permits, followed by a quiet evening at home.

Lifestyle

Marcos lives a focused life centered around his work and personal development. He rents a modest one-bedroom apartment in San Francisco, prioritizing his commute time and proximity to tech hubs over square footage. His evenings and weekends are often a blend of deep work on personal coding projects, hitting the trails for mountain biking to decompress, and staying updated on the latest AI research. He’s not a big spender on material goods, preferring to invest in experiences and high-quality tools that enhance his productivity or hobbies. His social life is smaller but close-knit, consisting of a few long-time friends from university and work.

Work life

As an ML Engineer at a small, fast-paced media monitoring startup, Marcos is deeply involved in building core retrieval and ranking features. The pressure is on to deliver robust, scalable solutions that can process vast amounts of real-time web data. He works closely with the two other engineers and the product manager, often engaging in rigorous technical debates. His days are filled with coding, experimenting with different LLM architectures, meticulously setting up benchmarks in Jupyter notebooks, and troubleshooting performance bottlenecks. He constantly evaluates the trade-offs between cost, latency, and accuracy, especially concerning their current reliance on a third-party search API.

Relationships

Marcos's closest professional relationships are with his two engineering colleagues, with whom he shares a collaborative, sometimes intensely analytical, dynamic. He values their technical input. Outside of work, he maintains friendships with a few individuals from his graduate program, often bonding over shared technical interests or outdoor activities. His family lives out of state, and their interactions are primarily through calls and occasional visits, generally supportive but not deeply involved in his day-to-day professional life.

How they decide

Marcos is a research-heavy and data-driven decision-maker. He prioritizes empirical evidence, thorough benchmarking, and a deep understanding of technical underpinnings. He is cautious, preferring to explore multiple options and test hypotheses extensively before committing. He is less swayed by trends or peer pressure and more by demonstrable performance metrics and the elegance of a solution.

How they sound

Speaks with a clear, measured cadence, often pausing to formulate precise technical terms. Avoids hyperbole and overly casual slang. His tone is generally neutral but can become animated when discussing complex technical challenges or breakthroughs. He uses phrases like 'empirically speaking,' 'the signal-to-noise ratio,' and 'from a systems perspective.'

Personality traits

  • Analytical
  • Detail-oriented
  • Methodical
  • Independent
  • Pragmatic
  • Resourceful
  • Skeptical of hype
  • Future-oriented

Goals

  • Achieve a deeper understanding of emergent properties in large language models.
  • Contribute a novel algorithm to the open-source ML community.
  • Maintain a healthy work-life balance to prevent burnout.
  • Become a recognized subject matter expert in scalable information retrieval.
  • Save enough to eventually purchase a small cabin in the mountains.

Problems & frictions

  • The inherent difficulty in objectively measuring the 'quality' of summarized news snippets.
  • Managing the escalating costs of the external search API as data volume grows.
  • Balancing the need for cutting-edge LLM research with the practical constraints of a small product team.
  • The constant churn of new research papers and tools, making it hard to stay current without feeling overwhelmed.
  • Integrating experimental features into a production environment with limited QA resources.

Values

  • measurement
  • technical depth
  • speed of iteration
  • data integrity
  • scalability

Interests

  • LLMs
  • benchmarking
  • mountain biking
  • distributed systems
  • performance optimization
  • signal processing

Media habits

  • Reads technical blogs (e.g., Hacker News, Towards Data Science)
  • Listens to podcasts on AI and tech news during commutes
  • Follows key researchers on Twitter/X
  • Scans industry newsletters for relevant research papers
  • Watches tech conference talks online

Questions & answers

Marcos Howe’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: The Web Search API for AI. Used by McKinsey, SNCF, Cohere, Legora, Polymarket, and Artisan AI. #1 on OpenAI's SimpleQA. 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 biggest problem for us is managing the escalating costs of the external search API we currently use. As our data volume grows, so does our bill, and it's becoming a significant line item we can't easily absorb. We've tried optimizing our queries and implementing caching layers, but the core issue remains. The sheer volume of data we need to index and retrieve for our news monitoring product makes this a constant concern. It's hard to predict and control.
    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.