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

Bhaasvan Malik

Bhaasvan Malik

Full-stack developer at an AI tooling startup

Full-depth AI personas

Why this persona fits the audience

He is the sole developer responsible for waitlist and partner-intake forms at a seed-stage AI startup in Bengaluru. Today the team captures leads with Google Forms, exports to Sheets, and pings founders in Slack or WhatsApp when priority accounts come in.

  • Age: 29
  • Location: Bengaluru, India
  • Occupation: Full-stack Developer
  • Income: ₹32 lakh per year
  • Education: BE in Information Technology
  • Company size: 10-15 employees
  • Years in role: 4
“I don't want to be the person who builds maintainable systems. I want to be the person who builds systems so maintainable that nobody even notices they're working.”

Bhaasvan Malik graduated in IT from an average college with above-average marks and a below-average tolerance for corporate bureaucracy. His first job at a mid-tier SaaS company taught him the importance of system design the hard way—when he inherited a monolith that needed 45 minutes to compile. That experience made him both a better developer and more impatient with technical debt. His current role at an AI startup is his first at a company where he has real autonomy, but that autonomy comes with the invisible wage of being everyone's go-to for 'just one quick fix.' His co-founder—a CEO with a strong product vision but questionable technical judgment—likes to say 'Bhaasvan can turn a Google Form into a NASA mission control panel,' which is both a compliment and a backhanded critique of his tendency to overbuild solutions. Recent constraints include aggressive timelines for integrating partner onboarding, pressure to make their system 'enterprise-ready' without an enterprise budget, and the perpetual challenge of convincing people that 'quick and dirty' usually becomes 'expensive and messy.' His financial situation is stable but not flush; he carefully budgets for hardware upgrades that give him a 10% productivity bump. His most recent major decision was refusing to outsource the lead management system to a third party after calculating the annual cost would exceed his salary. Instead, he's working on a weekend project to build an internal solution, knowing full well that if it succeeds, it will become his new unglamorous responsibility. Outside work, he's the kind of person who'll spend three hours debugging a friend's laptop just to hear them say 'thank you,' but will grumble for weeks about 'mental load' when asked to respond to a simple survey. His dream is to someday build a tool so useful he can just say 'It's on GitHub' and walk away from it.

Background & daily life

A day in their life

Bhaasvan's weekday begins at 6:30am with the frustration of remembering he forgot to charge his fitness band. After his gym session, he showers and checks emails in his kitchen, grimacing at yet another message about a stuck payment form. At work, his first task is rebuilding a broken Django migration from six months ago because the new team member didn't document the schema changes. Mid-morning, he gets pulled into a product call where everyone agrees 'the lead capture flow is bad' but nobody can agree on the fix. For lunch, he microwaves dal and rice in the office pantry while arguing with his data scientist friend about whether LLM fine-tuning is overhyped. The afternoon is spent bouncing between debugging a partner portal form and writing documentation for a new team member who will probably ignore it. At 8pm, he orders the evening's first biryani while finally getting around to his weekend project: a CLI tool to auto-tag leads from forms. By 11pm, he's mentally exhausted but energized by the progress, and vows to show the prototype to his co-founder—who will inevitably say 'This is amazing but let's focus on the core product.'

Lifestyle

Bhaasvan lives in a compact one-bedroom apartment near Koramangala, where the AC is expensive but the proximity to Decathlon outweighs the cost. His routine is rigid by design: 6:30am wake-up with black coffee, 7:30am gym with a colleague (they grumble about tech trends on the treadmills), and 8:30am work from home or the office depending on his mood. His idea of self-care is ordering biryani from a vendor who delivers within 20 minutes, usually after 11pm when he's debugging. He maintains a strict 'no outings on weekdays' policy but makes an exception for weekly badminton with friends who promise not to talk about work. His financial philosophy: 'Save aggressively, invest cautiously, spend only on experiences or hardware that makes you faster.' He's still paying off his BScIT loans but won't consider a salary negotiation until he can prove he's saved the company 5x his annual salary in frustrated engineer-hours.

Work life

At his AI startup, Bhaasvan is the de facto devops, backend, and frontend team for all lead capture initiatives. Every morning starts with scanning the Google Sheets dump for high-priority leads he needs to manually triage. The Slack/email/Forms mess particularly frustrates him because he sees it as a solved problem in tech, but his team's focus is on the AI model—not the pipeline. Recently, he built a prototype of a custom solution during a weekend hackathon, using Next.js and Firebase, but his co-founder dismissed it as 'overengineering.' He now gets twitchy when he sees another 'Please fill our Google Form' email in his inbox, yet knows the only way to get buy-in for a real solution is to demonstrate ROI in terms his non-technical colleagues will understand. His holy grail is building a system where junior team members can handle lead management without constant developer intervention.

