>What should they include ? Languages, technologies used, with relative experience in each, as well as projects you've worked on and what YOU contributed. >Wh

>What should they include ? Languages, technologies used, with relative experience in each, as well as projects you've worked on and what YOU contributed. >What are the most common mistakes developers make when talking about themselves ? 1. Not being specific about what the 'team' achieved and what you contributed for a given project you're describing. 2. Listing too many things, if I want a specialist in one area you're damaging your chances if you come across as too much of an all rounder. There's value in being able to pick up new things, but you don't want to look like you only work on each thing for 6 months. >What do you look for ? Technical competency in the area I'm looking at (completed projects), followed by the ability to communicate what you've actually worked on to demonstrate you understand the design decisions and trade-offs and how it actually works. It's not a bad thing if you've just plugged module A into module B, but that's not something you should be spending time telling me about if there's nothing interesting you've done. >Are there things that can influence you favorably ? Good organisation of the information is key.