Real, anonymous reports from people who interviewed for Software Engineer at Blue Origin, newest first and distilled into what to expect across the loop.
The process started with a single phone screen that lasted about 30 minutes on Microsoft Teams. That screen centered on my relevant experience and covered some general technical knowledge. It felt like a quick calibration call—enough to understand where I’d worked and how I thought technically.
I made it through the full process and still didn’t get an offer. What stuck with me was how it ended: I received a generic rejection email over the weekend, and there was absolutely no communication after that. After multiple follow-ups, I didn’t get any answers or even a proper explanation—just silence. The whole thing felt especially rough because the lack of communication didn’t match how much effort the earlier stages demanded.
The interview process typically begins with a recruiter screening that includes behavioral questions about the candidate's background and motivations, followed by a technical screening with the hiring manager. This stage sets the tone for the rest of the process, and candidates should be prepared for both behavioral and light technical inquiries.
Candidates can expect a mix of technical assessments, including coding challenges and system design questions, often structured around specific programming languages like JavaScript. The difficulty of these assessments can vary, but they generally require a solid understanding of core technical principles and problem-solving skills.
A significant component of the interview process involves presenting a project or portfolio, followed by a Q&A session with interviewers. Candidates should be ready to clearly communicate their work and defend their choices, as this part is heavily evaluated.
The final stages often include a panel interview format, which can consist of multiple back-to-back interviews with different team members. This setup tests candidates' abilities to communicate consistently and handle varied questions across different interviewers.
Candidates frequently report a lack of communication after the interview process, with many receiving generic rejection emails and minimal feedback. It's advisable for candidates to follow up for clarity, as the process can feel abrupt and uncommunicative.
The overall interview experience is described as structured yet intense, with a mix of behavioral and technical evaluations. Candidates should prepare for a demanding process that tests both technical skills and the ability to articulate their experiences effectively.