Why this persona fits the audience
Engineering manager at a 10-person custom software team that delivers Windows and web apps to mid-market clients. He coordinates nightly builds, package assembly, and client-specific deployment steps using scripts, shared folders, and Excel-based release tracking.
- Age: 39
- Location: Pune, India
- Occupation: Engineering Manager
- Income: ₹42 lakh total annual comp
- Education: BTech Computer Engineering
- Company size: 10 employees
- Years in role: 5
“In our line of work, a successful deployment isn't just about code that works; it's about the peace of mind that comes from knowing exactly what went out the door and why.”
Bhaswar Ganaka-Dwivedi is a 39-year-old Engineering Manager based in Pune, India, leading a ten-person engineering team at a boutique custom software studio. With a BTech in Computer Engineering from a reputable state university, he has spent nearly fifteen years navigating the evolution of the Indian IT sector. Currently, he earns a total annual compensation of ₹42 lakh, a figure that reflects his seniority and the niche nature of his work in delivering Windows and web applications to mid-market clients. His professional identity is defined by a relentless pursuit of order amidst the inherent chaos of custom development. Unlike large enterprises with massive DevOps teams, Bhaswar's team operates with lean resources, forcing him to wear multiple hats. He personally orchestrates the nightly build cycles, packages assemblies, and manages client-specific deployment steps. His toolkit is a hybrid of custom PowerShell scripts, network-shared folders, and a notoriously complex Excel-based release tracking system that he has refined over five years. This reliance on manual coordination stems from a desire for transparency and control; he believes that if he can see every variable in a spreadsheet, he can guarantee the quality of the product. However, this approach has become a bottleneck as the client base expands, leading to frequent midnight troubleshooting sessions. Bhaswar is a man of few words but high impact, known for his calm demeanor during crises and his strict adherence to accountability. He is a devoted father and husband, finding solace in the rhythm of cricket and the discipline of running. Despite the allure of modern, cloud-native CI/CD platforms, he remains skeptical of rapid technological shifts, preferring to optimize his existing workflows until they break beyond repair. His recent focus has been on documenting his team's processes to mitigate the risk of key-person dependency, hoping to eventually transition to a more scalable model without disrupting the delicate balance of his team's productivity.
Background & daily life
A day in their life
The day begins at 5:30 AM with a 45-minute run along the Kharadi canal, a ritual that clears his mind before the chaos of the office sets in. By 8:30 AM, he is in the office, checking the overnight build logs first thing, scanning for red flags in the automated scripts. His morning is filled with stand-up meetings where he assigns tasks and reviews the previous day's deployment status, often pausing to manually verify file integrity in shared folders. Lunch is a quick affair, usually eaten at his desk while responding to client emails about minor feature requests. Afternoons are dedicated to deep work: refining PowerShell scripts or auditing the Excel release tracker to ensure accuracy for the upcoming Friday deploy. He spends an hour coaching his son's cricket team on Tuesdays and Thursdays, finding joy in the structured physical activity. Evenings are reserved for family dinner and helping his younger child with homework. He ends his day around 9:00 PM, occasionally reviewing the next day's deployment checklist before sleep, ensuring nothing unexpected has been missed.
Lifestyle
Bhaswar lives in a well-maintained apartment in Kharadi, Pune, a suburb favored by tech professionals for its proximity to IT parks but quiet enough for family life. His routine is rigid: he wakes at 5:30 AM for prayer and a run, followed by breakfast with his wife, Priya, before the school drop-off. Evenings are split between coaching his son's cricket practice and managing household logistics. Financially, he is conservative; despite a comfortable income, he avoids luxury debt, prioritizing savings for his children's education and a future home purchase. Socially, he keeps a tight circle of colleagues and old college friends, preferring small dinners over large gatherings. He values his weekends for rest and occasional weekend drives to nearby hills, viewing leisure as essential recovery rather than social obligation.
Work life
At his custom software studio, Bhaswar manages a lean team of nine developers. The reality of his job involves constant context switching between coding strategy and administrative bottlenecks. His days are dominated by coordinating nightly builds and assembling Windows installers for various mid-market clients. He spends significant hours debugging deployment failures caused by manual script errors or version mismatches. Instead of modern CI/CD pipelines, he relies heavily on PowerShell scripts, network-shared folders, and complex Excel sheets to track release versions. The pressure comes from the need to deliver bespoke solutions under tight deadlines without compromising stability. He acts as the gatekeeper for quality, personally reviewing every build log before it goes to a client, often working late to ensure the morning deployment runs smoothly.
Relationships
Bhaswar is deeply embedded in his local community through his wife's extended family and his role as a coach in his son's neighborhood cricket league. His professional network is strong but localized, consisting mostly of peers in Pune's software sector. He trusts advice from senior mentors who have navigated similar career paths in the Indian IT landscape. While he maintains friendly relations with his developers, he rarely discusses personal struggles with them, preferring to keep the boundary between leadership and camaraderie clear. His wife, Priya, is his primary confidante, providing grounding when work stress mounts.
How they decide
Bhaswar is a cautious, evidence-based decision-maker who prioritizes stability and long-term reliability over speed or novelty. He rarely adopts a new tool based on marketing claims or peer recommendations alone; instead, he requires proof of concept, detailed technical documentation, and a clear comparison against his existing workflow. He tends to research thoroughly, often spending weeks evaluating a single solution, and seeks consensus from his senior technical leads before committing resources. He is highly sensitive to the risk of disruption, so any change must demonstrate a tangible reduction in friction or error rates before he will consider adoption.
How they sound
Bhaswar speaks in a measured, articulate tone, often using precise technical terminology mixed with practical business logic. His cadence is steady and deliberate, avoiding hyperbole or emotional language. He tends to speak in complete sentences, often prefacing statements with 'Based on the data...' or 'In my experience...'. He avoids slang and prefers formal address, even with close colleagues. When discussing problems, he focuses on root causes and systemic fixes rather than blaming individuals. He rarely uses absolute terms like 'always' or 'never', preferring qualifiers like 'typically' or 'in most cases'.
Personality traits
- Methodical
- Detail-oriented
- Pragmatic
- Steady
- Protective of team time
- Skeptical of hype
- Process-driven
- Quietly authoritative
- Risk-averse regarding stability
- Loyal to established tools
Goals
- Stabilize the nightly build process to reduce deployment failures by 50%
- Mentor junior developers to take ownership of their own deployment scripts
- Achieve a balanced work-life schedule to attend more family events
- Transition the team toward standardized automation tools to replace manual Excel tracking
- Secure a promotion to Head of Engineering within the next two years
- Complete a marathon within the next year
Problems & frictions
- Frequent silent failures in custom build scripts that only surface at client deployment
- Time-consuming manual verification of package versions across multiple client environments
- Difficulty scaling the current Excel-based tracking system as the client list grows
- Resistance from senior developers who prefer maintaining legacy 'known' methods over new tools
- High cognitive load from managing ad-hoc client requests that interrupt deep work
- Lack of clear audit trails for which code version was deployed to which client
Values
- accountability
- throughput
- team order
- fiscal prudence
- predictability
Interests
- project delivery
- Excel workflows
- cricket
- legacy .NET architecture
- marathon running
Media habits
- LinkedIn for industry updates
- Cricket streaming on Hotstar
- Technical blogs on Stack Overflow
- WhatsApp work groups
- Evening news on DD News
- Podcasts during commute