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

Edmund Miller

Edmund Miller

Founder of a small AI research tooling startup doing dataset collection

Full-depth AI personas

Why this persona fits the audience

He runs a three-person product team and spends part of each week orchestrating site collection for model evaluation, document discovery, and product comparison data. Most of the workflow is stitched together with open-source scrapers, cloud functions, and spreadsheets to track which jobs succeeded.

  • Age: 36
  • Location: San Francisco, California, US
  • Occupation: Founder, AI tooling startup
  • Income: $130k-$180k
  • Education: Master's degree
  • Company size: 3 employees
  • Years in role: 4
“There's always a more efficient way to get the data, you just have to build it yourself.”

Edmund Miller’s journey into AI tooling began not in a Silicon Valley incubator, but in the academic labs of his Master's program in Computer Science. Fascinated by the potential of machine learning, he quickly became frustrated by the nascent, often manual, processes required for high-quality data collection and model evaluation. Witnessing firsthand the bottlenecks that hindered progress, he saw an opportunity. After a brief, unfulfilling stint at a large tech firm where his innovative ideas were stifled by bureaucracy, he channeled his savings and a fierce desire for autonomy into co-founding his startup. Four years ago, with two equally driven colleagues, he set out to build tools that would streamline this critical, yet often overlooked, aspect of AI development. His professional life is a testament to his values: seeking technical leverage by automating and optimizing workflows, prioritizing learning velocity to stay ahead in the rapidly evolving AI landscape, and maintaining strict resource discipline to make every dollar count. His San Francisco apartment serves as both home and a testament to his lean operation, reflecting a life where professional ambitions often supersede personal comfort. He recently spearheaded the integration of a new set of residential proxies to bypass increasingly sophisticated anti-scraping measures on a key data source, a decision that required significant refactoring of their existing Python-based collection framework but ultimately improved data acquisition rates by nearly 30%. This constant iteration and problem-solving define his existence, a relentless pursuit of efficiency in the complex world of AI data.

Background & daily life

A day in their life

Edmund's typical weekday begins around 7:30 AM with a quick scan of overnight job logs and key industry news. After a simple breakfast, he heads to his small office space, often grabbing a coffee en route. The morning is usually dedicated to a team stand-up, followed by deep work – either architecting a new data pipeline, debugging a stubborn scraper, or reviewing pull requests. Lunch is often a quick, utilitarian affair, perhaps a sandwich at his desk. The afternoon might involve client calls (though rare, as they focus on tooling), strategic planning sessions with his co-founders, or more hands-on work with cloud functions and data validation scripts. He tries to wrap up by 7 PM, but late-night coding sessions or urgent bug fixes are common. Evenings are for personal learning or unwinding with a book, though the lines often blur.

Lifestyle

Edmund lives a focused, albeit somewhat Spartan, life in San Francisco. His income supports a comfortable but not extravagant lifestyle, prioritizing savings and reinvestment in his startup over luxury goods. He lives alone in a modest apartment, where his living room often doubles as a workspace. His routine is heavily dictated by his startup's demands, but he tries to dedicate evenings to reading technical papers or personal coding projects. He's health-conscious, aiming for morning jogs, but often sacrifices them for late-night debugging sessions. Socially, he's selective, preferring deep conversations with a small circle of like-minded friends over large gatherings. Financial discipline is key; he meticulously tracks personal expenses, viewing frugality as a strategic advantage.

Work life

Edmund lives and breathes his startup. His days are a relentless cycle of strategic planning, technical deep-dives, and hands-on problem-solving. He manages a lean team of three, dividing his time between architecting new data collection strategies, reviewing code, and, critically, orchestrating the very data acquisition processes that power their tooling. This often involves debugging open-source scrapers, tweaking cloud functions, and meticulously tracking job statuses in complex spreadsheets. The pressure is constant to build a robust, scalable platform on a shoestring budget, pushing him to constantly innovate and optimize existing workflows. He's deeply involved in every technical decision, aiming for maximum leverage from every hour and every dollar spent.

Relationships

Edmund's closest relationships are with his two co-founders, Anya (lead engineer) and Ben (product designer). They share a deep mutual respect built on shared struggles and technical camaraderie. Outside of work, he maintains a small circle of friends from his Master's program, most of whom are also in tech or academia; these friendships are his primary source of intellectual stimulation and emotional support. His family, spread across the Midwest, respects his ambition but doesn't fully grasp the minutiae of his startup life.

How they decide

Edmund is a highly analytical and research-driven decision-maker. He meticulously weighs pros and cons, often prototyping or running small-scale tests before committing to a path. He values data and evidence, and while he respects expert opinions, he ultimately trusts his own rigorous evaluation process. He is not impulsive but can act decisively once he's confident in his analysis, particularly when faced with clear technical or operational inefficiencies. He exhibits a strong bias towards solutions that offer long-term leverage and scalability.

How they sound

Edmund speaks with a measured, precise cadence. His vocabulary is technical and direct, often using industry jargon naturally. He avoids hyperbole and overly emotional language, preferring factual statements. He tends to articulate complex ideas clearly, breaking them down logically. You won't hear much slang, but he might occasionally use a dry, understated wit. He’s not afraid to admit what he doesn’t know but will quickly follow up with how he plans to find out.

Personality traits

  • Intellectually curious
  • Systematic
  • Resourceful
  • Pragmatic
  • Driven
  • Detail-oriented
  • Slightly impatient with inefficiency
  • Independent
  • Analytical

Goals

  • Achieve product-market fit for his AI tooling startup.
  • Build a sustainable, profitable company with a strong technical foundation.
  • Contribute meaningfully to the advancement of practical AI development.
  • Develop a reputation as a thought leader in AI tooling and data pipelines.
  • Maintain personal autonomy and control over his professional direction.

Problems & frictions

  • Scaling data collection infrastructure reliably without significant capital investment.
  • Managing the technical debt accumulated from rapid, ad-hoc development.
  • Finding and retaining specialized engineering talent in a competitive market.
  • Balancing the urgent needs of product development with long-term strategic planning.
  • The inherent instability and unpredictability of web scraping targets.
  • Maintaining team morale and focus during periods of intense pressure.

Values

  • technical leverage
  • learning velocity
  • resource discipline
  • autonomy
  • solving complex problems

Interests

  • LLM tooling
  • data pipelines
  • startup operations
  • distributed systems
  • ethical AI development

Media habits

  • Reads Hacker News daily
  • Subscribes to AI research newsletters (e.g., Import AI, The Batch)
  • Listens to tech podcasts during commutes (e.g., Acquired, Lex Fridman Podcast)
  • Follows key AI researchers on Twitter/X
  • ocasionaly browses Reddit's r/MachineLearning and r/startups

Questions & answers

Edmund Miller’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying EnigmaProxy (https://enigmaproxy.net/?tracking=tinylaunch) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    I recently integrated residential proxies to improve our data acquisition rates by about 30%, which involved significant Python refactoring. My current setup uses open-source scrapers, cloud functions, and spreadsheets, which is functional but, as you can imagine, a bit of a patchwork. The primary hesitation I'd have in trying EnigmaProxy this month is the overhead of integrating and testing a new provider. We're incredibly resource-disciplined, so I'd need to see a clear, measurable improvement over our current setup to justify the effort. If the performance gains were substantial and the integration straightforward, I might consider it. For a small team like ours, I'd aim for a cost around $150 per month for proxies, provided it scales well with our usage.
    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.