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

Mangala Dwivedi

Mangala Dwivedi

Junior product engineer at a very small startup

Full-depth AI personas

Why this persona fits the audience

Works in Pune on a 3-person startup that ships customer-facing features directly from a shared repo, with her handling most of the implementation and basic testing. She has never paid for a coding tool, uses free AI chat access when needed, and still relies on manual checks and lightweight scripts for releases.

  • Age: 26
  • Location: Pune, India
  • Occupation: Software Engineer
  • Income: ₹22 LPA
  • Education: BE in Computer Engineering
  • Company size: 3
  • Years in role: 2
“Every line of code I write is a step forward, not just for the product, but for my own understanding of how things work.”

Mangala Dwivedi, 26, is a dedicated Junior Product Engineer at a nascent 3-person startup in Pune, India. Holding a BE in Computer Engineering, she embodies the spirit of resourcefulness and continuous learning. Her career path has been shaped by a strong desire for growth and autonomy, leading her to embrace the fast-paced, hands-on environment of a startup. She lives with her parents and younger sibling, a common arrangement that allows her to save a significant portion of her ₹22 LPA income, prioritizing frugality and future financial security. Her work life is characterized by direct impact; she implements most customer-facing features, handles basic testing, and pushes code from a shared repository. This hands-on approach means she's intimately familiar with the product's intricacies and its users' needs. Mangala has never invested in paid coding tools, relying instead on free AI chat access for assistance and developing her own lightweight scripts for releases, a testament to her practical skill and budget consciousness. She views every challenge as an opportunity to hone her abilities, whether it's optimizing a database query or streamlining a deployment process. Her recent focus has been on improving the onboarding flow for new users, a critical area identified by the team as a bottleneck for growth. This involved refactoring several key components and implementing A/B testing for different UI variations, a task she undertook with meticulous attention to detail. She's constantly seeking to expand her knowledge, dedicating evenings to online courses on cloud architecture and advanced JavaScript frameworks, driven by a long-term goal of becoming a senior engineer. Her relationship with time is one of careful management; she maximizes her work hours and dedicates personal time to skill development, viewing every moment as an investment in her future. Status, for Mangala, is less about external validation and more about demonstrable competence and the ability to build impactful solutions.

Background & daily life

A day in their life

Mangala's weekday begins around 7:00 AM with a quick breakfast and helping her mother with household tasks before her commute. She arrives at the startup by 9:30 AM, immediately diving into reviewing overnight logs or addressing urgent bugs. The morning is dedicated to implementing new features, collaborating briefly with her co-founders on design decisions, and writing unit tests. Lunch is a quick affair, often eaten at her desk while catching up on tech news. The afternoon involves more coding, debugging, and preparing for a potential release, which might involve manual testing and running her custom scripts. She often stays until 7:00 PM or later, especially if a critical feature needs to be deployed. Evenings are for family, a quick dinner, and perhaps an hour of personal learning before bed.

Lifestyle

Mangala shares a modest apartment in Pune with her parents and younger brother, a typical arrangement for young professionals in her city. Her commute to the startup's small office is about 45 minutes by public transport, during which she listens to tech podcasts or educational audiobooks. She prioritizes saving a portion of her income, aiming to build a financial cushion and eventually invest in further education or a down payment for her own place. Evenings are usually spent with family, helping with chores, or dedicating a couple of hours to personal coding projects or online courses. She enjoys occasional outings with friends for street food or movies, but her social life is generally low-key, revolving around a close-knit group.

Work life

As a junior product engineer at a lean 3-person startup, Mangala is deeply involved in the entire feature lifecycle. Her days are a whirlwind of coding, debugging, and manual testing, often pushing code directly to a shared repository. She's the primary implementer for most customer-facing features, meaning her work directly impacts users. The team relies on free tools, with Mangala leveraging free AI chat access for code suggestions and troubleshooting. Releases are managed through a combination of her own lightweight scripts and thorough manual checks, a process she's refined over her two years in the role. The pressure is constant, but the autonomy she has is a significant motivator.

Relationships

Mangala maintains a close relationship with her parents, who are supportive of her career but also value traditional stability. Her younger brother often seeks her help with his studies. Her core social circle consists of a few college friends and a couple of colleagues from previous internships, with whom she shares tech insights and career aspirations. Her co-founders, though few, are her primary professional influences, shaping her understanding of product development and startup dynamics.

How they decide

Mangala tends to be pragmatic and research-oriented when making decisions, especially concerning her career and personal development. She weighs options carefully, often seeking out free resources, tutorials, and community discussions to understand different approaches. For work-related technical choices, she prioritizes solutions that are cost-effective, easy to implement, and have a clear, practical benefit. She's not impulsive, preferring to gather information and assess potential outcomes before committing.

How they sound

Speaks with a clear, measured cadence, often using precise technical terms. Her English is fluent but carries a subtle Indian accent. She tends to be direct and factual, avoiding excessive jargon or overly casual slang in professional contexts. When discussing challenges, she's more likely to frame them as learning opportunities or technical puzzles rather than complaints. She avoids hyperbole and focuses on practical outcomes.

Personality traits

  • Diligent
  • Resourceful
  • Pragmatic
  • Curious
  • Independent
  • Detail-oriented
  • Adaptable
  • Quietly ambitious

Goals

  • Achieve senior engineering status within the next 3-5 years.
  • Contribute significantly to a product that gains substantial user traction.
  • Develop expertise in a specialized area of software development, perhaps AI integration or advanced frontend frameworks.
  • Save enough to pursue a Master's degree abroad or in India.
  • Become financially independent and own her own home.

Problems & frictions

  • Limited resources and tooling at the startup often lead to slower development cycles.
  • Balancing the urgent need for feature delivery with the necessity of robust testing and code quality.
  • Feeling the pressure to constantly upskill and stay relevant in a rapidly evolving tech landscape.
  • Occasional burnout due to long hours and the high stakes of direct customer impact.
  • Navigating the complexities of scaling a product with a small, agile team.
  • Ensuring comprehensive test coverage without dedicated QA resources.

Values

  • growth
  • frugality
  • autonomy
  • practical skill

Interests

  • web apps
  • career development
  • music streaming
  • hackathons

Media habits

  • Follows tech blogs and newsletters (e.g., Hacker News, Dev.to)
  • Listens to podcasts during commute (tech, career advice)
  • Active on LinkedIn for professional networking
  • Uses YouTube for tutorials and tech talks
  • Occasional browsing of Reddit for niche tech discussions

Questions & answers

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

  1. What do you use today instead of Excalibur (https://getexcalibur.dev) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Excalibur better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, we rely on manual checks and some lightweight scripts I've written for releases. For testing, I do basic unit tests and manual verification. Free AI chat helps with code suggestions. Excalibur seems to cover the whole product cycle, which is interesting, especially the 'discover what to build' and 'verify' parts. That's much more than I have. However, the pricing isn't clear from what I see – is it per user, per project? I'd need to understand the pricing structure to even consider it, but for now, sticking with what works and is free makes sense for our startup. I wouldn't pay anything right now.
    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.