> Bullet points on resumes that talk about non-specific day-to-day responsibilities are mostly filler. This. A co-worker interviewed a guy last week who had

> Bullet points on resumes that talk about non-specific day-to-day responsibilities are mostly filler. This. A co-worker interviewed a guy last week who had 3 pages full of bullet points and when he asked him about his experience with any of them, he gave us some generic response like, "We used Java on project X that did Y". List 6-7 core skills; or better yet, list projects you worked on, the stack you built it on, and a very brief summary of how you kicked ass on it. He has example projects on his site, which is great; most people don't even have that. When I go into an interview as a developer, I always go in with a running example of a project that I built, with source code. Towards the end of the interview I'll bring it up: "I brought along a project I built; I'd love to go through it quick with you." At which point I go through the UI to show what it does and then open up the code to review the architecture and anything clever I did within the code itself. Note that this all happens in about 5 minutes; no one wants to sit through a 30 minute demo.