Slack Software Engineer Interview Questions

Code review exercise , manager meeting, software design and coding exercise . Code review exercise will test your ability to review a PR regarding how you detect code smells, bad practice, but it’s also behavioral since you need to know how to communicate suggestions and changes . Design and coding process will gauge your problem solving approach but not needed to completely solve

My interviewing manager was rude, and an overall poor interviewer. He jumped around very randomly and was unable to properly clarify any of his questions. It seemed like he was very unprepared.

I loved the interview process. My interviewer was super down to earth and we had an amazing conversation. (Tip: just be yourself!) The recruiter was very organized and responded to my emails in a timely manner. I couldn't have asked for a better interview.

Interview process was poor overall. I applied through a friend referral, which had a quick turn-around time. When I talked with the recruiter, she asked me one small question (“what front end experience do you have?”) and after 5 minutes the conversation was over. I attempted to prod and ask some follow up questions, but there was no interest on her part. 30 minutes later, I get an email from her saying they weren’t going through with my application. Felt like I wasted 5 good minutes on nothing.

After recruiter call, which went very smoothly and professionally, there is a hiring manager interview. The recruiter walked me through what to expect and how to prepare for it. I was initially set to interview with a manager, and few hours before the interview I was told they are switching up the person who should be interviewing me, because the manager in not available. The replacement was a developer and not a manger, and although I was told by the recruiter that this interview will be only behavioral and not technical, the interviewer expected to hear about technical aspects on each and every question they asked, and when you are trying to communicate the behavioural aspects in your answers, you don't feel the necessity to dive deep in technical aspects of the problem. There were also technical irrelevant questions in the interview which was unexpected and surprising. The interviewer was indirectly doing a tech screen and not a behavioural interview, which would have been fine if I knew this is not a behavioural interview, but wasn't the case. They were unmotivated to hear any of the answers, would tell me to give a different and more technical example of the situation because the one I talked about wasn't exciting enough for them, and they looked very distracted 5 seconds into my answers, which made me feel very uncomfortable. Overall the process was handled very unprofessionally specially for a company like Slack. I then heard from the recruiter that they are not moving forward with the process because "the team" has decided I am not a good fit with no feedback, while the team was just one developer whose total years of development experience was half what I had.

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.

First day was a recruiting call After that a call with the hiring manager And then they had you do a GitHub PR review where they ask you to find 10 things wrong but there’s more than 10 things I thought I did pretty good on it because I gave like more than 10

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.

I did an online assessment on codability first. A few days later, then I had a 30 min phone screen. Then in about a week, a 45 technical interview on zoom.

1. 20 mins Recruiter call 2. 45 min Hiring Manager interview (went really well IMO). 3. Take home exercise - Perform a code review and leave descriptive comments (spent a while on this) but rejected me after this round with no feedback whatsoever. I think it went really well but felt like a huge waste of time.