Adobe Computer Scientist interview questions

I was interviewed in the Noida office. The hiring and interview process was all very smooth and systematic. They treat you very well as long as you are in the office. The questions asked were all very meaningful. The only problem I see is the lack of clarity of what they are looking for. Right in the first round, I told the interviewer that I haven't worked on a particular topic. They told me it doesn't matter much and I was interviewed all day up to the director round (5 rounds in total). Then they told me that they will get back to me post selection meet. They never got back to me. I wrote to them, but they don't bother to reply. Through some internal contacts, I managed to get the feedback. And I was rejected on the basis of that particular topic I told the guy in the first round.

Contacted by recruiter through email. Got a HackerRank test to complete within a few days, after sharing my resume. The test had different sections - Aptitude, Computer Science MCQ, Programming, etc.. After completing the test, I was scheduled for an on-site interview in their Noida office, on a Saturday. The first (and only) round was with a guy who didn't tell me anything about himself and didn't even have my resume beforehand. Asked me superficial questions like the different kinds of exceptions in Java (checked, unchecked), the difference between them and how and when we could use them, difference between unique key and primary key in SQL, the output of a javascript/jsp code snippet, static class in Java, etc.. He didn't seem quite satisfied with my answers (even when I told him that the primary key is chosen among the unique keys as per the use case) and then perhaps upon realizing that my work profile was mostly in data and backend processing, asked me to compute the no of ways to traverse a linked list from begin to end, where each node had a link to it's next node and the next node's next node. I told him my approach and wrote some combinatorial expressions but he perhaps didn't get what he was looking for. All in all, I'd say that the HRs were quite active in setting up the whole interview process but the interviewer lacked depth and unlike other technical interviews, where you are expected to write code or solve some design problem, the interviewer was stuck with some nuances of a language (Java, JSP, etc.) or some bits of knowledge which may hardly be put to practice anyways. Didn't ask me to code at all. Maybe it didn't matter. I don't know why Adobe interviews are so odd or removed from the actual work one may do or if their work is so unique and different indeed. Maybe the interviewers just want to bring in people like them, who have the same knowledge as themselves.The interviewer was perhaps deliberately testing me, only for edge cases as that's what their work may be all about.