Applied online and recruiter reached out for an HR screening followed by a discussion with the hiring manager(90mins). Then a 24hr take home assessment(2 questions). Then after a long gap I was invited for technical panel interview (1. with a director, 2. with team members(leads) 3. with team members(lead + arch)). Basic programming questions, data structures, a lot of OOP and design patterns. More questions on the take home assessments, choices I made during implementation and trade-offs, etc. They move slow and the interview process took a lot of time with gaps in between. I had positive feedback, but ended up receiving a automated rejection after the interview and no feedback on why I was rejected.

I received an initial phone interview from the recruiter. It was not a technical round. I was rejected due to my experience. They wanted someone with a more related profile to the Job description.

During the hiring process, there are two stages: an initial HR call followed by a panel interview. The technical questions primarily revolve around fundamental computer science concepts, remaining approachable and not overly challenging. The interviewers exhibit a friendly and amiable demeanor. However, the recruiting process lacks clarity. The job requirements encompass a broad spectrum, spanning various professional tracks within software engineering, including hardware, software, and firmware. It's not until the final interview stage that clarity emerges regarding the specific direction and team allocation. This ambiguity regarding job titles and requirements can potentially lead to a time inefficiency for both the applicant and the hiring company. Moreover, while it's a personal observation and subject to interpretation, the working environment appears less diverse. Throughout the process, there seems to be a lack of diversity in terms of the racial representation among the individuals involved.