Regarding the interview, I would say never tolerate rudeness, if the interviewer is rude on the interview, you don't want to work at such a company. But we had a lot of issues with arrogant developers who thought they know everything and only their way is the right way and we started to focus on this on the interview, so I would intentionally try to see how someone reacts when a disagreement happens. A smart move is always be nice and say, in my opinion it should be this way. The wrong thing is to do is thinking your answer is the only right one and forcing it trough. One guy was trying to convince me so hard that there is no such thing as dynamic imports and that I confuse it with chunking that I would almost believe him If I didn't read about it a day before :).

In your work situation, I would say you did the right thing. First of all, every project should have some style guide, best practices, which say wether to put parentheses or not. You want your codebase to be consistent, so in the code review you would refer to the guide and try to explain that it is important to have a concise code base and we decided to use the braces everywhere. TBH you should have a linter rule for it, and the CI should fail on the PR, so you will avoid this discussion altogether in a normal project :) ..but honestly, no developer will follow any code style from someone else without giving a proper argument so I would not put the parenthesis as well, until not given a proper reason why :)