Slalom logo

Slalom Solutions Architect Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 43 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
83.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Slalom.

Showing 3 of 43
Slalom logo
Slalom

Solutions Architect

Engineering · more than a year ago

Senior Average Negative experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer Group
Interview formats
Technical Behavioral Group

So I had 5 interviews with different North American teams, covering team fit and technical stuff. Honestly, it felt like a total waste of time because the main hiring team never even interviewed me. I kept getting passed around to these regional teams, and even though I did great in all those chats and they were all good people, after I accepted a conditional offer, I finally met the team I'd be working with. What was supposed to be a casual lunch turned out to be another 'interview' post-offer! The job I was set to start is now being advertised again. My guess is the technical lead felt threatened, but who knows. Definitely a big red flag for me. I wouldn't recommend this company, either for business or as an employer.

Confirmed questions1 question
  • Could you answer some AWS-specific questions?
Slalom logo
Slalom

Solution Architect

Engineering · more than a year ago

Senior Average Negative experience No offer 6 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Technical Technical Technical Technical Technical Technical

So I got a call from a recruiter. After the initial technical interview, they told me my skills didn't really match. But they decided to keep going with the interviews anyway (which felt like a big red flag). I ended up going through 5 more rounds of interviews, and in the end, they said they didn't have a suitable role for me right now. It was a huge waste of my time, especially since they knew my profile wasn't a good fit but still scheduled 6 interviews. Definitely a really bad experience.

Confirmed questions5 questions
  • Can you describe an AWS migration project you've worked on?
  • What are your thoughts on AWS Compute technicalities?
  • Let's discuss some technical aspects of AWS Networking.
Slalom logo
Slalom

Solutions Architect

Engineering

Mid Easy Positive experience Accept offer 2 rounds
Interview process
Recruiter call Onsite Onsite
Interview formats
Behavioral Behavioral

A recruiter reached out on LinkedIn. Since the timing was good and the message caught my eye, I replied. I ended up speaking with the recruiter either the same day or the next morning. The first onsite interview was scheduled really fast, within a day or two. It was with the hiring manager and a technical person. Unlike other interviews, the hiring manager seemed genuinely interested in what I was looking for in my career, and we chatted for way longer than planned. I then had a second round of interviews, one of which included the local executive. Again, everyone was friendly, and it felt more like a two-way conversation to see if it was a good fit for both of us, rather than just a Q&A. Slalom really values culture fit, so that's a major part of their interview process.

Confirmed questions1 question
  • What are you most interested in doing next in your career?

Slalom Solutions Architect Interview Questions

Quoted word for word from Slalom interview reports.

Could you explain the benefits of using an event-driven architecture?

Read reports

How would you approach integrating two systems, considering they require both nightly batch processing and real-time synchronous read capabilities?

Read reports

Can you elaborate on AWS Security from a technical standpoint?

Read reports

What are the best practices for Apex triggers and what is your experience with trigger frameworks?

Read reports

What approach would you take to test a web app where users can edit records?

Read report

What is your definition of outcome-based design, and how would you strategically guide client engagements with this principle?

Read report

Can you describe how you'd automate testing for a typical 3-Tier web app?

Read report

What do you foresee as the stakeholder reception to your proposed solution?

Read report

Could you describe how you would whiteboard a highly available, multi-tier, public-facing solution within a cloud environment?

Read report

Formats, difficulty and experience

Across all 43 Slalom interview reports.

Interview formats

Behavioral 36.5%
Technical 35.6%
Presentation 11.5%
Case 7.7%
Group 2.9%

Interview difficulty

Easy 16.3%
Average 72.1%
Difficult 11.6%

Candidate experience

Positive 83.7%
Negative 14%
Neutral 2.3%