Gusto Software Engineer interview questions

TL;DR -- very disorganized, confusing and slow process. 1) Call with recruiting manager -- very quick, just about fit 2) Technical Screen -- Went well. Asked to implement the reduce() function in Ruby. I didn't know Ruby, but the interviewer answered any questions I had about the language. 2.5) Don't hear back for over a week, email the recruiter again. 3) Got offered an onsite, and started scheduling it with the recruiter. Yay! 4) Got my onsite invitation rescinded after a couple days, because.... reasons? This was absurdly unprofessional, and I never got an explanation from anyone. 5) Another technical phone screen -- same kind of question, but with an engineer with poor connection and an accent. It is hard to learn a language over the phone when you can't understand the other person. I've seen this on a couple other reviews (for ZenPayroll), but the second interviewer was also very impatient. Not sure if that's a trend or not, but it sure is annoying.

They contacted me and set up an interview. The first interview was with an engineer lead and he talked more than I did. A little weird but it's fine. In the second interview, an engineer asked me to implement reduce() in Ruby. I was not very familiar with script language and he is not good at explaining the concept and very impatient. In my opinion, if I understand the way script language works, the interview would be pretty easy. But there is a learning curve and with all those new terms, I didn't get the concept very quickly. There are a couple of questions, and he expected me to provide the correct answer in seconds, otherwise, he told me the answer without letting me try to figure it out. The interview was supposed to be one hour, but he told me all answers and finished it in 30 minutes. I wouldn't want to work with someone impatient. Everyone needs some time to learn. If it is for an engineer position, the interview is Ruby and you have no choice! I did brush a little bit ruby before-hand, however, I found that it was very distracted to use some new language. I paid a lot attention to the syntax, but forgot about the logical edge cases. In sum, the interview is very informal.