POV-Ray : Newsgroups : povray.off-topic : Interesting interview questions Server Time
8 Oct 2024 17:14:45 EDT (-0400)
  Interesting interview questions (Message 14 to 23 of 63)  
<<< Previous 10 Messages Goto Latest 10 Messages Next 10 Messages >>>
From: Jim Henderson
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 18:19:25
Message: <4b578f7d$1@news.povray.org>
On Wed, 20 Jan 2010 09:15:50 -0500, Warp wrote:

>   However, from a practical point of view those pragmatic answers are
> much, much better than any convoluted answer you could come up with.
> Why? Because if you come up with a convoluted answer it shows that you
> tend to come up with convoluted solutions to simple problems, rather
> than doing the practical thing and just consult a manual or other source
> which *already* knows the answer, which would be the best thing to do in
> a practical situation in the job.

Except that often times in the real world the answers aren't so 
straightforward, and some creativity is being figured.  The answer to the 
question isn't important, it's how you got there.  I do agree that on 
their own they're not useful, but in conjunction with other questions 
(both "interesting" questions and "non-interesting" questions) can tell a 
lot about the candidate.

Jim


Post a reply to this message

From: Darren New
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 19:27:07
Message: <4b579f5b$1@news.povray.org>
Jim Henderson wrote:
> On Wed, 20 Jan 2010 08:11:28 -0800, Darren New wrote:
> 
>> Warp wrote:
>>>   I have hard time parsing that question.
>> It *is* messed up. The usual question is something like
>>
>> You have a race two miles long. For the first mile, one car goes 60MPH
>> and the other goes 30MPH. How fast does the other car have to go to
>> finish the race at the same time as the one going 60MPH?
> 
> Even then it doesn't parse correctly, because they've given you the 
> speeds for both cars - so asking how fast the slower car should go 
> doesn't make sense, because you've been told how fast it is going.

The race is two miles long. The slow car goes at a speed for one mile. 
What's the speed in the second mile?

(I guess I left out that the fast car keeps going the same speed.)

> And I'm not sure that discarding the length of the track allows the 
> question to be answered even then. 

No, that would eliminate the ability to answer.

Anyway, that's an easy question to answer. A slightly better version is this:

You want to average 60MPH over two minutes. You go 30MPH for the first mile. 
How fast do you have to go to average 60MPH for two minues?

Second alternate question: you want to average 60 MPH. You drive 10 miles at 
30MPH. How many miles do you need to drive at 90MPH to average 60MPH?

-- 
Darren New, San Diego CA, USA (PST)
   Forget "focus follows mouse." When do
   I get "focus follows gaze"?


Post a reply to this message

From: Darren New
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 19:28:45
Message: <4b579fbd$1@news.povray.org>
scott wrote:
> http://www.glassdoor.com/blog/top-oddball-interview-questions-2009
> 
> A lot of them seem like genuinely useful questions to ask candidates, 

Google had a lot of these kinds of questions. Stuff like "how can you 
determine how big a machine's cache is?"

I couldn't figure out if they wanted a program to measure the timing of 
something assuming different cache sizes and look for the step in the 
timing, or "look it up in the x86 instruction set manual".

-- 
Darren New, San Diego CA, USA (PST)
   Forget "focus follows mouse." When do
   I get "focus follows gaze"?


Post a reply to this message

From: Darren New
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 19:33:45
Message: <4b57a0e9@news.povray.org>
scott wrote:
> http://www.glassdoor.com/blog/top-oddball-interview-questions-2009


As for delightfully fun puzzles I got at an interview, I got this one:


You have an infinitely long line. Two robots are dropped on parachutes onto 
the line at random, and each drops its parachute (leaving it behind) where 
it lands. Your task is to crash the two robots into each other.

Each robot runs the identical program starting at the beginning, and the 
parachutes are identical, and they are in all ways identical other than 
where they land, which is random.

You have the following instructions available for programming the robots:

Move the robot one step left.

Move the robot one step right.

Move the instruction pointer to a particular instruction (i.e., "goto")

Skip the following instruction if you're standing on a parachute.

-- 
Darren New, San Diego CA, USA (PST)
   Forget "focus follows mouse." When do
   I get "focus follows gaze"?


Post a reply to this message

From: Jim Henderson
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 19:34:13
Message: <4b57a105@news.povray.org>
On Wed, 20 Jan 2010 16:27:06 -0800, Darren New wrote:

> Jim Henderson wrote:
>> On Wed, 20 Jan 2010 08:11:28 -0800, Darren New wrote:
>> 
>>> Warp wrote:
>>>>   I have hard time parsing that question.
>>> It *is* messed up. The usual question is something like
>>>
>>> You have a race two miles long. For the first mile, one car goes 60MPH
>>> and the other goes 30MPH. How fast does the other car have to go to
>>> finish the race at the same time as the one going 60MPH?
>> 
>> Even then it doesn't parse correctly, because they've given you the
>> speeds for both cars - so asking how fast the slower car should go
>> doesn't make sense, because you've been told how fast it is going.
> 
> The race is two miles long. The slow car goes at a speed for one mile.
> What's the speed in the second mile?

That makes more sense - but fairly easy to answer algebraically.

> (I guess I left out that the fast car keeps going the same speed.)
> 
>> And I'm not sure that discarding the length of the track allows the
>> question to be answered even then.
> 
> No, that would eliminate the ability to answer.

How so?  If you know the distances and speeds, then the time at which 
both cars reaches the end of the distance becomes a solvable problem.

