JackH barfed: [QUOTE] message om... Ok, well to be more specific, it's for a programming role. I've not been in the game for a while, but they're looking for people primarily with AS400 RPG skills, something which whilst most who know how to do structured programming could pick up with ease, isn't exactly the most common of systems / programming languages to have direct experience and training (1) in. So... given I've been doing 'other', largely irrelevant to this particular type of role things for a living for a while, what I want to know is, how indepth do I go into my previous experience in this game, as in, on the last CV I did, I was told by one person that they thought I'd gone into a bit too much depth about some of the actual projects I'd undertake. That, and I've normally structured my CV chronologically - which means the stuff they'll actually be interested in, will be buried away from the first page... and it doesn't seem all that orthodox to me, to not list it in this way. Sorry if some of this seems a bit 'duh'... it's just these jobs rarely come up down this neck of the woods, and I'd really like to make sure I give myself the best possible chance to at least get a foot in the interviewing process door, without falling at the first hurdle. Ta for all the other advice given in this thread so far. :-) (1) Inhouse, and IBM courses. [/QUOTE] I'd summarise all recent and non relevant experience from current, back to the relevant stuff, expand that but don't write detailed explanations about it all, just summarise all important stuff. I like to do bullet points on all major points, then write a paragraph containing a little info about each bullet point, then use that paragraph in the CV. It draws their attention to the right part, and gives them just enough info so they'll be interested and want to know more, and hence call you in for an interview.
