Is it worth putting a skill that is a prerequisite of a lot of other skills on my resume

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
35
down vote

favorite
3












One of the sections of my resume mentions a lot of different JavaScript skills I have.



For example:




AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...




That section just keeps going on about different skills and technologies I know in JavaScript and it's starting to get big.



I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.



So I'm asking is it a good idea to just remove JavaScript from that section?







share|improve this question















  • 40




    You have no way of knowing how they process the resume, whether they do or don't pre-screen for keywords, and whether that screening is clever enough to recognize implied skills.
    – keshlam
    Jul 14 '16 at 18:22







  • 27




    I would never make the assumption that someone who knows JavaScript knows jQuery.
    – Andy Lester
    Jul 14 '16 at 22:22






  • 2




    You should tailor your resume for each different job application. Removing the irrelevant information for that particular job will make it more likely that somebody will get to the relevant information before they stop reading and file it on the "reject" pile. If somebody has the task of filtering 500 applications in half a day, you can work out for yourself how much time they will spend reading each one!
    – alephzero
    Jul 15 '16 at 0:26






  • 2




    Have different CV depending of who you are going to send it to. If you are going to send it to a recruiter, stuff it with keywords (5 years exp jQuery, 5 years exp JavaScript, 2 years exp Angular1, 3 months exp Angular2), etc... If you know that your CV is going to a directly CTO, just explain how badass programmer you are.
    – Daniel
    Jul 15 '16 at 5:59







  • 18




    Anecdote: A friend got a PhD in computational fluid dynamics, or CFD as EVERYONE calls. He got rejected by HR in several jobs because he had CFD written in his CV, so he didn't have the minimum required skills for the job, as he didn't know computational fluid dynamics. My point: HR has no idea of technicalities , if they have been asked for javascript, and they don't see it, they'll reject your CV.
    – Ander Biguri
    Jul 15 '16 at 11:55

















up vote
35
down vote

favorite
3












One of the sections of my resume mentions a lot of different JavaScript skills I have.



For example:




AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...




That section just keeps going on about different skills and technologies I know in JavaScript and it's starting to get big.



I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.



So I'm asking is it a good idea to just remove JavaScript from that section?







share|improve this question















  • 40




    You have no way of knowing how they process the resume, whether they do or don't pre-screen for keywords, and whether that screening is clever enough to recognize implied skills.
    – keshlam
    Jul 14 '16 at 18:22







  • 27




    I would never make the assumption that someone who knows JavaScript knows jQuery.
    – Andy Lester
    Jul 14 '16 at 22:22






  • 2




    You should tailor your resume for each different job application. Removing the irrelevant information for that particular job will make it more likely that somebody will get to the relevant information before they stop reading and file it on the "reject" pile. If somebody has the task of filtering 500 applications in half a day, you can work out for yourself how much time they will spend reading each one!
    – alephzero
    Jul 15 '16 at 0:26






  • 2




    Have different CV depending of who you are going to send it to. If you are going to send it to a recruiter, stuff it with keywords (5 years exp jQuery, 5 years exp JavaScript, 2 years exp Angular1, 3 months exp Angular2), etc... If you know that your CV is going to a directly CTO, just explain how badass programmer you are.
    – Daniel
    Jul 15 '16 at 5:59







  • 18




    Anecdote: A friend got a PhD in computational fluid dynamics, or CFD as EVERYONE calls. He got rejected by HR in several jobs because he had CFD written in his CV, so he didn't have the minimum required skills for the job, as he didn't know computational fluid dynamics. My point: HR has no idea of technicalities , if they have been asked for javascript, and they don't see it, they'll reject your CV.
    – Ander Biguri
    Jul 15 '16 at 11:55













up vote
35
down vote

favorite
3









up vote
35
down vote

favorite
3






3





One of the sections of my resume mentions a lot of different JavaScript skills I have.



For example:




AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...




That section just keeps going on about different skills and technologies I know in JavaScript and it's starting to get big.



I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.



So I'm asking is it a good idea to just remove JavaScript from that section?







share|improve this question











One of the sections of my resume mentions a lot of different JavaScript skills I have.



For example:




AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...




That section just keeps going on about different skills and technologies I know in JavaScript and it's starting to get big.



I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.



So I'm asking is it a good idea to just remove JavaScript from that section?









share|improve this question










share|improve this question




share|improve this question









asked Jul 14 '16 at 18:17









Benjamin Albert

291310




291310







  • 40




    You have no way of knowing how they process the resume, whether they do or don't pre-screen for keywords, and whether that screening is clever enough to recognize implied skills.
    – keshlam
    Jul 14 '16 at 18:22







  • 27




    I would never make the assumption that someone who knows JavaScript knows jQuery.
    – Andy Lester
    Jul 14 '16 at 22:22






  • 2




    You should tailor your resume for each different job application. Removing the irrelevant information for that particular job will make it more likely that somebody will get to the relevant information before they stop reading and file it on the "reject" pile. If somebody has the task of filtering 500 applications in half a day, you can work out for yourself how much time they will spend reading each one!
    – alephzero
    Jul 15 '16 at 0:26






  • 2




    Have different CV depending of who you are going to send it to. If you are going to send it to a recruiter, stuff it with keywords (5 years exp jQuery, 5 years exp JavaScript, 2 years exp Angular1, 3 months exp Angular2), etc... If you know that your CV is going to a directly CTO, just explain how badass programmer you are.
    – Daniel
    Jul 15 '16 at 5:59







  • 18




    Anecdote: A friend got a PhD in computational fluid dynamics, or CFD as EVERYONE calls. He got rejected by HR in several jobs because he had CFD written in his CV, so he didn't have the minimum required skills for the job, as he didn't know computational fluid dynamics. My point: HR has no idea of technicalities , if they have been asked for javascript, and they don't see it, they'll reject your CV.
    – Ander Biguri
    Jul 15 '16 at 11:55













  • 40




    You have no way of knowing how they process the resume, whether they do or don't pre-screen for keywords, and whether that screening is clever enough to recognize implied skills.
    – keshlam
    Jul 14 '16 at 18:22







  • 27




    I would never make the assumption that someone who knows JavaScript knows jQuery.
    – Andy Lester
    Jul 14 '16 at 22:22






  • 2




    You should tailor your resume for each different job application. Removing the irrelevant information for that particular job will make it more likely that somebody will get to the relevant information before they stop reading and file it on the "reject" pile. If somebody has the task of filtering 500 applications in half a day, you can work out for yourself how much time they will spend reading each one!
    – alephzero
    Jul 15 '16 at 0:26






  • 2




    Have different CV depending of who you are going to send it to. If you are going to send it to a recruiter, stuff it with keywords (5 years exp jQuery, 5 years exp JavaScript, 2 years exp Angular1, 3 months exp Angular2), etc... If you know that your CV is going to a directly CTO, just explain how badass programmer you are.
    – Daniel
    Jul 15 '16 at 5:59







  • 18




    Anecdote: A friend got a PhD in computational fluid dynamics, or CFD as EVERYONE calls. He got rejected by HR in several jobs because he had CFD written in his CV, so he didn't have the minimum required skills for the job, as he didn't know computational fluid dynamics. My point: HR has no idea of technicalities , if they have been asked for javascript, and they don't see it, they'll reject your CV.
    – Ander Biguri
    Jul 15 '16 at 11:55








