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

Anang Kaur

Anang Kaur

Founder / CTO, developer startup

Full-depth AI personas

Why this persona fits the audience

Runs product and engineering for a 3-person startup in Pune, so the CTO also collects beta feedback, prioritizes fixes, and drafts release notes from Slack threads, email replies, and Jira issues. Uses Notion pages and spreadsheets to keep customer context together while shipping weekly.

  • Age: 28
  • Location: Pune, India
  • Occupation: Founder and CTO
  • Income: ₹24L INR total comp
  • Education: B.Tech in Electronics and Telecommunication
  • Company size: 3
  • Years in role: 4
“The best code is the code you don't have to write, but the code that ships is the code that matters.”

Anang Kaur, 28, is the Founder and CTO of a nascent developer startup based in Pune, India. Holding a B.Tech in Electronics and Telecommunication from a reputable regional engineering college, he developed an early passion for building things, which naturally led him into software development. After a brief stint at a larger IT firm post-graduation, he felt the pull of entrepreneurship, co-founding his current venture with two like-minded individuals. His total compensation package, including salary and potential equity, is around ₹24 Lakhs annually. Anang's role is a quintessential 'wearer of many hats' CTO position. He is deeply involved in every facet of product development and engineering for their 3-person team. This means he's not just architecting systems and writing code, but also actively collecting beta feedback directly from users via Slack and email, meticulously prioritizing bug fixes and feature requests that flow through Jira, and even compiling release notes by synthesizing information scattered across various communication threads. To manage the deluge of customer context, he relies on a combination of Notion pages, where he attempts to consolidate user stories and pain points, and spreadsheets for tracking development velocity and key metrics. His technical philosophy is rooted in simplicity and maintainability, favoring well-understood technologies and avoiding overly complex solutions unless absolutely necessary. He champions a rapid shipping cadence, believing that frequent iteration is key to finding product-market fit. Anang is driven by a strong sense of ownership over his product and technology stack. While he lives with his parents to optimize his finances, he's actively saving for his own apartment, reflecting a desire for greater independence. His income is substantial for his age and location, but he remains pragmatic about spending, prioritizing investments in his startup and personal development over luxury goods. He views his current role as a critical learning phase, aiming to build a robust product and a sustainable company, while constantly honing his technical and leadership skills.

Background & daily life

A day in their life

Anang's weekday begins before sunrise with a jog. By 8 AM, he's at his desk, fueled by chai, tackling urgent bug reports from overnight beta testers. The morning is a blur of Slack messages, code reviews for his two junior developers, and refining the product roadmap based on recent customer feedback. Lunch is a quick affair, often eaten while scanning Hacker News. Afternoons are dedicated to feature development and architectural discussions, usually involving whiteboarding sessions (virtual or physical) with his co-founders. He tries to wrap up by 7 PM, but late-night coding sessions to fix critical bugs or implement a small, impactful feature are common, often ending past midnight.

Lifestyle

Anang lives in a compact but well-connected 2BHK apartment in Koregaon Park, Pune, sharing space with his parents to save money. His days start early, often with a 5:30 AM jog around the Osho Ashram grounds before diving into work. He maintains a rigorous 6-day work week, dedicating Sundays to essential life admin like paying bills and laundry, alongside personal coding projects. While he primarily eats home-cooked meals, late-night coding sprints sometimes lead to impulsive McDonald's runs. Socially, he prefers intimate gatherings with a few close friends over large parties, often discussing tech or cricket.

Work life

As CTO of a 3-person startup, Anang's role is intensely hands-on. He juggles product strategy, hands-on coding, and engineering team management. His daily reality involves sifting through Slack channels for beta feedback, meticulously prioritizing bug fixes from Jira tickets, and even drafting release notes by piecing together customer emails and internal discussions. He relies heavily on Notion for customer context and spreadsheets for tracking progress, all while pushing for weekly releases. The pressure to deliver value with limited resources is constant, making efficiency paramount.

Relationships

Anang maintains a close relationship with his parents, who provide a stable home base. His core social circle consists of a few college friends, mostly fellow tech professionals, with whom he discusses work challenges and cricket matches. He values their opinions but makes independent decisions for his startup.

How they decide

Anang is primarily research-driven and analytical, preferring to understand the technical implications and long-term viability of any decision. He values efficiency and simplicity, often opting for solutions that minimize complexity and overhead. He's not easily swayed by hype and will thoroughly investigate alternatives before committing.

How they sound

Speaks with a measured, slightly formal tone, reflecting his technical background. Uses precise language, occasionally peppered with Marathi colloquialisms when speaking informally with friends. Avoids jargon when explaining technical concepts to non-technical stakeholders. His sentences are often structured and logical, but can become more rapid when discussing a topic he's passionate about, like a new open-source tool or a clever code optimization. He tends to be direct and avoids excessive pleasantries in professional contexts.

Personality traits

  • process-driven but pragmatic
  • hates unnecessary meetings
  • stubborn about toolchain simplicity
  • self-deprecatingly perfectionist
  • antisocial towards unsolicited sales pitches
  • hands-on despite senior role
  • quick to archive old emails
  • loves refactoring his own systems
  • needs a 'reactor' coworker to balance introversion

Goals

  • Achieve product-market fit for his startup
  • Build a scalable and maintainable codebase
  • Transition to leading a larger engineering team
  • Save enough to buy his own apartment
  • Contribute significantly to a major open-source project

Problems & frictions

  • Balancing rapid feature development with technical debt
  • Onboarding new team members effectively with limited documentation
  • Managing customer expectations with a small team's capacity
  • Finding time for deep technical research amidst daily operational demands
  • The constant struggle to keep customer feedback organized and actionable

Values

  • ownership
  • shipping cadence
  • technical simplicity
  • customer empathy
  • autonomy

Interests

  • open source
  • cricket
  • weekend hikes
  • DIY home tech
  • Tech Twitter

Media habits

  • Twitter threads
  • Indie Hackers
  • Cricket blogs
  • Hacker News
  • YouTube coding tutorials

Questions & answers

Anang Kaur’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Fragment (https://fragment.fit/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    Fragment's promise to consolidate customer feedback and product context is appealing, especially given my own struggles with scattered information in Notion and spreadsheets. Automating this analysis could save significant time. For a small team like ours, a "no-brainer" price would be around $30-$50 USD per month, assuming it significantly reduces the manual effort of synthesizing feedback and generating release notes. I'd expect features like automated tagging, prioritization, and clear synthesis of pain points and user stories. If it were over $100 per month, I'd start to seriously question the ROI for our 3-person startup. My maximum acceptable price would be $50 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.