Time to start thinking about your job hunt as a search optimization problem.
When I first got started in my career I created 10 email addresses and used them to make 10 accounts on Dice.com I made 10 very different versions of my resume and started tracking the types of companies I got responses from. If I had an interview I would take notes about the style of the interview at that company and I tweaked the resumes to try to get more responses from the types of companies I enjoyed interviewing with.
Code problems are rough, I've built some cool stuff in my day but the anxiety of a quick solve on something I have never seen before breaks my brain. How can I have a 4am miracle at 11am infront of a whiteboard.
I have a strategy that has helped me land several jobs I really enjoyed.
Be up front, tell the company ahead of time your sense is that you consistently fail to demonstrate your skills with these types of problems some companies might tell you to fuck off and that will be it. But some companies might find a different way to get what they want out of you.
Additionally do as many in person interviews as possible for parts of the field you aren't interested in. In 2015 I started doing a search and felt rusty, so I made a dev ops oriented resume and interviewed for like 30 dev ops jobs. I didn't want to work in Dev Ops I'm a data guy. But it's amazing how getting comfortable going in for an interview will make you better at the interviews you want to land.
Also as someone who has been a hiring manager I have observed a funny problem that people with CS degrees have. Most early career CS people are really boring there is very little character to who they are. They are essentially a product of the curriculum that taught them.
Go build some opinions on something thats not part of a bandwagon trend then find ways to bring it up in your interview. It will help you be more memorable.
I'm a Data Scientist but I love interrogating app developers about how they feel about authentication methods like JWT and I talk about the parts of Angular that impressed me and finally helped me break through into Javascript. I don't use those things as answers to questions I just bring them up as part of conversation during the interview. It demonstrates that you have depth and can contribute beyond being a ticket monkey.
When you said you knew X and the VP asked you if you y, z he didn't need you to know those things he just wanted to see if you were a one trick pony
if you had said
"I'm not familiar with y and z but I am really fascinated by v and w which I have studied on my own time can you tell me how y and z compare to v and w"
No matter how he responds you just go "Wow it would be really cool to get to work with you guys and see how you integrate y and z that sounds super interesting"
If a VP wont let that dialogue happen and they just want to power trip and interrogate you remember: the biggest mistake people make at car dealerships is forgetting that they can get up and walk out.
Its your job hunt take back the power.