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

Sujata Kaniyar

Sujata Kaniyar

Technical program manager

Full-depth AI personas

Why this persona fits the audience

Coordinates a 5-person engineering and data team at a Bengaluru startup, turning rough architecture notes from meetings into simple diagrams in Google Slides and a shared notebook. Uses them in sprint planning and release handoffs.

  • Age: 36
  • Location: Bengaluru, India
  • Occupation: Technical program manager
  • Income: ₹24L-₹36L
  • Education: BE in Information Science
  • Company size: Early-stage startup (15-20 employees)
  • Years in role: 5
“I don't just manage timelines; I'm the one making sure the map actually matches the territory we're building.”

Sujata Kaniyar is a 36-year-old Technical Program Manager based in Bengaluru, navigating the volatile waters of an early-stage startup with a rare blend of technical acumen and organizational discipline. Holding a Bachelor of Engineering in Information Science, she transitioned from pure software development to program management five years ago, driven by a realization that her true strength lay in connecting disparate technical dots rather than writing the code itself. Currently, she coordinates a lean team of five engineers and data specialists, acting as the glue that holds their ambitious, often shifting, product vision together. Her workspace is a testament to her pragmatic approach: a clutter-free desk dominated by a dual-monitor setup, a whiteboard covered in eraser dust, and a stack of notebooks filled with handwritten schematics. Unlike larger corporations with dedicated architects, Sujata operates in a vacuum of resourcefulness. She frequently finds herself converting the rambling, metaphor-heavy architecture discussions held during late-night brainstorming sessions into crisp, digestible diagrams using Google Slides and Miro. This manual translation process is her daily battle, consuming hours that could be spent on strategic planning. Financially, she is prudent. Earning between ₹24L and ₹36L annually, she balances a comfortable lifestyle with a fierce determination to save for a down payment on a home. She views money not as a means of indulgence but as a buffer against the inherent instability of the startup ecosystem. Professionally, she is highly conscientious, often staying late to ensure that release handoffs are flawless, fearing that a single misunderstood requirement could derail weeks of work. While she enjoys the camaraderie of her small team and finds joy in the rhythmic structure of sprint cycles, the constant need to improvise tools and processes weighs on her. She dreams of a workflow where her creative input isn't bogged down by the limitations of static presentation software, envisioning a world where ideas can be captured visually as naturally as they are spoken, allowing her to focus on the people behind the code rather than the slides themselves.

Background & daily life

A day in their life

Sujata wakes up at 5:30 AM, starting with a cup of filter coffee and ten minutes of meditation before the city stirs. By 7:30 AM, she's commuting via metro to her office in Electronic City, listening to a podcast on system architecture. Her morning is dominated by stand-up meetings where she translates vague feature requests into actionable tasks. Midday brings a critical sync with the CTO, where she frantically sketches a new data pipeline flow on her tablet, then digitizes it into a slide deck. Afternoons are spent debugging process bottlenecks, chasing status updates, and refining release notes. She leaves by 7:00 PM, grabbing dinner on the go, and spends the evening reviewing the next day's sprint plan or tending to her plants. She sleeps by 11:00 PM, knowing tomorrow requires the same level of precision.

Lifestyle

Sujata lives in a modest two-bedroom rental in Koramangala, a hub of Bangalore's tech scene. Her evenings are a ritual of decompression: she tends to her balcony herb garden, a quiet counterpoint to the digital noise of her day. She balances a strict budget, prioritizing savings for a future home down payment over luxury dining, though she enjoys monthly cultural outings to classical concerts. Socially, she maintains a tight circle of three close friends from college who understand her work-life balance struggles. Her health routine involves morning yoga and a disciplined diet, reflecting her belief that physical stamina is necessary for mental endurance in high-pressure environments.

Work life

