Real, anonymous reports from people who interviewed for Software Engineer at Panasonic, newest first and distilled into what to expect across the loop.
After a short recruiter screen, I moved into a virtual round with the hiring manager where we went over my resume and basic qualifications. That led into a more technical round where I answered two LeetCode-style questions—one described as easy and another that was easy-to-medium. The whole thing felt pretty structured, with a clear progression from background to coding.
My interview felt surprisingly relaxed. I spoke with a supervisor who was calm and casual, and I actually enjoyed the conversation more than I expected. They went through the projects they were working on, which made the exchange feel interesting rather than purely interrogative.
The interview process often begins with a straightforward HR screening focused on background, qualifications, and logistical questions, serving as a preliminary fit check rather than a deep dive into technical skills.
Candidates typically face a technical assessment that includes coding questions, often in a structured format, focusing on core technical knowledge and problem-solving abilities relevant to the role.
Interviews frequently incorporate behavioral questions and discussions about past experiences, emphasizing how candidates communicate their thought processes and relate their background to the role.
The overall atmosphere of interviews can vary, with some candidates reporting a relaxed and conversational tone, while others experience a more formal or even hostile environment, impacting their comfort levels.
The interview process is generally well-structured, often involving multiple rounds that include technical and behavioral assessments, with some candidates noting a clear progression through the stages.
Candidates have reported mixed experiences regarding communication from the company, with some experiencing prompt follow-ups while others faced delays or a lack of closure after interviews.