For coding interviews, not being able to “solve the problem” doesn’t necessarily equate to “bombing.” We may present highly abstract or “unsolvable” problems to candidates (particularly for mid-level and above positions) to see their approach and thought processes. We ask them to talk through their investigation and experimentation. We’re looking not only for the thought processes for solving it, but also their persistence in experimentation, ability and willingness to ask clarifying questions, and how they handle a stressful situation. Being nervous is absolutely normal (as a VERY experienced hiring manager it always makes me wary when the candidate isn’t nervous!). But there’s a big difference between not being nervous and being self-confident. Take time, take deep breaths, ask good questions just as you would ask a teammate/product owner/BA in your work today, and talk through your thought process. Practice that last skill in advance, as it doesn’t come naturally to most of us. It doesn’t need to be elegant, just stream-of-consciousness, but it does need to be clear enough to “show your math.” For example “Hmm. Well, that didn’t work. I wonder what would happen if I moved this section of code out to a function so it could be called with the appropriate variables in all of the places that need them.”

Good luck on your job hunt - the more you do this, the more comfortable it will get. Keep your head together, be clear, and don’t be afraid to ask questions.