I have a job interview coming up next week and I understand there is an open book test with some quick technical questions.
I've never done a open book test and I'm unsure as to what it involves.
views:
119answers:
6
+6
A:
I think it's a test that you're allowed to use books, maybe even internet help forums ect.
The problem - is that usually in this kind of tests the questions tests you ability to think, and not to "know" data, so the answer shouldn't be immateriality available.
Dani
2010-03-25 08:34:38
yep. If it is a closed book test (I had one last week), you are not allowed to use books or other sources. In an open book test, you are allowed to use your books.
Ralf
2010-03-25 08:36:37
That's what it meant when I was in school: Instead of "Right! Books closed and under the desk, here are the exam papers," it was "Right! Here are your exam papers. You can use your reference material, but not talk to one another."
T.J. Crowder
2010-03-25 08:36:43
These days in a general interview I don't see how books might help you.. you will be tested for speed, and knowledge, even if you accidentally get the right books, the time you waist on looking things you should know... will kill you test.
Dani
2010-03-25 14:23:50
A:
It sounds like a test in which you can use any book and, possibly, the internet.
The only problem I see is that they might expect you to bring the books. My books are weighty.
Daniel Daranas
2010-03-25 08:35:54
A:
I think it means that you have access to resources that will help you find the information you need - such as MSDN (for .NET development) text books etc.
They're designed to test that you have the ability to locate information effectively.
Andy Shellam
2010-03-25 08:35:55
A:
It means you are allowed to use resources. You do not need to remember everything.
Padmarag
2010-03-25 08:36:29
A:
As Dani said, an "open book test" is a test where you can use reference material, you don't have to have all of the knowledge in your head, you can look things up (what's the order of those arguments again?). It's a much more realistic way to see how a programmer works.
They'll be looking for how you approach the problem, what reference material you use, how you use it, that sort of thing. Best thing to do is pretend they're not there and get on with the work.
T.J. Crowder
2010-03-25 08:38:36
Oh jees, that sounds daunting. I hate technical tests, I always feel as though I've done so poor and the time always applies pressure.
2010-03-25 08:54:20
@user275074: Don't worry. I've been on the other side of this many times and it's not easy on the interviewer, either. :-) We're not looking for perfection, sometimes not even a functional result, we're looking at the person. Believe in yourself and your skills. If you go off the rails and realize it, say so and start again. Don't try to be someone you're not. All of that adds up to a good interviewee, and if they see that, good. If they don't, maybe you don't want to work with them.
T.J. Crowder
2010-03-25 09:08:36
@User275074 - to add to T.J words... you will be surprised how many "so called" programmers can't accomplish even a simple task, so as long as you know what you're doing, even if problem is not solve, this is what most places will look like. Personally I look on coding techniques, to figure out if the programmer is experience enough, I care less about solving the problem (although solving is always an advantage) - I'm saying - getting the job done is not the only parameter.
Dani
2010-03-25 14:27:44
A:
Hey mate. I've got a similar test with PHP next month. To complete the question, what were you asked?
PHPaul
2010-04-01 10:50:39