| Technical interview questions are bound to come up | | | | there and answer the questions they ask. It should be |
| when your job involves some technical content and | | | | quite straightforward to bring up the topic of the |
| because that includes so many different subjects, | | | | problems that occur and the solutions you have come |
| what we can only do here is show you HOW to deal | | | | up with. |
| with technical interview questions. | | | | If it doesn't come out readily during the interview, when |
| If you really know your subject from practical | | | | they ask if you have any questions you should |
| experience, then in any particular area, you should also | | | | immediately ask them about the main problems that |
| be able to say what could go wrong. Other interview | | | | they have had at their site, and then discuss how they |
| candidates who don't have your experience or if they | | | | are solving them. You can then go on to talk about |
| had only done a course on the subject, wouldn't be | | | | similar problems that you have had and what you |
| able to answer any questions on what might go | | | | have done to correct them. If they haven't come |
| wrong. If they had only been slightly exposed to the | | | | across some of these issues yet, they might be very |
| technical subject then their replies to such technical | | | | keen to have you on board for when they do. |
| interview questions would probably be very limited. | | | | But even if they have come across the problems, by |
| But if you had genuine and extensive experience of a | | | | bringing them up you will show your understanding of |
| technical area, then you could probably give a lengthy | | | | the subject and that you are able to sort out problems |
| answer about the possible problems and their solutions. | | | | that can occur. |
| From an interviewer's point of view, someone who | | | | If you are an interview candidate, make sure that you |
| knows what can go wrong demonstrates knowledge | | | | have prepared a list of technical interview questions |
| more effectively than giving someone a technical test. | | | | about what can go wrong and prepare some |
| Knowing what can go wrong and the ways of | | | | statements about how you would put it right; go to the |
| avoiding it is the way to produce a successful | | | | interview determined that you are going to make this |
| outcome to any technical task. | | | | point. |
| So if your interviewer does not ask technical interview | | | | Advantages Of This Approach To Technical Interview |
| questions like that, you should aim to turn the interview | | | | Questions |
| round so that you are able to bring out your | | | | Competence and compatibility are the two key factors |
| knowledge of the particular technical area or skill that | | | | in a decision to hire and it's true that companies tend to |
| they need to know about. | | | | take on people that they like. If you are able to talk to |
| Before you go to the interview, think about all the | | | | them as a knowledgeable equal (or superior) in a |
| things that may go wrong in this area or when applying | | | | subject that they know and like talking about, you build |
| this particular skill. Also think about how you have | | | | the all-important 'rapport' with your interviewer as you |
| solved these problems to make them right. | | | | talk about common problems you've both met and |
| So, when you go to the interview, be determined to | | | | solved. As the rapport builds, so do your chances of |
| get this across; that you know what the issues are | | | | being offered the job! |
| and how you can solve them. Don't just passively sit | | | | |