Slalom Software Engineer Interview Questions
& Process

The process was quite fast and I received feedback. The outcome wasn't what I was hoping for, but I admit I barely prepared. I do recognize that if I had studied the week before, I could have gotten a better result.

I applied for a role that I felt matched my experience and a recruiter got in touch fast. They seemed keen to speed things up, usually setting up interviews with just a day or two notice. After finishing four interviews within two weeks, I was told a decision would be coming. A few days after my last interview, I heard the team liked me and I should expect an offer, just needing some paperwork and a background check. For almost two weeks, I heard nothing, even when I asked for updates. Then, over a month after I first interviewed, I was told the position actually needed someone more experienced and I wouldn't get an offer. I was upfront about my experience the whole time and was told they were looking for someone with my background. I don't think they intentionally misled me, but going through a long interview process with such a bad grasp of what the job actually needs shows really bad organization and incompetence from management, and it's disrespectful to people looking for work. They should have just told me politely that they wanted someone with more experience right after I applied; instead, they wasted my time. My advice is don't let them waste yours.

Applying to Slalom felt like a never-ending cycle of disappointment. I went for three roles over a year, two local and one Slalom Build, really wanting to join because of their reputation. The first time, I waited 5 months total, was told I'd get an offer, then nothing. Months later, I reapplied. The job description was so unclear, it was like they were hiding something. My first interviewer asked for work samples to critique as a 'colleague,' but instead just forwarded them to the next manager. This manager was late, eating, and clearly didn't want to talk to me. Fast forward to the Software Engineer role: I aced the phone screen and coding interview, with the interviewer even saying I'd passed and the recruiter would call. Four days later, the recruiter called saying I wasn't ready, with vague feedback about API experience and a suggestion to reapply in 6-12 months. The communication was all over the place, promises were broken, and their transparency claims felt false. It's baffling how a 'best place to work' can have such a chaotic hiring process. They really didn't seem to want me there. If you're interviewing, brush up on SQL, design patterns, REST APIs, OOP principles (like SOLID), and FizzBuzz.