jobs

Resume vs Curriculum Vitae

Old farts like me often have long and detailed LinkedIn profiles that we just copy as Curriculum Vitae when applying for leadership roles.

This is based on two assumptions:

  • People are good at glancing over long texts, reading between lines and forming opinions.
  • Automated resume ranking tools are better at extracting data from long and detailed curriculum vitae rather than one-page resumes.

Both are wrong:

  • HR are not people. Senior HR partners do not read CVs, junior HR may not be as skilled as your Software Engineering pals at reading at drawing conclusions. Your CV has to be digested into a shorter resume for them.
  • None except big tech uses automated resume ranking tools, and even these let junior HR filter the results.

So better:

  • Use your long and detailed CV to feed to ChatGPT so that it tailors it to the individual job description.
  • Assume that people reading your resume are less skilled.

Finally, a curriculum vitae can be roughly translated from Latin as the course of one's life while resume is... well, a resume of your course of life, tailored to a particular situation.

Use one or the other when appropriate.

Tags: 

Recruiter with level SPECIALIST

Here's a an email that I just received from a Belgian recruiter (name changed):
On Fri, Apr 11, 2014 at 04:26:33AM -0400, Abdullah Rahmoyan wrote:
>
> For a well known financial institution, I am currently looking
> for a senior Java developer to take part in a 6 months project.
>
>
> The requested skills are:
>
> - BACK-END AND FRONT-END with level SPECIALIST
>
> - DEVELOPMENT KNOWLEDGE with level SPECIALIST
> - BUILD TOOLS, WEB SERVERS with level SPECIALIST
> - AND DATABASES with level SPECIALIST
> - DESIGN REST SERVICES with level EXPERT
> - AND API'S with level EXPERT
> - JAVA EE6, JAVASCRIPT with level SPECIALIST
> - ANGULARJS,POSTRESQL with level SPECIALIST
> - FULL DETAIS TO BE SENT with level SPECIALIST
> - BY EMAIL with level SPECIALIST