I was first called by a product/project manager who asked me the typical questions. I told him that I didn't have a lot of hands on experience in the current web development stack, but that was fine for him as I was willing to learn. He wanted to take me in with less experience in that area because he liked the overall business experience I had and technical skills. They sent me an exercise to do, which I did (using these technologies), and was called for a face to face interview. At the face 2 face I was interviewed by 3 developers who were not communicated in any way that I wasn't an expert in web development (but apparently were expecting that). Even though I answered all the questions quite well in the refactoring phase and the presentation phase, I wasn't able to go much further in the web architecture phase, because I just don't have the knowledge yet. To me it felt that for this last thing they discarded me, it was pretty clear. I stressed out that my experience in that particular area wasn't that big but I was willing to learn (expressed for example by the exercise presented and general knowledge of tools, etc.), but that wasn't enough. I never met in person the product/project manager. I think the main drawback in the interview process is that the project/product area's desires didn't reach the actual interviewers, which are just developers, and they can easily discard a candidate just because he/she doesn't have a current level of expertise they expect or is written down in a preset interview process.