>“Everyone wants the next Steve Wozniak to walk through the door, but really, they should be asking to see if they can do the job. … Most interviews have a com

>“Everyone wants the next Steve Wozniak to walk through the door, but really, they should be asking to see if they can do the job. … Most interviews have a combination of the following. a) The interviewer wants to talk about himself/herself. b) Talk about how great the company is and how much of the kool-aid they drink. c) Ask one tech question and base their decision on that. d) Ask a few very obscure questions. e) Talk about big-O / Binary search / your education. f) Code samples... What could a code sample possible mean to someone who has no idea what the pitfalls of the code/problem/database is. Useless. Hiring is based on commenting ability? g) Play the game of are going to scrape and bow for them. Alpha males. h) Don't have a clue what they are talking about, got the job because they know someone. They ask questions from some article they read. i) Haven't read your resume. Less than 25% of interviews actually bother asking you questions about if you can do the job. Write some code.. ha, one in ten.