Slack Pune Staff Engineer Kalpak: A Backend Platform Day

Slack's engineering culture is built around flexible schedules, focused work blocks, and deliberate connection time. For Kalpak, a Staff Engineer on the Platform Admin team in Pune, that structure supports a day that balances deep backend work with family life — including two young kids and a household navigating pandemic-era remote work.

Morning Routine: From Yoga to Online School

Kalpak's day starts early with a deliberate wind-up. After his final alarm at 6:30 am, he makes his bed — a habit he says sets a positive tone and gives him a sense of accomplishment to carry into the day — then steps onto his balcony for fresh air. By 7:15 am he's into 45 minutes of yoga and Surya Namaskar, a practice he picked up from his parents, before showering and dressing.

By 8:15 am he's helping his 4-year-old son get ready for online school and preparing breakfast for the family while playing instrumental music. His daughter is just 7 months old, born during lockdown — a period that tested and ultimately reinforced Slack's family-friendly policies. Kalpak highlights 12 weeks of paternity leave spread across the year, the company's "Friyay" initiative (one Friday off per month), flexible work hours, and a manager and team that adjusted meeting schedules to protect both productivity and rest.

Code Reviews and Morning Connection

At 9:30 am, with tea in hand, Kalpak reviews his notes from the previous evening and his calendar before scanning unread Slack messages. Mornings often overlap with the San Francisco team for casual hangs — tea, drinks, or a code kata. His favorite kata is Romans to decimal (and vice versa), which he spruces up by imposing a time limit or practicing test-driven development.

By 10:00 am he shifts into code reviews, which he prefers to tackle with a fresh mind. Slack's Pune team treats review time as both a quality gate and a knowledge-sharing session. Kalpak notes he enjoys the constructive and creative comments from developers — everything from standard-library suggestions to playful quips like "This change looks good, 'May the force be with you' Let's launch 🚀." Recent release celebrations also happen here, with Pune and SF members joining together.

Maker Time and the Org-Apps Launch

Slack reserves three uninterrupted hours, three days a week, as Maker Time — a no-meeting block across product, design, and engineering. For Kalpak, this is his most productive window. His focus has been on Org-Apps, which enables scalable distribution of Slack apps across Enterprise Workspaces, and which the team recently launched to everyone after a well-received beta. He's also involved in refactoring a large piece of code around OAuth flows during Slack app installation.

One bug on his plate involved the user experience when an Enterprise Workspace Administrator grants or revokes Slack app access to teams. The goal was to show which teams are eligible and to add select-all and pagination capabilities. Kalpak suspected the backend API pulling indexed results was the culprit. Pairing with SF colleagues on similar code paths previously gave him a starting point for a solution, but his morning focus was interrupted when his son announced his online lesson was over and ready for games.

Pairing on a Backend Fix

After a longer-than-usual pandemic-era lunch — playing with his toddler, reviewing his son's drawings, and dividing chores among his wife, parents, and himself — Kalpak is back at his desk by 1:30 pm. Opening VSCode, he investigates the break in granting and revoking app access. He enlists teammates Dinesh and Neha to pair, and together they surface edge cases that pagination would introduce. Following the same code path, they find the root cause: a change in the backend API is returning an extra count. The fix corrects both the pagination cursors and the user experience issue, and Kalpak quickly raises a PR.

Wednesday afternoons bring "Chai Time" at 3:00 pm — a video call connecting Pune office members across departments for random discussions and fun facts, continuing a tradition that started in-person. At 3:30 pm he syncs with Dinesh on planning, designing, and breaking up stories for the OAuth refactor. It's a critical flow at the start of app installation with Slack, and the hour-and-a-half session focuses on decomposing the work after they've already identified the core problems.

Winding Down with Global Sync

By 5:30 pm Kalpak updates his notes, posts his daily standup to the team channel, and cuts off from the office for family time, dinner, and playing with the kids. The evening isn't quite over, though: at 9:30 pm the entire engineering team — Pune and SF — holds a sync. They're disciplined about not overshooting to respect personal time across time zones. Early in the week this time is for planning and project status; once a month it's a retrospective; most Wednesdays are reserved for technical discussions.

At 10:30 pm, after story time and putting the kids to bed, Kalpak winds down with family conversation about anything learned that day. The made bed waiting for him, he says, is a small reminder of his accomplishments — and a cue for a sound sleep.