They tried to follow Amazon's interview process and failed heavily.

They have a screening round, then candidates are placed into a pool of three interviews comprising two coding rounds and a design round.

Initially, in all three rounds, they state you can write in any language. However, if you start writing in a language other than Java, they will ask you to switch to Java!

The design round is merely for namesake; it comprises a coding question followed by Java questions.

They want solutions presented in a manner typical of banking companies, not necessarily in the most efficient way. For example, I was asked to design an ETL tool that processes account statements in CSV and stores the processed results of the final amount in a database. Initially, I proposed a scalable solution. As I come from a banking background, they asked how general banking industries like PayPal would approach it. I suggested the Spring Batch method, and they were pleased!

At this point, I decided this was not a good company for a technology-loving person. We would have to work with legacy methodologies that no one uses anymore.

Furthermore, the interviewer asked questions like how to concatenate multiple strings, wanting the term 'StringBuilder!' specifically.

I rejected the offer because banking companies always seem to prefer following legacy code and avoid innovation.

How to design an ETL tool that processes account statements in CSV and stores the processed results of the final amount in a database?

Concatenate multiple strings in Java.

Print all possible combinations of a string.

Find all paths from a given node, given a root node and a distance.