|
|
|
|
|
by Sukotto
5696 days ago
|
|
Personally I think resume's are loads of crap and I do my best to avoid giving them out. I find it a much better strategy to talk about what problems a manager is facing and how my joining the team will help resolve those problems. To answer your question though... Try to quantify what kind of impact your work had to either the top or bottom line and avoid talking down the team or technology used. Barring that, talk about what kinds of problems the project solved and what it helped the team/group/company accomplish. If you can't even do that, then I would just mention the workplace and job title and talk up other parts of your history and/or skill set |
|
This. I have a short list of 3-4 references and 3-4 gigs that I've done that I use with all my potential new clients. This covers pretty much any scenario I have the capability to handle on my own. Aside from that, I don't much advertise my other work unless it applies. I'd rather talk about the potential new client's issues and how I've dealt with them in the past, in specifics, than talk of a job gone wrong that has nothing to do with their need.