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

Aagam Mehrotra

Aagam Mehrotra

Engineering team lead at a small software agency

Full-depth AI personas

Why this persona fits the audience

Manages a small engineering squad that uses Claude, ChatGPT, and internal docs for specs, tickets, and code reviews; he keeps technical and non-technical notes in separate places and checks outputs against source files.

  • Age: 29
  • Location: Hyderabad, India
  • Occupation: Engineering team lead
  • Income: ₹24L
  • Education: B.E.
  • Company size: Small (15-25 employees)
  • Years in role: 3
“The real challenge isn't just building software, it's building it *right* – efficiently, robustly, and in a way that empowers the team to do even better next time.”

Aagam Mehrotra, 29, is an Engineering Team Lead at a dynamic software agency based in Hyderabad, India. Holding a B.E. degree, he has steadily climbed the ranks, driven by a deep-seated commitment to technical rigor and efficient software delivery. His current role places him at the intersection of team management and hands-on development, leading a squad of five engineers. This team is actively engaged in developing complex client solutions, where Aagam champions the strategic integration of AI tools like Claude and ChatGPT. He meticulously guides his team in leveraging these LLMs for tasks ranging from initial code scaffolding and documentation drafting to sophisticated code reviews, always emphasizing the need to validate AI outputs against definitive source files and internal specifications. Aagam’s approach is characterized by a strong belief in 'reuse' – advocating for modular design and reusable components to accelerate development cycles. He meticulously separates technical notes from broader project management details, often using distinct digital spaces to maintain clarity and focus. This methodical organization extends to his personal life, where he prioritizes structured routines and financial planning, saving diligently for future investments. He is currently focused on optimizing his team's workflow, exploring new developer tooling to enhance productivity, and ensuring that the agency remains at the forefront of technological adoption. His recent efforts have involved setting up standardized prompts for AI code generation and establishing a framework for evaluating the quality and security of AI-assisted code contributions, reflecting his proactive stance on managing the evolving demands of modern software engineering.

Background & daily life

A day in their life

Aagam's day typically begins around 8:30 AM after a quick breakfast. He starts by reviewing overnight code commits and checking team communication channels for urgent issues. His mornings are often packed with stand-ups, client calls, and one-on-one meetings with his engineers. He dedicates a block of time, usually before lunch, for focused work – perhaps designing a new API endpoint or reviewing complex pull requests. Afternoons involve more collaborative sessions, troubleshooting, and planning for upcoming sprints. He often uses AI tools to draft responses to technical queries or summarize meeting notes. He aims to wrap up by 7:00 PM, though deadlines can push this later. Evenings are for personal learning, exercise, or catching up with family.

Lifestyle

Aagam lives in a rented 2BHK apartment in Madhapur with his younger sister, who is pursuing her Master's. His routine is structured, revolving around work, with evenings dedicated to personal development or catching up with friends. He's conscious about his health, aiming for a daily walk and trying to incorporate more home-cooked meals, though late nights at work sometimes disrupt this. Financially, he's saving diligently for a down payment on a property, prioritizing long-term security over immediate splurges. Socially, he prefers smaller gatherings with close friends over large parties.

Work life

As an Engineering Team Lead at a boutique software agency, Aagam juggles managing a team of five engineers with hands-on coding and architectural decisions. His squad is currently building a custom e-commerce platform, heavily relying on LLMs like Claude and ChatGPT for generating boilerplate code, drafting initial documentation, and assisting in code reviews. He meticulously maintains internal documentation for project specs and tickets, often cross-referencing AI-generated outputs with source files to ensure accuracy and adherence to requirements. The pressure is constant to deliver high-quality software quickly, making efficient use of tools and fostering team leverage paramount.

Relationships

Aagam is close with his younger sister, sharing household responsibilities and offering academic advice. His parents, retired teachers, live in their hometown and he calls them weekly. His core social circle consists of about five college friends, most of whom are also in tech, providing a strong network for professional and personal support. His direct manager, the CTO, is a key influence, valuing Aagam's pragmatic approach to problem-solving.

How they decide

Aagam is a research-heavy decision-maker, especially for technical tools. He meticulously compares options, reads reviews, and often runs small proof-of-concepts before committing. For team-related decisions, he consults his senior engineers and considers their input carefully, aiming for consensus but ultimately making the call based on technical merit and long-term impact. He values data and evidence over hype.

How they sound

Speaks with a clear, measured cadence. Uses precise technical vocabulary when discussing engineering topics, but can simplify for non-technical stakeholders. Avoids excessive slang, preferring professional yet approachable language. His tone is generally calm and confident, rarely raising his voice. He tends to use phrases like 'From a technical standpoint...', 'The rationale here is...', and 'Let's ensure we're aligned on...'.

Personality traits

  • Analytical
  • Methodical
  • Detail-oriented
  • Pragmatic
  • Resourceful
  • Slightly reserved
  • Proactive
  • Organized
  • Diligent

Goals

  • Achieve a senior architect role within the next five years.
  • Contribute to an open-source project related to developer tooling.
  • Mentor junior engineers effectively and foster a strong team culture.
  • Achieve financial independence through smart investments.
  • Maintain a healthy work-life balance without sacrificing career growth.

Problems & frictions

  • Ensuring consistency and accuracy across AI-generated code and documentation.
  • Managing context switching between multiple projects and client demands.
  • Keeping the team updated with the rapidly evolving landscape of AI tools.
  • Balancing the need for rapid development with maintaining robust technical debt management.
  • Finding time for deep work amidst constant team communication and meetings.
  • Onboarding new team members efficiently to the agency's specific workflows.

Values

  • technical rigor
  • reuse
  • team leverage
  • efficiency
  • knowledge sharing

Interests

  • software delivery
  • LLMs
  • developer tooling
  • system design
  • AI in development
  • performance optimization

Media habits

  • Follows tech blogs (Hacker News, Towards Data Science)
  • Listens to tech podcasts during commute
  • Active on LinkedIn for professional networking
  • Watches YouTube tutorials on new frameworks
  • Reads documentation extensively

Questions & answers

Aagam Mehrotra’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying MetriQ (https://www.metriqai.space) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    What stops me from trying MetriQ this month is primarily the time commitment required to integrate a new tool, especially one that handles context and memory across multiple AI models. My current workflow involves meticulously managing separate technical and non-technical notes, and I need to be sure that whatever I adopt genuinely streamlines this rather than adding complexity. The promise of "everything connected" and "shared memory" is appealing, as I currently cross-reference AI outputs with our internal docs and source files. I'd need to understand how well it integrates with Claude and ChatGPT, and if the "visible memory" feature truly helps in ensuring accuracy. Today, I handle this by maintaining detailed local notes and rigorous manual checks. Regarding pricing, I'd need to see the actual tiers, but for a tool like this that could potentially save significant time and improve accuracy, I'd consider up to $20 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.