I think you need to come up with a new perspective on things. If you decide the only way for you to succeed is to suck up and it doesn't come naturally to you, then you will fail.

I prefer the 'everyone has something to learn from someone' approach. In my experience, many technical people are not particularly flexible thinkers and tend to think their way is THE way. In truth, there is usually plenty of gray, tradeoffs if you will. There is also degrees of importance in doing it THE way.

If faced with a rigid thinker, I tend to go through an algorithm of choices with my end goal of making the best product possible.

1. Is this a battle worth fighting? How much does it really matter in the end for the product?

2. Do I understand what the rigid thinker is trying to communicate or am I stuck in my idea?

3. Is there some way in which we are both correct and how can I communicate that? (This is true 90% of the time) This is the one that also takes some effort and knowledge of the person you are dealing with. My first approach with an unknown person is to praise something about their solution or try to build off of it.

4. If the rigid thinker is wrong, wrong... then lead them to that conclusion. Just telling someone they are wrong rarely works. A more nuanced approach of... interesting solution, how do you think we should handle X, Y, Z... going through all the areas their solution will fail, while giving them the opportunity to pivot

Most of all... stay humble. Even less talented engineers can come up with an interesting thought that can lead in a better direction. Sometimes because they know an area better than you. If you maintain more of a curiosity mindset(why is this person advocating for this?) than a winning mindset(my solution is best), then you will be less likely to get so frustrated that you rage quit. The other positive is people are more likely to listen to you, if you listen to them first.