I spoke with a recruiter who provided me with the basic requirements and discussed open positions. I then began the process with a hiring manager screening. This was focused on one specific accomplishment from my career, with questions revolving around it. The interview felt somewhat formulaic, more like checking boxes than an organic conversation.
This screening went well and led to a take-home coding test. The task involved building a basic iOS app from a single API. It was unclear what exactly they were looking for beyond making the app functional without spending excessive time on it, so I adhered to that guidance. In retrospect, I should have dedicated more time to this project, as it ultimately led to the rejection of my offer.
Following the test, I had a technical interview that felt more like a screener. This interview centered on college-level questions and also felt largely formulaic, although the interviewer was personable.
After about 10 days without any reply or information, I received a standard rejection letter. I was informed that I performed well on the technical interview, but the take-home test did not meet their standards. However, no specific standards were provided, nor was it clarified what they were looking for.
Overall, I felt the experience was positive. However, I wish I could have discussed my broader experience, previous work, and the value I've delivered to other companies more extensively. I believe this would have been more beneficial than the somewhat vague coding challenge.
What are design patterns, and why do we use them?
The following metrics were computed from 1 interview experience for the Slack Senior Software Engineer/Tech Lead role in Austin, Texas.
Slack's interview process for their Senior Software Engineer/Tech Lead roles in Austin, Texas is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Slack's Senior Software Engineer/Tech Lead interview process in Austin, Texas.