Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela Slack (San Francisco, CA) em mar. de 2019
Entrevista
Everyone involved with my on-boarding went above and beyond their call of duty to accommodate a very expedited timeline. The process is straight forward. It begins with an introductory call with a recruiter followed by a technical exercise to be completed at your discretion. The exercise will differ depending on the role being pursued. If all goes well, a phone call with your prospective team's manager is scheduled followed by an onsite interview. The recruiting team will provide details of what is to be expected. Use this information to prepare and you will have everything you need to have a successful onsite. In my experience, there was no trickery or deviation from what I was informed to expect. I found the people at Slack to be beyond amazing and they clearly practice what they preach.
Candidatei-me online. Fiz uma entrevista na empresa Slack.
Entrevista
My experience is similar to many others' experiences here. I believe they post jobs and do some interviews to show their presence in the market but do not have much to offer.
Candidatei-me por indicação de um funcionário. Fui entrevistado pela Slack (Toronto, ON) em jul. de 2021
Entrevista
I applied for the Toronto opening through someone working at slack. The first round was 30 min HR phone interview comprising of general HR questions. Second round was a 45 min zoom call with the hiring manager. He asked questions about my previous projects and how I collaborated with the other teams. In the third round I had to review a Junior Developer's pull request trying to be as kind and empathetic as possible. The 4th and final round was a 4:30 hour interview with 4 people.
The first 45 min session was regarding system design; I was asked to design a chat messenger. The second 45 min session was again with the hiring manager who went a little more in detail into my experience. Next I had a break for 30 min. The third 45 min session was about team work and collaboration. The fourth session was a pair programming session. I was given a link to download code and develop a feature for a private channel. The emphasis here was not on how much I could complete, but on the way I would code in real life. The final 15 mins was a wrap up call with the HR
Perguntas de entrevista [1]
Pergunta 1
How would your team mates describe you as?
Some non technical qualities that are important in an Engineer.
Describe a scenario when someone has strongly opposed you.
Candidatei-me online. O processo levou 1 semana. Fui entrevistado pela Slack em fev. de 2021
Entrevista
Applied online through the careers website and was emailed a few weeks later to set up an initial chat with a recruiter. It seemed the 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. It was going well until the recruiter asked about the percentage of time I spent on the backend vs. frontend. Expecting a predominately 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 setup an initial chat and screen me as a candidate if you intuition is to hire someone based on their answer of how much time they have spent on a technology? Additionally asking a percentage of how much one works on the backend or frontend does not determine their aptitude of that knowledge. I may spend 50% frontend/50% backend but I definitely am adept at both principles.
Perguntas de entrevista [3]
Pergunta 1
Describe an API you built and the number of requests it receives per hour.
