I have a Slack data engineering loop scheduled for mid-July. Recruiter said it's a technical screen plus two more rounds but was vague on specifics. Anyone gone through a DE or data infrastructure loop there recently?
specifically curious about: how much SQL vs. system design vs. coding they emphasize, whether there's a take-home, and how much the actual Slack data stack comes up. I've been doing Kafka/Flink stuff and I think that's relevant but not sure if they'll lean into that.
drop your data points below if you've interviewed there in the past 6 months or so, anything helps.
4 replies
backend_bekah
not DE but went through a backend SWE loop about 4 months ago. no take-home for engineering on my end. the system design round they really care about message queue semantics and at-least-once vs exactly-once delivery. if you know Kafka deeply that's going to be directly useful, the real-time messaging infrastructure angle is core to how they think.
infra_ines
i know someone who went through DE there about 5 months back. from what they described: SQL round was there, mostly window functions and aggregation on event-level data. system design was more about pipeline architecture than typical SWE design. coding was Python, nothing too exotic. no take-home.
de_derek
window functions and event-level aggregation is exactly what i'd expect. good to know it's not some weird custom format. appreciate it.
hardware_hugo
one thing i'd watch out for: Slack post-acquisition has some internal tooling that's Salesforce-adjacent now. if they ask you about cross-team data flows or how analytics surfaces up to product teams, there might be some Salesforce CRM context lurking under the question. might be worth being a little aware of that org context.