40




40




You have no way of knowing how they process the resume, whether they do or don't pre-screen for keywords, and whether that screening is clever enough to recognize implied skills.
– keshlam
Jul 14 '16 at 18:22





You have no way of knowing how they process the resume, whether they do or don't pre-screen for keywords, and whether that screening is clever enough to recognize implied skills.
– keshlam
Jul 14 '16 at 18:22





27




27




I would never make the assumption that someone who knows JavaScript knows jQuery.
– Andy Lester
Jul 14 '16 at 22:22




I would never make the assumption that someone who knows JavaScript knows jQuery.
– Andy Lester
Jul 14 '16 at 22:22




2




2




You should tailor your resume for each different job application. Removing the irrelevant information for that particular job will make it more likely that somebody will get to the relevant information before they stop reading and file it on the "reject" pile. If somebody has the task of filtering 500 applications in half a day, you can work out for yourself how much time they will spend reading each one!
– alephzero
Jul 15 '16 at 0:26




You should tailor your resume for each different job application. Removing the irrelevant information for that particular job will make it more likely that somebody will get to the relevant information before they stop reading and file it on the "reject" pile. If somebody has the task of filtering 500 applications in half a day, you can work out for yourself how much time they will spend reading each one!
– alephzero
Jul 15 '16 at 0:26




2




2




Have different CV depending of who you are going to send it to. If you are going to send it to a recruiter, stuff it with keywords (5 years exp jQuery, 5 years exp JavaScript, 2 years exp Angular1, 3 months exp Angular2), etc... If you know that your CV is going to a directly CTO, just explain how badass programmer you are.
– Daniel
Jul 15 '16 at 5:59





Have different CV depending of who you are going to send it to. If you are going to send it to a recruiter, stuff it with keywords (5 years exp jQuery, 5 years exp JavaScript, 2 years exp Angular1, 3 months exp Angular2), etc... If you know that your CV is going to a directly CTO, just explain how badass programmer you are.
– Daniel
Jul 15 '16 at 5:59





18




18




Anecdote: A friend got a PhD in computational fluid dynamics, or CFD as EVERYONE calls. He got rejected by HR in several jobs because he had CFD written in his CV, so he didn't have the minimum required skills for the job, as he didn't know computational fluid dynamics. My point: HR has no idea of technicalities , if they have been asked for javascript, and they don't see it, they'll reject your CV.
– Ander Biguri
Jul 15 '16 at 11:55





Anecdote: A friend got a PhD in computational fluid dynamics, or CFD as EVERYONE calls. He got rejected by HR in several jobs because he had CFD written in his CV, so he didn't have the minimum required skills for the job, as he didn't know computational fluid dynamics. My point: HR has no idea of technicalities , if they have been asked for javascript, and they don't see it, they'll reject your CV.
– Ander Biguri
Jul 15 '16 at 11:55











7 Answers
7






active

oldest

votes

















up vote
61
down vote



accepted










It should not be a problem to keep it unless perhaps you're really running out of space. As many non-technical recruiters may be reviewing your qualifications, it wouldn't hurt to have it on the resume. I think for some, JavaScript may be more recognizable than say, PhantomJS.






share|improve this answer





















  • I guess I'll just have to find another less important keyword in that section to remove. Thanks for the answer.
    – Benjamin Albert
    Jul 14 '16 at 18:38






  • 67




    I'd even categorize all of those as "JavaScript expertise" - make that the heading and then list all the details. It gets the hitword on your resume and collects the information nicely.
    – bethlakshmi
    Jul 14 '16 at 18:54






  • 4




    +1 and I agree with using a category of JavaScript as bethlakshmi suggests. I've actually had manager's, after I told them of my experience with Node/jQuery, ask if I have any experience with JavaScript. I've also experienced saying I have experience in JavaScript, and then the manager/interviewer say, "Oh, you've worked with Java?" As a specialist, remember: you are supposed to be the expert, so be friendly to people who don't exactly know what all the terms mean. Their checks cash just as well as anyone else's.
    – BrianH
    Jul 14 '16 at 22:42










  • @bethlakshmi That would be a great idea if I had extra space on my resume. Unfortunately I'm asking this question because I need extra space and I thought removing JavaScript (and other keywords) would be a good idea because I thought it's obvious I know JavaScript if I have all these other skills.
    – Benjamin Albert
    Jul 15 '16 at 4:40






  • 5




    It might be worth it to keep JavaScript in as long as you are skilled in native javascript. Many can use jQuery and/or other frameworks, but are unable to build complex apps in pure JavaScript. If this is your case, it might be good idea to mention "native expertise" as well
    – Adam Fischer
    Jul 15 '16 at 11:13


















up vote
35
down vote













Another factor is automated screening processes. You and any remotely technical recruiter/manager would know that Node.js or React implies JavaScript capabilities but if they never see your resume because the automated system filters out your resume it isn't going to matter.



It is always a good idea to make your that your resume specifically lists any requirements the job posting has and matches the way they list the requirement. Don't abbreviate or use an industry synonym or some skill that is a super-set of the required skills. If they want an expert in Widget 123 then list Widget 123 on your resume not Widgets 100-200.






share|improve this answer



















  • 3




    Yes, what I was going to answer. An ATS looks for keywords, it has no intelligence of it's own to link things together. So if the job advert mentions Javascript, you need to have Javascript in your resume, or it's points against you.
    – The Wandering Dev Manager
    Jul 14 '16 at 19:22

















up vote
25
down vote














So I'm asking is it a good idea to just remove JavaScript from that
section?




No, leave it in.



First, many non-technical recruiters look only for keywords given to them by the hiring manager. If the manager specifies "must know JavaScript" you want JavaScript to be included.



Second, a lot of software used by recruiters and HR is keyword-driven. So you want to match the keyword "JavaScript".



Lastly, leaving it off saves exactly one word. Not worth the risk.






