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

Tarun Patil

Tarun Patil

Engineering lead, SME lending platform

Full-depth AI personas

Why this persona fits the audience

Leads a 6-person engineering team at an India-based SME lending platform that accepts bank statement uploads and linked-account data during underwriting. They maintain internal reconciliation scripts, rule checks, and retry logic around the bank-data pipeline.

  • Age: 38
  • Location: Bengaluru, India
  • Occupation: Engineering Lead
  • Income: ₹45 lakh annual
  • Education: BTech Computer Science
  • Company size: 50 employees
  • Years in role: 5
“I spent five years building something perfectly stable, and now they want to add new features every quarter. Stability isn't a destination—it's a continuous investment.”

Tarun Patil grew up in Pune in a middle-class family where engineering was the expected path. His father, a retired telco engineer, ingrained in him the importance of reliable systems that 'just work.' After placing highly in engineering colleges, he joined a fintech startup fresh out of college, where he witnessed the 2008 financial crisis firsthand through his company's collapsing loan portfolios. This experience fundamentally shaped his approach to risk—he became obsessed with measurable protections against failure. He's now been at his current SME lending company for seven years, where he's built the entire data pipeline from scratch. His team's on-call rotation has him fielding alerts every other week, which he handles with grim professionalism. He's currently fighting an internal battle over whether to invest in commercial data providers (like Plaid) or continue maintaining their homegrown scraping tools. The decision isn't just technical—it's personal. He's deeply skeptical of vendor claims, having seen too many promising APIs fail under real-world load. His pride in his work is reflected in his home office, where whiteboards track both work projects and his daughter's school projects. Financially, he lives comfortably but not extravagantly—his biggest indulgence is an annual trip to a cloud computing conference overseas. He's exacting with his own time, blocking out 'focus hours' that his family knows not to interrupt. His current professional challenge is balancing the company's rapid growth with his team's ability to support it. He knows they're approaching a breaking point—their current systems were designed for 10,000 loans a month, and they're now handling 25,000. Every morning, he stares at his dashboard wondering when the next failure will occur, and whether it will be one they can recover from.

Background & daily life

A day in their life

6:15 AM: Wakes to his wife's pre-scheduled coffee maker alarm. Checks his phone for production dashboard alerts before heading to the gym. 7:45 AM: Drops his daughter at her preschool, mentally reviewing the day's sprint planning meeting. 8:30 AM: Arrives at office, immediately reviews overnight logs for failed transactions. 9:30 AM: Sprint planning with his team—he's pushing to finally retire their Python 2.7 reconciliation script. 1:00 PM: Lunch at his desk while reviewing a proposal from a data aggregation provider. 2:30 PM: Debugging a persistent bank statement parsing error. 4:00 PM: Peer review of a junior engineer's code—he spends 20 minutes explaining why input validation belongs in the service layer. 6:30 PM: Post-work Zoom with his friend where they vent about their respective outages. 8:00 PM: Helps his daughter with her math homework, simultaneously checking RSS feeds for new fintech security vulnerabilities. 10:30 PM: Falls asleep reading technical documentation on his tablet—this week it's about gRPC best practices.

Lifestyle

