Hour and half phone interview and 'bring some code'

[tim123]

1. Data protection doesn't apply to companies, only individuals.

I think the original poster meant "client confidentiality"

tim

[eyetie]

Bring some compiled code and read it out in hex.

Dom Joly would be *so* proud.

[swamp]

Bring some compiled code and read it out in hex.

[eyetie]

1. Data protection doesn't apply to companies, only individuals.

2. Following on from that, if anyone has code with details which clearly identifies an individual, they either need to edit it out or, most probably, look for an alternative career.

3. Ask them what they will be looking for e.g. examples of OO principles or design patterns. There may be a clue in the spec, Watson.

4. Good jobs are thinner on the ground than a coke can that's been sitting on the M25 middle lane since last Xmas. 1.5 hours is a long time but could be a good way to read your boss' mind before you decide whether you want to work for him.

5. www.xkcd.com/518

[thunderlizard]

Does it have to be your code? (or even if it does, how will they know..?)

Isn't it an opportunity to find some textbook interesting code, rather than client production stuff, and talk about the intricacies? Like the thing that uses an Interpreter pattern to suss out Roman numerals; or the XSL script that can solve a Sudoku?

[DS23]

...I find it impresses the hell out of clients when I start waffling on about it.

yeah right. how do you know they are pot noodling and/or rolling their eyes and moving their index fingers at their heads in a circular motion?

[moorfield]

I have a website with a few simple demo Java/J2EE apps running on a PC at home, specifically done for these kind of interviews. I find it impresses the hell out of clients when I start waffling on about it.

[Turion]

1.5 hours is very long for a phone interview. My longest was 1 hr, but normally 30mins max. Shortest was 3 mins, as the project was unsuitable. At least you do not have to waste time (and money) travelling so I'm a great fan of phone ints.

[ratewhore]

Shirley as a dev you can knock something up quickly (hell - you all cut and paste for a living anyway) then talk your way through it with confidence...

[jmo21]

YOU may have broken an NDA if you have some code from a previous job/client

[TheFaQQer]

It may well breach some kind of intellectual property / NDA rather than data protection law.

Knock up something in your own time to discuss, but how you are meant to do that over the phone, I don't know.

I wrote some utilities which are on my website, which I'm happy to discuss, but clients have never asked me for a code sample before.

Best of luck with the interview, if you go ahead.

[SirSickboy]

I've had to send in or demo code for some interviews in the past.

Usually I send in something i've written in my spare time a few years ago and follow it up with an explanation. As for at interview, i'm a web dev so i just demo the latest public app or site i've built. That way they can get an idea of how the app works and follow it up with questions on how i've built it.

[Shimano105]

I've got this lined up but I'm a bit thrown by the 'bring some code to go through' line.

First of all there will undoubtedly be a data protection issue if I take some clients code and go through it to a total stranger.

Second, 'some code' WTF? A tad vague methinks.

Is this standard practise these days or is it 10ft bargepole time?