- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Admin
Admin
Admin
Interviewing is a totally different skill from actually doing the job and I would have stayed for the practice.
Admin
I am surprised JAVA doesn't come with a square root function. I thought all these new flash-in-the-pan modern languages were supposed to have all the bells and whistles.
Yet another case where I would shine in an interview, possibly even convincing the company to undergo an organizational switch to a real programming language in the process.
Admin
Perhaps he wanted to know if that last fellow knew anything about how algorithms are actually created. Since anybody who knows what a square root actually is should be able to create an algorithm to approximate one to any desired precision in about ten seconds.
Admin
If you are trying to program your way out of a zombie apocalypse, you probably have a heck of a lot of code to write, and you'd better get it done NOW NOW NOW!
Plus you might not want to venture outside to go the bookstore.
Admin
Yeah. I mean tell them you don't know a formula but it's clear they want you to try and figure it out. This isn't a dumb "how many piano tuners are there" question, but an attempt to see if you can do maths.
Admin
How can you possibly answer interview questions if you treat them like production code? It's a bizarre standard, but suddenly everyone pulls it out because some guy was asked how he'd implement a library function.
Admin
I found out much later that I knew someone in another department at that company, and walking away from this person (interviewer) was absolutely the right thing to do.
Admin
Snoofle quit his job‽?
Admin
Bookstore is one of the places you want to go in an apocalypse. It's not a priority but with no internet it'll be pretty useful in the longterm to get books on basic medicine and electronics, etc.
Admin
Please show me how to use those built-in instructions in a Java program.
Admin
Admin
None of my computer science teachers ever told me that programming was about math. Where did you get that idea? However, I'd expect candidates to have at least completed high school.
BTW, “I've been programming for 30 years” doesn't impress me. I've worked with people with as much experience as you or more who were still totally incompetent.
Admin
√2
See, that was not soo difficult, or was it?
Admin
Weird -- that was exactly what I thought up after I read that. It's a crappy, but simple as...
Admin
The interviewer doesn't want to know how the candidate thinks he would react to a problem outside of his training. The interviewer wants to know how the candidate would actually react. Apparently in this case it's to rage out of the office.
I'd love to see his take on the Kobiyashi Maru.
("Interview 2.0"? Problems like that have been a standard part of technical interviews for decades.)
Admin
For the last one, I think it was a fail on both parts. The interviewer should've known when to cut his losses and tried a different tact. But the interviewee is obviously a bit of a prima donna without patience. His side of the story is the interviewer was being unreasonable but to the interviewer he wasn't answering the question, just deflecting it. The interviewer probably told his co-workers about the bullet they just dodged in the guy who would have trouble holding down a job if he didn't curb the attitude. Truth is they're probably better off without each other.
Admin
Admin
Back in 1994, the programmers responsible for maintaining a legacy ERP systems asked me how to calculate the cubic root of a number, because they were using COBOL and apparently they didn't have a math library available. I explained them how to do that using Newton's approximation, which was good enough for the problem at hand.
In my experience, being completely unable to handle this kind of problem without using a library function is not something I'd like to see in my fellow team members.
Admin
Actually, it was a test to see how patient and creative you are when your superiors give you completely unrealistic project specs. Which happens often at many, many employers.
Admin
"Now you've done it and insulted sqrt(2), claiming that it does not even exist."
Yeah, you don't want to piss of sqrt(2). He's been working out. Stomach crunches mostly. His physique is completely ab-surd.
Admin
Yes, Interview 2.0 questions have been around for a long time; but they've been mostly pointless for a long time too.
I have found, mostly through sheer repetition, that certain things done by interviewers during an interview are (at least in my case) pretty good indicators that I don't want the job. I used to try my darnedest to answer such questions, only to get the job and realize I should have run away. After a while, you just learn to recognize the clues.
Does it apply in every situation? Of course not. Are there times when I will try and answer such questions? That depends on how they are framed.
But just because you're in an interview doesn't mean you should put up with pointlessness. It wastes your time, tells you a great deal about the interviewer and possibly what the job would be like were you to accidentally get it. It's not an absolute rule, but at least in my own experience, is usually a reasonably reliable indicator.
Admin
It's also amazing how differently people perceive the same interaction.
Last time I was on the interview trail, a person asked how to reverse the characters in a string (C#, asp.net). I suggested using String.reverse.
"Well, what if that wasn't available?"...We then talked a bit about creating a method to do so, null-checking, what's their requirements for a cases like that or empty string. I may have even mentioned extension methods to avoid the null problem.
Anyway, I got home, called the recruiter and said that I didn't think it had gone very well, as the interview just kind of ended after that.
Twenty minutes later, she called back and said they loved me, asking if I had time that afternoon to meet with the VP-type guy for a final interview.
Strange how I thought that part went really badly, and they thought it went well, apparently. Never thought that they might be going for, "does this guy not reinvent the wheel?" until I saw snoofle++'s answer.
Admin
Admin
Admin
BTW, I imagine the dialog would have continued like this: Me: I'd try to remember or work out Newton's formula. Interviewer: Assume Newton was never born. Me: Then we wouldn't be here.
Admin
That could get interesting, what if this turned into something more? Would Siri go out on a date with it?
Admin
No, they were able to ask an expensive consultant ;-)
Well, maybe something along the lines of "approximation" would have been good enough for an answer. Just walking away is a sign of a short-tempered personality, you should work on it.
Admin
Sorry, Jeff, but we have some lovely parting gifts for you!
Admin
Admin
Assume you weren't even asked the question and this interview isn't actually happening. You are back at home. A path leads to the North and the South.
Admin
Usually, the walking-away is in response to more than one warning sign. This was just the last bit of pointlessness I was willing to tolerate. The previous questions all caused alarms.
As I said earlier, it turned out that my PHB-radar was dead-on with this guy.
Besides, if I had taken that job, I wouldn't be working HERE!
Admin
The neverending "you can't win" questions always remind me of the bear joke.
"Hey, Jim, what would you do if you were in the forest and you met a bear?" "I'd back away slowly." "But it's mad, it attacks you!" "I shoot it." "You don't have a gun!" "I run away." "It runs faster than you!" "I climb a tree." "It climbs better than you!" "I jump in the river." "It swims faster than you!!" "Listen, Mike, whose side are you on, mine or the bear's?"
And the punchline variation:
"I'd hide." "It's much better than you at hiding and you'll never find it again!"
Admin
The WTF in the square root of stupid is that the candidate didn't understand that one workable solution (that doesn't involve a formula) would be an algorithm based around recursion. I think the interviewer learned more than the interviewee.
Admin
Au contraire: some of us are proud of the fact that we do not suffer fools gladly. Sometimes this can hurt a fools feelings. Isnt life tragic?
Admin
And the other punchline variation:
"Id pick up a handful of shit and fling it at the bear." "What if there is no shit?" "There will be!"
Admin
I had a similar experience when interviewing for a job after graduation.
At school we'd learned to use those automated design tools with round-trip code generation. Rational Rose being the prime example.
In the job interview, they asked me what I thought about tools like that. I had listed it on my resume, and they used it within the company.
So I was honest. I told them I didn't think they were very practical beyond "toy" scale projects. They were great for academia but I didn't feel they would be useful beyond a very general design session. Often you realize mid-way through coding that the design you drew out just isn't going to work, and you need to redo things. Change method names, change class relationships. Trying to "round trip" between the design tool and your code IDE would take too long. Better to hash out the broad-strokes design in the tool, then code and test, and then when things are relatively stable, reverse-engineer from the code to generate your final UML diagrams for the documentation.
I was bracing for the worst, but everyone in the room was smiling. Apparently I had just described their exact frustrations with the new processes being pushed down from upper management. They were impressed that my answer was realistic, well-reasoned, that I didn't completely trash-talk the tool or its usefulness, nor did I unrealistically embrace it.
I got the job!
Admin
Am I crazy, or could you not have just done this? Math.pow(x, 0.5)
Admin
Admin
If the interviewer is using his communications skills at full throttle, then I certainly wouldn't like to work with/for him! If that's his best about explaining the requirements, I cannoy imagine what kinf of hell he makes for others when he's workign with a real project.
Admin
Admin
For those who still don't see the WTFery of the square root thing, how about this. A guy is interviewing to be a carpenter.
Interviewer: If you had to put two pieces of wood together, how would you do it? Carpenter: I guess I could nail them together, or maybe glue. I: But what if you didn't have any nails or glue? C: I'd go out to Home-O-Rama and buy some. I: But what if there was no Home-O-Rama? C: Then I'd go to a hardware store. I: But what if there were no such thing as nails or glue? How would you make them? C: Can I have some of what you're smoking?
Yeah, maybe he could have come up with a different question, but using square root as the subject was like asking a carpenter how he would make nails if they hadn't been invented yet.
Besides, how many of you even use square roots in your day-to-day work? I've been programming for decades and never had to do something that used square roots.
Admin
The ancient Babylonians had a square root algorithm:
This series converges on sqrt(x).
If that doesn't shut him up, leave.
Admin
The real WTF is expecting someone to come up with a square root function during an interview. Maybe some people could remember enough about it to figure it out, but I'd say that candidate's answers were perfect. Is the next question going to require the candidate to invent calculus on the spot too?
Admin
Admin
Admin
More import would be an attempt to see if you write proper Englishes.
Admin