When evaluating senior level and up developers, I look for a mandatory quality -- opinionated but open.
You need to be opinionated in choosing your technology, and often this falls down to "I am most comfortable with and have the most experience with X". In the current technology ecosystem, there are thousands of competing language/framework/database/ops choices. Many will have overlapping pros/cons, and you may never reach the corner cases that distinguish them. When that is the case, experience will give you a gut feeling, and you should stick with this feeling. Additionally, you should usually give preference to the tools you have used before as that will reduce implementation time and trouble, as well as increase efficiency. That's being opinionated.
However, you must always be able to back your reasoning with facts. "X is good for this project because." If you can't do that, then your opinion is uninformed and not useful. Additionally, you must always be open to there being a Y that is categorically better than X for the task. And if someone brings that to your attention, and has a good rationale, and the cost and time of implementing Y is within the projects budgets, you must be open to using Y. That's being open.
So when someone questions why I use X, I do not hesitate to say it's because I prefer X, and I think X is good for this project because of factors A, B, and C. If someone says "Y would be better than X here", I'll listen to their justification and weigh the cost of learning Y. If it's convincing, I'll give Y a shot (after doing my due diligence). Having a large toolbox at your disposal is invaluable, but there's simply too many tools in tech now to be able to learn them all. Pick ones you like using (or at least are the least hateful of the choices you have -- Ansible, looking at you), and be open to learning something new if there's a very compelling reason to do so.