I've only been into the first 3 rounds with a code challenge and they were very polite and friendly during the all 3 interview so far. The last round was with 3 engineers which all of them were very smart and friendly and it was more a chat
Interview questions [1]
Question 1
How could you do something different on the way I implemented the code.
I participated in the first three steps of the hiring process: - Screening with a Recruiter - Management interview with an Engineering Manager - Take-home coding exercise The first two steps were great. The interviewers make sure you are very comfortable and don't ask tricky questions. They just want to know how you do your job. What could be improved in my opinion is the third step. The assignment is too big for those unfamiliar with Elixir and there are no clear criteria for what is being evaluated from the start. Example: should the candidate focus on writing idiomatic Elixir or making sure the features requested are impeccable? Or is documenting the code more important than anything else? Knowing that would probably make my process have a different outcome. They mention that there's no time limit for the exercise, but it's very hard for a candidate who cares about the position not to try to give their best in the shortest time possible to not lose the position to some candidates that started the process earlier.
We want to express our sincere appreciation for taking the time to share your specific feedback for improvement, and will make sure it reaches the right people. Code exercises are an important part of the engineering hiring process that we strive to get right. Thank you for your interest in working with Remote!