44 of the questions in our question bank, which currently numbers more than 10,000, are relevant to Slack Full Stack Software Engineer interviews.
All interview questions are provided by recent candidates for the position of Slack Full Stack Software Engineer, labeled and organized by Prepfully, and then published following verification by Slack Full Stack Software Engineers. RoleCompany.
Tell a tale of a time when you disagreed with a team member’s strategy.
60-minute session with a Slack Full Stack Software Engineer expert. Make sure you‘re ready to rock your real interview.
Add recent questions that you are aware of. This question bank only stays relevant with your help.
60-minute session with a Slack Full Stack Software Engineer expert. Make sure you‘re ready to rock your real interview.
Add recent questions that you are aware of. This question bank only stays relevant with your help.
Coding Interview | Software Engineer @ Slack
Interviews for Top Jobs at Slack
Software Engineer Interview
I applied online. The process took 3 weeks. I interviewed at Slack in Feb 2022
Interview
My experience echoed a lot of the reviews on here. The hiring manager was distant and clearly not interested in actually interviewing me. They didn’t ask a single question about my experience. They actually didn’t ask a single question about anything, besides a couple placeholder technical questions. I had to awkwardly try to keep the conversation going, which was obviously going nowhere. A few days later I received an email from the recruiter letting me know they were not moving forward. I would not have moved forward, either, after this off putting interaction.
- What does X function achieve?
Software Developer Interview
The process took 2 weeks. I interviewed at Slack (New York, NY)
Interview
The process was recruiter screen with light technical questions, main technical (two interviewers, not Leetcode-based), behavioural (life story style), system design. Technical questions were all relevant to Slack’s product. Great experience.
- Describe a time when you made a mistake at work
Software Engineer Interview
The process took 4 weeks. I interviewed at Slack
Interview
Interview process began with a recruiter call, followed by a zoom call with a hiring manager. It took a week and a half to get any feedback from the hiring manager call to setup the next steps for a take home assignment. After getting that setup I completed the assignment very quickly and received a call saying that I passed but they had moved the position out of the country. Basically a huge waste of time, no information was given for how to proceed given that I passed all the steps up to the take home assignment or what to do when I apply again. Would expect something like this from a small startup not something like Slack. So disappointed.
- Review a PR like you would on the job
What we look for in interviewees
Our top priority is to find talented engineers who are enthusiastic about programming and exhibit a high level of craftsmanship. We value those who have a passion for discovery and are genuinely curious about how things work and what our customers need, as well as those who can elevate their entire team rather than just themselves. People who are highly collaborative and comprehend the value of a diverse team with various backgrounds, thoughts, ideas, and lived experiences, as well as those who take ownership of their decisions and complete tasks, do very well at Slack.
Add recent questions that you are aware of. This question bank only stays relevant with your help.
60-minute session with a Slack Full Stack Software Engineer expert. Make sure you‘re ready to rock your real interview.
All interview questions are provided by recent candidates for the position of Slack Full Stack Software Engineer, labeled and organized by Prepfully, and then published following verification by Slack Full Stack Software Engineers. RoleCompany.
Tell a tale of a time when you disagreed with a team member’s strategy.
Since we believe this is the best indication of how you would write code on a daily basis at Slack, we’d like to get a sense of how you write code in the real world. Technical exercises are a good predictor of future performance on the job, even though the Slack codebase is bigger and more complex than any other. Great engineers can be found at both well-known companies and smaller startups, so everyone has a chance to succeed regardless of their current position. “.
“I submitted two applications: one via the website and the second at a conference. A month or so (roughly two months) after submitting my resume at the conference, I was given a coding challenge. A week later, I had a phone interview with a recruiter. Great conversation. About two weeks later, I spoke on a Zoom call with an engineer who inquired about my experience with iOS development, previous internships, and projects. Received a phone call with an offer a week later. ”.
FAQ
Is Slack interview hard?
Glassdoor users rated their interview experience at Slack as 50. 0% positive with a difficulty rating score of 3. 0 out of 5 (where 5 denotes the most difficult level)
What is the slack interview process like?
This conversation, which typically lasts an hour, is in-depth and covers your background, the technical challenges you are currently facing, and what you are hoping to find in your next position. Please feel free to ask any questions you may have about Slack; we encourage you to do so.
Does slack LeetCode?
Yes, you might be asked to use whiteboards to draw out a system, but you won’t have to answer questions about how to reverse a binary tree or anything similar. Once more, many FAANG companies will ask you questions similar to those in LeetCode.
What are the questions asked in Cisco interview?
Examiners will ask questions about probability, permutations and combinations, algebra, simple and compound interest, number series, profit and loss, etc. during the interview rounds of the aptitude test. Technical test: Questions about digital electronics, CMOS and microprocessors, as well as computer networking, C, algorithms, and data structures.
