Interview Feedback: The interview process was efficient, and I had a positive experience with the team, sensing a genuine collaborative potential. However, when discussing the proposed compensation, which was notably lower than my current package, I faced the assertion that I was "chasing money." I was told that some team members had chances to double their salaries elsewhere but gave more weight to the company's ethos and values. I respect these choices, but it's vital to understand that every candidate's motivations differ. Discussions around compensation require tact and empathy. Advice to Management: I suggest training recruitment teams to navigate compensation conversations with greater sensitivity, ensuring all candidates feel respected.
Interview questions [1]
Question 1
2 x Pair programming 1 x System design 1 x Leadership
Recruiter ghosted the meeting - This is next level in this market. Recruiter scheduled a meeting - the position gets filled - recruiter mails me 10 mins after the call that the position is filled If he realised at the last moment, least should have the decency to fake talk with me and then say that they found a better candidate
Sharethrough response
3y
Thank you for taking the time to share your experience with us. I would like to first apologize for the negative experience you had during your interview process. It is never our intention to waste anyone's time or be unprofessional, and we are truly sorry that this was your experience.
We take feedback like yours very seriously and will use it to continue to improve our recruitment process.
I applied through an employee referral. The process took 4 weeks. I interviewed at Sharethrough (Montreal, QC) in Sept 2022
Interview
The first step is to discuss with a recruiter to make sure that you will enjoy to work here. We discussed about the company culture, its main products, how I like to work, salary expectations, etc. Afterwards, there's a technical interview that I found rather unique. I did pair programming and TDD with the interviewer, but I was in the role of the navigator. You can discuss and help him write the code to pass pre-determined tests. Nothing too difficult, think easy-difficulty puzzles on LeetCode. Then I met my future team lead. He asked me some questions about how I approach problems, what kind of projects I've worked on before, what I value in a project, etc. Then I met my potential future teammates, product manager and team lead. It included another pair programming session, this time as the driver. This one felt more like a day-to-day regular user story, where we had to add a feature to an existing project. I ran out of time before the end but that didn't seem like a big deal. I found the pair programming approach interesting and I could tell right away that we'd get along. The recruiter reached back to me shortly after with an offer, he was really helpful and answered any questions I still had. Good luck!
Interview questions [1]
Question 1
Have you ever worked on an architecture problem, how did it go?