Meeting with the hiring manager at the site. We sat in a small conference room, and I was requested to write a solution to a coding problem on a paper with a pen. Done it "perfectly" according to the interviewer. Proceeding to a design problem the team has encountered, my solution was different than the one the interviewer was set on. At the end of the interview, I was given very positive feedback stating I performed greatly, and that I am a good match (did not request the feedback, never happened to me before, seems unprofessional). The day after, the clueless recruiter called to say that the interview was not good and they would proceed with other candidates. I asked how come, given the feedback I received the day before? All she said was "sorry for the misunderstanding" I replied: No problem, good luck to you. The interviewer kept interrupting the interview with continuous phone calls, which he later proceeded to have inside the room while I solved a question. This was extremely rude and far from professional, to say the least. Overall, a horrible experience with this company, a totally bad impression. Everyone was extremely unprofessional.

You have a 30-minute interview with two parts: First Part: Project Discussion and Your Role In this section, you’ll briefly introduce a project you worked on in your last job. Focus on: Project Overview: Provide a short description of the project, including its goals, technologies, and impact. Your Role and Responsibilities: Elaborate on your specific contributions. Explain the main responsibilities you had, such as design, implementation, or problem-solving. Highlight any key achievements, challenges you faced, and how you addressed them. Second Part: Coding Challenge – Shuffle an Array In this section, you’ll be asked to code a solution for shuffling an array using any language you prefer. One commonly used method is the Fisher-Yates Shuffle Algorithm. It is efficient and produces an unbiased shuffle.