Prospa Interview Questions

It was 4 rounds with various people. I think I met 6 people in total. Everyone was really lovely. They did a great job of selling the company and were very friendly.

Live coding, they would sit with you as you code and check your what you're trying to do through a big monitor screen. This is not as effective as they thought it would be because of the pressure the programmer has to go through. The talent acquisition only brief me that I would have to take initiative of the company details but they are very dishonest, they should've just gave me an honest feedback. After that, no follow ups or update will be given to you if you passed or not, contrary to what they did from the hiring process, they kept on calling using different numbers.

I received a call on the same day I had applied for the role. In the next conversation, a f2f was set up with a head of product. During the interview, I realised the interviewer didn't even review my resume or my portfolio before calling me for a meeting. I felt that was laid back and unprofessional approach for hiring a senior role. I recommend to the hiring managers to at least learn well about the candidate as it shows how much home work you have done before. Please know this - To hire good talent, place good interviewers that can represent the organisation well and entice the right talent.

Pros: Great process. Amazing interviewers. 30 min telephonic interview . Face to face 1 hour behavioural followed by 1.5 hour technical interview. Great conversation with behavioral interview guys. Cons: very dishonest feedback. Answered all questions asked in all parts of the process. Every single of them in the entire 2.5 hour duration. Technical interview had 4 coding questions. Had almost 24 test cases of which ~ 20 passed. Was given excellent feedback at the spot. As i was trying to fix the 4~5 failing test cases, i was told not to worry about the failed ones as I did great with rest of the questions. (Exact words) Result- rejected. Reason given- struggled in technical interview. Its not about the outcome, its about demotivating someone with dishonest feedback. 20 out of 24 test cases passed. Code had no compilation or runtime errors. All cases handled with modern linq /lambda technique. Looking back, i feel It was one of my best interviews and I couldn't have done better. Lesson learnt- I've failed many interviews in the past and might fail many in future but a dishonest feedback is much worse than failure. It can take a toll on candidate's mental state. Reason for getting rejected I think- asked for salary more than Prospa was offering for the role. So why not just say that directly? Very unprofessional from such a reputed organisation.

4 stage interview- 1st stage was a 1 hour phone call, 2nd stage was a face to face with hiring manager and work shopping problem solving skills and approach, 3rd stage was a challenge question and 4th stage was a cultural interview with culture ambassadors and hiring manager and manager-once-removed