Real, anonymous reports from people who interviewed for Software Engineer at HARMAN, newest first and distilled into what to expect across the loop.
My interview journey started with an onsite format that quickly turned into coding-focused problem solving. I was given LeetCode-style medium questions timed to the session, and the mix included dynamic programming as well as binary search. The problems were doable within the allotted time, and the whole round felt like a direct test of getting to the right approach under pressure rather than vague discussion.
After a recruiter screening call, my process moved quickly into a technical interview with a team lead. That round mixed theory questions with a single coding task, and it felt like they were checking both how I thought and how I could translate it into working code. A bit later I had another deeper technical discussion where the focus shifted toward core fundamentals and DSA—more of the “dig into the reasoning” style than puzzle-solving.
The interview process typically begins with an initial screening call followed by an aptitude test that assesses quantitative reasoning, logical thinking, and basic programming skills. This stage is crucial for filtering candidates based on analytical problem-solving abilities.
Candidates can expect a technical coding interview that focuses on fundamental programming concepts, data structures, and algorithms, often including LeetCode-style questions. The difficulty is generally average, with an emphasis on both problem-solving and the ability to articulate thought processes clearly.
Following technical assessments, candidates will participate in behavioral interviews that often use the STAR method to evaluate past experiences and cultural fit. These conversations are designed to gauge how well candidates align with the company's values and team dynamics.
In some interviews, there is a strong focus on discussing past projects and technical depth, where candidates are expected to explain their work and the technologies they've used. This can include in-depth discussions on specific programming languages and frameworks relevant to the role.
The overall atmosphere of the interviews can vary, with some candidates reporting a friendly and supportive environment, while others experienced a more intense or even hostile dynamic, particularly in technical rounds. This can impact candidate performance and comfort levels.
Candidates often leave the interview process without offers, reflecting on the clarity of expectations and the importance of demonstrating both technical skills and cultural alignment. Feedback on performance can vary, with some candidates feeling they understood the requirements better than others.