The 'Test' conundrum

[northernladuk]

Best if that works both ways I find

Old Greg would agree. He likes it both ways.

[SueEllen]

When you're working through an agency, who exactly do you think is your client? Your outlook is all wrong. The agency is contracting you for THEIR client, it's a simple thing that many IT Contractors struggle with. You have NO contract with OUR client.

Oddly other agents don't have a problem with me supplying references directly to the end-client. I expect it's because they want me to take the contract as well...

[oliverson]

I was of a similar mind.

Done a few in the past which just vanished into the ether, so to speak, but secured my most recent role off the back of having completed a fairly hefty programming test.

Depends what else you've got in your queue I guess....

Same here. These things come along once in a while but not too often. The test was a supposed hour or two but I spent a full day on it, on and off. Ordinarily I'd have avoided it but there market was very quiet and I'd just finished a role so I took the test on. In the face-to-face interview we got the code on the screen and I was asked about design decisions that were made. All in all it was a fair interview and the test was a fundamental part of the process rather than being just a barrier put before me. I landed the role and I'm actually there now so yes, it was worth my time. But similarly I've had some totally ridiculous requirements and I've knocked them back. You just have to weigh up what is being asked relative to what else you have on at that time.