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

Deeptendu Dwivedi

Deeptendu Dwivedi

Fantasy startup backend developer

Full-depth AI personas

Why this persona fits the audience

Maintains cricket and football fixtures, scores and player stats for a 3-person fantasy startup in Bengaluru; he mixes public APIs, scraped pages and a shared spreadsheet because the product is still small and the team watches costs closely. He is the one writing the sync jobs and chasing edge cases when schedules change.

  • Age: 28
  • Location: Bengaluru, India
  • Occupation: Backend developer
  • Income: ₹24 LPA
  • Education: BTech in Information Technology
  • Company size: 3 people (including 2 co-founders)
  • Years in role: 2
“If the data isn't right, the whole game is rigged. And if we're spending too much to get it, we're losing before we even start.”

Deeptendu Dwivedi grew up in a middle-class family in a smaller city in Karnataka, where his aptitude for mathematics and logic was evident early on. His father, an accountant, instilled in him a strong sense of financial prudence, while his mother, a teacher, encouraged his curiosity. This upbringing shaped his core values of accuracy and frugality. He pursued a BTech in Information Technology at a reputable college in Bengaluru, where he excelled academically, particularly in data structures and algorithms. During his studies, he developed a passion for open-source software and the power of APIs, seeing them as elegant solutions to complex problems. He also honed his chess skills, appreciating the strategic depth and the need for precise calculation. After graduating, he worked for a year at a mid-sized IT services company, finding the work uninspiring and the corporate structure stifling. Seeking more autonomy and a direct impact, he joined his current startup two years ago. The small team and lean budget meant he had to be incredibly resourceful, learning to stitch together data solutions using a combination of public APIs, web scraping techniques, and even manual data entry via shared spreadsheets when absolutely necessary. He recently spent two weeks debugging a particularly stubborn issue where a football league changed its API endpoint without notice, forcing him to rewrite significant portions of his data ingestion scripts under tight deadlines. He views his role not just as a developer but as a guardian of data integrity for their fantasy platform, constantly balancing the need for speed with the absolute requirement for accuracy, all while keeping a hawk's eye on operational costs. He lives modestly, saving diligently, and sees his current role as a crucial stepping stone, building valuable experience in a high-growth, albeit challenging, domain. His relationship with time is one of constant optimization, always looking for ways to automate repetitive tasks and free up cycles for more complex challenges. Money is a tool for security and future growth, not for ostentatious display.

Background & daily life

A day in their life

Deeptendu's weekday typically begins around 7:00 AM. After a quick breakfast and checking overnight cricket scores, he dives into his work. The first few hours are dedicated to monitoring existing data sync jobs, checking for errors, and addressing any immediate issues from the previous day's matches. He then focuses on developing new features or improving existing scripts, often involving intricate Python code for data parsing or API integration. Lunch is a simple affair, usually eaten at his desk while browsing tech news. The afternoon might involve a brief sync-up with his co-founders to discuss priorities or data discrepancies. He often works until 7:00 or 8:00 PM, especially if there's a live match with complex data requirements or a critical bug to fix. Evenings are for unwinding with a game of chess or reading.

Lifestyle

Deeptendu's life revolves around his work and personal interests. He lives a frugal but comfortable life in a modest apartment, prioritizing savings for future investments or perhaps a down payment on a small property. His routine is disciplined: early mornings for coding or catching up on international cricket matches, followed by work. Evenings are often spent playing chess online, reading tech blogs, or occasionally meeting a couple of close friends for a quick dinner. He cycles or uses public transport to save money and avoid Bengaluru's traffic, viewing it as a small act of environmental responsibility. His social life is limited but meaningful, focused on a few like-minded individuals.

Work life

As the sole backend developer for a nascent fantasy sports startup, Deeptendu's days are a constant juggle. He's responsible for the entire data pipeline, from fetching live scores and player statistics to ensuring they're accurately reflected in the fantasy platform. This involves writing and maintaining Python scripts that pull data from a mix of public APIs, web scraping (often from sites with inconsistent structures), and even manually updating a shared Google Sheet when automated methods fail. He's acutely aware of the company's tight budget, which dictates his choice of tools and infrastructure. The pressure is on to keep costs low while ensuring data accuracy and timely updates, especially when match schedules shift unexpectedly, which is a frequent occurrence.

Relationships

Deeptendu maintains a small circle of close friends, mostly fellow developers he met during his BTech or through online communities. He has a good, albeit somewhat distant, relationship with his parents back in his hometown, calling them weekly. His co-founders, one focused on product and the other on marketing, are his primary professional collaborators. They trust his technical judgment implicitly, given the startup's size.

How they decide

Deeptendu is a highly analytical and research-driven decision-maker, especially concerning technical tools and processes. He meticulously weighs cost against functionality, often experimenting with free or open-source options first. He's not impulsive and prefers to understand the underlying mechanics before committing to a solution. Peer recommendations from trusted developer communities carry weight, but he always validates them with his own testing and evaluation.

How they sound

Speaks with a measured cadence, often pausing to find the precise technical term. His English is clear and grammatically correct, with a subtle South Indian accent. He avoids jargon when explaining things to non-technical people but uses precise technical language with peers. He tends to be direct and factual, rarely using hyperbole. He might occasionally use a mild expletive when encountering a particularly stubborn bug.

Personality traits

  • Methodical and detail-oriented
  • Pragmatic about perfectionism
  • Quietly opinionated about data quality
  • Prefers tinkering and problem-solving
  • Distrusts overly complex or expensive solutions
  • Competitive in games, not necessarily in social settings
  • Values tools that are reliable and cost-effective
  • Frustrated by unpredictable data sources
  • Enjoys the challenge of optimizing processes
  • Resourceful in finding free or low-cost tools

Goals

  • Achieve stable, scalable data infrastructure for the startup
  • Contribute to a product that gains significant user traction
  • Master advanced Python and data engineering techniques
  • Build a personal portfolio of open-source contributions
  • Achieve financial independence within the next 7-10 years

Problems & frictions

  • Inconsistent and unreliable data sources from sports leagues/providers
  • The constant need to adapt scraping scripts to website changes
  • Limited budget for premium data feeds or robust infrastructure
  • Balancing speed of development with long-term maintainability
  • The pressure of being the single point of failure for data operations
  • Managing unexpected schedule changes in live sports events

Values

  • accuracy
  • frugality
  • speed
  • autonomy
  • data integrity
  • efficiency

Interests

  • cricket
  • APIs
  • Linux
  • chess
  • open-source software
  • optimizing scripts

Media habits

  • Follows cricket news sites (esp. Cricinfo)
  • Reads Hacker News and Reddit (r/programming, r/linux)
  • Watches tech talks and chess analysis on YouTube
  • Uses X (Twitter) for quick tech updates and developer discussions
  • Listens to podcasts on software development during commutes

Questions & answers

Deeptendu Dwivedi’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Trusted sports data provider that offers live scores, fixtures, stats, odds etc. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The single biggest problem is data accuracy and latency, especially when schedules change unexpectedly. We rely on a mix of APIs, scraping, and manual updates, which is error-prone and time-consuming. Debugging these inconsistencies can take hours, often impacting our fantasy game's integrity. This directly costs us developer time that could be spent on new features, and potentially customer trust if the data is wrong. We've tried building more robust parsers and alert systems, but it's a constant battle against external data source changes.
    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.