- Call with Talent acquisition manager. - Home Assignment. - After the submission of the assignment, I didn't receive a response for one week so, I contacted the recruiter for feedback. - Later I received that there would be a technical interview. - I received only one interview slot but It didn't work for me so, I replied back. - I found then the next day it was scheduled at the same time slot which didn't work for me & ignoring my mail. - I had to reply & suggest different slots so, maybe I could solve this conflict. - Then on the next day the interview was canceled & I received a general rejection mail with no feedback The company needs to be more professional instead of wasting the candidate's time.

The interview process was quite straightforward and fully interactive. The first stage was a 30-45 minute skype call with the very friendly recruiter where I got to introduce myself and talk about my experiences with regards to the skills and tools that were highlighted in the job description. It was entirely a friendly and relaxed conversation, I was given the opportunity to discuss some of the things I knew about Payconiq prior to the call and the recruiter also further enlightened me about what Payconiq is all about as well as other specify details about the role. The second stage involved a brief but exciting coding assignment to test my ability to write clean and maintainable code with lots of empathizes on unit testing and instrumentation testing. I had about a week to complete this assignment which was quite enough time for me. I got feedback on the assignment 2 days later. The third stage involved, a technical interview with two top-level android developers in the company, the interview took place with a Skype video call that lasted for about an hour. At that point, we got to review my coding choices from the previous step, identified possible pitfalls and discussed better approaches to avoiding them. Overall the developers were supportive but I wish was less nervous during this process. I got asked several questions to test my understanding of some of the tools I used including RxJava, and Mockito. There were also broader questions about unit testing, coding architecture patterns, and android components. You can also expect certain questions about method signatures used in popular android classes. Unfortunately, I didn't get past the third stage but I got very in-depth and useful feedback about my performance in the entire interview process, especially from the third stage. Nonetheless, I had a positive experience and I would give it another shot if I got the chance.