The interview process consisted of three steps:

• Briefing with HR
• First round coding test
• Second round onsite interview

The recruiter was warm and quick with updates.

I did not proceed past the first round of the coding test, although I felt it went really well. There were two interviewers: a software engineer (who didn't seem to have much experience with interviewing) and an engineering lead. It was labeled a "pair programming" session, but there was not much input or useful suggestions from the interviewers; it could have simply been called a "coding test round".

I presented two approaches to solve the problem and asked if the program should be extensible to cater to certain cases. It turned out I had guessed his plan to extend to those cases, and for a moment, he refused to reply to my question, asking me to focus on the basic case first. I had to explain again that choosing the right approach out of the two would depend on this answer, so he had to "reveal" his plan. I am not sure what he achieved with this approach to interviewing.

Additionally, I asked what they would expect from my code (aside from the solution itself) at the beginning of the test so I could cater to that. This question seemed unexpected, and I did not get a clear answer. The feedback mentioned that, given I chose Java as my language, I should have made use of some of Java's cool features.

Currency conversion problem.

Inputs: from, to, rate INR USD 0.014 AUD USD 0.72

Then what is:

1. USD to INR
2. AUD to INR (which the interview didn't want to reveal, though easily guessable)

Expected output should be the conversion rate.