I went through Boeing's interview process this spring after about 14 months of searching. I'm writing this partly to process it and partly because I think the behavioral prep advice floating around is wrong for Boeing specifically.
Most behavioral advice is written for tech startups or FAANG. The subtext is usually: show you move fast, you own things aggressively, you have conviction and push through resistance. Boeing is almost the opposite. They operate in a heavily regulated safety-critical environment and the behavioral questions reflect that.
Questions I actually got across two behavioral rounds: Tell me about a time you identified a quality or safety issue and what you did about it. Describe a situation where you disagreed with a technical decision made by someone senior to you. How did you handle it? Tell me about a time you had to coordinate across multiple teams to complete something. What broke down and how did you fix it? Give an example of when you had to adapt your communication style for a non-technical audience.
The through-line: they want engineers who raise concerns early, who communicate clearly across functions, and who don't just barrel through when something feels wrong. The question about disagreeing with a senior was specifically probing whether I'd stay quiet or speak up.
Useful framing for your stories: Boeing's core values include safety, quality, and integrity. If your STAR story has a moment where you noticed a risk and escalated, that lands. If your story is about moving fast and breaking things, soften the 'breaking things' part or pick a different story.
I also got asked one that felt almost philosophical: what does quality mean to you in software? Worth thinking about before you go in.