How many are too many interviews?

  • Im going for a position in a large multinational. Its a semi dev position. I applied for it as i want to get experience in areas of development outside of databases.

    Ive had 5 interviews!

    1st - meeting with my would be manager to assess my interest and a general view of who i am.

    2nd - meeting wtih two would be co-workers to see my technical ability.

    3rd - meeting with manager and would be co-worker to assess my ability.

    4th - meeting with co-worker's, writing algorithms on a white board.

    5th - meeting with dept head writing algorithms on the white board.

    Many of these interviews were duplicates of previous interviews and it seems like an overly drawn out process.

    Also, there is some c# coding in this role. As they know i dont code on a daily basis they decided to test me. test was to write a linked list class with a method that will link and sort two lists.

    I had 10 mins to do this. I question if even seasoned dev's could code this in 10 mins on a whiteboard.

    Are companies becomming overly fussy about chosing candidates now days?

  • Five seems to me to be a lot... but it probably means that they are down to you and someone else, and are having troubles deciding on which one to select.

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • WayneS (4/16/2011)


    Five seems to me to be a lot... but it probably means that they are down to you and someone else, and are having troubles deciding on which one to select.

    Large multinationals are often hamstrung by bureaucracy. Yes, 5 interviews seems a bit OTT; but probably the recruitment procedures require the initial interview by prospective manager to check on general acceptability, then a peer assessment interview, then if that is satisfactory a technical interview with the prospective manager; and if the prospective manager is not at least at department head level, he won;t be able to hire you - the bureaucracy will require an interview with the department head, so you get to 4 anyway. I guess this department head wanted a peer assessment by the whiteboard method to determine whether it was worth his time to see you - I certainly would have in my day (but there would only be three interviews in all and they would all happen on the same day). Or it could be as Wayne said - they are having difficulty in deciding between two people.

    I think I could still code a list class and a method to take two lists and produce their sorted concatenation in under 10 minutes on a whiteboard, but not in C# (because I don't really know it) or C++ (because it's a bloody awful language), although it's a long time since I wrote anything like that.

    Tom

  • I usually see only 2 or 3 interviews at most. First one is a phone tech screening to weed out the bs artists. Next is a manager interview to test discuss your abilities and team fit. Third if necessary can be either a heavy tech review or a business screening, depending on the position type.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply