For starters, I’m honored to be summoned at the same time as the amazing @deprecated. Thank you, @HAWK for thinking of me.
As always, Joe has hit the nail right on the head. There’s no way to tell what will be asked, and there’s little value in cramming for any kind of test, interviews included.
If you’re worried about your technical knowledge, perhaps a better use of your time would be spending it thinking about how you’ll respond to questions you can’t answer. And let’s face it: go to enough interviews, and there will be questions you can’t answer.
I always follow a few rules when I’m asked a question at an interview I can’t answer:
- Be honest-- nothing is more damning than trying to BS an answer.
- Explain what background knowledge I have.
- Explain how I’d go about finding an answer to the question (resources, people, etc.)
The pressure to be omnipotent is often self-inflicted. Having a process and resources available to learn new skills and concepts within our industry is essential, especially given the constantly-shifting nature of our work.