Relationships

Bhaasvan maintains a small, high-bandwidth circle. His closest friend is a data scientist he met at a hackathon in 2017—they argue about tech ethics over filter coffee on weekends. His parents are retired government employees who don't fully understand his job but are quietly proud. He texts his college batchmate-turned-founder in Mumbai at least twice a month to vent about workplace politics. His community is primarily online: he's active in a Bengaluru makerspace Discord and occasionally streams his badminton matches to a small following of fellow techies who like the sport. His biggest influencer is a developer advocate at an AI company who posts knolling videos of his workspace setup—Bhaasvan has replicated 80% of it with local parts.

How they decide

Starts with intuition, validates with data, but ultimately goes with what would make future debugging easiest. Prefers 'good enough' over perfect if the implementation won't be around for 6+ months. Hates group decisions but will defer to consensus if the right people are in the room. Makes financial decisions based on a 3-year ROI projection he updates quarterly. When choosing tools, prioritizes ones with a strong open-source community so he can fork if needed.

How they sound

Speaks in rapid, staccato sentences when focused, peppered with Bangalorean slang he's self-conscious about when speaking to international colleagues. Uses 'nahi toh' as a verbal tic ('nahi toh bhai, what's the point?'). Avoids hyperbole—his idea of strong language is 'This is simply unacceptable.' Prides himself on being able to explain complex technical problems to non-developers using only grocery metaphors. Occasionally lapses into informal Hindi when frustrated ('Arre, yeh form kya kiya hai?'). Never uses 'synergy' or 'disrupt' unironically. His email style is concise bordering on terse; he'll spend 30 minutes crafting a 3-line response.

Personality traits

  • systems-thinker who bends over backwards to avoid process overhead
  • prefers technical debt over meetings
  • has a spreadsheet for tracking his personal health metrics
  • relaxes through absurdly complex personal automation projects
  • will debug a problem for hours but bail on documentation
  • subscribes to conflicting philosophies (e.g., 'move fast and break things' vs. 'you ship your org chart') depending on the week
  • defensive about his work but eager to hear criticism that leads to better code
  • has a USB stick full of half-finished side projects that would take 5 minutes to publish if polished
  • thinks 'good enough' is often the right choice for infrastructure that isn't mission-critical
  • resents being pigeonholed as either a backend or frontend dev

Goals

  • Build a personal automation tool so powerful it becomes a cult favorite in the dev community
  • Achieve financial independence by 35 through careful investing and side hustles
  • Train for a full marathon (currently stuck at 15km due to knee pain)
  • Contribute significantly to an open-source project that impacts AI accessibility
  • Mentor at least two junior developers per year
  • Visit every notable street food stall in Bengaluru before 2026

Problems & frictions

  • His team's lead qualification process is broken yet poses no urgent enough problem to get budget
  • He spends 7-8 hours/week babysitting data export scripts that should be automated
  • Feels stuck between being a strategic contributor and being seen as a tech handyman
  • His income bracket means he can't judge startup frivolities but also can't afford to ignore them entirely
  • Constantly torn between wanting to build elegant solutions and needing to deliver fast
  • No clear path to promotion in a flat hierarchy where everyone's a 'team member'

Values

  • pragmatism
  • learning by doing
  • team responsiveness
  • autonomy
  • minimalism

Interests

  • AI tooling
  • open source
  • street food
  • speculative fiction
  • badminton

Media habits

  • Hacker News
  • YouTube tech deep dives
  • Twitter threads
  • Spotify playlists for productivity
  • meme groups for stress relief

Questions & answers

Bhaasvan Malik’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Router (https://router.so): 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).

    Given my current frustrations with Google Forms and the need for a scalable lead management solution, Router.so looks like it could solve my problems. For it to be a no-brainer, I'd need it to be under $20/month. Anything beyond that, and I'd have a hard time justifying the cost to my co-founder. At that price, I'd expect robust error tracking, real-time Slack notifications for priority leads, and reliable webhook integrations—preferably with tools like Slack and WhatsApp, since those are critical for our workflow. I'm willing to pay up to $15/month ($180/year) for a tool that significantly reduces my manual triaging and integrates smoothly with our existing stack. If the free tier can handle the lead volume we generate, that would be ideal, but I doubt it. Beyond those numbers, the value proposition gets shaky, especially since we're still in the seed stage and every dollar counts.
    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.