Good benefits, remarkably easygoing for a big company.
As an employee, you will work on one or more projects.
When a project nears its end, you should expect a layoff notice.
Boeing talks the talk about finding new work for those whose projects have come to an end, and to some degree they follow through. However, by and large, if your project ends, your employment with Boeing will as well.
The software development environment is crude. Corporate IT drives resources toward what is most convenient for Corporate IT rather than what is best for the engineers or customers.
Innovation is frowned upon, so they are always a decade or more out of date with practices in the outside world.
Allow middle management to fail. Otherwise, they will continue to take the least-risk approach, and that leads to stagnation.
The focus on "ethics" is a joke. There's "Boeing Ethics," which simply means following written procedures, and "Real Ethics," which means doing the right thing when no one is looking. Boeing has taken the English word "ethics" and redefined it to mean what they want it to instead of what it actually is, which is downright unethical in my book.
Not bad, but since the software test is in pen and paper, you should practice pseudocode and not cheat. Interviews are now in the post-AI era, where companies use it extensively or not at all.
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.
Three engineers interviewed me at my university during a career fair. Two were mechanical, and one was a DevOps engineer. They introduced themselves and asked me some questions. Overall, it was very relaxed.
Not bad, but since the software test is in pen and paper, you should practice pseudocode and not cheat. Interviews are now in the post-AI era, where companies use it extensively or not at all.
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.
Three engineers interviewed me at my university during a career fair. Two were mechanical, and one was a DevOps engineer. They introduced themselves and asked me some questions. Overall, it was very relaxed.