CV rewrite questions

[doodab]

1. A few years back I did a stint for a consultancy firm that no longer exists. Is it acceptable to name the end clients? At the moment I have "well known blue chip blah blah" and I think naming the end clients would look better. I don't want to list them as seperate engagements because the key point is that I developed a product that was sold to these end clients by the consultancy (or perhaps I should?)

2. How do you work out years experience of a particular skill? For example, if you have had a job where java was 80% of your workload for 5 years, that's 5 years experience, not 4, isn't it. How about if you have 5-6 years where C was 80% of your workload and then you've used it sporadically since then, perhaps 50% on some jobs, 20% on others and not at all on others. Is it acceptable to say e.g. 10 years discounting just the jobs where you didn't use it at all?

[Spacecadet]

1. A few years back I did a stint for a consultancy firm that no longer exists. Is it acceptable to name the end clients? At the moment I have "well known blue chip blah blah" and I think naming the end clients would look better. I don't want to list them as seperate engagements because the key point is that I developed a product that was sold to these end clients by the consultancy (or perhaps I should?)

I'm contracting for a consultancy at the moment and I've split the CV entry into the different end clients. Mainly because the end clients are household names and its unlikely that anyone would have heard of the consultancy.

I'm also fortunate that the main body of work for each end client was done in succession and under different contracts.

TBH there are no rules as to how you format this stuff on your CV
My last perm job, which lasted just under 5 years warranted 3 separate sections on my CV just to break it up as I change role in the company

[NotReallyButSeriously]

In my current situation I don't have a great deal of working history so I try to "beef up" my Cv with skills. I put things down like Windows Operating Systems - 10 years. If any one asks I say I've been using it for 10 years so I have 10 years experience in it.

To be honest though I don't see how years experience is relevant to anything. I think categorising skills as Basic, Intermediate or extensive is a better idea. Then if you've got something that you really want to stand up highlight it in red with alternate letters in blue & a flashing ants outline.

[doodab]

I'm contracting for a consultancy at the moment and I've split the CV entry into the different end clients. Mainly because the end clients are household names and its unlikely that anyone would have heard of the consultancy.

I'm also fortunate that the main body of work for each end client was done in succession and under different contracts.

Yeah, that's sort of my problem, if I go with separate clients then 5 household names in 18 months doesn't look so good IMO and I can't easily say I developed this product from conception to realization, was tech lead of the development and various implementation teams, did the technical pre-sales stuff with the worlds largest defense contractor and so on. And I want that sort of "yes, I deal with big companies from start to finish" experience on there.

[doodab]

Then if you've got something that you really want to stand up highlight it in red with alternate letters in blue & a flashing ants outline.

Yeah, a bit of graphic design goes a long way. Most of the numpties that read them don't understand the actual words

[Spacecadet]

Yeah, that's sort of my problem, if I go with separate clients then 5 household names in 18 months doesn't look so good IMO and I can't easily say I developed this product from conception to realization, was tech lead of the development and various implementation teams, did the technical pre-sales stuff with the worlds largest defense contractor and so on. And I want that sort of "yes, I deal with big companies from start to finish" experience on there.

Then pick the main 2/3 that you spent the most time with or at least could talk the most about.
Alternatively, give the end clients sub headings under the umbrella of the consultancy.

Like I said, apart from not telling lies, there are no hard and fast rules about CV's. It's a sales tool end of.
Just don't be caught bulltulipting

[Spacecadet]

In my current situation I don't have a great deal of working history so I try to "beef up" my Cv with skills. I put things down like Windows Operating Systems - 10 years. If any one asks I say I've been using it for 10 years so I have 10 years experience in it.

I helped interview someone recently, the guy we interviewed had 10 years experience. But that experience was limited. So yeah, he had 10 years experience but it was clearly almost worthless.
2 years hard experience is better than a lifetime of mediocre button pushing

[TheFaQQer]

1. A few years back I did a stint for a consultancy firm that no longer exists. Is it acceptable to name the end clients? At the moment I have "well known blue chip blah blah" and I think naming the end clients would look better. I don't want to list them as seperate engagements because the key point is that I developed a product that was sold to these end clients by the consultancy (or perhaps I should?)

I would mention names, unless you were under an NDA. I've worked permie and contract for consultancies and tend to name both where it helps (e.g. Accidenture Consulting - Enron). If the end-client isn't big enough, then make it vague and tell people it's an NDA but name the consultancy.

2. How do you work out years experience of a particular skill? For example, if you have had a job where java was 80% of your workload for 5 years, that's 5 years experience, not 4, isn't it. How about if you have 5-6 years where C was 80% of your workload and then you've used it sporadically since then, perhaps 50% on some jobs, 20% on others and not at all on others. Is it acceptable to say e.g. 10 years discounting just the jobs where you didn't use it at all?

I don't quote years of experience on my CV. If it's something that you haven't touched for a while, but want the gig and reckon you can do it, then you can blag a little, e.g. "How long have you been doing PL/SQL? Well, my first role was in 1995..."

[SueEllen]

I don't quote years of experience on my CV. If it's something that you haven't touched for a while, but want the gig and reckon you can do it, then you can blag a little, e.g. "How long have you been doing PL/SQL? Well, my first role was in 1995..."

WHS

If an client via an agent wants years of experience then they tend to email you the page with those questions on.

Plus with my CV formats it makes it easier to move around, add or remove skills quickly to match the role description and email it to the agent.

[doodab]

WHS

If an client via an agent wants years of experience then they tend to email you the page with those questions on.

Plus with my CV formats it makes it easier to move around, add or remove skills quickly to match the role description and email it to the agent.

I suppose I could list technologies with roles and let them draw their own conclusions.