share|improve this answer






























    up vote
    10
    down vote













    Not everyone who reads your resume will have the technical expertise of the hiring manager.




    I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.




    That might be, if everyone that will read your resume is the hiring manager. The hiring manager is probably only one person out of 5-10 that will look at it.



    Scenario 1: HR clerk gets assigned the task of going and searching for resumes on the web, or a resume site like Monster. Clerk reads your resume and says "This guy looks good, but he only knows React and jQuery, and we need someone who knows JavaScript." Passed over.



    Scenario 2: HR clerk searches Monster for "JavaScript", and your resume never shows up in search results.



    Scenario 3: HR clerk is the filter on all inbound resumes. He knows only to forward on the people who know JavaScript. Rejected.



    Scenario 4: It's time for a group interview, so the hiring manager hands out your resume to her superiors, or other members of your team who aren't programmers. "This person doesn't even meet the minimum requirements!" says the VP.



    This applies to more than your JavaScript examples:



    • If you know Rails or Sinatra, then also say you know Ruby.

    • If you know Oracle or Postgres, then also say you know SQL.

    • If you know Debian or RedHat, then also say you know Linux.

    • If you know C++, and you also know C, then list them both.

    • etc etc etc





    share|improve this answer























    • two Scenario 3's?
      – Aaron Hall
      Jul 15 '16 at 3:34






    • 1




      +1 for "This applies to more than your JavaScript" this is way I asked this question because it applies to more than just JavaScript on my resume.
      – Benjamin Albert
      Jul 15 '16 at 4:59







    • 7




      "If you know C++, then also say you know C." Please don't. These are two different languages.
      – etarion
      Jul 15 '16 at 6:27










    • @etarion: Thanks, I've clarified it.
      – Andy Lester
      Jul 15 '16 at 14:10






    • 1




      @etarion: C++ is a close superset of C so the claim is not such a stress. If one was to be that precise, the Debian -> Linux implication is not correct either.
      – WoJ
      Jul 15 '16 at 17:15

















    up vote
    2
    down vote













    I think that it's best to leave JavaScript in for an additional reason: the answer implies that you are familiar with and can work with plain old "vanilla" JavaScript, which sometimes you do have to do. Sometimes an employer for whatever reason isn't going to let you install an Angular or node.js framework on a site or even jQuery (I've seen it before, usually when the library impacts with something someone wrote for the site years before). Sometimes the job might entail "middle end" work that's neither directly involved with creating controllers and views or working with the back end per se. If you're familiar enough with JS, including its foibles, yes, you should list that.



    The other issue here is that a lot of employers - maybe even the majority now - don't actually read your resume at first, they run it through a scanner looking for keywords and only come back to actually flip through it if the keywords are there. It's entirely possible that someone who needs a JS developer didn't bother to put Angular or React in as keywords because, I don't know, they don't actually use Angular or React for instance. If you don't say Javascript too you might miss out precisely because a human isn't interacting with your resume at the first level.






    share|improve this answer




























      up vote
      1
      down vote













      Note: I consider this to be an excellent example of a more general principle. In general, when communicating, you want to communicate in a way that will be understood. That involves knowing your audience. If you are applying to a local shop, with 6 current staff in total, named JavaScript Improvers, Inc., and you are customizing your resume which will be sent directly to the CTO, then you may be able to leave off certain information. In general, knowing your audience is always helpful. For most larger companies, as stated in other answers, you don't want to assume that your audience understands basic technical terms, pre-requisites, etc. (They may be humans who don't know enough about some pre-requisites, or computer programs that may not have certain pre-requisites identified.) As Joe Strazzere's answer mentions, you don't want to miss out on a common search term.



      However, rather than just "leaving it in", and thereby mixing JavaScript with the other technologies, I have another idea: Removing JavaScript from that section might be a good idea. At the same time, rename the section from "skills" to "other skills". Then, separately, create another JavaScript section:





      JavaScript-Related Skills



      • AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...


      Other Useful Skills



      • Infinite loops, buffer overflows, Heisenbugs, dividing by zero, off-by-ones, syntax errors, etc.



      (The above example is just meant to demonstrate the basic concept. Clearly you'll want to customize what is seen above. Specific details on precisely how to do that can vary depending on other characteristics about your specific resume.)






      share|improve this answer




























        up vote
        -1
        down vote













        Many recruiters would not know. For a sure a word search would not know. Yes list it if you think there is a market.






        share|improve this answer





















          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "423"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          noCode: true, onDemand: false,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f71366%2fis-it-worth-putting-a-skill-that-is-a-prerequisite-of-a-lot-of-other-skills-on-m%23new-answer', 'question_page');

          );

          Post as a guest

























          StackExchange.ready(function ()
          $("#show-editor-button input, #show-editor-button button").click(function ()
          var showEditor = function()
          $("#show-editor-button").hide();
          $("#post-form").removeClass("dno");
          StackExchange.editor.finallyInit();
          ;

          var useFancy = $(this).data('confirm-use-fancy');
          if(useFancy == 'True')
          var popupTitle = $(this).data('confirm-fancy-title');
          var popupBody = $(this).data('confirm-fancy-body');
          var popupAccept = $(this).data('confirm-fancy-accept-button');

          $(this).loadPopup(
          url: '/post/self-answer-popup',
          loaded: function(popup)
          var pTitle = $(popup).find('h2');
          var pBody = $(popup).find('.popup-body');
          var pSubmit = $(popup).find('.popup-submit');

          pTitle.text(popupTitle);
          pBody.html(popupBody);
          pSubmit.val(popupAccept).click(showEditor);

          )
          else
          var confirmText = $(this).data('confirm-text');
          if (confirmText ? confirm(confirmText) : true)
          showEditor();


          );
          );






          7 Answers
          7






          active

          oldest

          votes








          7 Answers
          7






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          61
          down vote



          accepted










          It should not be a problem to keep it unless perhaps you're really running out of space. As many non-technical recruiters may be reviewing your qualifications, it wouldn't hurt to have it on the resume. I think for some, JavaScript may be more recognizable than say, PhantomJS.






          share|improve this answer





















          • I guess I'll just have to find another less important keyword in that section to remove. Thanks for the answer.
            – Benjamin Albert
            Jul 14 '16 at 18:38






          • 67




            I'd even categorize all of those as "JavaScript expertise" - make that the heading and then list all the details. It gets the hitword on your resume and collects the information nicely.
            – bethlakshmi
            Jul 14 '16 at 18:54






          • 4




            +1 and I agree with using a category of JavaScript as bethlakshmi suggests. I've actually had manager's, after I told them of my experience with Node/jQuery, ask if I have any experience with JavaScript. I've also experienced saying I have experience in JavaScript, and then the manager/interviewer say, "Oh, you've worked with Java?" As a specialist, remember: you are supposed to be the expert, so be friendly to people who don't exactly know what all the terms mean. Their checks cash just as well as anyone else's.
            – BrianH
            Jul 14 '16 at 22:42










          • @bethlakshmi That would be a great idea if I had extra space on my resume. Unfortunately I'm asking this question because I need extra space and I thought removing JavaScript (and other keywords) would be a good idea because I thought it's obvious I know JavaScript if I have all these other skills.
            – Benjamin Albert
            Jul 15 '16 at 4:40






          • 5




            It might be worth it to keep JavaScript in as long as you are skilled in native javascript. Many can use jQuery and/or other frameworks, but are unable to build complex apps in pure JavaScript. If this is your case, it might be good idea to mention "native expertise" as well
            – Adam Fischer
            Jul 15 '16 at 11:13















          up vote
          61
          down vote



          accepted










          It should not be a problem to keep it unless perhaps you're really running out of space. As many non-technical recruiters may be reviewing your qualifications, it wouldn't hurt to have it on the resume. I think for some, JavaScript may be more recognizable than say, PhantomJS.






          share|improve this answer





















          • I guess I'll just have to find another less important keyword in that section to remove. Thanks for the answer.
            – Benjamin Albert
            Jul 14 '16 at 18:38






          • 67




            I'd even categorize all of those as "JavaScript expertise" - make that the heading and then list all the details. It gets the hitword on your resume and collects the information nicely.
            – bethlakshmi
            Jul 14 '16 at 18:54






          • 4




            +1 and I agree with using a category of JavaScript as bethlakshmi suggests. I've actually had manager's, after I told them of my experience with Node/jQuery, ask if I have any experience with JavaScript. I've also experienced saying I have experience in JavaScript, and then the manager/interviewer say, "Oh, you've worked with Java?" As a specialist, remember: you are supposed to be the expert, so be friendly to people who don't exactly know what all the terms mean. Their checks cash just as well as anyone else's.
            – BrianH
            Jul 14 '16 at 22:42










          • @bethlakshmi That would be a great idea if I had extra space on my resume. Unfortunately I'm asking this question because I need extra space and I thought removing JavaScript (and other keywords) would be a good idea because I thought it's obvious I know JavaScript if I have all these other skills.
            – Benjamin Albert
            Jul 15 '16 at 4:40






          • 5




            It might be worth it to keep JavaScript in as long as you are skilled in native javascript. Many can use jQuery and/or other frameworks, but are unable to build complex apps in pure JavaScript. If this is your case, it might be good idea to mention "native expertise" as well
            – Adam Fischer
            Jul 15 '16 at 11:13













          up vote
          61
          down vote



          accepted







          up vote
          61
          down vote



          accepted






          It should not be a problem to keep it unless perhaps you're really running out of space. As many non-technical recruiters may be reviewing your qualifications, it wouldn't hurt to have it on the resume. I think for some, JavaScript may be more recognizable than say, PhantomJS.






          share|improve this answer













          It should not be a problem to keep it unless perhaps you're really running out of space. As many non-technical recruiters may be reviewing your qualifications, it wouldn't hurt to have it on the resume. I think for some, JavaScript may be more recognizable than say, PhantomJS.







          share|improve this answer













          share|improve this answer



          share|improve this answer











          answered Jul 14 '16 at 18:22









          Bernard Dy

          1,3871125




          1,3871125











          • I guess I'll just have to find another less important keyword in that section to remove. Thanks for the answer.
            – Benjamin Albert
            Jul 14 '16 at 18:38






          • 67




            I'd even categorize all of those as "JavaScript expertise" - make that the heading and then list all the details. It gets the hitword on your resume and collects the information nicely.
            – bethlakshmi
            Jul 14 '16 at 18:54






          • 4




            +1 and I agree with using a category of JavaScript as bethlakshmi suggests. I've actually had manager's, after I told them of my experience with Node/jQuery, ask if I have any experience with JavaScript. I've also experienced saying I have experience in JavaScript, and then the manager/interviewer say, "Oh, you've worked with Java?" As a specialist, remember: you are supposed to be the expert, so be friendly to people who don't exactly know what all the terms mean. Their checks cash just as well as anyone else's.
            – BrianH
            Jul 14 '16 at 22:42










          • @bethlakshmi That would be a great idea if I had extra space on my resume. Unfortunately I'm asking this question because I need extra space and I thought removing JavaScript (and other keywords) would be a good idea because I thought it's obvious I know JavaScript if I have all these other skills.
            – Benjamin Albert
            Jul 15 '16 at 4:40






          • 5




            It might be worth it to keep JavaScript in as long as you are skilled in native javascript. Many can use jQuery and/or other frameworks, but are unable to build complex apps in pure JavaScript. If this is your case, it might be good idea to mention "native expertise" as well
            – Adam Fischer
            Jul 15 '16 at 11:13

















          • I guess I'll just have to find another less important keyword in that section to remove. Thanks for the answer.
            – Benjamin Albert
            Jul 14 '16 at 18:38






          • 67




            I'd even categorize all of those as "JavaScript expertise" - make that the heading and then list all the details. It gets the hitword on your resume and collects the information nicely.
            – bethlakshmi
            Jul 14 '16 at 18:54






          • 4




            +1 and I agree with using a category of JavaScript as bethlakshmi suggests. I've actually had manager's, after I told them of my experience with Node/jQuery, ask if I have any experience with JavaScript. I've also experienced saying I have experience in JavaScript, and then the manager/interviewer say, "Oh, you've worked with Java?" As a specialist, remember: you are supposed to be the expert, so be friendly to people who don't exactly know what all the terms mean. Their checks cash just as well as anyone else's.
            – BrianH
            Jul 14 '16 at 22:42










          • @bethlakshmi That would be a great idea if I had extra space on my resume. Unfortunately I'm asking this question because I need extra space and I thought removing JavaScript (and other keywords) would be a good idea because I thought it's obvious I know JavaScript if I have all these other skills.
            – Benjamin Albert
            Jul 15 '16 at 4:40






          • 5




            It might be worth it to keep JavaScript in as long as you are skilled in native javascript. Many can use jQuery and/or other frameworks, but are unable to build complex apps in pure JavaScript. If this is your case, it might be good idea to mention "native expertise" as well
            – Adam Fischer
            Jul 15 '16 at 11:13
















          I guess I'll just have to find another less important keyword in that section to remove. Thanks for the answer.
          – Benjamin Albert
          Jul 14 '16 at 18:38




          I guess I'll just have to find another less important keyword in that section to remove. Thanks for the answer.
          – Benjamin Albert
          Jul 14 '16 at 18:38




          67




          67




          I'd even categorize all of those as "JavaScript expertise" - make that the heading and then list all the details. It gets the hitword on your resume and collects the information nicely.
          – bethlakshmi
          Jul 14 '16 at 18:54




          I'd even categorize all of those as "JavaScript expertise" - make that the heading and then list all the details. It gets the hitword on your resume and collects the information nicely.
          – bethlakshmi
          Jul 14 '16 at 18:54




          4




          4




          +1 and I agree with using a category of JavaScript as bethlakshmi suggests. I've actually had manager's, after I told them of my experience with Node/jQuery, ask if I have any experience with JavaScript. I've also experienced saying I have experience in JavaScript, and then the manager/interviewer say, "Oh, you've worked with Java?" As a specialist, remember: you are supposed to be the expert, so be friendly to people who don't exactly know what all the terms mean. Their checks cash just as well as anyone else's.
          – BrianH
          Jul 14 '16 at 22:42




          +1 and I agree with using a category of JavaScript as bethlakshmi suggests. I've actually had manager's, after I told them of my experience with Node/jQuery, ask if I have any experience with JavaScript. I've also experienced saying I have experience in JavaScript, and then the manager/interviewer say, "Oh, you've worked with Java?" As a specialist, remember: you are supposed to be the expert, so be friendly to people who don't exactly know what all the terms mean. Their checks cash just as well as anyone else's.
          – BrianH
          Jul 14 '16 at 22:42












          @bethlakshmi That would be a great idea if I had extra space on my resume. Unfortunately I'm asking this question because I need extra space and I thought removing JavaScript (and other keywords) would be a good idea because I thought it's obvious I know JavaScript if I have all these other skills.
          – Benjamin Albert
          Jul 15 '16 at 4:40




          @bethlakshmi That would be a great idea if I had extra space on my resume. Unfortunately I'm asking this question because I need extra space and I thought removing JavaScript (and other keywords) would be a good idea because I thought it's obvious I know JavaScript if I have all these other skills.
          – Benjamin Albert
          Jul 15 '16 at 4:40




          5




          5




          It might be worth it to keep JavaScript in as long as you are skilled in native javascript. Many can use jQuery and/or other frameworks, but are unable to build complex apps in pure JavaScript. If this is your case, it might be good idea to mention "native expertise" as well
          – Adam Fischer
          Jul 15 '16 at 11:13





          It might be worth it to keep JavaScript in as long as you are skilled in native javascript. Many can use jQuery and/or other frameworks, but are unable to build complex apps in pure JavaScript. If this is your case, it might be good idea to mention "native expertise" as well
          – Adam Fischer
          Jul 15 '16 at 11:13













          up vote
          35
          down vote













          Another factor is automated screening processes. You and any remotely technical recruiter/manager would know that Node.js or React implies JavaScript capabilities but if they never see your resume because the automated system filters out your resume it isn't going to matter.



          It is always a good idea to make your that your resume specifically lists any requirements the job posting has and matches the way they list the requirement. Don't abbreviate or use an industry synonym or some skill that is a super-set of the required skills. If they want an expert in Widget 123 then list Widget 123 on your resume not Widgets 100-200.






          share|improve this answer



















          • 3




            Yes, what I was going to answer. An ATS looks for keywords, it has no intelligence of it's own to link things together. So if the job advert mentions Javascript, you need to have Javascript in your resume, or it's points against you.
            – The Wandering Dev Manager
            Jul 14 '16 at 19:22














          up vote
          35
          down vote













          Another factor is automated screening processes. You and any remotely technical recruiter/manager would know that Node.js or React implies JavaScript capabilities but if they never see your resume because the automated system filters out your resume it isn't going to matter.



          It is always a good idea to make your that your resume specifically lists any requirements the job posting has and matches the way they list the requirement. Don't abbreviate or use an industry synonym or some skill that is a super-set of the required skills. If they want an expert in Widget 123 then list Widget 123 on your resume not Widgets 100-200.






          share|improve this answer



















          • 3




            Yes, what I was going to answer. An ATS looks for keywords, it has no intelligence of it's own to link things together. So if the job advert mentions Javascript, you need to have Javascript in your resume, or it's points against you.
            – The Wandering Dev Manager
            Jul 14 '16 at 19:22












          up vote
          35
          down vote










          up vote
          35
          down vote









          Another factor is automated screening processes. You and any remotely technical recruiter/manager would know that Node.js or React implies JavaScript capabilities but if they never see your resume because the automated system filters out your resume it isn't going to matter.



          It is always a good idea to make your that your resume specifically lists any requirements the job posting has and matches the way they list the requirement. Don't abbreviate or use an industry synonym or some skill that is a super-set of the required skills. If they want an expert in Widget 123 then list Widget 123 on your resume not Widgets 100-200.






          share|improve this answer















          Another factor is automated screening processes. You and any remotely technical recruiter/manager would know that Node.js or React implies JavaScript capabilities but if they never see your resume because the automated system filters out your resume it isn't going to matter.



          It is always a good idea to make your that your resume specifically lists any requirements the job posting has and matches the way they list the requirement. Don't abbreviate or use an industry synonym or some skill that is a super-set of the required skills. If they want an expert in Widget 123 then list Widget 123 on your resume not Widgets 100-200.







          share|improve this answer















          share|improve this answer



          share|improve this answer








          edited Jul 14 '16 at 20:25


























          answered Jul 14 '16 at 19:06









          Evan Steinbrenner

          76539




          76539







          • 3




            Yes, what I was going to answer. An ATS looks for keywords, it has no intelligence of it's own to link things together. So if the job advert mentions Javascript, you need to have Javascript in your resume, or it's points against you.
            – The Wandering Dev Manager
            Jul 14 '16 at 19:22












          • 3




            Yes, what I was going to answer. An ATS looks for keywords, it has no intelligence of it's own to link things together. So if the job advert mentions Javascript, you need to have Javascript in your resume, or it's points against you.
            – The Wandering Dev Manager
            Jul 14 '16 at 19:22







          3




          3




          Yes, what I was going to answer. An ATS looks for keywords, it has no intelligence of it's own to link things together. So if the job advert mentions Javascript, you need to have Javascript in your resume, or it's points against you.
          – The Wandering Dev Manager
          Jul 14 '16 at 19:22




          Yes, what I was going to answer. An ATS looks for keywords, it has no intelligence of it's own to link things together. So if the job advert mentions Javascript, you need to have Javascript in your resume, or it's points against you.
          – The Wandering Dev Manager
          Jul 14 '16 at 19:22










          up vote
          25
          down vote














          So I'm asking is it a good idea to just remove JavaScript from that
          section?




          No, leave it in.



          First, many non-technical recruiters look only for keywords given to them by the hiring manager. If the manager specifies "must know JavaScript" you want JavaScript to be included.



          Second, a lot of software used by recruiters and HR is keyword-driven. So you want to match the keyword "JavaScript".



          Lastly, leaving it off saves exactly one word. Not worth the risk.






          share|improve this answer



























            up vote
            25
            down vote














            So I'm asking is it a good idea to just remove JavaScript from that
            section?




            No, leave it in.



            First, many non-technical recruiters look only for keywords given to them by the hiring manager. If the manager specifies "must know JavaScript" you want JavaScript to be included.



            Second, a lot of software used by recruiters and HR is keyword-driven. So you want to match the keyword "JavaScript".



            Lastly, leaving it off saves exactly one word. Not worth the risk.






            share|improve this answer

























              up vote
              25
              down vote










              up vote
              25
              down vote










              So I'm asking is it a good idea to just remove JavaScript from that
              section?




              No, leave it in.



              First, many non-technical recruiters look only for keywords given to them by the hiring manager. If the manager specifies "must know JavaScript" you want JavaScript to be included.



              Second, a lot of software used by recruiters and HR is keyword-driven. So you want to match the keyword "JavaScript".



              Lastly, leaving it off saves exactly one word. Not worth the risk.






              share|improve this answer
















              So I'm asking is it a good idea to just remove JavaScript from that
              section?




              No, leave it in.



              First, many non-technical recruiters look only for keywords given to them by the hiring manager. If the manager specifies "must know JavaScript" you want JavaScript to be included.



              Second, a lot of software used by recruiters and HR is keyword-driven. So you want to match the keyword "JavaScript".



              Lastly, leaving it off saves exactly one word. Not worth the risk.







              share|improve this answer















              share|improve this answer



              share|improve this answer








              edited Jul 15 '16 at 16:21









              Community♦

              1




              1











              answered Jul 14 '16 at 19:10









              Joe Strazzere

              222k101648913




              222k101648913




















                  up vote
                  10
                  down vote













                  Not everyone who reads your resume will have the technical expertise of the hiring manager.




                  I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.




                  That might be, if everyone that will read your resume is the hiring manager. The hiring manager is probably only one person out of 5-10 that will look at it.



                  Scenario 1: HR clerk gets assigned the task of going and searching for resumes on the web, or a resume site like Monster. Clerk reads your resume and says "This guy looks good, but he only knows React and jQuery, and we need someone who knows JavaScript." Passed over.



                  Scenario 2: HR clerk searches Monster for "JavaScript", and your resume never shows up in search results.



                  Scenario 3: HR clerk is the filter on all inbound resumes. He knows only to forward on the people who know JavaScript. Rejected.



                  Scenario 4: It's time for a group interview, so the hiring manager hands out your resume to her superiors, or other members of your team who aren't programmers. "This person doesn't even meet the minimum requirements!" says the VP.



                  This applies to more than your JavaScript examples:



                  • If you know Rails or Sinatra, then also say you know Ruby.

                  • If you know Oracle or Postgres, then also say you know SQL.

                  • If you know Debian or RedHat, then also say you know Linux.

                  • If you know C++, and you also know C, then list them both.

                  • etc etc etc





                  share|improve this answer























                  • two Scenario 3's?
                    – Aaron Hall
                    Jul 15 '16 at 3:34






                  • 1




                    +1 for "This applies to more than your JavaScript" this is way I asked this question because it applies to more than just JavaScript on my resume.
                    – Benjamin Albert
                    Jul 15 '16 at 4:59







                  • 7




                    "If you know C++, then also say you know C." Please don't. These are two different languages.
                    – etarion
                    Jul 15 '16 at 6:27










                  • @etarion: Thanks, I've clarified it.
                    – Andy Lester
                    Jul 15 '16 at 14:10






                  • 1




                    @etarion: C++ is a close superset of C so the claim is not such a stress. If one was to be that precise, the Debian -> Linux implication is not correct either.
                    – WoJ
                    Jul 15 '16 at 17:15














                  up vote
                  10
                  down vote













                  Not everyone who reads your resume will have the technical expertise of the hiring manager.




                  I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.




                  That might be, if everyone that will read your resume is the hiring manager. The hiring manager is probably only one person out of 5-10 that will look at it.



                  Scenario 1: HR clerk gets assigned the task of going and searching for resumes on the web, or a resume site like Monster. Clerk reads your resume and says "This guy looks good, but he only knows React and jQuery, and we need someone who knows JavaScript." Passed over.



                  Scenario 2: HR clerk searches Monster for "JavaScript", and your resume never shows up in search results.



                  Scenario 3: HR clerk is the filter on all inbound resumes. He knows only to forward on the people who know JavaScript. Rejected.



                  Scenario 4: It's time for a group interview, so the hiring manager hands out your resume to her superiors, or other members of your team who aren't programmers. "This person doesn't even meet the minimum requirements!" says the VP.



                  This applies to more than your JavaScript examples:



                  • If you know Rails or Sinatra, then also say you know Ruby.

                  • If you know Oracle or Postgres, then also say you know SQL.

                  • If you know Debian or RedHat, then also say you know Linux.

                  • If you know C++, and you also know C, then list them both.

                  • etc etc etc





                  share|improve this answer























                  • two Scenario 3's?
                    – Aaron Hall
                    Jul 15 '16 at 3:34






                  • 1




                    +1 for "This applies to more than your JavaScript" this is way I asked this question because it applies to more than just JavaScript on my resume.
                    – Benjamin Albert
                    Jul 15 '16 at 4:59







                  • 7




                    "If you know C++, then also say you know C." Please don't. These are two different languages.
                    – etarion
                    Jul 15 '16 at 6:27










                  • @etarion: Thanks, I've clarified it.
                    – Andy Lester
                    Jul 15 '16 at 14:10






                  • 1




                    @etarion: C++ is a close superset of C so the claim is not such a stress. If one was to be that precise, the Debian -> Linux implication is not correct either.
                    – WoJ
                    Jul 15 '16 at 17:15












                  up vote
                  10
                  down vote










                  up vote
                  10
                  down vote









                  Not everyone who reads your resume will have the technical expertise of the hiring manager.




                  I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.




                  That might be, if everyone that will read your resume is the hiring manager. The hiring manager is probably only one person out of 5-10 that will look at it.



                  Scenario 1: HR clerk gets assigned the task of going and searching for resumes on the web, or a resume site like Monster. Clerk reads your resume and says "This guy looks good, but he only knows React and jQuery, and we need someone who knows JavaScript." Passed over.



                  Scenario 2: HR clerk searches Monster for "JavaScript", and your resume never shows up in search results.



                  Scenario 3: HR clerk is the filter on all inbound resumes. He knows only to forward on the people who know JavaScript. Rejected.



                  Scenario 4: It's time for a group interview, so the hiring manager hands out your resume to her superiors, or other members of your team who aren't programmers. "This person doesn't even meet the minimum requirements!" says the VP.



                  This applies to more than your JavaScript examples:



                  • If you know Rails or Sinatra, then also say you know Ruby.

                  • If you know Oracle or Postgres, then also say you know SQL.

                  • If you know Debian or RedHat, then also say you know Linux.

                  • If you know C++, and you also know C, then list them both.

                  • etc etc etc





                  share|improve this answer















                  Not everyone who reads your resume will have the technical expertise of the hiring manager.




                  I'm starting to think that almost anyone searching for an employee with Node.js or React skills would know that you cannot have those skills without knowing JavaScript.




                  That might be, if everyone that will read your resume is the hiring manager. The hiring manager is probably only one person out of 5-10 that will look at it.



                  Scenario 1: HR clerk gets assigned the task of going and searching for resumes on the web, or a resume site like Monster. Clerk reads your resume and says "This guy looks good, but he only knows React and jQuery, and we need someone who knows JavaScript." Passed over.



                  Scenario 2: HR clerk searches Monster for "JavaScript", and your resume never shows up in search results.



                  Scenario 3: HR clerk is the filter on all inbound resumes. He knows only to forward on the people who know JavaScript. Rejected.



                  Scenario 4: It's time for a group interview, so the hiring manager hands out your resume to her superiors, or other members of your team who aren't programmers. "This person doesn't even meet the minimum requirements!" says the VP.



                  This applies to more than your JavaScript examples:



                  • If you know Rails or Sinatra, then also say you know Ruby.

                  • If you know Oracle or Postgres, then also say you know SQL.

                  • If you know Debian or RedHat, then also say you know Linux.

                  • If you know C++, and you also know C, then list them both.

                  • etc etc etc






                  share|improve this answer















                  share|improve this answer



                  share|improve this answer








                  edited Jul 15 '16 at 14:10


























                  answered Jul 14 '16 at 22:33









                  Andy Lester

                  76749




                  76749











                  • two Scenario 3's?
                    – Aaron Hall
                    Jul 15 '16 at 3:34






                  • 1




                    +1 for "This applies to more than your JavaScript" this is way I asked this question because it applies to more than just JavaScript on my resume.
                    – Benjamin Albert
                    Jul 15 '16 at 4:59







                  • 7




                    "If you know C++, then also say you know C." Please don't. These are two different languages.
                    – etarion
                    Jul 15 '16 at 6:27










                  • @etarion: Thanks, I've clarified it.
                    – Andy Lester
                    Jul 15 '16 at 14:10






                  • 1




                    @etarion: C++ is a close superset of C so the claim is not such a stress. If one was to be that precise, the Debian -> Linux implication is not correct either.
                    – WoJ
                    Jul 15 '16 at 17:15
















                  • two Scenario 3's?
                    – Aaron Hall
                    Jul 15 '16 at 3:34






                  • 1




                    +1 for "This applies to more than your JavaScript" this is way I asked this question because it applies to more than just JavaScript on my resume.
                    – Benjamin Albert
                    Jul 15 '16 at 4:59







                  • 7




                    "If you know C++, then also say you know C." Please don't. These are two different languages.
                    – etarion
                    Jul 15 '16 at 6:27










                  • @etarion: Thanks, I've clarified it.
                    – Andy Lester
                    Jul 15 '16 at 14:10






                  • 1




                    @etarion: C++ is a close superset of C so the claim is not such a stress. If one was to be that precise, the Debian -> Linux implication is not correct either.
                    – WoJ
                    Jul 15 '16 at 17:15















                  two Scenario 3's?
                  – Aaron Hall
                  Jul 15 '16 at 3:34




                  two Scenario 3's?
                  – Aaron Hall
                  Jul 15 '16 at 3:34




                  1




                  1




                  +1 for "This applies to more than your JavaScript" this is way I asked this question because it applies to more than just JavaScript on my resume.
                  – Benjamin Albert
                  Jul 15 '16 at 4:59





                  +1 for "This applies to more than your JavaScript" this is way I asked this question because it applies to more than just JavaScript on my resume.
                  – Benjamin Albert
                  Jul 15 '16 at 4:59





                  7




                  7




                  "If you know C++, then also say you know C." Please don't. These are two different languages.
                  – etarion
                  Jul 15 '16 at 6:27




                  "If you know C++, then also say you know C." Please don't. These are two different languages.
                  – etarion
                  Jul 15 '16 at 6:27












                  @etarion: Thanks, I've clarified it.
                  – Andy Lester
                  Jul 15 '16 at 14:10




                  @etarion: Thanks, I've clarified it.
                  – Andy Lester
                  Jul 15 '16 at 14:10




                  1




                  1




                  @etarion: C++ is a close superset of C so the claim is not such a stress. If one was to be that precise, the Debian -> Linux implication is not correct either.
                  – WoJ
                  Jul 15 '16 at 17:15




                  @etarion: C++ is a close superset of C so the claim is not such a stress. If one was to be that precise, the Debian -> Linux implication is not correct either.
                  – WoJ
                  Jul 15 '16 at 17:15










                  up vote
                  2
                  down vote













                  I think that it's best to leave JavaScript in for an additional reason: the answer implies that you are familiar with and can work with plain old "vanilla" JavaScript, which sometimes you do have to do. Sometimes an employer for whatever reason isn't going to let you install an Angular or node.js framework on a site or even jQuery (I've seen it before, usually when the library impacts with something someone wrote for the site years before). Sometimes the job might entail "middle end" work that's neither directly involved with creating controllers and views or working with the back end per se. If you're familiar enough with JS, including its foibles, yes, you should list that.



                  The other issue here is that a lot of employers - maybe even the majority now - don't actually read your resume at first, they run it through a scanner looking for keywords and only come back to actually flip through it if the keywords are there. It's entirely possible that someone who needs a JS developer didn't bother to put Angular or React in as keywords because, I don't know, they don't actually use Angular or React for instance. If you don't say Javascript too you might miss out precisely because a human isn't interacting with your resume at the first level.






                  share|improve this answer

























                    up vote
                    2
                    down vote













                    I think that it's best to leave JavaScript in for an additional reason: the answer implies that you are familiar with and can work with plain old "vanilla" JavaScript, which sometimes you do have to do. Sometimes an employer for whatever reason isn't going to let you install an Angular or node.js framework on a site or even jQuery (I've seen it before, usually when the library impacts with something someone wrote for the site years before). Sometimes the job might entail "middle end" work that's neither directly involved with creating controllers and views or working with the back end per se. If you're familiar enough with JS, including its foibles, yes, you should list that.



                    The other issue here is that a lot of employers - maybe even the majority now - don't actually read your resume at first, they run it through a scanner looking for keywords and only come back to actually flip through it if the keywords are there. It's entirely possible that someone who needs a JS developer didn't bother to put Angular or React in as keywords because, I don't know, they don't actually use Angular or React for instance. If you don't say Javascript too you might miss out precisely because a human isn't interacting with your resume at the first level.






                    share|improve this answer























                      up vote
                      2
                      down vote










                      up vote
                      2
                      down vote









                      I think that it's best to leave JavaScript in for an additional reason: the answer implies that you are familiar with and can work with plain old "vanilla" JavaScript, which sometimes you do have to do. Sometimes an employer for whatever reason isn't going to let you install an Angular or node.js framework on a site or even jQuery (I've seen it before, usually when the library impacts with something someone wrote for the site years before). Sometimes the job might entail "middle end" work that's neither directly involved with creating controllers and views or working with the back end per se. If you're familiar enough with JS, including its foibles, yes, you should list that.



                      The other issue here is that a lot of employers - maybe even the majority now - don't actually read your resume at first, they run it through a scanner looking for keywords and only come back to actually flip through it if the keywords are there. It's entirely possible that someone who needs a JS developer didn't bother to put Angular or React in as keywords because, I don't know, they don't actually use Angular or React for instance. If you don't say Javascript too you might miss out precisely because a human isn't interacting with your resume at the first level.






                      share|improve this answer













                      I think that it's best to leave JavaScript in for an additional reason: the answer implies that you are familiar with and can work with plain old "vanilla" JavaScript, which sometimes you do have to do. Sometimes an employer for whatever reason isn't going to let you install an Angular or node.js framework on a site or even jQuery (I've seen it before, usually when the library impacts with something someone wrote for the site years before). Sometimes the job might entail "middle end" work that's neither directly involved with creating controllers and views or working with the back end per se. If you're familiar enough with JS, including its foibles, yes, you should list that.



                      The other issue here is that a lot of employers - maybe even the majority now - don't actually read your resume at first, they run it through a scanner looking for keywords and only come back to actually flip through it if the keywords are there. It's entirely possible that someone who needs a JS developer didn't bother to put Angular or React in as keywords because, I don't know, they don't actually use Angular or React for instance. If you don't say Javascript too you might miss out precisely because a human isn't interacting with your resume at the first level.







                      share|improve this answer













                      share|improve this answer



                      share|improve this answer











                      answered Jul 15 '16 at 0:07









                      NotVonKaiser

                      6,5051533




                      6,5051533




















                          up vote
                          1
                          down vote













                          Note: I consider this to be an excellent example of a more general principle. In general, when communicating, you want to communicate in a way that will be understood. That involves knowing your audience. If you are applying to a local shop, with 6 current staff in total, named JavaScript Improvers, Inc., and you are customizing your resume which will be sent directly to the CTO, then you may be able to leave off certain information. In general, knowing your audience is always helpful. For most larger companies, as stated in other answers, you don't want to assume that your audience understands basic technical terms, pre-requisites, etc. (They may be humans who don't know enough about some pre-requisites, or computer programs that may not have certain pre-requisites identified.) As Joe Strazzere's answer mentions, you don't want to miss out on a common search term.



                          However, rather than just "leaving it in", and thereby mixing JavaScript with the other technologies, I have another idea: Removing JavaScript from that section might be a good idea. At the same time, rename the section from "skills" to "other skills". Then, separately, create another JavaScript section:





                          JavaScript-Related Skills



                          • AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...


                          Other Useful Skills



                          • Infinite loops, buffer overflows, Heisenbugs, dividing by zero, off-by-ones, syntax errors, etc.



                          (The above example is just meant to demonstrate the basic concept. Clearly you'll want to customize what is seen above. Specific details on precisely how to do that can vary depending on other characteristics about your specific resume.)






                          share|improve this answer

























                            up vote
                            1
                            down vote













                            Note: I consider this to be an excellent example of a more general principle. In general, when communicating, you want to communicate in a way that will be understood. That involves knowing your audience. If you are applying to a local shop, with 6 current staff in total, named JavaScript Improvers, Inc., and you are customizing your resume which will be sent directly to the CTO, then you may be able to leave off certain information. In general, knowing your audience is always helpful. For most larger companies, as stated in other answers, you don't want to assume that your audience understands basic technical terms, pre-requisites, etc. (They may be humans who don't know enough about some pre-requisites, or computer programs that may not have certain pre-requisites identified.) As Joe Strazzere's answer mentions, you don't want to miss out on a common search term.



                            However, rather than just "leaving it in", and thereby mixing JavaScript with the other technologies, I have another idea: Removing JavaScript from that section might be a good idea. At the same time, rename the section from "skills" to "other skills". Then, separately, create another JavaScript section:





                            JavaScript-Related Skills



                            • AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...


                            Other Useful Skills



                            • Infinite loops, buffer overflows, Heisenbugs, dividing by zero, off-by-ones, syntax errors, etc.



                            (The above example is just meant to demonstrate the basic concept. Clearly you'll want to customize what is seen above. Specific details on precisely how to do that can vary depending on other characteristics about your specific resume.)






                            share|improve this answer























                              up vote
                              1
                              down vote










                              up vote
                              1
                              down vote









                              Note: I consider this to be an excellent example of a more general principle. In general, when communicating, you want to communicate in a way that will be understood. That involves knowing your audience. If you are applying to a local shop, with 6 current staff in total, named JavaScript Improvers, Inc., and you are customizing your resume which will be sent directly to the CTO, then you may be able to leave off certain information. In general, knowing your audience is always helpful. For most larger companies, as stated in other answers, you don't want to assume that your audience understands basic technical terms, pre-requisites, etc. (They may be humans who don't know enough about some pre-requisites, or computer programs that may not have certain pre-requisites identified.) As Joe Strazzere's answer mentions, you don't want to miss out on a common search term.



                              However, rather than just "leaving it in", and thereby mixing JavaScript with the other technologies, I have another idea: Removing JavaScript from that section might be a good idea. At the same time, rename the section from "skills" to "other skills". Then, separately, create another JavaScript section:





                              JavaScript-Related Skills



                              • AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...


                              Other Useful Skills



                              • Infinite loops, buffer overflows, Heisenbugs, dividing by zero, off-by-ones, syntax errors, etc.



                              (The above example is just meant to demonstrate the basic concept. Clearly you'll want to customize what is seen above. Specific details on precisely how to do that can vary depending on other characteristics about your specific resume.)






                              share|improve this answer













                              Note: I consider this to be an excellent example of a more general principle. In general, when communicating, you want to communicate in a way that will be understood. That involves knowing your audience. If you are applying to a local shop, with 6 current staff in total, named JavaScript Improvers, Inc., and you are customizing your resume which will be sent directly to the CTO, then you may be able to leave off certain information. In general, knowing your audience is always helpful. For most larger companies, as stated in other answers, you don't want to assume that your audience understands basic technical terms, pre-requisites, etc. (They may be humans who don't know enough about some pre-requisites, or computer programs that may not have certain pre-requisites identified.) As Joe Strazzere's answer mentions, you don't want to miss out on a common search term.



                              However, rather than just "leaving it in", and thereby mixing JavaScript with the other technologies, I have another idea: Removing JavaScript from that section might be a good idea. At the same time, rename the section from "skills" to "other skills". Then, separately, create another JavaScript section:





                              JavaScript-Related Skills



                              • AngularJS, React, jQuery, Node.js, Express, PhantomJS, Tape etc...


                              Other Useful Skills



                              • Infinite loops, buffer overflows, Heisenbugs, dividing by zero, off-by-ones, syntax errors, etc.



                              (The above example is just meant to demonstrate the basic concept. Clearly you'll want to customize what is seen above. Specific details on precisely how to do that can vary depending on other characteristics about your specific resume.)







                              share|improve this answer













                              share|improve this answer



                              share|improve this answer











                              answered Jul 16 '16 at 2:45









                              TOOGAM

                              2,356512




                              2,356512




















                                  up vote
                                  -1
                                  down vote













                                  Many recruiters would not know. For a sure a word search would not know. Yes list it if you think there is a market.






                                  share|improve this answer

























                                    up vote
                                    -1
                                    down vote













                                    Many recruiters would not know. For a sure a word search would not know. Yes list it if you think there is a market.






                                    share|improve this answer























                                      up vote
                                      -1
                                      down vote










                                      up vote
                                      -1
                                      down vote









                                      Many recruiters would not know. For a sure a word search would not know. Yes list it if you think there is a market.






                                      share|improve this answer













                                      Many recruiters would not know. For a sure a word search would not know. Yes list it if you think there is a market.







                                      share|improve this answer













                                      share|improve this answer



                                      share|improve this answer











                                      answered Jul 14 '16 at 18:21









                                      paparazzo

                                      33.3k657106




                                      33.3k657106






















                                           

                                          draft saved


                                          draft discarded


























                                           


                                          draft saved


                                          draft discarded














                                          StackExchange.ready(
                                          function ()
                                          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f71366%2fis-it-worth-putting-a-skill-that-is-a-prerequisite-of-a-lot-of-other-skills-on-m%23new-answer', 'question_page');

                                          );

                                          Post as a guest

















































































                                          Comments

                                          Popular posts from this blog

                                          What does second last employer means? [closed]

                                          List of Gilmore Girls characters

                                          Confectionery