Friday, 25 February 2011

Lessons learned from job hunting

These may be obvious, but I'm ranting on writing this to sum up some of my experiences of releasing my CV into the wild...


Vary greatly
Some understand technology terms, others just match acronyms from your cv.

Love to talk
Well I don't. Not about the same stuff another recruiter told me 5 minutes ago anyway!
Email me the job spec as I don't have to slip out the office to talk to you all.

Have poor geography skills

Guildford and Sutton might both be in Surrey, but they are 23 miles apart. These locations are not interchangeable on a job advert.
Similarly, look at my home counties location before contacting me about 2 week contracts in Edinburgh or Belfast.

Are sparing with the truth
Queue a couple of interviews where the job role and my requirements were vastly different.

Are pushy ****ers
Which part of 'I'm not interested' don't you understand?

WILL send your CV WITHOUT your permission.
Even when asked not to.

Like to post fictitious roles to attract CVs
One recruiter even admitted this.

Like to take their time...
In responding to your communication, even though they expect the opposite behaviour from you.

Are slow to respond to polite requests
How many times have I asked you to remove me from your system?

Obviously the above rant cannot be leveled at ALL recuiters. Sadly though there exists a young, commission hungry and unscrupulous element who let the rest down. Parallels with the reputation of estate agents can be drawn.

Is a very expensive place. To commute to, to travel around, to get lunch in.
Money to compensate this has got to be good.

Is a 'catch all' job title.

At 3 different roles, it has been  -
  1. Development focused
  2. Maintenance focused
  3. Architecture focused
Maybe I can forgive recruiters a little as duties range so wildly...

Anyway, I've signed a new contract for an exciting new challenge in April, so all the above is behind me.
Phew! Breath deeply, and relax....

1 comment:

thirtyfootscrew said...

Nice summary, on the DBA roles list I'd also add...

4. We don't know what one is but we think we need one.

... I've seen that once or twice.