I applied online, the process took a little more than a week with a bit of prodding to get a first round interview. Interviewer had ample personal, professional and online resources to look me up but clearly didn't avail himself of any. He asked lots of rapid fire questions about my work with OAuth 2.0 that were either fairly basic or poorly formed / uninformed . Lots of questions that resulted in 'it completely depends on hypothetical business needs / protocol type' or 'technically yes but often no'. He did not like that, I can only assume he thought he asked a simple / straightforward question and circling back with a deeper dive into why that answer's the case produced essentially "don't BS with me, I gave you your feedback, we've moved on". I think that the main takeaway for me (and you) is that you need to be prepared for east-coast style abrasive and direct. They're looking for confidence by way of competence. In using this info to adjust your style; you don't try to nicely explain things because their questions clearly belie they don't understand what their asking. For me - I'm totally cool with direct and abrasive types (I can be one too) but I wish instead of nice I'd have switched gears to see how he had handled responses like "Ask bad questions, get bad answers" or "don't know the answer to the question you're asking - don't ask it" or "can you be more specific, your question is so broad it doesn't really make sense that you are asking me that". I'm marking "Did you get an offer?" as "no" but only because I won't be pursuing it further, I heard enough to decide not to work in that type of environment.

First round was an online coding round with questions on binary trees, linked lists, maps, arrays. Second round was a phone conversation with questions on java concepts and especially garbage collection. Third round was a mini-project that is to develop a Java SpringBoot application Angular JS on the frontend and dataset is Titanic dataset from Kaggle.