Her days are a marathon of bridging gaps between abstract ideas and executable code. At a small startup, she wears multiple hats, often acting as the de facto architect when engineers are too busy coding. The core friction is translating chaotic meeting scribbles into clean, understandable visual artifacts using basic tools like Google Slides and sticky notes. She spends significant time manually updating Jira tickets and aligning five engineers across different time zones. The pressure comes from the ambiguity of early-stage product development; she must ensure that every sprint goal is technically feasible while keeping the broader roadmap intact, often working late to finalize release documentation that leaves no room for misinterpretation.

Relationships

Sujata is deeply embedded in her immediate family, particularly her parents in Hyderabad whom she calls weekly. Her husband, an architect, is her primary sounding board for structural logic, though they rarely discuss his professional details. In the office, she relies heavily on her engineering lead, Ravi, whose trust she has earned through consistent delivery. She is part of a women-in-tech meetup group in Bangalore, which provides a support network but feels secondary to her immediate professional survival needs.

How they decide

She is a methodical researcher who values peer validation over marketing hype. Before adopting any new process or tool, she conducts a rigorous cost-benefit analysis, often running small pilots with trusted colleagues. She avoids impulsive decisions, preferring to gather data points and consult with her engineering leads to ensure the choice doesn't introduce unnecessary complexity. Her loyalty lies with solutions that prove their utility in real-world scenarios rather than theoretical features.

How they sound

Her speech is measured and articulate, blending standard English with occasional Kannada or Hindi phrases common in Bangalore corporate settings. She speaks with a direct, solution-oriented cadence, avoiding jargon unless explaining it to non-technical stakeholders. She rarely uses hyperbole, preferring precise verbs like 'align,' 'finalize,' and 'execute.' She avoids complaining about the company culture openly, focusing instead on constructive feedback. Her tone is consistently calm, even during crises, projecting an air of unshakeable competence.

Personality traits

  • methodically organized
  • calm under pressure
  • visually oriented thinker
  • pragmatic idealist
  • reliable connector
  • detail-obsessed
  • direct communicator
  • tech-savvy but tool-skeptical
  • time-conscious
  • culturally grounded

Goals

  • Establish a standardized, reusable diagramming framework for the entire engineering org.
  • Secure a promotion to Senior TPM within the next 18 months.
  • Reduce technical debt accumulation by improving sprint planning clarity.
  • Achieve financial stability to purchase a property in Bangalore by age 40.
  • Mentor junior engineers on system design communication.
  • Launch a side project focused on developer productivity tools.

Problems & frictions

  • Visual artifacts created in slide decks become outdated immediately after creation.
  • Time lost recreating diagrams for different stakeholders (investors vs. devs).
  • Difficulty capturing complex voice conversations into structured flowcharts quickly.
  • Lack of version control for architectural decisions made in informal meetings.
  • Friction in getting remote engineers to agree on a single source of truth.
  • Burnout from context-switching between deep technical work and administrative coordination.

Values

  • coordination
  • follow-through
  • technical literacy
  • clarity
  • efficiency

Interests

  • release planning
  • diagramming
  • team workflows
  • product ops
  • urban gardening
  • classical Carnatic music

Media habits

  • LinkedIn for industry trends
  • Twitter/X for tech gossip
  • Spotify for background focus playlists
  • Newsletters like 'The Pragmatic Engineer'
  • Podcasts on systems thinking
  • Local Bengali news apps

Questions & answers

Sujata Kaniyar’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: Voice-first canvas for sketchnoting and whiteboarding. Ideate, sketch, and edit diagrams in real time on a voice-first canvas. Speak naturally to build… 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.

    This 'Maker launch on TinyLaunch' sounds interesting, a voice-first canvas for sketchnoting. My biggest problem right now is the time I spend manually translating architectural discussions into static diagrams in Google Slides. It's incredibly time-consuming, easily taking up a few hours each week that I could use for strategic planning. We've tried using a shared whiteboard, but it's not easily accessible offsite and lacks version control. I'm not sure how a 'voice-first' approach would integrate with our existing workflow or if it truly solves the digitization and editing bottleneck.
    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.