Great work-life balance. Insurance is quite good.
Pay is relatively less than Qualcomm.
I passed one phone screen with the task leader, which involved a single C question wisely known among embedded and firmware engineers. Upon arriving for the onsite interview, it became clear that the coding questions would not effectively determine i
A recruiter contacted me via email, having found my profile on LinkedIn. This felt like a poaching attempt, as my current role, which I haven't held for more than a year, was clearly listed, and the company is a competitor to one of Google's division
After a short communication, I've selected timeslots for the interview: 1. Interview with HR about role and skills. 2. Technical interview where you should solve the task (using an IDE is prohibited). The company did not provide you with feedback a
I passed one phone screen with the task leader, which involved a single C question wisely known among embedded and firmware engineers. Upon arriving for the onsite interview, it became clear that the coding questions would not effectively determine i
A recruiter contacted me via email, having found my profile on LinkedIn. This felt like a poaching attempt, as my current role, which I haven't held for more than a year, was clearly listed, and the company is a competitor to one of Google's division
After a short communication, I've selected timeslots for the interview: 1. Interview with HR about role and skills. 2. Technical interview where you should solve the task (using an IDE is prohibited). The company did not provide you with feedback a