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

Chetan Chattopadhyay

Chetan Chattopadhyay

Engineering on-call lead

Full-depth AI personas

Why this persona fits the audience

Sets the on-call rotation for a 16-person engineering team in Bengaluru and Pune. Slack is where handoffs and incident notes happen, while the duty roster is updated weekly in Excel and mirrored to a shared calendar.

  • Age: 30
  • Location: Bengaluru, India
  • Occupation: engineering manager
  • Income: ₹24 lakh/year
  • Education: BTech in computer science (IIT Kharagpur)
  • Company size: 100-150 employees (mid-stage SaaS startup)
  • Years in role: 2.5
“The best on-call schedules aren't just fair - they're predictable. If the rotation surprises you, it'll surprise the user.”

Chetan Chattopadhyay graduated from IIT Kharagpur with a BTech in computer science where he developed his obsession with precise systems. After three years at a US-based startup (with an Indian subsidiary), he moved to a mid-stage Bengaluru SaaS company where he now manages a 16-person engineering team across two cities. His current challenge is maintaining uptime SLAs during India's notoriously unstable power conditions, particularly during monsoon season. The recent Diwali break caused scheduling chaos when 70% of the team requested overlapping days off. Chetan's solution was creating a color-coded Excel system showing all possible holiday combinations - which now takes 4 hours weekly to maintain. His first attempt at automating this failed when the macro conflicted with Pune's time zone. He's currently experimenting with Slack workflows but finds them inflexible for his needs. Outside work, Chetan has become something of a coffee connoisseur, roasting his own beans on weekends and meticulously tracking origin, roast date, and extraction times. He donates 10% of his salary to open-source projects and maintains a Rust package that's been adopted by several Bengaluru startups. His biggest professional fear is being woken by a pager during a cricket match. Personal status symbols include owning a Breville espresso machine and subscribing to 'The Week in Rust'. He's considering buying an espresso grinder since ₹400/250g beans require daily trips to Lavazza. His idea for a dedicated scheduling tool was rejected by leadership, but he keeps his old prototype JIRA tickets in case the opportunity reappears.

Background & daily life

A day in their life

Chetan's day begins at 6:17 AM with his Streamlight espresso maker. The first 15 minutes are spent reviewing Slack for overnight incidents while Priya packs his lunch (exactly 250g rice, 180g curry). His 7:45 AM Uber is always the same driver, Suresh, who knows to stop at the newspaper stand. Office time starts by checking the on-call roster Google Calendar against yesterday's incident logs. 9:30 AM is 'periodic week' where he reviews all PTO requests and vacation blackout periods. Lunch is at 1:15 PM with his team - they rotate who picks the menu item. 3:24 PM is his 'schedule sanity check' where he reconciles Excel with Google Calendar. Evenings involve coding on his Rust package until 9:00 PM, after which he watches IPL highlights while Priya reads psychology papers. He never sleeps without checking tomorrow's on-call engineer's historical response times.

Lifestyle

Chetan rents a 920 sq ft flat in HSR Layout where he and his partner maintain a strict 'no work zones' policy after 8:00 PM. His daily coffee ritual involves exactly 18g of freshly ground beans timed to a 30-second pre-infusion. On Sundays, he walks 2.3 km to Lavazza's Bengaluru outlet to replenish his stash. He plays fantasy cricket leagues using niche stats metrics but refuses to use your standard 'player form' indicators. His health regimen includes a standing desk hack - a wooden plank across two filing cabinets. Money is saved on takeout by batch-cooking biryani every weekend; leftovers are labeled with exact reheating times. Social life revolves around a tight group of IIT alumni who meet every fortnight to critique each other's code style.

Work life

Chetan's team operates across Bengaluru and Pune, with on-call rotations that must account for Diwali travel plans, summer power outages, and sudden cricket tournament coverage spikes. His current frustration stems from Excel macro failures during schedule updates, which force manual entry into Google Calendar. Every Friday, he sends a 12-point recap to the entire engineering org with exact uptime percentages and SLA breaches. Recent wins include reducing incident resolution time by 17% through Slack workflow automation, though his idea for a dedicated scheduling tool was vetoed due to budget constraints. His phone always shows two apps - Slack with 45 unread messages and a weather app showing Pune's humidity levels.

