Bose Interview Questions
& Process

The overall process was very slow. I applied online and a recruiter contacted me about 2 months later. The initial screening involved basic questions about the role and my skills. About a week later, I had an interview with the head of audio, which also covered basic role information but delved into technical aspects. We ran out of time, so a second screening interview with another engineer was scheduled to finalize questions. I proceeded to panel interviews, meeting separately with 4 engineers for an hour each. Each engineer focused on their area of expertise (DSP, mechanical, spatial audio, speaker design) and asked questions related to my resume.

I went through 3 rounds of interviews, 2 were virtual and the last one was in person where I met different team members. The interviewers were really professional and I liked talking to them, I was seriously thinking about taking the job. But the recruiting team was super unprofessional. They missed 2 calls and I had to chase them to reschedule. They also ghosted my emails about next steps and when I'd hear back after the final round. Not sure if it was bad luck or Bose's way of saying no, but it left a terrible impression and I won't apply there again.

I spoke with two recruiters. The first one was great, very communicative about what to expect. After passing the HM round, I was handed off to a "Senior" Recruiter. We chatted about next steps, but then they ghosted me. I followed up a week later about scheduling and heard nothing. I had to reach out to the first recruiter again. I eventually got an email saying the role wouldn't be open for a few months, but they wanted to continue. Three months later, I reached out again and after a couple of weeks of silence, the HRM system sent an automated rejection email saying I wasn't moving forward. For such a well-known company, this was the worst and most unprofessional recruiting experience I've had, especially with that second recruiter.

So for the AWS Cloud Engineer role, they want to make sure you really know your stuff. You gotta get into the nitty-gritty of the main AWS services like EC2, S3, VPC, and all that. Definitely need to have actually used AWS, like, get your hands dirty so you can show them what you can do. And obviously, you need to be good at solving problems, like figuring out what went wrong in AWS and how to build stuff. They also want you to be able to talk about it well, like explain techy things so anyone can get it. Oh, and keep up with what's new in AWS, shows you're really into it.