This was one of the worst interview experiences I have had. As a technical person, we should be open-minded and seek multiple solutions to a technical problem. When this interviewer asked me a question about dependency injection, a topic I am pretty familiar with, I offered a few standard and elegant solutions. However, the interviewer was not happy, having fixed on one specific solution in their mind. This demonstrated narrow-mindedness and a lack of broad technological background.

Incidentally, interviews with Oracle have always been unpleasant. A few years back, I had a full loop with the company, and two separate interviewers did not know the correct algorithm for the exact questions they asked. Coincidentally, when I implemented the most optimal solutions, both of them said my answer had a bug. When I walked through the execution with the examples they gave, they couldn't point out what was wrong and had to admit my solution worked.

In the end, I received a rejection letter. I would not join a team with members of such technical capability anyway. For the record, in that round, I received multiple offers from companies much stronger than Oracle.

API design around dependency injection