RSS feed [root] /jobs /weblog /career



title search:


Tue Jun 27 17:11:29 HKT 2017

interviewer tip

The best way I've found to interview candidate developers is to pair program with them to do real work on the actual code of the project that is hiring. If not possible, give programming exercise which is:

The exercise must involve working with current development tools.
The exercise must require the candidate to apply important features of the language.
The exercise must involve understanding and working with existing code.
The exercise must involve error handling.
The exercise must involve testing.
The exercise must offer scope for domain modelling.
The exercise must involve asking questions.
The exercise must be realistic.
The exercise must involve changing requirements.
The exercise must offer the candidate enough rope to hang themselves.
The exercise must test many different skills and practices.

A good interview programming exercise takes at least an hour. -

The other interesting reading -[..]ass-kickin-interviewscreening-questions/

Phone interview -

Questions that somebody like to ask... although I think this guy is a bit arrogance -[..]y-favorite-java-developer-interview.html

Another interview question and answer -[..]/howto-pass-silicon-valley-software.html

How about lie at CV?[..]mon?entry=lying_on_your_r%C3%A9sum%C3%A9

Interviewing in google -

What interviewee should asked at interview -[..]programmer-should-ask-on-a-job-interview

What should not waste time to ask the candidate -[..]303_use-technique-ace-job-interview.html

Beware of the small things during interview -

The concern of putting negotiable in salary -

how-to-carry-out-technical-recruitment -[..]s/how-to-carry-out-technical-recruitment[..]ing-Process-is-your-engineering-process/

(google search) (amazon search)
download zip of files only