HARMAN Android Engineer Interview Questions
& Process

The interview process had two rounds. The first round was purely theoretical, covering basic Android development concepts. The second round involved two interviewers who asked about Android basics, OOP, and a basic data structures and algorithms question involving strings. I answered most questions, but the hour-long session felt intense due to the rapid-fire questioning, which was tough for a fresher. A low point was when I couldn't answer a simple question, and the interviewers reacted sarcastically, which really shook my confidence and made the rest of the interview difficult. After that, I was mostly focused on finishing the interview. This was the only negative aspect; overall, it was a good learning experience.

I applied on LinkedIn and heard back from a recruiter within 2 days. The first round was with the technical manager. It was a good experience overall, but I wasn't selected. The reason was that I'm looking for a job in Android mobile app development, but they were focused on car applications. Honestly, I applied just to get interview experience. As expected, they didn't seem to understand my career goals. They asked me several low-level OS questions specific to cars, which I couldn't answer. This was the first interview in my career where they asked over 20 questions.

They were looking for Android developers but it seemed like they cared more about memorization than problem-solving. He started by asking standard Core Java questions even though my experience was limited to Android and I hadn't covered those specific Core Java topics. I managed to answer all but one question using my intuition and problem-solving skills, and it turned out my answers were correct. The interviewer seemed disappointed that I didn't know the answer immediately. He then asked about my experience with threads, which I didn't have, and he appeared quite disheartened, as if I wasn't the type of candidate he was seeking.