3 ms·

"7. Apply for a job for which you are clearly overqualified for (I got one resume from a software engineer)." This is something that I hate. I know many people

"7. Apply for a job for which you are clearly overqualified for (I got one resume from a software engineer)." This is something that I hate. I know many people who are in this situation. They're highly qualified, but due to too many people in that field for a local area, or in general, they just can't find work in it. So to tide themselves over until they CAN get one, they look for a much more simpler job. Only to get told, time and time again, they are 'overqualified'. Why is this such a bad thing?

nazgulnarsil 18y ago
the employer in these situations feels that the person will be unhappy at a position so obviously beneath them. the employer can also assume that the person will be leaving as soon as they do find a job they're qualified for. unhappy employee who could leave any time. doesn't sound good to me.
- ajkirwin 18y ago
  Yes, but this is surely the kind of thing that you resolve in an interview. Maybe this person could be quite happy in this position. Maybe they're looking to broaden their horizons. You just don't know.
  - nazgulnarsil 18y ago
    as an HR director, i'd have "yes", "no", and "maybe" stacks of applications. If my "yes" pile is big enough, I'm throwing out the "maybe" pile. Don't make the mistake of thinking a resumes' job is to accurately represent you to prospective employers. Your resume is an advertising brochure that should be tailored to fit each position you apply for.
    - denglish 18y ago
      I agree with tailor, but it still needs to "accurately represent" - there really isn't any point getting to an interview you shouldn't be at. Just waists everyone's time.
      - nazgulnarsil 18y ago
        sure, but the average hacker is smart enough to do most jobs, including ones they aren't technically qualified for. It has been my experience that most of the skills vital to any particular job will be learned on-site anyway. Experience is just shorthand for "are you basically competent?".
        lief79 18y ago
        True to a point and possibly for the majority of jobs, provided that you aren't trying to bill yourself as a consultant (expert in whatever technology). I'm also assuming that the "average hacker" implies that you are eliminating everyone who claims to be one, but is not even close from the list of hackers, in order to greatly improve the average. (The average "successful" hacker.) Now, even with the higher standard, the learning curve depends greatly on the complexity of the system and how much of a learning curve is permitted by the employer. If you are trying to work with a full J2EE system, and you haven't done it before, expect a steep 2-3 month learning curve, even if you are proficient in java. If they need someone to be productive within that first week, the average hacker won't be able to make it. There is just too much complexity and too many libraries to memorize in less time then that. I spent a good month or two learning the EJB 2.2 frameworks, Servlets, JSPs, javascript, etc at my last job. This job had a very steep 1 month learning curve with a modern Seam, Richfaces, JSF environment. I'd add on another month or two for anyone that doesn't already understand the core of the j2EE/web application stack. This small team has had people that haven't been able to pull it off. Now for the extreme example, my father has worked developing the base station for a satellite telephone system. He's commented on how half of the people brought in to help him got lost in the complexity and provided next to no additional productivity. I've also dabbled in pharmaceutical automation and in the telecommunication networks. Very steep learning curves in regulations and the complexities associated in both fields. In summary, competence often requires a lot more then just raw coding ability. Very few people can slide into a job under the radar and properly complete very hard problems where they don't have the expected domain knowledge. *Reviewing this, it's not really a direct response to what was said in the above thread. I was reading into the response too much.
fendale 18y ago
Being that for any job, you are supposed to tailor your CV to the position, is that not the time to omit the section that mentions your Engineering degree and relevant work experience if you know you are going to be over qualified? I guess its not really ethical to do that, and may even be illegal, but its not as bad IMHO as inventing qualifications and experience you don't have which is a definite no no!

nazgulnarsil 18y ago

the employer in these situations feels that the person will be unhappy at a position so obviously beneath them. the employer can also assume that the person will be leaving as soon as they do find a job they're qualified for. unhappy employee who could leave any time. doesn't sound good to me.

ajkirwin 18y ago
Yes, but this is surely the kind of thing that you resolve in an interview. Maybe this person could be quite happy in this position. Maybe they're looking to broaden their horizons. You just don't know.
- nazgulnarsil 18y ago
  as an HR director, i'd have "yes", "no", and "maybe" stacks of applications. If my "yes" pile is big enough, I'm throwing out the "maybe" pile. Don't make the mistake of thinking a resumes' job is to accurately represent you to prospective employers. Your resume is an advertising brochure that should be tailored to fit each position you apply for.
  - denglish 18y ago
    I agree with tailor, but it still needs to "accurately represent" - there really isn't any point getting to an interview you shouldn't be at. Just waists everyone's time.
    - nazgulnarsil 18y ago
      sure, but the average hacker is smart enough to do most jobs, including ones they aren't technically qualified for. It has been my experience that most of the skills vital to any particular job will be learned on-site anyway. Experience is just shorthand for "are you basically competent?".
      - lief79 18y ago
        True to a point and possibly for the majority of jobs, provided that you aren't trying to bill yourself as a consultant (expert in whatever technology). I'm also assuming that the "average hacker" implies that you are eliminating everyone who claims to be one, but is not even close from the list of hackers, in order to greatly improve the average. (The average "successful" hacker.) Now, even with the higher standard, the learning curve depends greatly on the complexity of the system and how much of a learning curve is permitted by the employer. If you are trying to work with a full J2EE system, and you haven't done it before, expect a steep 2-3 month learning curve, even if you are proficient in java. If they need someone to be productive within that first week, the average hacker won't be able to make it. There is just too much complexity and too many libraries to memorize in less time then that. I spent a good month or two learning the EJB 2.2 frameworks, Servlets, JSPs, javascript, etc at my last job. This job had a very steep 1 month learning curve with a modern Seam, Richfaces, JSF environment. I'd add on another month or two for anyone that doesn't already understand the core of the j2EE/web application stack. This small team has had people that haven't been able to pull it off. Now for the extreme example, my father has worked developing the base station for a satellite telephone system. He's commented on how half of the people brought in to help him got lost in the complexity and provided next to no additional productivity. I've also dabbled in pharmaceutical automation and in the telecommunication networks. Very steep learning curves in regulations and the complexities associated in both fields. In summary, competence often requires a lot more then just raw coding ability. Very few people can slide into a job under the radar and properly complete very hard problems where they don't have the expected domain knowledge. *Reviewing this, it's not really a direct response to what was said in the above thread. I was reading into the response too much.

fendale 18y ago

Being that for any job, you are supposed to tailor your CV to the position, is that not the time to omit the section that mentions your Engineering degree and relevant work experience if you know you are going to be over qualified? I guess its not really ethical to do that, and may even be illegal, but its not as bad IMHO as inventing qualifications and experience you don't have which is a definite no no!