One tech recruiter and the other is HR recruiter. Questions are pretty simple. Basically go through your cv and then technical questions then HR question. One question from one recruiter at a time. One tech recruiter and the other is HR recruiter. Questions are pretty simple. Basically go through your cv and then technical questions then HR question. One question from one recruiter at a time.
Interview questions [1]
Question 1
Javascript based questions. How to review other people's code.
I applied through an employee referral. The process took 3 days. I interviewed at Roadmunk (Kitchener, ON)
Interview
I was referred by an employee and got the call from their HR within a day. I was then given a code review assignment and that's when came to know about their behavior.
So the email containing the details didn't mention that I should not be removing the code even if thats not being used. Ideally if a code is not used, you shouldn't have it. That's what I suggested and they weren't happy. Secondly, no where in the assignment it was mentioned about test cases. So you do what you're asked for and I didn't do more than what was asked for. Again they weren't happy. They expected me to infer things on my own. It was just unfair. They didn't reply to my emails regarding this and I thought I should post a review online. I'm never applying there ever!
Well, if you reject someone and give a valid reason for that, it's a constructive feedback. They gave a useless feedback. I think they're not doing very well now so are confused about hiring more people or the HR needs to show that they're doing something so they jump on interviewing just to show what tasks they did on their timesheet. A justification for not getting laid off and keep receiving their pay. Well, if it's working for them. Keep it up!
Interview questions [1]
Question 1
It was just a code review for some priority queue implementation in javascript. It was mentioned that you need to just review it and suggest improvements. If required, write your own implementation.
Thanks for the feedback and sorry you feel this way. Just to touch on a couple of points and help out any future applicants at Roadmunk. We firmly believe that every developer should not only be able to identify test cases but habitually create them. So while we don't ask for it, we expect this as a base skill from all developers we interview - it's usually a hard stop for us if we've got to ask for it. That's just part of our developer expectations.
Our recruitment team does NOT just interview for the sake of it. We only post open roles and meticulously screen every applicant to understand if there is a true 2-way fit - i.e. are we going to be a good choice for the candidate and are they going to be a good choice for us. And that is truly something I will say, "keep it up" too. Please do feel free to reach out to me directly and I'm happy to discuss further.
Top companies for "Compensation and Benefits" near you