Quote:
Originally Posted by suzzer99
I swear if you just graduated from college and went on job interviews you would think that creative uses of call and apply, and class-based vs. prototype-based vs. whatever other wonky types of inheritance came before ES6 - were the most important things you need to know to be a successful JS developer.
Interviewers have asked you a lot of questions that have marginal relevance to performing well as a developer during your job search. Also, interviewers have not posed many questions that are highly relevant to performing well as a developer. This pretty much?
You are an accomplished developer, can handle a lot of development challenges well, and are willing to engage as a productive team member. Communicating that well with interviewers is the challenge you face. Keep in mind that if organizations are doing well in assessing their needs, meeting their technical challenges in a timely manner, producing high quality software products and all that good stuff have a very good idea as to what they're looking for in trying to fill developer roles. Therefore their interviews are likely to be more relevant and interesting. I usually infer that an awkward, irrelevant questions are a sign that maybe things aren't going so well at a place looking to hire.
Developers want to have a job and get paid. Generally speaking, developers are willing to believe that they can help influence organizations where things aren't going so well to improve their ways. Put another way, developers that need a job and/or a change of scenery are willing to put up with a certain amount of crap. So taking a position at an organization that has problems is something developers often do. Ymmv.
I could write a book about train wrecks I've witnessed and how places dealt with them.