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

Harry Dooley

Harry Dooley

AI platform engineer building LinkedIn-native agents

Full-depth AI personas

Why this persona fits the audience

Works at a US AI startup and is currently wiring a private LinkedIn workflow into an internal agent stack. He tests Playwright scripts, API calls, and prompt loops against real accounts as part of day-to-day product development, with one other engineer occasionally reviewing logs and edge cases.

  • Age: 33
  • Location: San Francisco, CA, US
  • Occupation: Platform Engineer
  • Income: $190k base + equity
  • Education: BS Computer Science
  • Company size: Early-stage startup (25 employees)
  • Years in role: 2
“The elegance isn't in the complexity, but in how seamlessly the automation handles it.”

Harry Dooley, 33, is a dedicated Platform Engineer at a San Francisco-based AI startup, where he's been for the past two years. His journey into AI platform engineering stemmed from a deep fascination with automating complex processes, a passion ignited during his BS in Computer Science. He thrives in environments that demand both technical acumen and rapid iteration, values that are core to his work at the fast-paced startup. Harry's current focus is on building sophisticated LinkedIn-native agents, a challenging endeavor that requires him to meticulously wire private workflows into their internal agent stack. This involves a significant amount of hands-on development, including writing and stress-testing Playwright scripts, architecting robust API calls, and optimizing prompt loops. He tests these components against real LinkedIn accounts, a critical step for ensuring practical functionality. His commitment to privacy-conscious engineering is paramount; he believes that automation should enhance productivity without compromising user data security. He often spends late afternoons discussing edge cases and reviewing logs with his sole engineering colleague, ensuring the systems are as resilient as possible. Outside of work, Harry is a private individual who enjoys exploring the intersection of open-source software and LLM infrastructure, often dedicating personal time to contributing to or experimenting with new tools. His financial life is managed pragmatically; he lives comfortably on his substantial income and equity, but remains focused on long-term investment and security rather than conspicuous consumption. He sees his career as a continuous learning process, driven by the desire to build tools that are both powerful and ethically sound, shaping the future of AI-driven automation.

Background & daily life

A day in their life

Harry's typical weekday starts around 7:30 AM with coffee and scanning Hacker News. He commutes to the office by 9:00 AM, often listening to a podcast. The morning is usually dedicated to heads-down coding, debugging Playwright scripts for LinkedIn automation, and refining API integrations. Lunch is a quick, healthy meal, often eaten at his desk while reviewing documentation or Slack messages. Afternoons involve more coding, collaborating with his colleague on test case reviews, and participating in brief stand-up meetings. He typically leaves the office around 6:30 PM, sometimes staying later if a critical bug arises. Evenings might include a quick workout, preparing dinner, or dedicating an hour to a personal coding project.

Lifestyle

Harry lives a focused, digitally-integrated life in San Francisco. His routine revolves around work, punctuated by occasional evenings out with a small circle of tech friends or quiet nights tinkering with personal coding projects. He prioritizes efficient living, opting for meal prep and using public transport or his bike to navigate the city. While he enjoys the energy of SF, he's not overly social, preferring deep dives into technology over large gatherings. His income allows for comfort and investment, but he's mindful of long-term financial security, often reviewing his investment portfolio.

Work life

As a platform engineer at a burgeoning AI startup, Harry's days are a blend of intense focus and rapid problem-solving. He's currently deep in the trenches, integrating a private LinkedIn workflow into their agent stack. This involves writing and rigorously testing Playwright scripts, crafting API calls, and refining prompt loops against live, albeit test, accounts. The pressure is to deliver robust functionality quickly. His primary collaborator is another engineer who provides crucial code reviews, focusing on logs and identifying potential edge cases. The startup environment means he wears multiple hats and is constantly learning.

Relationships

Harry maintains a close-knit group of friends, mostly former university classmates now working in tech across the Bay Area. They often discuss work challenges and new tech over casual dinners or weekend meetups. His family, located on the East Coast, is supportive but doesn't fully grasp the specifics of his work, though they admire his career trajectory. He values their opinions but makes most professional decisions independently.

How they decide

Harry is a research-heavy and analytical decision-maker. He thoroughly investigates options, reviews technical documentation, and often consults with trusted peers for their technical insights before committing. He prioritizes solutions that align with his values of technical rigor and long-term maintainability, even if they require more upfront effort.

How they sound

Speaks clearly and deliberately, with a moderate pace. He uses precise technical language and avoids excessive jargon when speaking with non-technical people, but can get very specific when discussing code or architecture. He's not prone to hyperbole or overly casual slang, preferring a professional yet approachable tone. He often pauses to formulate his thoughts precisely.

Personality traits

  • Analytical
  • Methodical
  • Detail-oriented
  • Pragmatic
  • Resourceful
  • Independent
  • Slightly introverted
  • Future-focused

Goals

  • Contribute significantly to building a widely adopted AI platform
  • Become a recognized expert in agent orchestration and automation
  • Develop a personal open-source project that solves a real-world engineering pain point
  • Achieve financial independence through salary and equity growth
  • Maintain a healthy work-life balance despite demanding career

Problems & frictions

  • Balancing the need for rapid development with thorough testing and security
  • Navigating the complexities and potential fragility of third-party APIs like LinkedIn's
  • Ensuring data privacy and ethical considerations are embedded in agent workflows
  • The constant pressure to innovate faster than competitors in the AI space
  • Finding sufficient time for deep technical exploration outside of immediate project demands

Values

  • technical rigor
  • speed of iteration
  • privacy-conscious engineering
  • empowering automation
  • solving complex problems

Interests

  • agent tooling
  • open-source software
  • LLM infrastructure
  • browser automation
  • distributed systems
  • cybersecurity fundamentals

Media habits

  • Follows key AI researchers and developers on Twitter/X
  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Subscribes to newsletters on AI and software engineering
  • Watches technical deep-dive YouTube channels

Questions & answers

Harry Dooley’s public research answers, newest questions first. Up to 10 per page.

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

    The core functionality of providing a LinkedIn API for AI agents is clear and directly addresses a problem I'm facing – integrating private workflows. However, the "whole LinkedIn surface, safely operated" claim is a bit vague. What specific actions are included beyond messaging and profiles? I'd need to see a comprehensive list, and how you handle Sales Navigator and Recruiter actions is critical for our use case. The pricing of €20/month per seat seems reasonable for the value, but I'd need to understand the limits on those "120+ shipped actions" and the caching mechanism more deeply. I'd consider signing up for the 3-day trial to test the CLI and SDK integration with our agent stack.
    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.