Reply to: Interview or consultation

[LondonManc]

It would depend on the role advertised and the spectrum of the questions asked.
If they've asked for five skill/experience areas and are focusing on only one, then they've probably got a specific issue. Fingers crossed you know how to solve it and tell them enough to convince them to hire you for it. If you're benched, it may be a week's work that can be slotted in and five more professional days that you can invoice for, as well as another satisfied client who can come back to you for repeat business.

[tomtom]

From my experience, I suspect some of empolyers are seriously considering hiring a contractor, Especially when whole interview is carried out with C/C++ test only, I would refuse further interview unless it is local.

[NotAllThere]

I doubt very much that many clients would go to the effort of arranging an interview just for some free consultancy.

[washed up contractor]

e.g. How do you find out a bug in some system?

Just tell them you test it by running various scenarios.

I see someone has suggested you tell them 'just enough' so they give you the job but dont tell them how to do the fix. Load of crap. Yes, theoretically but in practice you cannot because a persistent interviewer who wants the 'fix' will keep probing. And if you dont give the required answer will deduce you arent the one and move on to the next candidate.

At the end of the day it comes down to how much you want the job. If you're not prepared to travel 2 hours for an interview (I had to do this probably 80% of the time I was contracting), are you prepared to travel that distance for the work ie stay over or travel daily?

You cannot go around second guessing every client's attempting to get a dodgey cheap fix for their systems as it will just make you paranoid.

[northernladuk]

Ah.. So this is an actual interview you attended. I'm guessing it didn't go well and you are wondering what you did wrong?

[tomtom]

Yes, I was managing to answer this kind of questions carefully, But it ended up with not convincing them with details .

[WTFH]

If you're worried by this, surely the trick is not to give them enough information to actually solve the issue, but still give enough information demonstrating that you know how to solve the issue.

I'd go with this - give generic enough information demonstrating your knowledge. Do not ask them for specifics of the problem.
When you get to the end of your talk, then say to them that you have given an overview, and without going into the specific details, you can't give a more precise answer. When they ask you for more precise, let them know your rate.

If they give you a very specific problem, answer it generically. Also, maybe get them to give you a whiteboard and write your generic answer on it, make sure you fill the board and wipe it clear a few times during your answer. It's maybe also worthwhile wiping the board, writing up a few wrong bits and leaving them there for a few minutes, then saying "no, that's not the best way", and wipe them off. If anyone is taking notes, it will really annoy them.

[Hobosapien]

If you're worried by this, surely the trick is not to give them enough information to actually solve the issue, but still give enough information demonstrating that you know how to solve the issue.

Yep.

Nearest I've come to this is when during an interview they asking me to look at a system configuration that wasn't working as expected and wanted me to fix it. At that point it did cross my mind they'd only got me in to fix their problem so I told them what was wrong in high level detail but didn't fix it.

They seemed a bit put out, sort of confirming my suspicion, but they did try to offer me the contract a few days later. By then I had already secured a different contract by a telephone interview arranged on the way home from this one. Snooze and they lose.

[northernladuk]

if your leads help them fix the bugs, do they still hire you?

You are blowing this out of proportion.

It rarely happens, if there is a chance it will happen you've got to put the effort in to try and find out. How to do this has been explained. Up to you to make sure they don't make a chump out of you in the very unlikely event they want free consultancy.

If they do then you've got to chalk it down to experience and don't let it happen again.

You can't go round thinking there is some conspiracy every interview you have. If you can't cope with the methods of finding work as a contractor are you sure it's for you?

[tomtom]

if your leads help them fix the bugs, do they still hire you?

[gables]

If you're worried by this, surely the trick is not to give them enough information to actually solve the issue, but still give enough information demonstrating that you know how to solve the issue.

[WTFH]

It matters if you are asked to travel on your own for 2+ hours.

How far would you be prepared to travel for an interview?
Are you going through an agent, or going direct?
Have you asked the agent/client what the interview will be covering?
Is the job spec detailed or vague?
Is the contract one you might like, or are you desperate for work?
Why do you think it is not going to be an interview, but a free consultation?

[northernladuk]

It matters if you are asked to travel on your own for 2+ hours.

You could take your mum for the ride then?

[tomtom]

I thought you are losing your touch, when you didn't mention that in your first post

How long is the interview/consultation? If it's up to 1h does it really matter? Maybe it's both? Either way you make a (hopefully) good impression to a prospective client.

It matters if you are asked to travel on your own for 2+ hours.

[sal]

P.s. They aren't employers

I thought you are losing your touch, when you didn't mention that in your first post

How long is the interview/consultation? If it's up to 1h does it really matter? Maybe it's both? Either way you make a (hopefully) good impression to a prospective client.