Rituals and Rhythms

Christine, a senior frontend product engineer at Slack, starts her day long before the first commit. A morning routine of coffee, toast, and news podcasts gives way to a commute across the bay, where she knits until the bus drops her at the Salesforce Transit Center, just across from Slack’s San Francisco HQ. On Fridays, a second breakfast in the cafeteria doubles as a chance to catch up with colleagues before the workday formally begins.

Code Review Before Deep Work

Once at her desk, Christine’s first order of business is reviewing pull requests. Slack’s team "buckets" requests by tagging an entire team rather than an individual, which means reviewers often look at code outside their immediate focus. It’s a deliberate system designed to spread knowledge across the group — and Christine notes she invariably learns something new in the process.

A 9:45 standup follows, focused on the shared channels feature currently in progress. The team reviews major work streams, flags any technical discussions better handled in person, and checks whether target dates are realistic. This candid check-in lets concerns be raised early, rather than surfaced at the end of a sprint.

Cross-Team Demos and Tooling

Mid-morning is reserved for functional meetings that span frontend engineering — sometimes a workshop on system-wide improvements like a smarter model cache eviction strategy, sometimes a broader announcement session. Today, a team in Denver presents a sneak peek of Workflow Builder, a no-code approach to building Slack apps without standing up a server. The demo sparks immediate experimentation, as engineers begin piping messages into the frontend channel using the new tool.

Christine takes advantage of the moment to build a bot that posts anonymous questions to a tech-questions-only channel. The channel operates under strict ground rules: answer directly rather than linking out, keep messages relevant, and be kind to inexperience. She describes the result as an intellectually safe space.

Lunch, Retros, and the Context Bar

Lunch rotates between food trucks and group outings with frontend people from other teams, often centered on a deliberately odd icebreaker or a spirited debate about entrepreneurial clone ventures. This Friday it’s a group lunch with new hires, complete with a question about what fruit or vegetable one would most want to be.

The afternoon opens with a retrospective. Before the meeting, Christine posts her observations in the retro channel — noting both what went well (a thorough technical spec review paved a clear path) and what could improve (mid-project decisions deserved better documentation). During the meeting, the team discusses everything shared since the last retro, and reacts with ➕ emoji to points they support. The goal is actionable takeaways, with a summary posted afterward by the manager for anyone who couldn’t make it.

Back at her desk, Christine returns to the context bar — a strip above the message input, shown in shared channels and DMs, that displays a contact’s timezone or notification status. She and a former intern built the feature last summer, and now she’s refining it. Design questions are routed through a feature channel, with conclusions codified by a gavel emoji reaction — a lightweight decision log reviewed weekly with marketing and customer experience partners.

Bugs, Logs, and User Agents

After an interlude sampling oddly flavored potato chips and a Friday Ask-Me-Anything in the frontend channel (15 minutes with a volunteer engineer, a way to bond across a distributed team), Christine returns to a stickier problem. She’s chasing a puzzling bug and turns to logs she added a few days earlier. A pattern emerges in the user agents: Windows users on older browsers. Reproduction finally succeeds, a fix is prepared and deployed, and the Customer Experience agent who reported the issue gets both the cause and the solution.

Closing Out

A thorough pull request description — complete with linked documents, JIRA tickets, and manual testing instructions — pays off in faster approvals and a more forgiving git blame months later. Then it’s time to pack up, meet her partner at BART, and head to the East Bay for a workout and vegetarian tacos before an evening of knitting and a movie.

Editor’s note: This post is part of a series profiling engineers across Slack’s ecosystem. Prior installments covered the backend foundation team; future pieces will look at product engineering, mobile, and frontend roles.