I applied and heard from a recruiter a few weeks later. He passed along my information to the software team. I had a phone screen with 2 engineers and a manager. They asked a bunch of object oriented questions which, as an EE, I couldn't answer. They decided to pass on me, but suggested I interview with the hardware team. I had a phone screen a few days later with a hardware manager who asked me very in-depth questions about a project I worked on. A day later, I got a call from HR saying they wanted to fly me down for an interview.
I went down about a month and a half later (due to my busy schedule) and interviewed with a team of 4 (2 hardware engineers, 1 software engineer, and a manager). The whole day took about 6 hours, with an informal lunch break in the middle. I presented on previous projects/jobs and then interviewed with each one separately for 30-45 minutes each. They asked very tough questions. I also talked with HR for a while and got a tour of the facility. I got a phone call with an offer about a week later in which they gave me plenty of time to decide.
The whole time, I was incredibly impressed with HR. They were very quick to respond and gave me all of the necessary information.
There were lots of op-amp questions, as well as general analog questions.
There were also embedded software questions where you had to write code in C.
The following metrics were computed from 4 interview experiences for the Blue Origin Avionics Engineer role in Kent, Washington.
Blue Origin's interview process for their Avionics Engineer roles in Kent, Washington is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Blue Origin's Avionics Engineer interview process in Kent, Washington.