Process
Improvement over standard coding interviews, but how do you reject a candidate based on pull request reviewing skills and give no feedback on any step?
- First round: "Tell me about a time..." questions based on job experience. Conducted by an engineering manager. Good questions; they appreciate in-depth technical answers.
- Take-home GitHub pull request review.
- No feedback, only rejection via recruiter.
Questions
-
First round: "Tell me about a time..." questions based on job experience, conducted by the engineering manager. These were good questions, and they appreciated in-depth technical answers.
-
Take-home GitHub pull request review.
-
No feedback was provided, only rejection via the recruiter.
Was this helpful?
Interview Statistics
The following metrics were computed from 23 interview experiences for the Slack Senior Software Engineer role in United States.
Success Rate
Slack's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having mixed feelings for Slack's Senior Software Engineer interview process in United States.
Slack Work Experiences
- 5.0Good companySenior Software Engineer • Current EmployeeNew York, NYApril 3, 2024Pros: The pay is quite competitive.Cons: Lots of changes after the Salesforce acquisition.
- 1.0Changing organization in times of struggling stockSenior Software Engineer • Current EmployeeSan Francisco, CASeptember 3, 2025Pros: Efficiency-driven, with nice and smart people.Cons: It feels manager-driven, with a poor development experience and frequent re-orgs.
- 5.0An all-around great jobSenior Software Engineer • Current EmployeeSan Francisco, CAMay 10, 2024Pros: Best-in-class software to work on, down-to-Earth collaboration, smart people, and good diversity.Cons: Speed has been cranked up at the cost of quality lately. Timelines are regularly changed, and it's kind of a go-with-the-flow environment that can mean more work.