> Anyway, that's an easy question to answer. A slightly better version is
> this:
> 
> You want to average 60MPH over two minutes. You go 30MPH for the first
> mile. How fast do you have to go to average 60MPH for two minues?
> 
> Second alternate question: you want to average 60 MPH. You drive 10
> miles at 30MPH. How many miles do you need to drive at 90MPH to average
> 60MPH?

I agree, that question formulation would be easier to answer.

Jim


Post a reply to this message

From: Warp
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 19:41:36
Message: <4b57a2c0@news.povray.org>
Darren New <dne### [at] sanrrcom> wrote:
> Jim Henderson wrote:
> > On Wed, 20 Jan 2010 08:11:28 -0800, Darren New wrote:
> > 
> >> Warp wrote:
> >>>   I have hard time parsing that question.
> >> It *is* messed up. The usual question is something like
> >>
> >> You have a race two miles long. For the first mile, one car goes 60MPH
> >> and the other goes 30MPH. How fast does the other car have to go to
> >> finish the race at the same time as the one going 60MPH?
> > 
> > Even then it doesn't parse correctly, because they've given you the 
> > speeds for both cars - so asking how fast the slower car should go 
> > doesn't make sense, because you've been told how fast it is going.

> The race is two miles long. The slow car goes at a speed for one mile. 
> What's the speed in the second mile?

  I understood it to mean "when the faster car hits the one mile mark,
how fast should the slower car go from that point forward in order to
catch up and get to the finish line at the same time as the faster car"
(which is an interesting question).

  However, if it really meant "when the *slower* car hits the one mile
mark, how fast must it go from that point forward to catch up" it becomes
a trick question (because the faster car has already reached the finish
line by that point).

> Anyway, that's an easy question to answer. A slightly better version is this:

> You want to average 60MPH over two minutes. You go 30MPH for the first mile. 
> How fast do you have to go to average 60MPH for two minues?

> Second alternate question: you want to average 60 MPH. You drive 10 miles at 
> 30MPH. How many miles do you need to drive at 90MPH to average 60MPH?

  I like this version of two things going at different speeds more (I don't
remember the *exact* setup, so I'll just invent the numbers):

  A man and a dog are walking home, which is at a distance of 1 mile.
The man walks at 3 mph. The dog start running at 10 mph towards home.
When it reaches it, it turns around and runs back to the man (keeping
the 10 mph velocity at all times), then turns around and runs to home,
and so on, until the man reaches home. What's the total distance that
the dog ran?

  The problem sounds like you would need to calculate an infinite sum,
but there's actually a much simpler solution.

  (There's also an anecdote of this problem having been given to some
mathematician (don't remember name), and him giving the answer almost
immediately. The person who posed the problem then remarked that "ah,
you figured out pretty fast that you don't need an infinite sum to get
the answer, but that there's a much simpler way", to which the mathematician
responded "what? I *did* use an infinite sum".)

-- 
                                                          - Warp


Post a reply to this message

From: Jim Henderson
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 19:52:18
Message: <4b57a542$1@news.povray.org>
On Wed, 20 Jan 2010 16:33:44 -0800, Darren New wrote:

[...]

Now my brain is going to be busy for the next month..... ;-)

Jim


Post a reply to this message

From: nemesis
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 19:59:23
Message: <4b57a6eb$1@news.povray.org>
Darren New wrote:
> Google had a lot of these kinds of questions. Stuff like "how can you 
> determine how big a machine's cache is?"
> 
> I couldn't figure out if they wanted a program to measure the timing of 
> something assuming different cache sizes and look for the step in the 
> timing, or "look it up in the x86 instruction set manual".

I would just write:  "I'd google for it".  a bit of butt-kissing can't 
hurt... :D


Post a reply to this message

From: Darren New
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 20:00:46
Message: <4b57a73e$1@news.povray.org>
Jim Henderson wrote:
> That makes more sense - but fairly easy to answer algebraically.

That's why I think the original poster meant to ask the later questions, 
which are somewhat trickier.

>>> And I'm not sure that discarding the length of the track allows the
>>> question to be answered even then.
>> No, that would eliminate the ability to answer.
> 
> How so?  If you know the distances and speeds, 

Oh, you're discarding the length of the track, but you still know the distances?

I don't understand, but ... nevermind. :-)

>> You want to average 60MPH over two minutes. You go 30MPH for the first
>> mile. How fast do you have to go to average 60MPH for two minues?
>>
>> Second alternate question: you want to average 60 MPH. You drive 10
>> miles at 30MPH. How many miles do you need to drive at 90MPH to average
>> 60MPH?
> 
> I agree, that question formulation would be easier to answer.

Well, except for the first one. And the second one is unobvious, easy to 
fall into a trap.

-- 
Darren New, San Diego CA, USA (PST)
   Forget "focus follows mouse." When do
   I get "focus follows gaze"?


Post a reply to this message

From: Darren New
Subject: Re: Interesting interview questions
Date: 20 Jan 2010 20:02:17
Message: <4b57a799$1@news.povray.org>
Jim Henderson wrote:
> Now my brain is going to be busy for the next month..... ;-)

It took me a while, but it became easy once you think about it logically and 
approach the problem systematically.

-- 
Darren New, San Diego CA, USA (PST)
   Forget "focus follows mouse." When do
   I get "focus follows gaze"?


Post a reply to this message

<<< Previous 10 Messages Goto Latest 10 Messages Next 10 Messages >>>

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.