I got to the final round. They wanted me to use a public REST API that I've never seen before. I had to read the manual in front of them. I stumbled a bit, but I was eventually able to make an HTTP call to the API. The coding the call to the REST API and reading the REST API manual wasted a lot of time. I solved 1 and a half problems (DS and Algo) they gave me. We ran out of time and the interviewers said everything looked ok so far. Instead of finishing the rest of the final interview, I got an email a few minutes later that they rejected me. I think any normal person will have some initial difficulty using a REST API that they've never seen before. Out of a hundred interviews, this was the only one that required me to call a REST API. The reason why most companies don't do this type of question is that a bunch of boiler plate code has to be written from scratch. On top of that, you have to read that particular REST API's manual, which slows down the interview. I firmly believe that this is a bad interview question. This was mostly not problem solving, but tedious coding and manual reading. I cannot recommend interviewing here. They will find any reason to fail you.