Please create an account to participate in the Slashdot moderation system

 


Forgot your password?
Close
typodupeerror
×
Programming IT Technology

Core IT Interview Questions? 86

Posted by Cliff from the the-coder-inquisition dept.
Aengus asks: "We have a round of job interviews coming up and the people we will be interviewing will be of different backgrounds, so we are looking for a core set of general questions that you could apply to any IT/CS candidate that would display that they knew what they were talking about. ie questions that are not language or job specific. So far all we have come up with 'What algorithm is your favourite or most commonly used?'....." What questions have you been asked on interviews you have participated in?
This discussion has been archived. No new comments can be posted.

Core IT Interview Questions? More

Core IT Interview Questions?

Comments Filter:

  • There is no such thing .... (Score:5, Insightful)

    by nbvb ( 32836 ) on Friday May 31, 2002 @12:06AM (#3615060) Journal
    The question you just asked above is programmer-specific.

    I know Slashdot is very programmer-oriented, but we do need to remember that there _are_ other disciplines within IT/IS/CS/EE/whatever.

    I'm a sysadmin by trade --- I don't have an algorithm I use most often. If you asked me what my favorite was, I'd probably get into transactional two-phase locking protocols, just 'cuz I think they're neat. But I'm not a DBA, so what does it matter?

    You need to tailor the interview to the specific position that's open. You also should have real, honest-to-goodness technical people conduct the interview --- ideally, people from the team on which the position resides.

    It really makes a difference. I hate interviews with HR pukes. Give me a good technical interview anyway. The interview for my current job took 3 1/2 hours. It was a roundtable discussion with 3 members of the team I'm now a member of. Fantastic way to conduct an interview. Basically, we just shot the breeze discussing various sysadmin things from volume management to SunOS 4.1.whatever to stupid eeprom tricks... and of course, it all proves that I know what the heck I'm talking about. You can't talk that talk without walking the walk!

    All of this is just my personal opinion of course, but I think anything that says "generic interview" anything is useless!

    --DM
  • 1) Two cubes like they have at the bank. How to represent every day of the month using these two cubes?

    2) Room has 3 lights and 3 switches on the outside. You may not peek inside the room, only enter it and exit it. What is the minimum number of times you must enter the room to determine which switch controls which light.

    3) How can you build a domed roof on a building with squared walls?

    • 1) I can do it with one cube. Sides 1-6 are for monday-saturday. When I'm hiding the cube you can assume it's sunday.

      2) 0, apparently the 3 switches and lights are on the outside of the room.

      3) Just build it so the diameter equals the length from one corner to the diagonal opposite

      __
      /--\
      ||

    • Re:How do you think? (Score:2, Interesting)

      by Papineau ( 527159 )
      Warning: try to answer yourself before reading the rest of this comment.

      1) (Never saw those at a bank or elsewhere, but I think I can still figure out how they're made) So you need to be able to express all the numbers from 1 to 31, with 12 cube faces. You need 10 faces for 0 ,1, ... 8, 9. Then you need an extra 1, 2 and 3 for the tens. Which gives 13 faces, right? Wrong! You don't need two 3, as 33 is not a day of a month.
      Now how to distribute those 12 symbols on the 2 cubes: You need both 1 and both 2 on different cubes (obviously). The rest can then be spread anyway you want, even though there's probably a way which minimizes the number of cube switching during the month.
      Or, if you always want to show both cubes (which the previous answer didn't do), all you need is the 6 and the 9 to the inverse of each other. Then, cube A has 0, 1, 2, 3, 4, 5 and cube B has 0, 1, 2, 6, 7, 8 (with the 9 being an inverted 6).

      2) I'd say 2 times, assuming you know the initial state of the lights, 3 times otherwise.
      If you know the initial state, flip 2 switches, then see which lights have changed state. The one which didn't is the one connected to the switch you didn't use. Then reflip one of the 2 switches you started with. The light which has now changed state is connected to it, so the 3rd light and the 3rd switch are connected.
      If you don't know the initial state, there's no purpose to flip some switches randomly and then enter the room, so enter and look at the state of the lights. Then do as above.

      3) Build the dome on top of a flat roof with a round hole in the middle which connects the dome's base to the squared walls. Or if you don't care about the weather and/or the sun, make the diameter of your dome the same as the length of the walls: it will rest on the middle of each wall.

      My turn:
      1) How do you form 4 equal triangles with 6 matches? You can only connect the matches at their ends.
      2) How do you cut a cake in 8 equal parts with only 3 cuts?
      3) Assuming that with the previous question, not everybody had the same amount of topping, how do you cut the cake in 8 equal parts (topping included) with only 3 cuts?

      Those were fun to do: do you have more?

      • 1) See this site [mathforum.org] (Ben Whiton's answer)

        2) My cake isn't round or square, it is raised in the middle and then loops down on itself. With one cut I make 8 equal parts with icing.

        3) See #2.

      • 1. How do you make a Nazi Cross with five matches?
        2. A hole is drilled through the center of a sphere. The height of the resulting object (former sphere) is 6 inches. What is its volume?

        Neither of these is particularly useful in an interview; (1) is an old joke (Ans: Stick four of them in his ear and light them with the fifth) and (2), though interesting to solve, doesn't really reveal aptitude, IMO. But they're still two of my favorites.

        3. Given 12 balls - 11 identical and 1 either heavier or lighter than the others - and a balance beam, determine in as few weighings as possible which is the odd ball, and whether it is heavier or lighter.

        This one is getting a bit too well-known - I first heard it perhaps 20 years ago. But if someone can explain their answer they might have some aptitude for information theory and problem solving.

        4. Write a binary search.

        Anyone who can do this cold, with no boundary errors, gets a gold star.

        5. Find as many errors as you can in [some code]. Feel free to critique the style as well.

        The interviewer should provide code salted with her favorite bugs, whatever they may be.
        • 3. Umm, why not use 13 balls and make it more challenging (answer 3 weighings).. better yet give them a known fair ball and they can do 14. On the other hand, if it is known only that one ball may or may not be lighter or heavier, then 12 balls is the best you can do with three weighings... unless you have a fair ball in which case it is 13. I always thought this was a funny question because it shows the interviewer doesn't thouroughly understand the problem.
          • Please explain the 3 weighing solution with 12 balls when it is not know if the odd ball is lighter or heavier than the rest.
            • I wrote a lengthy analysis for a colleague not long ago, but I'm too lazy to format it for '/.' so you can find it here [oncampusdating.com].

              For the record I find that this problem is too difficult for an interviewing scenario unless the interviewee is familar with the problem or very very smart they are not going to find the correct solution in a short amount of time. Besides describing all the cases for the complete solution takes a few minutes. As you will see, the answer (3 weighings) can be found from an information approach without knowing the complete solution.
              • Thanks for posting a link to your 13 ball solution. But your method does not answer the second part of the question - whether the odd ball is lighter or heavier - in all cases.
                • Fair enough, that particular approach will not satisfy the second question for all cases. I can think of no constraint for why a solution satisfying the second question could not be found for 13 balls; afterall, there are only 26 possible cases for the 13 ball problem, while 3 weightings has 27 possible outcomes. Certainly, given a single reference coin, the 14 coin method w/reference can be used to find a complete solution for the 13 ball problem.
        • This one is getting a bit too well-known - I first heard it perhaps 20 years ago.

          I have a book, "The complete Book of Games and Stunts" published in 1956, that has this problem in it.
      • 2) I'd say 2 times, assuming you know the initial state of the lights, 3 times otherwise.
        I could do it in one. Turn on the first and second switches. Wait a minute and then turn the second one off. Now go into the room. The first light will be on. The second light will be off but will be hot. The third light will be off and will not be hot.
        • The second light will be off but will be hot.

          I've always felt that to be a stupid answer. Not only does it rely on many conditions (incandescent bulbs, bulbs are withing reach, room is not cold (imagine it was a freezer bulb)), it's also using a method not in the question.

          Normally, you want people to think "outside the box", but that is when people create their own boundaries, such as connecting nine dots with four lines, but here, there is no box, you are expecting the person to invent a method that "should" work.
      • 2) this is a classic brain teaser. What you do is flip the first switch and leave it one for a minute or so. Then flip it back off and flip the second switch. Walk into the room. If the light is on, then the second switch is the one. Otherwise check and see if the bulb is hot...

        3) build arches up from the tops of the square walls, if done correctly they will intersect the dome appropriately.

        your questions,
        1) Make a tetrahedron (thats a new one to me, I like it.)
        2,3) Cut the cake into quarters in the usual manner. Now, line up the four peices into a row cut down the row into eighths?

        My turn:
        Given cake and a knife only, what is the best way to cut a cake between three people so that no person can complain about receiving an unfairly small portion? And what is the minimun number of cuts necessary?
        • Given cake and a knife only, what is the best way to cut a cake between three people so that no person can complain about receiving an unfairly small portion? And what is the minimun number of cuts necessary?

          Three cuts.

          Tell the three people the rules:

          1) The cake will start with a cut (1) from an edge to the center
          2) The knife holder (non-biased third party) will rotate the knife in a clockwise manner
          3) At any time, any cake-receiver can say "Stop" and the knife holder will then cut the cake at that point and the person who said "Stop" gets the piece.
          4) Continue until all players have their piece (once more for 3 players).

          Of course they will complain about their small pieces, but it's their own fault for being too greedy.
        • Given cake and a knife only, what is the best way to cut a cake between three people so that no person can complain about receiving an unfairly small portion? And what is the minimun number of cuts necessary?
          Zero cuts!

          The first person eats the whole cake herself, without cutting it.

          The other two people can't complain about overly small portions, because they didn't get portions! They can complain that they didn't get any, but they can't complain that the poritions they got were overly small.
        • Given cake and a knife only, what is the best way to cut a cake between three people so that no person can complain about receiving an unfairly small portion? And what is the minimun number of cuts necessary?

          Two cuts. Person A cuts the cake in two. Person B cuts the larger of the two pieces in two. Person C chooses any of the three pieces. Person B chooses one of the two remaining pieces. Person A gets what's left.

      • 2) Room has 3 lights and 3 switches on the outside. You may not peek inside the room, only enter it and exit it. What is the minimum number of times you must enter the room to determine which switch controls which light.

        If you know the initial state of the lights and they are conventional lightbulbs, one time should suffice. Turn on two lights. Wait for 5-10 minutes. Turn one of them off.

        Now, when you go into the room you know one is on. Feel the other two lightbulbs. The one that is warm is the other switch.

        • If you know the initial state of the lights and they are conventional lightbulbs

          Say the initial state is all the lights are on (initial state is not necessarily all off). You'd get three warm bulbs. And that's assuming you can feel them (glass preventing you from touching, too high, etc.).
          • True. However, making the assumption that you can touch the bulbs, the logic could work in the inverse as well. Turn two lights off, wait a while for them to cool down, turn one back on, go into the room. One light will be off, one will be on and hot, one would be on but not that warm.
    • 1) Two cubes like they have at the bank. How to represent every day of the month using these two cubes?
      That's just semantic, isn't it? "I do delare, that this first cube represents every day of the month, and that this second cube doth represent every day of every other month."

      2) Room has 3 lights and 3 switches on the outside. You may not peek inside the room, only enter it and exit it. What is the minimum number of times you must enter the room to determine which switch controls which light.
      We don't have any information that these are necessarily standard binary switches, each corresponding to a distinct light in the room. It might be necessary to try every (spacial and temporal) combination and permutation to figure out what is going on.

      3) How can you build a domed roof on a building with squared walls?
      You find a builder in the yellow pages, and tell him to build a domed roof?

      With a hammer, nails, and wood?

      As long as the dome is somewhat sturdy and the diameters is between the width of the square and the diagonal of the square, the roof will just sit on top of the square just fine.

      What I don't see is what vague riddly questions like these have to do with job stills or job ability.

      Propose a task _relevant_ to the job in question ("There's an earthquake and the telepohone goes out...what do you do about..?") if you want to see reasoning skills. The important details to notice are not usually the answer given, but what iformation is deemed necessary to solve the problem and what questions the intervie asks in the process of solving the problem.
  • computer history:

    -They should have a general idea of how Bill Gates purchased MS-DOS from DEC and how Seymour Cray was out flying his airplane when the IBM sales people came to visit him, virtually guarenteeing that they would choose Microsoft

    -They should have general knowlege of how operating systems have evolved, for example the general progression of operating systems. Multics code was used to make UNIX v.7, which was used to make XENIX (by SCO), which was used to make both OS/2 and Windows NT. They should know that Penguins mean Linux.

    -They should know about various microprocessors, (8-bit) 8086, 80286, Z80, and i860; (16-bit) 80186, 68020 (32-bit) Pentium, etc.

    -It's also nice to know about computer languages, (structured) COBOL, FORTRAN; (OOP) Modula-2, APL; (database) SQL PLUS

    programming: general knowlege of algorithms. They should be able to name an efficient sort algorithm (bubble sort) and describe what an array is.

    Of course, these are all very general questions that only the most ill-informed would get wrong.

    • They should have a general idea of how Bill Gates purchased MS-DOS from DEC

      Actually, it was Digital Research ... and I've never heard the story about Seymour Cray, although I SERIOUSLY doubt that the God of vector machines was interested in the PC market ... TERMINALS for a Cray 1 cost more than a PC did, even when PCs cost $5K.

      They should know that Penguins mean Linux.

      To most of the world, penguins mean Antarctica, although I LOVE Tux.

      Multics code was used to make UNIX v.7 ...

      ... eventually ... but I think UNIX went through a few versions in the interim ... UNIX v.7 was the LAST AT&T in-house version before development went to Berzerkeley, which IIRC, carried BSD up to 4.2 before AT&T snatched it back to make SysV, leading to worlds of litigation without end ...

      which was used to make XENIX (by SCO)

      actually, XENIX was developed by Microsoft (shock and surprise) who licensed it to SCO, which lead to additional worlds of litigation without end ...

      ... which was used to make both OS/2 and Windows NT.

      I can't say much about OS/2 ... I've never even sat in front of an OS/2 box. The heritage of the NT kernel, however, is pure VMS ... NOT Unix. Read the various historical docs available on the web.
    • >> -They should have a general idea of how Bill Gates purchased MS-DOS from DEC and how Seymour Cray was out flying his airplane when the IBM sales people came to visit him, virtually guarenteeing that they would choose Microsoft

      Of course, it was Gary Kildall that legend has it was flying when IBM came to call. However, there are multiple accounts of what happened at that time. Here's a short selection:

      "Gary Kildall was not flying his plane" ... http://www.fool.com/Fribble/1996/Fribble961121.htm [fool.com]

      "... the point person for IBM, has sworn that he never met Kildall that day. Kildall swore that not only did he meet with [IBM], but ..." ... http://lists.essential.org/am-info/msg04566.html [essential.org]

      and the rather more sombre "What a tragedy. He was brilliant." (see "Subject: Kildall and DRI and IBM") ... http://people.smu.edu/rmonagha/4004.html [smu.edu]

      • There was a reason the story gained acceptance back then. Gary Kildall, and Digital Research, were very, very unbusinesslike. The story about Kildall flying was just an easily related example, that everyone could believe, considering everything else they knew.

        For example, CP/M operating system manuals from Digital Research sometimes were poor quality copies of originals printed using 8-pin dot-matrix printers that had worn ribbons.
    • how Bill Gates purchased MS-DOS from DEC

      Not DEC. (Not Digital Research, either, as someone else guessed.) Seattle Computer Products. And, according to some histories, not Bill Gates, but Paul Allen. (It did imitate CPM from DR, which in turn imitated RSX-22 from DEC.)

      They should be able to name an efficient sort algorithm (bubble sort)

      Ouch! Bubble sort, at O(n^3), is just about the least efficient determinstic sort possible. Ideally a move-based sort should move each item at most once - to the correct position. Bubble sort will move an item at most one position closer to the right spot with each exchange. You could be more inefficent only if you were to move items in the wrong direction! Use bubble sort in school if you must, but never thereafter.

      • Nah, bubble sort is O(n^2).
        There are plenty of less efficient sorts, like:
        - randomly permute the array and check if it's sorted; repeat (expected O((n+1)!))
        - recursively sort first third, last third, then first third again (worse than n^2)

        But, shame on you for falling for a troll. (And shame on me if I am being suckered as well! ;))
      • Actually bubble sort does quite well when the input is already sorted. much better than many other sorts.
    • ROFL!

      Now that is a troll I can respect! Well done. Not a single correct point (unless you count the reference to Tux). You are correct that only the most ill-informed would get these questions wrong. Love your "April 1" answers, too!

      To bad everyone had to take you seriously, but I supose that's the point of a troll, now isn't it. This one has the added bonus of possibly getting some poor twit in an interview parroting back the answers you fed them here. Bravo!

  • such as "Why is C++ better than C?"

    and see if they have the fortitude to disagree with you, or if they just tell you what they think you want to hear. (Of course, they might truly agree with you, but that's what the polygraph strapped to their arm is for...)

  • I was asked "Do you play Diablo II?". Needless to say, I got the job.

  • Not me, but someone I knew asked... (Score:3, Funny)

    by KurdtX ( 207196 ) on Friday May 31, 2002 @12:55AM (#3615228)
    "Quick! You have two minutes to name as many ways as possible to kill someone with a doorknob. Go."

    (Give it a try, then read on...)

    After a few seconds of silence and questioning looks (to which he just started looking at his watch) most people got going. It works great 'cause you don't hire the people that can't come up with any, and you have security escort out the ones that go for the whole two minutes.

  • THE question ... (Score:3, Insightful)

    by ninewands ( 105734 ) on Friday May 31, 2002 @12:59AM (#3615245)
    "Where do you go for information when somebody drops something in your lap that you know NOTHING about?"

    I answered "The man pages and O'Reilly Press" and got the job I have now (Unix admin at a major university) the interview panel shook their heads and said "Good answer" ... had I seen the question coming, I would have added http://www.linuxdoc.org ... the HOWTOs and FAQs are invaluable resources for problems like sendmail configuration, setting up an anonymous ftp server without compromising security, etc, etc, etc ...

  • My favorite interview question (not that I do any interviews myself those days, since we are not hiring, but what I recommend friends of mine... ;) ) for anyone who has U*IX listed in their resume together with Windows 3.1 and MS-DOS is:

    How do you exit vi?

    My guess that at least 50% would be gone, and we are in binary search mode, are not we? ;)

    Paul B.

    P.S. I personally am an emacs person, but if they EVER had to sit at the console of a bare-bones just-out-of-the-box non-Linux server, they would've see vi set as a default PAGER and would have to figure this out... ;-)

    P.P.S. And no, I do not mean vim with gtk interface :)
  • If you're expecting this new person to hit the ground running and you're offering no training or decent supervision/leadership then you want to make sure their experience is in the programs you use or it will be a short relationship. If you expect the person to slowly get up to speed after approriate training courses and induction then you need to look at their training and broader employment experience and history.

    So; not training, no help, no hope -- check to make sure they know SQL, ASP, Java, Javascript, PHP, Oracle, Lotus or whatever you use. Feel free to use recent problems as theoretical discussion points (but seriously, if you're like most places who've interviewed me you don't know your ASCII from your EBCDIC)

    Training, decent induction, mentor, leadership, real team -- you want someone with a high-level tertiary degree in a broad area that covers the job description, plus varied experience in a range of similar roles (a few political/delegation/project management questions would be good). A perfect skills match isn't as important as a good approach to the appropriate industry.

  • At one job, I was asked two questions--no more, no less--by one of my interviewers.
    • Why does Java suck?
    • Why is the answer you just gave wrong?
    ...Sounds counterintuitive, I know, but think about it for a moment. He wasn't asking me to give him facts; he was asking me what I thought, and then he asked me to think one hundred and eighty degrees opposite.

    The job was pure C programming, incidentally.

    I got the job--apparently, my second answer didn't suck as much as I was afraid it did--and I wound up working pretty closely with my interviewer. He told me later that mostly what he wanted to see was proof of life in my cerebral cortex. There are lots of people out there who can sling code, but there aren't many people out there who have given time and effort to applying their analytic and abstract reasoning skills.

    Slashdot is a beautiful example of a community of coders who have great code-fu, but tend to seriously lack in the reasoning department.
    • Slashdot is a beautiful example of a community of coders who have great code-fu, but tend to seriously lack in the reasoning department.

      STFU, assclown.
    • Those are absolutely fantastic questions, although they are very specific to programmers. The first question requires a general degree of knowledge about computer languages, including facets of language design and use that are only exposed when someone programs frequently. The second one tests your reasoning skills, especially your abilities to think outside the box (i.e. to put yourself in others' shoes). I like them, and I will adopt them as my own.
    • Where can I find the guy who asked you those two questions? I'd like to hire him.
  • This isn't going to help (actually it will - don't ask this for obvious HR reasons...) but in one interview I got asked:

    Interviewer: "Have you got a girlfriend?"
    Me: No.
    Interviewer: "Have you got a boyfriend?
    Me: No (and was tempted to ask him the same question).

    Mind you, [more] mind games were in play. I was asked to devise a solution to a problem but the interviewer then told me that I was completely wrong and that I should have done it another way. The aim was to see if I would a) not just cave in and just agree that his method was better and b) reasonably explain why I did it the way that I did.

    I got the job & for some reason took it...

    [And if you hadn't guessed, I'm male.]
  • One of the questions that has made me think was "What is the biggest technical chalege you have faced, and how did you overcome it". This is general enough for programers / tech support / sysadmin etc.
    If the inverviewee comes up with nothing, or nothing of significance then thay have no real experiance. If they come up with a biggie, then you can see how thier mind works, and what sort of things they have encountered.


  • Break a machine, slap it in front of them, ask them to fix it.

    Pop the graphics card slightly out, or put some duff RAM chips in, or a blank hard disk. See how they fix it. If they do.
  • "When did you stop beating your wife?"

  • There are two main ways to give an interview, in my experience as a candidate:

    • A complete technical Q / A session.
    • Just sit and chat for 30-60 minutes.

    I got my current job by just sitting and chatting to a couple of guys that were 'interviewing' me. There were a few technical questions but mostly it was assumed that I'd not lied on my CV, and they were just trying to decide if they could get along with me.

    The gruelling technical question interview is the kind of thing that I personally dread - I find that I do mostly OK, but I will wimp out and say 'search google' for things that I don't know. Sometimes that's an acceptable answer, sometimes it isn't.

    When I was last looking for a job I did come across these interview questions for SysAdmins.. [windborne.net] - the only question that appears to be missing is 'What's your username ...?' clickity-click ;)

    • Wow.. I suck! I just tried to do this test.. I guess I don't have much skills under unix, even though I have been an admin for 2.5 years.

      Time to read up!

      • I'm glad I'm not the only one to do badly!

        It has to be said, though, that a lot of those questions are very artificial and would be trivial to answer if you were in front of a computer. (Very hard to answer if you were doing this over a phone..)

  • * Describe a situation in which the best technical solution was not the best overall solution (or otherwise, not possible). What did you do?

    * Describe a project you worked on that failed. Why did it fail? What would you do differently?

    * Describe a project of which you inherited maintainence. Any thoughts?

    * Describe a project in which you transferred maintainence to somebody else. What state was it in and why?

    * Describe an instance in which you had a technical disagreement with a coworker. How did you resolve the issue.

    * What do you do to relax/recoup?

    (I'm serious about the last one...you want to know if this is somebody who is going to burn out fast, or whether they have enough experience to pace themselves, or have some strategy for keeping focused)
  • Go to monster.com. They have a whole slew of interview questions that are commonly asked and many are generic.

    Where do you want to be in 5 years?

    Questions about how you handle personal situations, like conflicts with other employees. How do you resolve them.

    Quesions like do you work better alone or in a group?

    You want to interview the person to get to know that they are a good person and someone you want to work with.

    I have heard of people being asked things like do you like to play ? This was cause they liked to do many employee related things. You may not want a 'homebody' working in a company full of people who like to snow board.

    Also what is thir favorit programming language or script? This is a good way to wead out those C++ programmers that are applying for a C job, or a scripter that is appling for a programmers job. Or someone who hate one or the other.

  • Give them a network drawing and a problem, and then ask for all the possible causes.

    My favorites are "mail doesn't work", "web doesn't work", "file sharing doesn't work".

    Only one is really necissary, and given the level of their answers you can judge the level of their knowledge (and problem solving abilities).

    Most people will at least get 'service is down, cable is broken, wrong username' and the such. Not everyone will get "broken dns, improper routing tables on machines, flooded network" sort of things...
  • "Are you a virgin?"
  • and you need to transfer a file from one to another. How many ways can you come up with to do so?

    This was probably my favorite tech interview question. (Thanks Eric!). It was a real mind twister. In the end, I think I came up with a dozen or so ways to do it, and I got the job.
  • I always liked the question "Why are manhole covers round?"

    There are several answers; the goal is to test for creativity: "So they don't fall down the manholes"; "So they're easier to transport (you can roll them rather than carry them)"; "So they don't have corners -- if they did, and were not seated properly, they could puncture a car's tires"; other answers?

    • Martin Gardner's answer to this was that if they were square they could be turned on edge and fall down the (square) hole.
      My answer has always been "Because manholes are round."
  • I had an interview with a consulting company. After a 30 minute chit-chat style interview, they gave me a paragraph with a problem. I was to pseudo code an answer to it. For me, that was one of the better interview questions I've received. Afterwards they gave me a copy of the answer. I pretty much got it right. I didn't get the job mostly because I was just out of school, and they needed experience.

Slashdot Top Deals

Love may laugh at locksmiths, but he has a profound respect for money bags. -- Sidney Paternoster, "The Folly of the Wise"

Close