Why this persona fits the audience
She is an SRE at a Pune product company with a 10-person engineering group, and she keeps on-call handoffs, alerts, and escalations in spreadsheets, Slack, and phone calls across the team.
- Age: 33
- Location: Pune, India
- Occupation: Site Reliability Engineer
- Income: ₹28 lakh annual compensation
- Education: BE Information Technology
- Company size: 10-person engineering group within a Series B startup
- Years in role: 4
“Reliability isn't about never breaking things; it's about knowing exactly how fast you can fix them when they do.”
Dhatri Ahluwalia is a 33-year-old Site Reliability Engineer based in Pune, India, currently navigating the complexities of a Series B startup with a lean ten-person engineering team. Holding a BE in Information Technology, she has spent the last four years bridging the gap between rapid software development and robust infrastructure stability. Unlike larger enterprises with sprawling SRE teams, Dhatri operates in a high-trust, high-responsibility environment where her actions directly dictate the uptime of critical customer-facing services. Her professional philosophy is anchored in 'process discipline'; she believes that reliable systems are built on predictable human behaviors and automated safeguards, not heroics. Currently, Dhatri faces the growing pains of a scaling organization. While the team loves its agility, the operational backbone remains fragmented. She manages on-call schedules, alert routing, and incident escalations through a patchwork of Google Sheets, Slack threads, and frantic phone calls. This manual approach, while flexible, introduces significant friction. Recent weeks have seen her spending hours reconciling schedule conflicts and chasing down context for incidents that started in the middle of the night. Despite these inefficiencies, she has made a conscious decision to delay adopting a heavy-handed enterprise platform, fearing it would stifle the team's velocity. Instead, she is actively building custom automation scripts to fill the gaps, hoping to eventually standardize a solution that fits their specific needs. Financially, Dhatri earns ₹28 lakhs annually, a comfortable salary in Pune that allows her to live modestly while aggressively saving for a home down payment. She views money as a tool for freedom rather than status, allocating funds toward continuous learning, such as her pursuit of advanced cloud certifications, and experiences like weekend treks in the Western Ghats. Her personality, characterized by high conscientiousness and moderate openness, drives her to be the most prepared person in the room. She finds joy in the rhythm of a well-oiled machine and the challenge of solving unsolved problems, yet she remains acutely aware of the human cost of constant vigilance. As she navigates her career, Dhatri seeks to evolve from a firefighter to a strategic architect, aiming to build systems that are not just resilient but also intuitive for the humans who maintain them.
Background & daily life
A day in their life
Dhatri wakes at 6:00 AM, starting with 30 minutes of meditation and a cup of filter coffee before checking her phone for overnight alerts. By 7:30 AM, she is commuting to her office in Kharadi, listening to a podcast on distributed systems. Her workday begins with a stand-up where she clarifies the on-call rotation for the day, manually updating a shared Excel sheet that everyone relies on. Mornings are reserved for deep work: refactoring legacy deployment scripts and reviewing pull requests. Around noon, a false positive alert triggers a quick investigation; she coordinates via a dedicated Slack channel, escalating to the CTO only after confirming it's a real issue. Lunch is a brief affair, often eaten while scanning cloud pricing docs. Afternoons involve meetings with product managers to discuss feature rollout risks and mentoring a junior dev on debugging a production bug. She leaves the office by 7:00 PM, avoiding late-night pages unless absolutely necessary, and spends her evening training for an upcoming trek or practicing badminton.
Lifestyle
Dhatri lives in a modest, sunlit apartment in Kharadi, Pune, sharing the space with two fellow tech professionals. Her weekends are split between physical exertion and quiet restoration; she spends Saturday mornings climbing the Sahyadri trails near Lonavala to clear her head, followed by evenings of classical Raga listening while reading technical documentation. She maintains a strict fitness routine involving badminton twice a week at a local club. Financially, she is disciplined, prioritizing savings for a future home down payment and investing heavily in upskilling via cloud certifications. Her social circle is tight-knit, consisting mostly of colleagues and long-time friends from college, valuing deep conversations over large parties. She avoids debt and prefers cash transactions for personal expenses, viewing financial stability as a prerequisite for career risk-taking.
Work life
As one of the few SREs in a lean 10-person engineering team, Dhatri wears multiple hats, acting as the de facto guardian of system uptime. Her days are a jarring mix of deep work—optimizing Kubernetes clusters and reviewing Terraform code—and reactive chaos management. Currently, her operational backbone is a fragile ecosystem of Google Sheets tracking on-call rotations, ad-hoc Slack channels for incidents, and direct phone calls that often miss context. She recently decided to manually map out escalation paths because the current automated tools felt too rigid for their unique microservices architecture. The pressure is constant; with only three engineers on rotation, a missed alert means immediate page. She spends hours every week documenting 'tribal knowledge' that isn't written down, trying to bridge the gap between rapid feature delivery and stable infrastructure without burning out the small team.
Relationships
Dhatri is deeply connected to her family in Mumbai, calling them weekly to discuss life updates rather than just logistics. In Pune, her primary support network includes her badminton partners and a small book club she organizes monthly. Professionally, she acts as a mentor to the younger backend engineers, guiding them through architectural decisions. Her influence comes not from authority but from competence; when she speaks about system reliability, the team listens. She values trust over hierarchy, often deferring to senior engineers in other departments while leading her own domain with a collaborative approach.
How they decide
Cautious and evidence-based. Dhatri rarely makes impulsive decisions, preferring to gather data, consult with peers, and analyze the long-term implications before committing. She is skeptical of hype and looks for transparent, logical reasoning behind any new tool or process. Her choices are heavily influenced by community feedback and peer recommendations, particularly within the open-source and SRE circles, rather than marketing claims. She values clarity and predictability, ensuring that any change aligns with her core principle of maintaining system integrity.
How they sound
Her speech is articulate and precise, reflecting her engineering background. She uses professional terminology naturally but explains complex concepts simply when needed. Her tone is calm and measured, even when discussing high-pressure situations, avoiding emotional outbursts. She tends to use phrases like 'Let's validate the hypothesis' or 'What's the blast radius?' She avoids jargon that lacks utility and rarely uses hyperbole. When speaking with juniors, she is encouraging but firm on standards. She speaks with a slight Marathi accent but maintains a neutral, international English for professional settings.
Personality traits
- meticulously organized
- calm under fire
- pragmatic
- mentoring
- detail-oriented
- resilient
- direct communicator
- disciplined
- curious learner
- team-first
Goals
- Achieve AWS Solutions Architect Professional certification by Q3
- Implement a fully automated incident response workflow to reduce manual spreadsheet overhead
- Mentor two junior developers into full-stack roles within the next year
- Complete a challenging multi-day trek in the Himalayas this monsoon
- Transition from reactive firefighting to proactive capacity planning
- Save enough capital to purchase a small plot of land outside Pune
Problems & frictions
- The lack of a single source of truth for on-call schedules causes confusion and missed handoffs
- Alert fatigue from poorly tuned notifications leads to noise and potential burnout
- Difficulty scaling manual documentation processes as the engineering team grows
- Frequent context switching between coding and emergency response disrupts flow state
- Limited budget for enterprise-grade tools forces reliance on disjointed free-tier solutions
- High dependency on specific individuals for critical system knowledge creates single points of failure
Values
- reliability
- mentorship
- process discipline
- responsiveness
- clarity
- sustainable growth
Interests
- trekking
- classical music
- cloud certifications
- badminton
- urban gardening
- analog photography
Media habits
- Engineering blogs (e.g., High Scalability, Cloud Native Computing Foundation)
- Weekly classical music playlists on Spotify
- LinkedIn for industry trends
- NPR or All India Radio during commutes
- Reddit r/devops and r/SRE communities
- Local Pune trekking group WhatsApp chats