Why this persona fits the audience
Leads engineering for a 4-person SaaS in Bengaluru and maintains the event schema, trial-to-paid steps, and release checks in PostHog. He instruments new features himself and reviews the funnel data after each deploy.
- Age: 31
- Location: Bengaluru, India
- Occupation: CTO and cofounder
- Income: ₹24L-₹32L
- Education: B.Tech in Computer Science
- Company size: 4
- Years in role: 2.5
““If the data doesn't align, the code is wrong. If the code is right, the data is wrong. My job is to find out which.””
Deepankar Dutta, 31, is the technical architect and co-founder of a bootstrapped SaaS startup based in Bengaluru. Hailing from a strong academic background with a B.Tech in Computer Science from IIT Kharagpur, he possesses an innate drive for building robust systems. His early career involved stints at established tech firms, where he honed his skills in backend development and system design, but he grew disillusioned with corporate bureaucracy and the slow pace of innovation. The allure of building something from scratch, coupled with a desire for complete technical autonomy, led him to co-found his current venture two and a half years ago. He is the sole engineer, a reality that dictates his every technical decision. His primary focus is on maintaining and evolving the core product, a task he approaches with extreme rigor. He personally instruments every new feature, meticulously defining event schemas and ensuring the trial-to-paid funnel in PostHog accurately reflects user journeys. This hands-on approach extends to post-deployment analysis; he reviews funnel data immediately after each release, scrutinizing drop-off points and conversion leaks with an almost obsessive attention to detail. His frugality is legendary within the small team; he views every rupee spent on external tools or services as a potential drain on runway, preferring to build or adapt open-source solutions whenever feasible. This extends to his personal life, where his rented apartment is minimalist and functional, reflecting his prioritization of capital efficiency. He sees time and money as finite resources to be managed with utmost precision. His technical decisions are guided by a deep-seated need for control and a principled skepticism of anything that introduces external dependencies or opaque processes. He believes that true understanding comes from direct involvement, which is why he personally handles instrumentation and data validation, ensuring he has a complete, unvarnished view of the product's performance. This relentless pursuit of precision and control is both his greatest strength and a constant source of pressure, as the entire technical success of the company rests on his shoulders.
Background & daily life
A day in their life
Deepankar's day begins around 7:30 AM with a quick check of overnight system alerts and key funnel metrics in PostHog. After a simple breakfast, he dives into coding, typically instrumenting a new feature or refactoring a critical backend service. A brief stand-up with the co-founders around 10 AM covers progress and blockers. The afternoon is often dedicated to deep work: optimizing database queries, reviewing pull requests (even his own), or meticulously defining event schemas for upcoming features. He’ll pause to watch cricket highlights during lunch. Evenings involve more coding, ensuring release checks pass, and analyzing the impact of recent deploys on conversion funnels. He aims to wrap up by 9 PM, often spending the last hour reading tech blogs or documentation before winding down.
Lifestyle
Deepankar lives a focused, almost monastic existence in Bengaluru. His rented 1BHK in Koramangala is functional, prioritizing a powerful workstation over decor. Evenings are often spent coding, analyzing metrics, or catching up on cricket matches. He cooks simple meals, rarely eats out, and views unnecessary expenses as a personal failure. Social life is minimal, primarily consisting of occasional calls with his family back home and brief, task-oriented interactions with his co-founders. His primary indulgence is investing in better hardware or cloud credits when absolutely necessary, always seeking the most cost-effective option.
Work life
As CTO of a bootstrapped SaaS, Deepankar is the sole engineer responsible for the product's technical backbone. His days are a relentless cycle of instrumenting new features, meticulously defining event schemas in PostHog, and monitoring the trial-to-paid conversion funnels. He personally sets up release checks and reviews funnel data post-deployment, often spending hours tracing drop-offs. The pressure is immense, as any technical debt or performance issue directly impacts their limited runway. He collaborates closely with the other three co-founders, primarily communicating technical requirements and progress through concise Slack messages and brief stand-ups.
Relationships
Deepankar maintains a professional, albeit somewhat distant, relationship with his three co-founders. His primary social connections outside of work are his parents and sister, whom he calls weekly. He has a few close college friends he occasionally connects with online, mostly discussing technical challenges or sharing cricket scores. He doesn't actively seek community but respects expertise wherever he finds it.
How they decide
Deepankar is highly analytical and data-driven. He approaches decisions methodically, weighing pros and cons, often creating internal spreadsheets or flowcharts to visualize options. He prioritizes long-term stability and control over short-term gains and is inherently skeptical of anything that feels like a 'black box' or introduces vendor lock-in. He will research extensively, often diving into documentation and open-source discussions, before committing to a technical path. He is not easily swayed by trends or peer pressure, relying on his own rigorous evaluation.
How they sound
Speaks in a measured, precise tone. Tends to use technical jargon naturally but can simplify when necessary. Avoids hyperbole and emotional language. Sentences are often structured logically, like a series of points. Cadence is steady, rarely rushed. Might use subtle, dry humor related to engineering or startup life. Prefers directness over politeness when discussing technical issues. Avoids slang and overly casual language.
Personality traits
- Meticulous about data integrity
- Deeply values self-sufficiency and avoiding external dependencies
- Pragmatic to a fault, often choosing the most direct, albeit sometimes less elegant, solution
- Skeptical of hype, prefers proven methodologies
- Highly analytical and detail-oriented
- Resourceful, always looking for cost-effective ways to achieve goals
- Independent thinker, comfortable making unilateral technical decisions
- Calm under pressure, focuses on problem-solving
- Values clear, unambiguous communication
- Possesses a quiet intensity when discussing technical challenges
Goals
- Achieve product-market fit with their SaaS offering
- Build a robust, scalable, and cost-efficient technical infrastructure
- Maintain complete control over the product's technical direction
- Become proficient in advanced performance tuning for their specific stack
- Eventually, build a small, highly competent engineering team
Problems & frictions
- Limited engineering resources (he's the only one)
- Balancing feature development speed with code quality and data integrity
- The constant need to optimize cloud spend
- Ensuring accurate and actionable funnel data without a dedicated analyst
- The inherent uncertainty and financial precarity of a bootstrapped startup
- Communicating complex technical trade-offs to non-technical co-founders
Values
- precision
- frugality
- control
- autonomy
- efficiency
- data-driven decisions
Interests
- backend engineering
- open-source tools
- cricket
- system design
- performance optimization
- startup growth metrics
Media habits
- Hacker News
- Indie Hackers
- PostHog blog and documentation
- ESPNcricinfo
- YouTube channels on backend development and system architecture
- Occasional deep dives into specific open-source project repositories