|
Complete waste of time. They are written for people who believe that you don't actually have to know anything to do well in a technical role.
Interviewers don't use them to "set questions".
Interviewees that use them to "answer questions" come unstuck, either because the interviewer then follows up on the reply, or because they get the job and can't do it.
Some people seem to think that if you learn the list by heart, you'll get the job and are set for life.
Rubbish: as soon as an interviewer asks a supplementary question it's obvious you are parroting. And even if by a miracle you get the job, it will be immediately clear that you can't do it, and you'll be out on your ear with an embarrassing hole in your employment record.
Me? I'd dump the lot: articles, tips, blogs. All a total waste of good electrons.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I always start an interview with I don't know is an acceptable response sometimes it even reduces the bullshit drivelled up as a response.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
"I don't know" is a good response - it's honest, and it doesn't waste anybodies time. Ignorance can be cured, but stupidity and dishonesty almost never... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Should we not make CP little more better by cleansing such article by suggesting the author to rephrase it
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Rephased garbage is still garbage.
If the authors could write a tutorial, or anything that taught you useful stuff, they would have.
"Interview questions" is a cop out for "I know very little in depth, so here's some surface stuff that I read in books" IMHO.
If it was up to me, I'd delete the lot! But...it isn't up to me (which is probably a Good Thing)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Rephrase in a sense that removal of the "Interview" word.
I just read an article here about Code review interview questions. Its total BS. I really wanted to comment and say pull down this blog.
It would be interesting if he presented some common mistakes or findings from his experience. It was just a intelligent "reuse" of words from the internet.
In reality if you are experienced person you will be asked "How did you handle code review in your current job. Anything worth sharing about few reviews" or "what do you think of very rigorous code review on all the codes and its implication?"
For a newbie just out of college, Code review will be just a abstract concept and honestly he should answer that he did not experienced it.
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Trouble is that if you take out the word "interview" it's obvious that it's loosely related aphorisms about a subject with little or no real knowledge - and the authors don't want that.
I suspect that most of them are posted just to get an article count for a resume rather than for any "real" purpose.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: I suspect that most of them are posted just to get an article count for a resume rather than for any "real" purpose
Exactly, I can whip up an article in 10 min about the "Interview question for Reliability Engineering". Will it be useful? Nope.
I just feel bad that most of them in CP are from fellow Indians and ponder what is the state of recruitment going on there. I better stay here and return back when I have taken my boots off.
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
I only like one set of interview questions that I have read and liked was was from Scott Hanselman and all he gave was the questions, the learning and understanding came from you the reader.
the remainder are just *******
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
One interview I went to it turned out that they had used the same questions that I found via google two days earlier.
I got the job, however soon left as it was not the sort of place I wanted to work(not meeting the other developers at either of the interviews did give me a bad gut feeling and most people in the business appeared to be rather miserable) - the mere fact that they had taken questions off google showed how uninterested they were in recruiting the right person.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
I see Interview Questions as a nice refresher to prepare for an interview, but if I am giving the interview I will ask about their experience with that question.
For instance, if I ask someone what a delegate is and they are somewhat close, I will then ask them if they've used it in real life and to provide an example. By digging a little deeper, you can get a feel of their level.
I cannot go by someone's resume all the time, because half of the time it says architect.
|
|
|
|
|
Those "articles" are utterly useless.
I have had a couple of people in front of me interviewing for a C# job and give me canned answers. It's easy to sniff them out. The tone and cadence of their answer changes when you get on a question they've memorized and I do throw some of those questions in. But, simplify things and you really get a sense of what you're dealing with. I've had people not able to tell me the difference between "public" and "private". See ya! A lot of the people I interview don't even make it to the whiteboard to write some code.
It's frickin' sad that there are "schools" and hiring managers our there that think "any monkey can write code". Wrong! The monkeys outnumber the humans that know what they're doing 20 to 1.
|
|
|
|
|
Dave Kreskowiak wrote: It's frickin' sad that there are "schools" and hiring managers our there that think "any monkey can write code". Wrong! The monkeys outnumber the humans that know what they're doing 200 to 1.
Or more, judging by QA. 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
True. I haven't had the joy of interviewing anyone in the last 2 years.
|
|
|
|
|
|
My mum's favourite joke;
Why don't elephants have sex under water?
They can't take their trunks off.
Edit: Reported spam or abusive! You've gotta be f***ing kidding me.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
modified 28-Jul-15 8:13am.
|
|
|
|
|
CAn't be bothered to read them, but the best stupid joke is "What's brown and sticky? A stick!"
veni bibi saltavi
|
|
|
|
|
What's pink and hard?[^]
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
How do you find Will Smith in the snow?
Could so easily have gone wrong....
|
|
|
|
|
haha!
That's the point, I think! 
|
|
|
|
|
As the first one appears to be spectacularly inaccurate and not at all funny I didn't bother reading beyond it. If these are the best, what are the rest like?
|
|
|
|
|
Member 9082365 wrote: If these are the best, what are the rest like?
Better. 
Marc
|
|
|
|
|
Member 9082365 wrote: If these are the best, what are the rest like?
The first rule of Alzheimer's club, is don't talk about chess club.
Jeremy Falcon
|
|
|
|
|
Favorite:
Q: How do you think the unthinkable?
A: With an itheberg.
Software Zen: delete this;
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
