Extremely disorganized hiring process. I was initially contacted by a recruiter about a Go position, which was then closed, but then a Java position was opened, but then it became a Go position with an India-based team, but then on the interview itself I was asked to write in Java. When I found out I was interviewing with an India-based team, I was asked to be more flexible with my schedule given the timezone difference. On the interview itself I wasn't even interviewed by that team, so I could've had a much easier time scheduling. The CoderPad screener asked me to hit a mock API and return the lowest price for a Source+Destination+Airline, which is trivial, but the team added artificial constraints to runtime (including API "response" time) implying they want you to pre-cache the pricing data, I was also told several times by the interviewer that I should cache the data - data that I haven't pulled yet from the API. It could be me misunderstanding the intended solution, but I feel if there's an API to hit, you should use the data from the API. I was told that they decided to go with another candidate, but maybe if it didn't take them well over a month to schedule the first screener with me, I would've had a fairer shot.