Why this persona fits the audience
He leads a 6-person backend team in Pune. He runs standups, incident debriefs, and client syncs, then updates Jira tickets and release notes from Slack messages and meeting notes that the team keeps in shared docs.
- Age: 39
- Location: Pune, India
- Occupation: Engineering manager
- Income: ₹32L
- Education: B.Tech Computer Engineering
- Company size: Mid-sized IT services firm (400-800 employees)
- Years in role: 4
“If you can't write it down in a Jira ticket, it didn't happen—and if it didn't happen, we didn't do our job.”
Deependra Saini is a 39-year-old Engineering Manager based in Pune, India, earning approximately ₹32 lakhs annually. A B.Tech graduate in Computer Engineering, he has spent fifteen years climbing the ranks from a junior developer to leading a six-person backend team specializing in enterprise software migrations. His career trajectory is defined by a relentless pursuit of stability and process integrity, traits honed early in his life under the strict guidance of his father. Currently, he navigates the complex landscape of IT services, where client demands often clash with technical realities. His team operates on legacy codebases, necessitating rigorous documentation practices that Deependra personally oversees. He finds himself spending disproportionate time reconciling disparate communication channels—Slack threads, shared Google Docs, and verbal meeting notes—into coherent Jira tickets and release notes. This manual synthesis is his biggest friction point; he believes the team's potential is stifled by the administrative burden of tracking ownership and actionable insights. Despite the stress, he remains a fixture of reliability, known for shielding his team from external noise while ensuring delivery deadlines are met. He is financially prudent, allocating most of his income toward his daughter's future and family obligations, viewing his role as a stabilizer for both his company and his household. Recently, he rejected a proposed AI tool integration because the implementation risk outweighed the perceived benefit, preferring to stick to their proven, albeit manual, workflows until a solution offered guaranteed zero-downtime migration.
Background & daily life
A day in their life
Deependra wakes at 5:30 AM, immediately heads to the balcony for 45 minutes of brisk running or weightlifting, ignoring the humid Pune heat. By 7:00 AM, he's back home, showering and having tea with his wife before dropping his daughter at preschool. At 8:45 AM, he arrives at the office (or logs in remotely). His first hour is a blur of Jira ticket triage and answering urgent Slack pings. Standup runs from 10:00 to 10:30 AM, followed by a grueling 45-minute client sync where he defends the current sprint timeline. Lunch is a quick samosa and chai with a junior dev. Post-lunch, he spends two hours manually transcribing notes from a whiteboard session into structured Jira comments, a task he dreads. Another client call at 4:00 PM shifts his focus again. He leaves by 7:30 PM, grabbing a quick dinner, then spends 8:30 PM helping his daughter with homework before finally collapsing. Sleep comes around 11:00 PM, exhausted but satisfied that the day's deliverables were met.
Lifestyle
Deependra lives in a semi-furnished 3BHK apartment in Baner, Pune, sharing the space with his wife, young daughter, and aging parents-in-law who help with childcare. His routine is rigid: 5:30 AM wake-up for an hour of gym or running before the chaos begins. Money is tight; he budgets strictly, prioritizing his daughter's education fund and home loan repayments over luxury. Weekends are split between family outings to local parks, cricket matches with friends, and household chores. He avoids expensive dining, preferring home-cooked meals, and maintains a conservative investment portfolio. Socially, he is selective, valuing deep connections with long-term colleagues and childhood friends over networking events.
Work life
His days are a marathon of context switching. He manages six backend engineers working on legacy enterprise migration projects. Mornings are consumed by standups and clearing Slack notifications. Afternoons involve client syncs where he must translate technical delays into business risks. The real friction lies in documentation: he spends hours manually converting verbal decisions from meetings into Jira tickets and release notes because the team's shared docs are fragmented across Slack threads and Google Docs. He feels a constant pressure to ensure 'zero defects' while managing client expectations, often staying late to verify that the 'actionable insights' from meetings are accurately captured for the next sprint.
Relationships
Deependra is the anchor of a close-knit extended family, often mediating disputes between his wife and parents. He has a small circle of five trusted engineering peers he meets for coffee, though he rarely discusses personal struggles there. His primary influence comes from his own father, a retired school principal, whose emphasis on discipline shapes Deependra's management style. He is respected by his team not for being loud, but for being the person who always fixes the process bottleneck. He is currently navigating the pressures of raising a child in a high-cost city while caring for aging parents.
How they decide
Cautious and evidence-based. He rarely adopts new tools without a pilot phase involving his team. He values peer recommendations and case studies over marketing hype. If a solution promises efficiency, he demands proof of ROI through concrete metrics like 'hours saved per week.' He is skeptical of 'magic buttons' and prefers incremental improvements that integrate seamlessly into existing workflows. He will delay a decision if the learning curve threatens immediate delivery targets.
How they sound
Speaks in a measured, clear tone with a slight Marathi accent when tired, otherwise standard Hinglish. He avoids slang and hyperbole, preferring precise verbs like 'execute,' 'deploy,' and 'rollback.' He rarely says 'I think' or 'maybe'; he defaults to 'We need to...' or 'The data shows...'. In meetings, he pauses frequently to ensure clarity, often repeating key points to confirm understanding. He dislikes jargon that obscures meaning and gets visibly impatient with vague timelines. When frustrated, he becomes quiet and direct, focusing purely on the procedural fix rather than emotional venting.
Personality traits
- methodical
- pragmatic
- reliable
- direct but polite
- anxious about ambiguity
- protective of team time
- detail-oriented
- status-conscious regarding professional reputation
- tech-savvy but tool-skeptical
- disciplined
Goals
- Achieve stable promotion to Director level within 3 years
- Reduce team burnout by automating administrative overhead
- Complete a half-marathon this year
- Secure a mortgage-free home for his parents
- Mentor two junior engineers to senior roles
- Maintain consistent fitness routine despite travel
Problems & frictions
- Fragmented information flow between Slack, Jira, and email causing data loss
- Time spent on manual documentation reduces coding oversight capacity
- Difficulty tracking ownership of action items after client calls
- Balancing strict delivery timelines with team well-being
- Legacy systems requiring manual intervention that AI tools haven't solved yet
- Budget constraints preventing adoption of premium collaboration suites
Values
- delivery
- clear ownership
- stability
- process integrity
- team growth
Interests
- cricket
- mentoring
- enterprise software
- fitness
- marathon running
- industrial automation
Media habits
- LinkedIn for industry trends
- The Hindu (digital edition) for morning news
- Local Marathi podcasts during commute
- Reddit r/sysadmin and r/devops for peer troubleshooting
- Spotify playlists for deep work sessions
- YouTube tutorials on specific API integrations