Yeah, depending on what layer they are looking at candidates for, services vs web vs backend DB. We tend to ask different question sets. At the bare minimum be able to back up any experience you claim to have with any frameworks, and best practices around development in those areas.
If they are a small team and they expect everyone to work on all of the layers, then they may make you write a small service to do 'X'. Or/and to add a presentation layer to it as well.
It depends on how much time is scheduled for the interview.
A lot of our technical questions were around intricate areas of the specific language to weed out people that just had minimal exposure to it..
Additionally we only did side questions on anything in your CE, if we saw the candidate did not have the specific language or experience we were looking for and we were asking to understand if they had the foundation and logic to be groomed into the position. Otherwise the questions and exercises were very pointed to the skill set we were looking for.
Of course they are also the oddball interviews where the exercise is more generic to test logic skills, etc. But that is mostly done by newer companies, not ones that have been established for decades.
Regardless good luck.
