I believed him. Then, right at the end, I asked a question I now ask in every single interview: "Can you share your screen and show me your Slack sidebar?"
He hesitated, but obliged. It was a bloodbath. He had 84 unread DMs. There were seven different channels with the word "urgent" in the title. The #eng-deployments channel was a wall of red error messages with people tagging @here every 12 minutes. Their "asynchronous culture" was actually a high-anxiety reaction engine.
I withdrew my candidacy the next morning.
Why the Slack test works
A company's culture is not what they write on their Notion wiki. A company's culture is how they communicate when something breaks on a Tuesday afternoon. And in 2026, 90% of that communication happens in Slack (or Teams, or Discord).
When you ask to see someone's Slack sidebar, you bypass the rehearsed PR answers. You get raw, unfiltered operational metadata. It is the digital equivalent of walking through the office and seeing if people look miserable.
What you are actually looking for
When they share their screen, you only need about 10 seconds to spot the red flags. Here is the exact checklist I use.
1. The DM-to-Channel Ratio
Look at the ratio of direct messages to public channels. If a manager has 40 active DM conversations and only 3 active channels, that company operates on whispers. It means decisions are made in private silos, knowledge is hoarded, and politics dominate. Healthy startups default to public channels so context is searchable.
2. The Naming Conventions
Are the channels named logically? (e.g., #team-frontend, #proj-billing-rewrite, #alert-datadog). Or is it a chaotic mess of #random-thoughts, #v2-final-FINAL, and #johns-sandbox? A messy Slack workspace almost always correlates with a messy codebase and a chaotic product roadmap.
3. The "Urgent" Channels
If you see channels like #firefighting, #urgent-requests, or #war-room, ask how often they are used. If the answer is "every day," you are not joining a product team. You are joining a trauma center.
How to ask without sounding crazy
You can't just demand to see their internal communications out of nowhere. You have to frame it as a question about operational cadence.
Try this script: "I'm really interested in how the team collaborates day-to-day. I've found that the way a company organizes its Slack workspace says a lot about its engineering culture. Would you be open to sharing your screen and just walking me through how your channels are structured?"
If they say no because of "security reasons," that's fine. Pivot to asking them to describe it. "No problem at all. Can you just describe your channel naming convention? If the site goes down right now, what specific channels light up?"
But if they say yes, pay close attention. The unread badges never lie.
