This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Building Blockchain Apps and have Michael Yuan on-line!
See this thread for details.
Win a copy of Building Blockchain Apps this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Liutauras Vilda
  • Knute Snortum
  • Bear Bibeault
Sheriffs:
  • Devaka Cooray
  • Jeanne Boyarsky
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • salvin francis
Bartenders:
  • Tim Holloway
  • Piet Souris
  • Frits Walraven

Is it fine to partition the skill section of resume into primary skills and secondary skills?

 
Ranch Hand
Posts: 1365
8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are some technologies which are part of our main skill set. Example the ones we might have been working on while working on projects in office during last few years. There are some skills which we might have worked on many years back but not in touch since long. Then there are some skills which we learnt by practicing on our own during weekends at home on sample projects as part of self learning but not worked on in office. Mostly out of the 3 categories mentioned here, one would be currently expert at on the first category but not so on the second and third one. Instead of putting all under skills section of resume and keeping it ambiguous for the reader , is it better to partition this section into primary skills and secondary skills. The first category will come under primary skills while the second and third may come under secondary skills.  Is it fine to do this way?

thanks
 
Bartender
Posts: 21756
148
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Around here, they like CVs to be no more than 2 pages, which is hardly sufficient as long as I've been doing things, but then again, they really don't want to hire anyone old enough to have more than 2 pages anyway.

And very frequently, the bulk of the CVs will never meet human eyes, because the demand is made of an MS-Word document which will be machine-scanned for keywords and summarily binned if it's not a good enough match. And by match, I mean "X" years with version "Y" of product Z (whether such a thing is physically possible or not). I'm afraid that Human Resource processors - and people - are not capable enough to deduce that if you have 10 years with DB2 that you just might be able to show competence with Oracle.

So where you put stuff is secondary to what's there.

On the other hand, if you do manage to get the right collection of buzzwords to get it passed on to a human, then the 2-Page Rule kicks in. So if you have any significant experience, it's best to handcraft your CV's according to the company and position you are targeting rather that expect a one-size-fits-all CV to do the job.

And if you haven't learned yet, they'd apparently prefer that you lie and claim more expertise than you have - even if it's more expertise than the product designers themselves can claim - than be honest and fail to meet the unalterable demands. Yes, I'm bitter. And cynical, because they can use a lie as an excuse to fire you if they want. Or worse, threaten you, if you're not sufficiently compliant. My own refusal to lie really upset a pair of recruiters for a local major insurance company once, because they knew I was more than capable, but would not tell a few "harmless fibs" so they couldn't advance me. It was, incidentally, DB2 versus Oracle experience.
 
Monica Shiralkar
Ranch Hand
Posts: 1365
8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

So where you put stuff is secondary to what's there.

On the other hand, if you do manage to get the right collection of buzzwords to get it passed on to a human, then the 2-Page Rule kicks in



thanks.I think if the resume gets shortlisted than since it clearly has primary skills and secondary skills section, the interviewer will have the idea while asking the questions whether this is primary or secondary and the candidate can tell this thing for secondary skill that I have not worked on them in office projects but practiced in sample applications at home.

I want to keep skills on which I have some expertise on under Primary Skills and keep others in Secondary Skills (examples the ones I have practiced as sample applications but not used in office projects or skills which I used in beginning of career and not used in last few years).   When I feel I have developed enough expertise on some of these secondary skills I would move those ones to Primary.
 
Monica Shiralkar
Ranch Hand
Posts: 1365
8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Tim Holloway wrote: really don't want to hire anyone old enough to have more than 2 pages anyway.
.



What is the reason why they do not prefer resumes more than 2 page long?
 
They worship nothing. They say it's because nothing lasts forever. Like this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!