I applied online through the careers website and was emailed a few weeks later to set up an initial chat with a recruiter. It seemed that the recruiter was fairly new at Slack and couldn't answer questions regarding Slack's engineering teams as well as products/features that I used.
The interview was going well until the recruiter asked about the percentage of time I spent on the backend versus the frontend. Expecting a predominantly backend distribution, the recruiter quickly told me that he would not be moving forward with me as I told him I was a full-stack developer and spent my time equally between both domains.
I would say that this is a poor representation of what I thought Slack was. Why even set up an initial chat and screen me as a candidate if your intuition is to hire someone based on their answer of how much time they have spent on a technology?
Additionally, asking for a percentage of how much one works on the backend or frontend does not determine their aptitude for that knowledge. I may spend 50% frontend and 50% backend, but I am definitely adept at both principles.
Describe an API you built and the number of requests it receives per hour.
How much time do you spend on the backend versus the frontend?
Tell me about your experience at your current role, as well as the technologies you use.
The following metrics were computed from 1 interview experience for the Slack Software Developer (Backend) role in Canada.
Slack's interview process for their Software Developer (Backend) roles in Canada is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Slack's Software Developer (Backend) interview process in Canada.