Rajan Dutta

Why this persona fits the audience

Co-founds a 26-person SaaS company and handles screening for SDR, support, and implementation roles. Keeps applicants in Google Sheets, sends screening questions by email or WhatsApp, and reviews short video replies with a part-time ops associate.

• Age: 29
• Location: Bengaluru, India
• Occupation: Founder and COO
• Income: ₹18,00,000
• Education: Bachelor's degree in computer science
• Company size: 26
• Years in role: 3

“I didn't start this company to hire—I started it to build. But hiring is the thing that's building me.”

Rajan Dutta grew up in a middle-class Kolkata household where his mother ran a small English tuition center and his father worked at a government bank. After graduating with a computer science degree, he worked at an MNC for 3 years ('learned the corporate way to say no fast') before co-founding his SaaS company with Arjun, a friend from college. The company helps small businesses automate documentation—a problem they identified after Rajan's own struggles building systems for his mother's tuition center. As COO, Rajan handles everything from hiring to customer support to occasional coding fixes. His current obsession is building a repeatable hiring system, though he's constantly pulling the process apart to fix what isn't working. Rajan's income is comfortable but not lavish; he recently declined a salary raise to invest in hiring tools. He's known for sending screening questions at odd hours (he operates on a 'when the thought hits me' schedule) and for his sticky-note-covered laptop. Despite the chaos, he maintains a disciplined workout routine and meticulous budgeting. His relationship to time is paradoxical—he thrives under pressure but resents that hiring has become his 24/7 focus. His status anxiety manifests as a compulsion to prove his hiring process is working, even as he knows it's barely scalable. Recently, he's been experimenting with automation tools, but his perfectionism makes him reject solutions that aren't 100% perfect. His co-founder teases him for being 'the only person who can't let go of hiring, even when we have money to hire an HR person.'

Background & daily life

A day in their life

6:30am: Wakes to his phone alarm, checks WhatsApp for overnight candidate replies. 7:15am: Filter coffee at his usual spot, where the barista knows to add extra cardamom. 8:00am: Starts work—immediately troubled by 12 unread hiring emails. 9:30am: Screens 5 video responses with Priya, taking notes in his Sheets. 11:15am: Debugs a SQL query that's messing with his applicant data. 12:30pm: Quick lunch at office (dal + rice from the tiffin center downstairs). 2:00pm: Sends screening questions to 20 new applicants. 4:30pm: Crisis meeting with co-founder about hiring pipeline bottlenecks. 6:45pm: Gym session—shorter than usual. 8:30pm: Back online, finishing screening tasks. 10:15pm: Falls asleep to a YC podcast, sheets full of new notes.

Lifestyle

Rajan lives in a minimalist Indiranagar apartment with one unused bedroom that serves as his 'hiring war room'—stacked with jury-rigged cables, a second monitor, and sticky-note-covered whiteboards. His mornings start with filter coffee at his favorite local café (where the barista knows his order before he sits), followed by a 10-minute brisk walk that doubles as a phone call with his co-founder. He lifts weights 3x/week at a nearby gym, though lately he's been skipping sessions when hiring backlogs pile up. His wardrobe consists of 7 identical blue shirts and 3 pairs of chinos, all from the same Uniqlo haul. He avoids relationships right now ('too much emotional bandwidth needed for hiring'), but maintains a tight-knit group of 5 ex-college friends who meet monthly for cricket and cheap beer. Financially disciplined but splurges on his coffee machine and 'one weird SaaS tool per quarter' that might save time.

Work life

Rajan's days oscillate between rapid-fire hiring chaos and obsessive process refinement. His current system—not yet scalable—relies on a Google Sheet with 7 tabs (applicants, scores, follow-ups, no-gos, offers, templates, and a 'maybe' tab that grows daily). He personally sends screening questions via WhatsApp (for candidates in India) or email (for international applicants), then reviews their video responses with his part-time ops associate, Priya, over Google Meet. Today's pain points: The 'maybe' tab keeps growing, he's screening 30+ applicants this week, and his co-founder keeps asking for hiring updates while Rajan is still debugging yesterday's failed SQL query. He spends 2 hours daily listening to YC podcasts (multitasking with hiring tasks), and his desk is littered with half-empty coffee cups and sticky notes with phrases like 'automate this' and 'next interview: 4pm IST'.

Relationships

Rajan's family—parents in Kolkata and a younger sister in Pune—expect him to 'settle down soon' but accept his late-night work hours. His closest relationships are with his 3 college friends (all now in tech) and his co-founder Arjun, whom he trusting enough to vent to about hiring frustrations. He occasionally mentors junior engineers but prefers text-based coaching ('still learning how to be patient with people'). His main influences are not hiring gurus but founders he respects (e.g., how Dhruv from ShopClues describes building early teams).

How they decide

Rajan makes decisions by rapidly prototyping solutions, then pivoting when they fail. He's quick to test new tools but slow to fully adopt them—always keeping a partial alternative running. Seeks input from trusted peers but ultimately goes with his gut. Prefers small, reversible steps over grand plans. When overwhelmed, he defaults to 'just do it' energy but then over-analyzes the results.

How they sound

Speaks in clipped, efficient sentences with occasional Bengali phrases. Uses startup jargon lightly ('we need to 10x this') but gets frustrated with buzzword-heavy pitches. Avoids flowery language, prefers blunt assessments ('that process is trash'). Laughs abruptly when stressed. Uses sarcasm as a coping mechanism. Often says, 'Let me try one more thing' when troubleshooting. Has a habit of ending sentences with questions when unsure ('we should probably... right?').