The interview process started with a screening interview with a recruiter and then a coding interview in codepad with two technical recruiters. I didn't manage to finish the whole exercise due to my lack of preparation for these questions like leetcode, but what surprise me was the feedback where they said that even had to help me with compile errors. I felt like the session should be collaborative, but it wasn't, every recruiter tip was taken as negative feedback as if "I needed help". In the compiler errors case, I ran the code and they immediately said to add a missing reference, which I obviously would find out when looking to console and this was taking into consideration as negatives. As I said I did not well in the exercise and I know it, but my feeling was that you can't get any tip from the recruiter or it will be considered as help needed and negative feedback. Also, I'd say that the company should take more care in this feedbacks because it sounds very robotic and not take into consideration any human side of the interview environment, it can give the impression that the company doesn't have a collaborative environment.

A recruiter approached me with the opportunity. I proceeded to interview them. The question I was asked was about the coin change problem. I gave two solutions: brute force and dynamic programming. When I mentioned that the dynamic programming solution is better in terms of time complexity, the interviewer told me that it will have the same time complexity as brute force. I told them that one will probably be O(n^m) and another one will probably be O(n*m). They literally told me that it is the same. Maybe they wanted me to explain how multiplication and exponents work? I don't know. Anyway, I proceeded to code my solution using dynamic programming. It took me 10-12 minutes to write the code but I got a syntax error. I told him that I need to set my initial values to infinity/MAX because we wanted the lowest denominations and then the solution will work. They didn't let me fix the syntax/write a print or even run my code the second time. I didn't ask to google. I copied that code to run on my machine later and as soon I fixed my syntax with the initial value, it worked. I kept telling him that since the return statement is outside the for loops and there is no break. You need to let the loops complete before judging whether or not the solution will work. But somehow, a nested FOR with an IF condition is a bit too complex.