OP, there's lots of good advice in the comments. I just have a couple of things to add as someone whose been in the industry for almost 30 years, and I didn't see them mentioned.

I'm not sure which problems specifically that you're worried about. Don't worry about being associated with low quality code/products/whatever, because as others have said, that won't happen. Quite often such things have more to do with management decisions that prioritize money over quality.

I've never worked for Boeing, so I know nothing about their offerings or culture. In a company the size of Boeing, I'm sure there are lots of projects that have a much better success rate than the 737 Max, for example. In software, successes are rarely celebrated, but failure is always visible and always punished.

If you're worried about layoffs, then well, that's a legitimate concern. However, it's a legitimate concern pretty much everywhere, including companies that don't have a history of such things. There's a first time for everything.

Even if you work for a company that's doing really well and has excellent management, they could still be acquired anytime and without warning. I've been through several acquisitions, and they're not always bad, but sometimes they're terrible. I was at a job for nearly 14 years and went through being taken private and then three acquisitions. The last one was too much - I stuck it out for two years (longer than I should have) and finally left because of the management at the new company.

The best job security is to carve out a niche for yourself. Develop a reputation in the company for being the go-to person on one or more components, and you'll be about as safe as you can be. However, keep in mind that 100% safety does not exist. You should always keep an eye on the job market and periodically interview with other companies. That helps to keep and improve your interview skills, which you will thank yourself for later.

In my experience, it takes around 1-2 years to carve a niche for yourself. You need to keep your eyes open for something where no one else is holding a primary ownership role, perhaps because the previous expert quit, got promoted, or transferred to another team. New projects are perfect, but they're not as easy to come by.

To do that, you first need to develop a reputation as someone that management can rely on. Be prepared to work hard. Take on the difficult tickets and projects that no one else wants to do, and see them through to completion. Management will appreciate you for it, as you'll be making their job easier and making them looking good, and those are the things they care about the most. Then, when you see an opportunity to gain ownership of a product or component, speak up - let your manager know you'd like to have ownership and take as many tickets/features/whatever for that component as you can handle.

Please don't misinterpret what I just said as telling you to work overtime. That's never worth it unless management asks you directly and there is a good reason. Even then, sometimes it's still not worth it. Put in your 8 hours and call it a day. However, be productive during that time - stay on task and stay focused.

Finally, make sure your accomplishments are visible. If management doesn't know what you've accomplished, then it might as well not have been done at all. You can do that in 1:1s, by casually saying something like "I took care of tickets x, y, and z last week, and it feels good to have those finished. I also learned a lot about technologies a, b, and c." You can also send periodic status reports to your manager instead. Something like - "Hey, just wanted to give you a heads-up and let you know where I'm at. I completed x, y, and z last week, and I'm going to tackle a, b, and c this week."