Interview Questions
I am not sure where to start on this one. I have had about a dozen technical interviews in the past couple of weeks, both phone and in person. Some interviews were non-technical, score! Candidate walks to home plate. While others have been technical grill sessions.
I was recently interviewed by a Senior Architect who works for a Microsoft Partner of the Year. Well, no fluff here it was Shrimp on the Barbie from the very beginning and must add it was quite humbling. Score for the interviewer, but I passed (read squeaked by).
The interview with the Architect was followed by an in-person software architecture and design session. WTF! Anyone for grilled Mexican with a side of rice and beans? I was a bit nervous, but it was the best technical interview to date.
Here is where I wanted to go when I started this post. After the above grilling and design session, I was asked to participate in a phone screen and then an in-person interview with another company. This time with a non-technical group, what a disappointment.
Below are some of the questions I was asked in the last interview:
- What is the purpose of the web.config file?
- Describe functionality of master pages?
- Describe use of Try Catch Finally handler?
- When do you use XML comments?
- Provide types and examples of SQL Joins?
- Correct this snippet of code.
I know that we have various levels of knowledge, skills, and abilities so I am not criticizing the non-technical group for asking the questions they asked in the interview, just noting that I was disappointed that it was not another grill session.
Topics discussed at the BBQ include:
- Stack versus Heap (cloning objects, boxing operations)
- Generics (design time, compile time, runtime issues)
- Boxing and Unboxing (performance implications)
- Interface versus Abstract class (limitations, maintainability, uses)
- Threading (shared classes, instance classes, locking mechanisms)
- Database (design, referential integrity, consistency checks, lock types)
- Finalize Method versus Dispose Method (explicit, implicit calls, CLR)
June 25th, 2008 - 22:07
Holy crap. what a great post. I feel your comments (in parentheses) for the BBQ topics are SOLID GOLD. They convey little detailed information, but they still let lead to the blood beneath the scab. Talk about value…
The knowledge that you contain about those comments that you so casually posted are worth good money. Think about that. I’m practically sitting here with $40 to burn for descriptive expansions on your final BBQ comments.
All around, your best post yet.
June 26th, 2008 - 07:40
I have recently been on the interview panel for an associate (entry level) programmer. We didn’t BBQ anyone, but I was amazed at some of the answers to some very simple questions. When we asked one of our interviewees what peaked his interest in this position and why he wanted to work for us, he responded with “Oh… nothing in particular.” Ding Ding Ding!!! We have a winner! While technical knowledge is nice… personality and people skills is still a huge factor.
June 26th, 2008 - 08:50
Hey… I applied for that job, why wasn’t I called for an interview. I have the best reference EVER – I’m married to the person whose position you’re filling!
June 26th, 2008 - 09:04
ya, if you want to hire friends instead of getting work done. You need both, man. They are not mutual exclusive attributes, but I’d take someone that could get the job done over someone with a pleasant attitude.
It’s too bad more people aren’t like me. *swoon*
June 27th, 2008 - 08:22
I have been attending a lot of tech interviews too. All mine were really tough.
Mine were reverse a single linklist in c# (not using the LinkList Class) on the whiteboard.
Design a Geneology database System …
and more to come in a future post.