There are a couple reasons that you might be getting bad candidates. Since you are working for a large company, you will be getting candidates who are more int

There are a couple reasons that you might be getting bad candidates. Since you are working for a large company, you will be getting candidates who are more interested in stability then anything else. i.e. your 9-5ers. Your posting could just be to generic and focused on Java. i.e. throw some of the other technologies that you use into the job posting, JSP, Tiles, Struts, Ajax, etc. Hopefully the candidates will have some experience in the full stack then. Secondly, be picky on who gets through your candidate selection. My process was to scan their resume for keywords that showed me they had experience in what I wanted (the full stack). I would then have HR ask them 10 tech questions over the phone. If they seemed to do alright with that I would have them brought in. The very first thing they did was take a technical test based upon the desired skill for the job. If they passed I would meet with them, if not I would send them packing. The key is to not waste your time on interviewing all the 'ok' people but interview only the good people. You have to have them jump through some hoops before you meet them face to face.