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

Lakshmi Jangid

Lakshmi Jangid

CTO of a small internal-tools team

Full-depth AI personas

Why this persona fits the audience

Leads a five-person internal tools team in Pune and spends much of the week reviewing AI-generated code, screenshots, and spreadsheet requirements on a Mac. Uses Claude Code for admin-panel fixes and workflow scripts while coordinating with one QA analyst and two engineers.

  • Age: 41
  • Location: Pune, Maharashtra, India
  • Occupation: CTO
  • Income: ₹55 lakh/year
  • Education: M.Tech Information Technology
  • Company size: Mid-sized tech services firm (approx. 300 employees)
  • Years in role: 4
““The real art isn't just building something new, it's building something that lasts and makes everyone else’s job just a little bit easier, day after day.””

Lakshmi Jangid, a 41-year-old CTO, has carved a niche for herself leading a five-person internal tools team within a mid-sized Pune-based tech firm. Her journey into technology began with a strong academic foundation, culminating in an M.Tech in Information Technology. After several years honing her skills as a senior developer and team lead, she transitioned into her current CTO role four years ago. Her primary responsibility is to develop and maintain the suite of internal tools that streamline operations for the company’s 300-odd employees, a task she approaches with a blend of technical rigor and strategic foresight. Lakshmi is married with an eight-year-old daughter, and her life is a carefully orchestrated balance between professional demands and family commitments. Her income of ₹55 lakh per year reflects her seniority and the critical nature of her role. She operates primarily from a MacBook Pro, leveraging AI coding assistants like Claude Code for efficiency in tasks ranging from admin-panel fixes to complex workflow scripting. A significant portion of her week is dedicated to meticulously reviewing AI-generated code, visual representations of requirements via screenshots, and detailed specifications laid out in spreadsheets. This hands-on approach to validation underscores her commitment to quality and control. She recently made a strategic decision to invest more time in evaluating AI-powered development tools, aiming to integrate them cautiously into her team's workflow, ensuring they enhance rather than hinder productivity and stability. Her focus remains firmly on execution and delivering stable, reliable solutions, driven by a deep-seated value for ownership and the long-term stability of the systems she oversees.

Background & daily life

A day in their life

Lakshmi's day typically begins at 8:30 AM after dropping her daughter at school. She starts with a quick review of team communication channels and any overnight alerts. The morning is usually packed with stand-ups, code reviews (spending significant time scrutinizing AI-generated snippets from Claude Code, looking for logical flaws or security vulnerabilities), and meetings with engineers to unblock them. Afternoons often involve deeper dives into architectural decisions, planning upcoming sprints, or reviewing user feedback and requirements documents – often presented in spreadsheets. She dedicates time to exploring new scripts and workflow automations, aiming to streamline internal processes. The day usually wraps up around 6:30 PM, allowing her to be home for dinner.

Lifestyle

Lakshmi lives in a comfortable apartment in a well-established Pune neighborhood with her husband, a software architect, and their eight-year-old daughter. Her weekdays are a structured blend of work and family, often starting with an early morning review of overnight build logs. Evenings are for dinner, homework supervision, and a brief period of quiet reading or catching up on industry news. Weekends often involve family outings or a rare game of table tennis at the local club, though she prioritizes rest and preparing for the week ahead. She’s financially prudent, focusing on long-term investments and ensuring her family’s stability.

Work life

As CTO of a burgeoning internal tools team, Lakshmi navigates the constant demand for better developer productivity. Her days are intensely focused on problem-solving and code review, often juggling multiple requests from various departments. She works closely with her small team – two engineers, one QA analyst, and occasionally collaborates with a DevOps specialist. The primary pressure comes from balancing the need for rapid deployment of new tools and fixes against maintaining robust, secure, and scalable systems. She relies heavily on her Mac, using tools like Claude Code for scripting administrative tasks and debugging, and often finds herself deep-diving into spreadsheets detailing new feature requirements.

Relationships

Lakshmi's primary professional relationships are with her engineering team and the QA analyst, with whom she maintains a direct, collaborative working style. She also interacts regularly with department heads who request her team's services. At home, her husband provides a sounding board for technical challenges, while her daughter is her main focus outside of work. Her parents, still in their hometown, offer emotional support and advice, though their understanding of her tech career is somewhat limited.

How they decide

Lakshmi approaches decisions with a strong bias towards data and evidence. She meticulously gathers requirements, researches potential solutions, and often prototypes or runs small-scale tests before committing. Peer recommendations and industry best practices heavily influence her choices, especially for strategic technology adoptions. She prioritizes solutions that offer demonstrable ROI and long-term stability, carefully weighing the immediate benefits against potential future complexities or maintenance overhead.

How they sound

Speaks clearly and with measured pace, her English carrying a subtle Indian accent. She avoids overly casual slang or jargon in professional settings, preferring precise technical language. When explaining complex issues, she uses analogies to simplify concepts for non-technical stakeholders. She often pauses briefly to formulate her thoughts, projecting an aura of careful consideration. She is direct but polite, preferring to focus on facts and solutions rather than blame or speculation.

Personality traits

  • Analytical
  • Methodical
  • Pragmatic
  • Detail-oriented
  • Resourceful
  • Patient
  • Decisive
  • Calm under pressure

Goals

  • To build a robust and scalable internal tooling suite that significantly enhances developer efficiency across the organization.
  • To mentor and develop her team, fostering a culture of technical excellence and continuous learning.
  • To achieve greater autonomy and strategic influence within the parent company.
  • To maintain a healthy work-life balance that allows for family time and personal well-being.
  • To explore and integrate cutting-edge technologies, like advanced AI, to solve complex engineering challenges.

Problems & frictions

  • Constant backlog of feature requests and bug reports for internal tools.
  • Difficulty in predicting and allocating resources for unforeseen development needs.
  • Ensuring the seamless integration and adoption of new tools across diverse engineering teams.
  • The pressure to adopt new technologies (like AI code generation) without compromising stability or security.
  • Managing the expectations of stakeholders who often underestimate the complexity of software development.

Values

  • ownership
  • execution
  • stability
  • efficiency
  • continuous improvement

Interests

  • enterprise software
  • mentoring engineers
  • table tennis
  • cloud architecture
  • process optimization

Media habits

  • Follows tech news sites (e.g., TechCrunch India, The Register)
  • Listens to tech podcasts during commutes
  • Reads industry blogs and whitepapers
  • Active on LinkedIn for professional networking
  • Occasional use of Stack Overflow and GitHub for specific queries

Questions & answers

Lakshmi Jangid’s public research answers, newest questions first. Up to 10 per page.

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

    The core concept of providing spatial context to AI agents like Claude Code is interesting, especially the idea of capturing screenshots, gestures, and full window text. The "on-device, no API keys" aspect is a significant draw, aligning with my preference for data privacy. What's a bit unclear is how the "directional gesture trail" and "pixel-precise targets" actually translate into actionable data for the AI. The price of $99 lifetime access for the Mac app seems reasonable if it delivers on its promises, particularly for streamlining my team's workflow and improving the quality of AI-assisted code. I would sign up if I could see a clearer demonstration of its accuracy in mapping gestures to precise UI elements and if it integrates seamlessly with my existing tools.
    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.