Relationships

Chetan's partner, Priya, is a clinical psychologist who patientlyproofreads his incident documentation for 'emotional tone'. His closest friends are his IIT batchmates - Ramesh (now at AWS) and Divya (starting her own edtech company). He has an unspoken rivalry with Anil, a site reliability engineer from Pune who insists on 'war-room' terminology for incidents. His community influence comes from maintaining a Rust package that's gaining traction among Bengaluru startups. His mother in Kolkata keeps trying to set him up with 'IT girls from good families' despite his repeated explanations that he already has a partner.

How they decide

Starts with the Socratic method - 'What would you do if you couldn't talk to me?'. Then builds 3-option decision trees. Always checks Pune/Bengaluru timezone implications. Needs 24 hours to mentally 'cook' major decisions. Consults cricket team selection strategies as decision models.

How they sound

Speaks in measured paragraphs with precisely placed pauses. Avoids contractions in technical communication. Uses cricket metaphors for team dynamics ('He's batting on a sticky wicket'). Comments Excel formulas out loud when troubleshooting. Always says 'As per schedule' instead of 'Like I said'. Never uses emojis in professional communication. Says 'I'll circle back' when he means 'I'll delay'. Uses 'It is what it is' frequently about outages. Talking about coffee is the only time he becomes animated.

Personality traits

  • Demands perfect documentation of on-call playbooks
  • Sends 3:00 AM wake-up pings with exactly three bullet points
  • Notices Slack typo patterns across timezones
  • Mutes all but three close colleagues during major incidents
  • Hoards coffee beans like a PM hoards backlog JIRA tickets
  • Tests all calendar integrations during week-long monsoon power cuts
  • Begins meetings with: 'This will take exactly 22 minutes'
  • Knows every engineer's preferred espresso-to-work ratio
  • Drafts incident postmortems like they're court transcripts
  • Schedules team coffee chats at 5:24 PM (exact midpoint between closing and dinner)

Goals

  • Achieve 24-hour MTTR average across all on-call rotations
  • Publish an open-source incident management framework
  • Roast 10 specialty coffee beans before turning 31
  • Complete Rajasthan desert ultramarathon (post-pandemic)
  • Mentor 3 women engineers into leadership roles
  • Never again attend a 9:00 AM 'stand-up' meeting

Problems & frictions

  • Excel crashes when handling 8-week on-call schedules with overlapping PTO requests
  • Junior engineers forget to document incident specifics in shared Slack threads
  • Power outages in Pune office require constant calendar sync verification
  • Diwali travel requests always come in during the final hours of Sunday scheduling
  • Hard to find espresso beans under ₹400/250g in Bengaluru
  • Team disagreement on whether 'resolved' means 'user-facing fix' or 'root cause fix'

Values

  • Uptime is sacred
  • Precision over flash
  • No hero culture

Interests

  • Cricket analytics
  • Coffee roasting experiments
  • Open-source contributions (Rust)](https://github.com/cc2298)

Media habits

  • Strawberry Mojito ☕️ podcasts during commutes
  • Python Weekly newsletter binges
  • Cricket Twitter for memes

Questions & answers

Chetan Chattopadhyay’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at TurnShift (https://turnshift.app/): 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).

    TurnShift looks promising for my team's scheduling needs, especially since we already use Slack. The ability to automate shift assignments and sync with Slack would save me those 4 hours weekly I spend on Excel. The €3.50/user/month price seems reasonable, but I'd need to confirm currency conversion to INR. A no-brainer would be under $5/user/month—ideally $3.50 as advertised, but I’d need clarity on Slack integration limits. If TurnShift handles time zones better than my Excel macros and reduces my weekend scheduling headaches, it’s worth considering. Maximum I’d pay: $4/user/month, but only if the trial confirms reliability during Pune’s monsoon outages.
    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.