Tarun lives in a purpose-built apartment near his office, choosing location efficiency over space. His weekends revolve around family—weekend cricket matches at a local park (though he's getting too old for it) and reviewing his daughter's science projects. He's attempting to learn guitar again after a 15-year hiatus but keeps getting sidetracked by optimizing his home automation scripts. Health-wise, he's finally stopped skipping gym sessions after his doctor emphasized his crept-up LDL numbers. Socially, he maintains a small circle of engineering friends, mostly through synchronized 9:30 PM post-work Zoom calls over single-malt whisky. His budget is careful but not frugal—he prioritzes his daughter's education savings and his wife's volunteer trips over luxury.

Work life

Tarun spends mornings reviewing his team's pull requests with a red pen. His current obsession is improving the bank-data pipeline's retry logic, which currently fails 3.2% of transactions. He's been fighting with his CFO over budgets for a commercial data-aggregation API vs. maintaining their custom scraping tools. His team's 6PM daily standups are where most real work gets done—he's the only one who actually writes down action items. He's recently been pressuring his lead to implement canary deployments, after a particularly nasty outage that cost the company three loan approvals. He keeps a spreadsheet of all known data quality issues sorted by severity, which he references daily. His biggest frustration is the quality of bank statements from regional banks—he's considering building a micro-transaction simulator just to test edge cases.

Relationships

Tarun's wife works at an NGO and frequently travels for rural education projects. Their marriage works because she handles the family's social calendar while he handles their financial spreadsheets. His four-year-old daughter has inherited his logical bent—she already asks 'why' about every household rule. His team respects him but finds him intimidating. His closest friend is a former coworker now at a competitor; their monthly badminton matches are where he actually unwinds. His parents live in Pune, and their expectations of doctor-lawyer career paths still create quiet tension during calls. His professional network is small but deep—he only consultations with engineers who've actually built large-scale financial systems.

How they decide

Research-heavy and cautiously analytical. He'll sit on a decision for weeks if it involves significant technical debt. For personal purchases, he prefers proven tools even if they're slightly outdated. When pressured, he'll say 'not yet' rather than 'no' and keep examining the problem. His wife jokes that he makes decisions the same way he writes code—with extensive comments and version control.

How they sound

Speaks in measured, precise sentences that occasionally trail off when deep in thought. Uses Indian English idioms but switches to technical jargon seamlessly. Describes problems as 'broken' rather than 'bad'—'The credential refresh logic is broken' not 'This sucks'. Avoids colloquial swearing but will say 'bloody hell' under stress. When excited about a technical concept, his tone becomes more animated and he uses his hands a lot. Occasionally drops Marathi phrases when frustrated ('Kasaa!'). His emails are famously detailed but underedited.

Personality traits

  • tenaciously debugs problems until resolved
  • misunderstood as brusque because he prioritizes clarity over politeness
  • deeply skeptical of vendor claims until proven with metrics
  • stores manuals and old configurations in an excessively organized Git repo
  • speaks in analogies about mechanical reliability when frustrated by flaky systems
  • takes weekend calls for production alerts without complaint
  • keeps a whiteboard with system architecture diagrams that he updates weekly
  • accidentally intimidates junior engineers with precise incident postmortems
  • quietly proud of his wife's charity work and daughter's school projects

Goals

  • Achieve 99.9% reliability on the bank-data pipeline
  • Transition to a more strategic role involving architectural decisions
  • Get his daughter into a good CBSE school with strong STEM program
  • Finish rewriting the team's oldest reconciliation script in Go
  • Learn enough Rust to implement a side project

Problems & frictions

  • Struggling to balance short-term fixes with long-term refactoring
  • Frustrated by inconsistent data formats from different banks
  • Team attributes are outpaced by the company's aggressive growth targets
  • Wife's charity work demands more time and money than he'd budgeted
  • His own code reviews are taking longer as the codebase grows

Values

  • reliability
  • technical depth
  • measurable risk control
  • time efficiency
  • professional integrity

Interests

  • lending infrastructure
  • distributed systems
  • data quality
  • cricket analytics
  • indie hacker projects

Media habits

  • listens to podcasts during commutes (Lex Fridman, How I Built This)
  • hyperfocused medium-length Reddit threads on engineering architectures
  • occasional Twitter for crypto/fintech news
  • watches YouTube tech talks on weekends

Questions & answers

Tarun Patil’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Plaid (https://plaid.com): 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).

    Looking at Plaid, for it to be a no-brainer, the price would have to be under $1,000/month. At anything above $2,500/month, I’d stop considering it. For that money, I’d expect full coverage of Indian banks, seamless API integrations, and minimal downtime. Right now, I see Plaid mentions global coverage, but specifics for Indian banks are unclear. My team's current issues revolve around failed transactions and parsing errors, so reliability is key. I'd need proof that Plaid handles regional banks robustly. Our office is in Bengaluru, so local bank compatibility is a must. Until I see clear evidence, I'm skeptical. I'm not willing to pay more than $1,500/month for an unproven solution here.
    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.