[trymas]

> What helped enormously was studying the same questions that interviewers are likely to pull from. Once I studied hard on interview Q&A I went from no offers to getting three in the same week.

Interesting to hear on what are the sources 'that interviewers are likely to pull from'? And probably some guidelines as well, because interviewers like to be stingy and want to hear _the right_ answers.

[nrjdhsbsid]

Study google search results for "interview questions language X" with X being anything mentioned on the application. If js is listed expect things like the difference between == or === and whether variable declarations are hoisted for example.

Other questions I got were things like "can a static class be extended in language X" and other questions that test your trivia abilities but don't really matter when writing code 99% of the time. Like for js, everyone knows not to use == but most people don't know exactly why.

What I did was read several books on the language semantics for my top 2 languages cover to cover multiple times. The process was painful but I was prepared for nearly anything.

Answer quickly even if you might be wrong. Concise answers are perceived as more correct from what I've experienced.