Not being "100% tech bro" is usually a positive. Assuming your technical skills are where you say they are, I would focus on your communication and making sure

Not being "100% tech bro" is usually a positive. Assuming your technical skills are where you say they are, I would focus on your communication and making sure you are able to clearly verbalize your thought processes in an interview. Having just this post to go by, I notice you don't use proper grammar or punctuation when you write. You also use many run-on sentences, as if you're just spewing out what is in your head before formulating it clearly. But I know HN is not a formal place, so maybe this is not how you write in professional communication. Do you feel that you can confidently express what is in your head when faced with a question during an interview? Do you put effort into writing professionally when communicating with potential employers through email? Another thing that stuck out at me in your post: being able to "confuse" experienced devs with things is not usually a good thing. As a senior, you need to be able to communicate and explain concepts clearly in a way that is _not_ confusing to people. Finally, a question: since you are applying for a senior position, I am guessing you already have a few years of junior and mid-level jobs under your belt. Is that a correct assumption?