The recruiting team was “really, really“ good.
A recruiter reached out regarding an opportunity on LinkedIn. After we spoke and finding that the role and my skills were not aligned, the recruiter actually connected me with another opportunity that another recruiter was filling.
I decided to do the interview loop because I heard quite a bit about Slalom culture and I was curious what it was all about.
I did an initial technical phone screen, after which I was asked to come onsite.
There were 3 interviews onsite, mostly behavioral questions, with some technical stuff peppered in. Of the interviewers, I got along with 2, and they seemed humble and friendly. The 3rd interviewer made me extremely uncomfortable; they stared at me without breaking eye contact and also had those typical technical consultant arrogance qualities when I was speaking to them. I guess one finds quite a few of these types in the consulting world where “beta engineers” pass off as SMEs because they learned React.js by watching video tutorials over the weekend. I worked at real software organizations for a while, so I know what a true SME is. In any case, it seemed like they wanted to hire for buzzwords versus measuring problem-solving and CS engineering skills. At no point during the interview loop did I experience any type of extraordinary culture.
Finally, they came back with an offer that was significantly below what I was currently making. I turned it down and didn’t negotiate further.
What do you do in your current role?
Questions about past projects and work.
The following metrics were computed from 6 interview experiences for the Slalom Cloud Architect role in United States.
Slalom's interview process for their Cloud Architect roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Slalom's Cloud Architect interview process in United States.