Divjot Mishra

Why this persona fits the audience

Co-founded a 14-person AI startup in Hyderabad with 6 contractors in the US and UK; he oversees offer letters, contractor milestones, and payment tracking through Google Sheets, Slack threads, and ad hoc bank transfers.

• Age: 34
• Location: Hyderabad, India
• Occupation: CTO & Co-founder
• Income: ₹30,00,000
• Education: MTech in Computer Science
• Company size: 14 employees (8 full-time in-house, 6 global contractors)
• Years in role: 2.5 years

“I don't care how many lines of code we write if the payroll system forces me to spend my Saturday fixing spreadsheets instead of shipping features.”

Divjot Mishra, 34, is the CTO and co-founder of a burgeoning AI startup headquartered in Hyderabad, India. With an M.Tech in Computer Science from a prestigious local institute, he pivoted from a role as a senior backend engineer at a major fintech firm to founding his own venture two and a half years ago. Driven by a belief in 'technical leverage,' Divjot architected a product that leverages open-source models to solve niche enterprise problems, aiming to scale rapidly without the burden of a bloated workforce. This philosophy led to a unique organizational structure: a core team of eight full-time engineers in Hyderabad supported by six specialized contractors in the US and UK. Currently, Divjot finds himself trapped in the paradox of being a technical leader bogged down by administrative logistics. While his team builds sophisticated algorithms, he personally manages the entire contractor lifecycle—from drafting offer letters and negotiating rates to tracking milestone deliveries via a fragile, color-coded Google Sheet. His recent decision to switch from a manual bank transfer system to a more structured accounting approach was driven by a near-miss with a tax compliance issue involving a UK-based consultant. He is deeply skeptical of 'all-in-one' platforms that promise simplicity but demand heavy customization, preferring tools that integrate seamlessly with his existing stack of Slack, GitHub, and Google Workspace. Despite earning a comfortable income of ₹30 lakhs annually, Divjot views his time as the scarcest resource, constantly calculating whether a new tool saves him more hours than it costs to learn. He operates with a quiet intensity, balancing the high-stakes pressure of fundraising with the granular details of ensuring every contractor gets paid on time, all while trying to remain a hands-on coder.

Background & daily life

A day in their life

Divjot wakes up at 5:15 AM for a quick run, returning by 6:45 AM to shower and prepare breakfast for Aanya. By 8:30 AM, he is commuting to the office, listening to a podcast on distributed team dynamics. At 9:30 AM, he attends a standup with his in-house team, followed by deep work on the AI architecture. Around 1:00 PM, he tackles the 'boring stuff': reviewing a contractor's milestone submission from a developer in Austin, cross-referencing it against the Google Sheet, and sending a payment request via bank transfer. After lunch, he joins a video call with the UK team to discuss API latency issues. The afternoon is spent debugging a deployment pipeline and drafting a new NDA template for a prospective freelancer. He leaves the office around 7:30 PM, stops by the gym briefly, and returns home to help with bedtime routines. Once Aanya is asleep, he spends another hour checking emails from the US team before finally closing his laptop at 11:00 PM.

Lifestyle

Divjot lives in a modern, high-rise apartment in HITEC City with his wife, Priya, and their two-year-old daughter, Aanya. Their home is a mix of domestic warmth and office utility, often featuring a second monitor on the dining table used for late-night coding or contract reviews. His routine is rigid: morning runs at 5:30 AM followed by school drop-off, then a long commute where he consumes audiobooks on behavioral psychology. Evenings are split between family dinner and reviewing global team standups that occur early in the US evening. He is health-conscious, avoiding alcohol to maintain cognitive sharpness, and manages finances with a spreadsheet-based budget that tracks both personal savings and company burn rate. Socially, he keeps a tight circle of fellow founders in Hyderabad's startup ecosystem, preferring deep one-on-one coffee chats over large networking events.

Work life

As CTO, Divjot spends his days juggling architectural strategy with the mundane friction of managing six contractors spread across London, New York, and Austin. His primary workspace is a dual-monitor setup where he switches between GitHub, Jira, and a complex, color-coded Google Sheet that serves as his single source of truth for contractor deliverables. He is currently manually reconciling invoice discrepancies with three different US-based freelancers, a task that eats into his product development time. The pressure stems from the need to move fast while ensuring every contractor milestone is documented to avoid future legal headaches. He relies heavily on Slack for asynchronous communication, often staying online until midnight to align with US stakeholders. His coworkers are a mix of junior Indian engineers he mentors and senior external contractors he rarely meets face-to-face.

Relationships

Divjot is married to Priya, a marketing manager who provides the emotional anchor and practical reality check for his ambitious ventures. They rely on Priya's mother for childcare support twice a week. Professionally, he maintains a close mentorship bond with his non-technical co-founder, Anjali, who handles business development, though they occasionally clash on resource allocation. He has a loose network of five other Hyderabad-based CTOs with whom he shares 'war stories' about scaling issues, meeting monthly for dinner. He feels most influenced by successful ex-industry leaders who prioritized lean operations over rapid, unfunded growth.

How they decide

Divjot approaches decisions with a 'build or buy' analysis framework, heavily weighted toward 'build' if the solution is simple enough to be coded in a weekend. He is research-heavy, reading documentation and case studies extensively before committing to any workflow change. However, once a decision is made based on data, he executes with speed and expects immediate adoption. He is peer-influenced but only by those he trusts technically, often seeking validation from his small founder circle before adopting a new tool. He avoids impulsive purchases, preferring free trials or pilot programs, but will pay immediately if the ROI is clear and the implementation friction is low.

How they sound

His speech is precise and direct, favoring technical terminology and efficiency. He speaks with a mild Telugu accent but adopts standard English in professional settings, often using phrases like 'let's unblock this' or 'is there a dependency?' He avoids vague promises and prefers concrete timelines. In casual conversation, he might use startup slang like 'bandwidth' or 'tech debt,' but generally avoids overly corporate jargon. He tends to pause briefly to formulate thoughts rather than rambling, and he rarely raises his voice, even when frustrated by operational inefficiencies.