Boeing is a very stable environment at the site I work at. It is a generally laid-back atmosphere with strong compensation. Most of its benefits are competitive with peer companies, and generally, it would take a lot to get fired or laid off.
Unfortunately, that stability also seeps into a seeming inability to make cuts based upon performance. It reminds me of Office Space, where you only need to do just enough to not get fired.
As long as you don't care how long it takes to move up, this is a great environment. Forget what people might have told you about Boeing having great fringe benefits, such as education reimbursement. Benefits have been on the decline lately.
The business is facing some headwinds, which results in our "Industry Leading" benefits now becoming merely "competitive." And by competitive, they mean average.
Start taking 360 reviews of everyone and actually listen to them. Several of the managers in my area know little to nothing about who is a strong employee and who is a weak employee. At times, the only interaction between a manager and an employee are at the mid-year PM and end-of-year PM. Then, a minimum of research is done to have something to put down on the review.
Straightforward and communicative interview process with a team happy to move quickly. Fewer technical questions, more focused on processes and procedures. Unfortunate timing in the job offer process ended due to a hiring freeze.
Though it was pre-recorded, there was one behavioral question, one coding question, and one recording of you explaining your solution. The question was impossible, and I later looked it up to see it wasn’t actually solvable.
They had me write a sample of code solving a hypothetical scenario, and then write some unit tests to validate the code. I then presented the code to a panel of four.
Straightforward and communicative interview process with a team happy to move quickly. Fewer technical questions, more focused on processes and procedures. Unfortunate timing in the job offer process ended due to a hiring freeze.
Though it was pre-recorded, there was one behavioral question, one coding question, and one recording of you explaining your solution. The question was impossible, and I later looked it up to see it wasn’t actually solvable.
They had me write a sample of code solving a hypothetical scenario, and then write some unit tests to validate the code. I then presented the code to a panel of four.