3 ms·

From the resume writer's perspective, the problem is that you have no idea what standard the interviewer uses, so you pretty much have to use the standards of y

by edanm 16y ago

From the resume writer's perspective, the problem is that you have no idea what standard the interviewer uses, so you pretty much have to use the standards of your peers. For example, I have programmed a little in many, many languages, and consider myself reasonably good in Python and C++. I know plenty of people who are less experienced than me who would write that they are "experts" in C++/Python, and would list those languages I wouldn't think to list 'cause I only know them a little. So what should I write on my resume? I'm trying to compete with these people, after all.

dkarl 16y ago
My resume includes separate lists for technologies/languages I am "advanced" or "proficient" in and technologies/languages I have done some work with. To give an example, I can slowly and painfully write PL/SQL when it's necessary, but I would not feel comfortable deploying it without asking a PL/SQL guru to review it, so I don't describe myself as "proficient." I described my Java skills as "advanced" after doing a couple of years of professional Java development, but I downgraded my Java to "proficient" after spending several years away from it. I describe myself as "advanced" if I'm ready to do professional-quality work from day one. If you go by the standards in the marketplace, well, there aren't any. We interviewed a candidate for a highly technical position only to find out that most of the technology experience listed on her resume was indirect exposure doing administrative and liaison work for technical teams. She was more technical than the typical corporate product manager or account manager position, but she wasn't remotely close to being qualified for the position we advertised. Strange thing was, she seemed to understand the position and clearly wanted it... not sure what that was about, but it proves you can't assume anything.

by edanm 16y ago

dkarl 16y ago

My resume includes separate lists for technologies/languages I am "advanced" or "proficient" in and technologies/languages I have done some work with. To give an example, I can slowly and painfully write PL/SQL when it's necessary, but I would not feel comfortable deploying it without asking a PL/SQL guru to review it, so I don't describe myself as "proficient." I described my Java skills as "advanced" after doing a couple of years of professional Java development, but I downgraded my Java to "proficient" after spending several years away from it. I describe myself as "advanced" if I'm ready to do professional-quality work from day one. If you go by the standards in the marketplace, well, there aren't any. We interviewed a candidate for a highly technical position only to find out that most of the technology experience listed on her resume was indirect exposure doing administrative and liaison work for technical teams. She was more technical than the typical corporate product manager or account manager position, but she wasn't remotely close to being qualified for the position we advertised. Strange thing was, she seemed to understand the position and clearly wanted it... not sure what that was about, but it proves you can't assume anything.