Prioritize some work you can tell good stories about in behavioral interviews.
If you have a conflict with a coworker, for example, that's something you will be asked about. Instead of avoiding it or getting louder about what you think, get together and see if you can learn what they value that it leading them to their conclusions. Echo back to them what you think it is until they feel like they've been seen and understood. Maybe invite them to collaborate on an experiment so the decision can be based on data instead of speculation, or reach out for coaching from someone you respect. Find boundaries that let you determine how you will behave, rather than trying to get someone else to behave the way you want them to. Or whatever other features of your conflict-resolution skills you want to practice.
"Technical decision making" is another common one: look for a place where there is more than one option, and figure out how to efficiently and effectively lead the team to consensus on a solution.
"Tell me about a time you saw a problem and were able to make it better" is another I've seen. Take up a thing you think your team could use more of, like tests or documentation or alerting or retros, and figure out what is making that hard to get done (one easy trick: try doing it. See what stops you.) Figure out who you need to get on board with trying something different.
If you can't get those experiences in your current role, consider finding a non-profit that needs some coding where you could have more autonomy & getting permission from your current employer to do some work there (on your personal equipment.)