Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto più di 5 mesi. Ho sostenuto un colloquio presso Slalom (Houston, TX) nel mese di apr 2015
Colloquio
I was contacted by a recruiter on LinkedIn from a common connection. She was enthusiastic throughout the whole process and the hiring process took roughly 2.5 weeks.
I have to say the whole recruiting team at Slalom is amazing. They go the extra mile to make you feel welcome, really understand the growing business' needs, and have a healthy check on the company's culture and long-term objectives.
After being an employee here for 2 years, it's not uncommon for the recruitment team to ask employees to jump in on the hiring process, often asking for group volunteers to get to know and provide feedback on potential leadership candidates. They take all feedback honestly, and really enable the employees to create the management culture they want to work for.
Domande di colloquio [1]
Domanda 1
How would a teammate describe your involvement and contributions to a project?
Thanks for coming back to Glassdoor and leaving a review of your interview experience. Hiring the best is a top priority and it takes a strong recruiting organization as well as the support from all of our employees. We appreciate your continued involvement in helping make the recruiting experience positive for all of our great candidates.
Altre recensioni di colloqui per Senior Engineer presso Slalom
Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto più di 2 mesi. Ho sostenuto un colloquio presso Slalom (Seattle, WA) nel mese di ago 2016
Colloquio
1. Recruiter chat
2. Tech screen with Solution Architect
3. Technical interview with Solution Principal
4. In person casual chat with Practice Area Director
5. Offer extended via same recruiter via phone call and email of offer letter
This info is specific to the Seattle, WA branch, so keep that in mind. I can't speak to how other branches operate. My situation was unique as I was remote in Cincinnati, OH and interviewing for a position in Seattle, WA via a referral from my buddy that worked there already. Usually, they'll have you come to the office in person and have it not be a remote process. Since, I wasn't moving without the promise of employment, this wasn't an option for myself.
Overall, this was probably the most respectful process I've ever been through for recruitment. When I interview, I want to know the status of what's going on and next steps. I don't like my time wasted or to be strung along. They were very informative and I always knew that I was being considered and/or waiting for scheduling conflicts to be resolved on their end. An old work collegue I referred ended up taking over a week to find out he didn't pass screening, so your mileage may very.
In terms of time, it was a long process. It was mostly due to my situation and both sides accommodating that. I've heard local hires go from interview start to offer letter in a matter of weeks. Again, your mileage will vary depending on location and who is involved in the process.
Domande di colloquio [1]
Domanda 1
1. What's the difference between an interface and an abstract class?
2. Create a function that gives you the n-th number in the fibbonaci sequence.
3. Write HTML to produce a sketched out page.
4. Write javascript to hit service to interact with said page.
5. Given multiple SQL tables, perform a variety of queries. This included joins, grouping and other basic SQL knowledge.
6. Given certain implementations you came up with for previous questions, what are the pros and cons if your approach? Could you have done this better? How?
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Slalom (Seattle, WA) nel mese di giu 2015
Colloquio
The hiring process started with meeting a recruiting manager. He explained the company, the core values, and the culture. Then I was taken on a grand tour of the facility. It was actually a terrific experience, and a huge part of my decision to go forward.
Then about a week went by before a 30-minute phone interview could be scheduled with a solution architect. This one probably played a huge part in their decision to go forward with me.
Then another week went by before the 2 hour in-person interview, with two different solution architects. I was extended an offer at this time, which was formalized over the next few days.
Domande di colloquio [1]
Domanda 1
The phone interview tested me on various technical skills, like web-related questions, database questions, computer science questions, etc.
My interview centered on laying out a solution for a mobile product, based on a set of requirements. We covered the data layer, the service layer, and the beginnings of possible web-based front end.
