Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Doing well at interviews

Doing well at interviews

Scheduled Pinned Locked Moved IT & Infrastructure
careerhelpcsharpdesignquestion
6 Posts 5 Posters 2 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • U Offline
    U Offline
    User 4483848
    wrote on last edited by
    #1

    I seem to do quite bad at job interviews :( Has anybody got any suggestions that may help me? It looks like coding/development skills are irrelevant for interviews, and all you need to interview skills. I have seen a lot of senior people who earn far more than me who are incompetent, which makes me very embarassed about my salary and position. You can't say these things in interviews though, or it will look bad. The biggest problem I have is proving how good I am in an interview. If I compare myself to other people then I'll just look bad for putting others down, and if I have no proof at all then I'll just look silly. It is very rare for there to be proper technical tests in interviews too, although if there are, then I usually do very well. People seem to go for 'X years of experience' on CV's, but for me that is meaningless, it doesn't mean that they are any good at it. It's really frustrating for me because I know that I'm very good. The other thing that annoys me is when employers care about degrees. Do they not realise how basic a degree is these days? A degree is meaningless after one or two years experience IMHO. Interviewers also don't seem to understand the value of some of my skills. Knowledge of languages isn't so important to me, but knowledge of other things like design patterns etc. is a far better IMHO. These skills will also last longer, design patterns will still be useful even when C# is replaced by something newer. I'm fed up with it all really. I'd really like to become self employeed/freelance, but if it doesn't work out then I would risk not being able to pay my mortgage, which is a risk that I can't take. I also sometimes consider a career change, but it's a shame because I know that I'm good and I would still end up developing in my spare time anyway. With the credit crunch it is difficult to do anything anyway.

    L K P 3 Replies Last reply
    0
    • U User 4483848

      I seem to do quite bad at job interviews :( Has anybody got any suggestions that may help me? It looks like coding/development skills are irrelevant for interviews, and all you need to interview skills. I have seen a lot of senior people who earn far more than me who are incompetent, which makes me very embarassed about my salary and position. You can't say these things in interviews though, or it will look bad. The biggest problem I have is proving how good I am in an interview. If I compare myself to other people then I'll just look bad for putting others down, and if I have no proof at all then I'll just look silly. It is very rare for there to be proper technical tests in interviews too, although if there are, then I usually do very well. People seem to go for 'X years of experience' on CV's, but for me that is meaningless, it doesn't mean that they are any good at it. It's really frustrating for me because I know that I'm very good. The other thing that annoys me is when employers care about degrees. Do they not realise how basic a degree is these days? A degree is meaningless after one or two years experience IMHO. Interviewers also don't seem to understand the value of some of my skills. Knowledge of languages isn't so important to me, but knowledge of other things like design patterns etc. is a far better IMHO. These skills will also last longer, design patterns will still be useful even when C# is replaced by something newer. I'm fed up with it all really. I'd really like to become self employeed/freelance, but if it doesn't work out then I would risk not being able to pay my mortgage, which is a risk that I can't take. I also sometimes consider a career change, but it's a shame because I know that I'm good and I would still end up developing in my spare time anyway. With the credit crunch it is difficult to do anything anyway.

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Put yourself in the shoes of the interviewer. You know that "years of experience" and "degrees" are merely indications. How do you find the right person for the job?

      Member 4487083 wrote:

      Interviewers also don't seem to understand the value of some of my skills. Knowledge of languages isn't so important to me, but knowledge of other things like design patterns etc. is a far better IMHO. These skills will also last longer, design patterns will still be useful even when C# is replaced by something newer.

      A recruiter won't be interested in the fact that an abstract idea will outlast a programming language. They're [i]looking[/i] for [i]someone[/i] who can do the job, based on some vague terms. Some recruiters won't even know what XML is, and they don't have to care.

      Member 4487083 wrote:

      I also sometimes consider a career change, but it's a shame because I know that I'm good and I would still end up developing in my spare time anyway. With the credit crunch it is difficult to do anything anyway.

      Well, just keep programming in your spare time. You won't need much credit to be writing shareware, and that can be a nice step-up to your own business. Back to the original question;

      Member 4487083 wrote:

      I seem to do quite bad at job interviews Has anybody got any suggestions that may help me?

      "Servitude" :) Ask where their pain is, ask where the current problems lie. Start matching some of your strengths to their weaknesses. Don't patronize the messenger that comes looking for a programmer, instead, try to give the messenger the idea that you are the person who they were looking for. If you feel to disheartened to continue as a programmer, then try a job at your local MacDonalds - your ambitions will return a lot sooner in such an environment. Good luck :thumbsup:

      "please help in this regard. give the visual basic code for this as soon possible."

      U 1 Reply Last reply
      0
      • L Lost User

        Put yourself in the shoes of the interviewer. You know that "years of experience" and "degrees" are merely indications. How do you find the right person for the job?

        Member 4487083 wrote:

        Interviewers also don't seem to understand the value of some of my skills. Knowledge of languages isn't so important to me, but knowledge of other things like design patterns etc. is a far better IMHO. These skills will also last longer, design patterns will still be useful even when C# is replaced by something newer.

        A recruiter won't be interested in the fact that an abstract idea will outlast a programming language. They're [i]looking[/i] for [i]someone[/i] who can do the job, based on some vague terms. Some recruiters won't even know what XML is, and they don't have to care.

        Member 4487083 wrote:

        I also sometimes consider a career change, but it's a shame because I know that I'm good and I would still end up developing in my spare time anyway. With the credit crunch it is difficult to do anything anyway.

        Well, just keep programming in your spare time. You won't need much credit to be writing shareware, and that can be a nice step-up to your own business. Back to the original question;

        Member 4487083 wrote:

        I seem to do quite bad at job interviews Has anybody got any suggestions that may help me?

        "Servitude" :) Ask where their pain is, ask where the current problems lie. Start matching some of your strengths to their weaknesses. Don't patronize the messenger that comes looking for a programmer, instead, try to give the messenger the idea that you are the person who they were looking for. If you feel to disheartened to continue as a programmer, then try a job at your local MacDonalds - your ambitions will return a lot sooner in such an environment. Good luck :thumbsup:

        "please help in this regard. give the visual basic code for this as soon possible."

        U Offline
        U Offline
        User 4483848
        wrote on last edited by
        #3

        Shareware is a possibility, although I'm not sure that I can think of a product that somebody would want to buy. I'll starting thinking about it though. The other problem I see is that different people can want very different things in interviews, and you often don't find out what they want until it is too late. For example some don't mention hobbies and interests, but others seem to think that they are important.

        1 Reply Last reply
        0
        • U User 4483848

          I seem to do quite bad at job interviews :( Has anybody got any suggestions that may help me? It looks like coding/development skills are irrelevant for interviews, and all you need to interview skills. I have seen a lot of senior people who earn far more than me who are incompetent, which makes me very embarassed about my salary and position. You can't say these things in interviews though, or it will look bad. The biggest problem I have is proving how good I am in an interview. If I compare myself to other people then I'll just look bad for putting others down, and if I have no proof at all then I'll just look silly. It is very rare for there to be proper technical tests in interviews too, although if there are, then I usually do very well. People seem to go for 'X years of experience' on CV's, but for me that is meaningless, it doesn't mean that they are any good at it. It's really frustrating for me because I know that I'm very good. The other thing that annoys me is when employers care about degrees. Do they not realise how basic a degree is these days? A degree is meaningless after one or two years experience IMHO. Interviewers also don't seem to understand the value of some of my skills. Knowledge of languages isn't so important to me, but knowledge of other things like design patterns etc. is a far better IMHO. These skills will also last longer, design patterns will still be useful even when C# is replaced by something newer. I'm fed up with it all really. I'd really like to become self employeed/freelance, but if it doesn't work out then I would risk not being able to pay my mortgage, which is a risk that I can't take. I also sometimes consider a career change, but it's a shame because I know that I'm good and I would still end up developing in my spare time anyway. With the credit crunch it is difficult to do anything anyway.

          K Offline
          K Offline
          Kevin McFarlane
          wrote on last edited by
          #4

          As a long-term "resting" contractor I feel your pain. :(

          Member 4487083 wrote:

          It looks like coding/development skills are irrelevant for interviews, and all you need to interview skills.

          For contractors it is mostly technical questions and/or technical tests. However, mostly these do not test how good a developer you are but are more like trivial pursuits - i.e., memory tests.

          Member 4487083 wrote:

          People seem to go for 'X years of experience' on CV's, but for me that is meaningless, it doesn't mean that they are any good at it.

          See The Years of Experience Myth[^] However, the problem is this. In a severe downturn recruiters receive 100+ CVs/Resumes for each role. They cannot interview everyone to find out whether they are a "good" developer. So they have to use a filter. For want of anything better that will be years of experience in the specific skills advertised. It's very frustrating but I don't see a way around this.

          Kevin

          1 Reply Last reply
          0
          • U User 4483848

            I seem to do quite bad at job interviews :( Has anybody got any suggestions that may help me? It looks like coding/development skills are irrelevant for interviews, and all you need to interview skills. I have seen a lot of senior people who earn far more than me who are incompetent, which makes me very embarassed about my salary and position. You can't say these things in interviews though, or it will look bad. The biggest problem I have is proving how good I am in an interview. If I compare myself to other people then I'll just look bad for putting others down, and if I have no proof at all then I'll just look silly. It is very rare for there to be proper technical tests in interviews too, although if there are, then I usually do very well. People seem to go for 'X years of experience' on CV's, but for me that is meaningless, it doesn't mean that they are any good at it. It's really frustrating for me because I know that I'm very good. The other thing that annoys me is when employers care about degrees. Do they not realise how basic a degree is these days? A degree is meaningless after one or two years experience IMHO. Interviewers also don't seem to understand the value of some of my skills. Knowledge of languages isn't so important to me, but knowledge of other things like design patterns etc. is a far better IMHO. These skills will also last longer, design patterns will still be useful even when C# is replaced by something newer. I'm fed up with it all really. I'd really like to become self employeed/freelance, but if it doesn't work out then I would risk not being able to pay my mortgage, which is a risk that I can't take. I also sometimes consider a career change, but it's a shame because I know that I'm good and I would still end up developing in my spare time anyway. With the credit crunch it is difficult to do anything anyway.

            P Offline
            P Offline
            Pete OHanlon
            wrote on last edited by
            #5

            If you can get to the interview stage, you're halfway there to getting the job. As an employer, I don't care what people put down as their experience because I don't trust CVs. That's just the hook to get you to the interview, and I'll just use it to refer to your answers because I want to see if you can remember what you wrote. It's amazing how many candidates I catch out in blatant lies because they can't remember the bull they put on the CV. If I ask you a question, I want to see how you respond. I want to know that you can field odd questions, and that you can back your opinions up with evidence that you've dealt with issues before. If you talk about a particular piece of work, tell me about the problems you faced and how you overcame them (both technically and personally) because I want to know how you'll fit into the team, and that you really did contribute to the project. If you've been to an interview and haven't got the job, then ask for feedback. Ask why you didn't get the job - I never mind telling agencies/candidates why they didn't get selected. Remember that you can blow an interview before you've even spoken a word. Wear smart clothes, and hide any offensive tattoos. Use a breath freshener before you go into the room, and have neat hair. If there's a handshake, have a firm grip but not a bone crusher. A lot of interviewers will chat to you about your journey on the way into the interview room - this is to put you at ease, and you can use this to your advantage. Be friendly, but not matey - nobody likes to be called "Chum" or "Pal" by an interviewee. Don't pass comment about the receptionist - I stopped an interview within 3 minutes because an interviewee did precisely that; they didn't even have to wait to find out whether or not they'd got the job - I gave feedback instantly. Never, ever, bad mouth anybody. I don't want to hire somebody who trashes the last guy she worked for. If you are asked why you want to leave your current job, have something ready. I usually find that the old "I feel that I've reached the maximum of my potential in my current position, and I'm looking for a dynamic team where I can grow and develop new skills" is an effective way to bat this one into the undergrowth. You've ticked all the boxes with that one; you didn't trash your previous employer; you look like you're ambitious and keen to learn; and you have an answer. Practice speaking without saying "ummm". There's a game I sometimes play with the team in meetings where everybody has to say ummm when the sp

            M 1 Reply Last reply
            0
            • P Pete OHanlon

              If you can get to the interview stage, you're halfway there to getting the job. As an employer, I don't care what people put down as their experience because I don't trust CVs. That's just the hook to get you to the interview, and I'll just use it to refer to your answers because I want to see if you can remember what you wrote. It's amazing how many candidates I catch out in blatant lies because they can't remember the bull they put on the CV. If I ask you a question, I want to see how you respond. I want to know that you can field odd questions, and that you can back your opinions up with evidence that you've dealt with issues before. If you talk about a particular piece of work, tell me about the problems you faced and how you overcame them (both technically and personally) because I want to know how you'll fit into the team, and that you really did contribute to the project. If you've been to an interview and haven't got the job, then ask for feedback. Ask why you didn't get the job - I never mind telling agencies/candidates why they didn't get selected. Remember that you can blow an interview before you've even spoken a word. Wear smart clothes, and hide any offensive tattoos. Use a breath freshener before you go into the room, and have neat hair. If there's a handshake, have a firm grip but not a bone crusher. A lot of interviewers will chat to you about your journey on the way into the interview room - this is to put you at ease, and you can use this to your advantage. Be friendly, but not matey - nobody likes to be called "Chum" or "Pal" by an interviewee. Don't pass comment about the receptionist - I stopped an interview within 3 minutes because an interviewee did precisely that; they didn't even have to wait to find out whether or not they'd got the job - I gave feedback instantly. Never, ever, bad mouth anybody. I don't want to hire somebody who trashes the last guy she worked for. If you are asked why you want to leave your current job, have something ready. I usually find that the old "I feel that I've reached the maximum of my potential in my current position, and I'm looking for a dynamic team where I can grow and develop new skills" is an effective way to bat this one into the undergrowth. You've ticked all the boxes with that one; you didn't trash your previous employer; you look like you're ambitious and keen to learn; and you have an answer. Practice speaking without saying "ummm". There's a game I sometimes play with the team in meetings where everybody has to say ummm when the sp

              M Offline
              M Offline
              Member 1709723
              wrote on last edited by
              #6

              Pete O'Hanlon wrote:

              Never, ever, bad mouth anybody. I don't want to hire somebody who trashes the last guy she worked for. If you are asked why you want to leave your current job, have something ready. I usually find that the old "I feel that I've reached the maximum of my potential in my current position, and I'm looking for a dynamic team where I can grow and develop new skills" is an effective way to bat this one into the undergrowth.

              while i agree with this for a number of reasons, it has always bothered me for not being able to just come out and say : 'i work for/with a bunch of scumbags/lepers/whatever - this was only revealed to me after i was hired and got to know them - i would like to rectify this now' it essentially encourages lying/political correctness, and then we wonder why the world sucks so much come on, we all know that often there is not a personality fit and we want a change - why not be able to say it like it is? </rant off>

              Opium is my business. The bridge mean more traffic. More traffic mean more money. More money mean more power. Speed is important in business. Time is money. You said opium was money. Money is Money. Well then, what is time again? icalburner.net

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups