Your Resume Sucks II: How to Fix the skills

One thing that I've emphasized from Part 1 is that each resume is telling a story about you. It is self-promotion, selling you to the hiring manager. It is propaganda, trying to influence the reader regarding your suitability for a particular job. 

Remember your English essay lessons? About every sentence must support the paragraph, and every paragraph must support the section, and every section must support the overall statement? 

Same goes for your resume. EVERY word on the resume must support your summary... that you deserve the job, not in a begging way, but in a "of course I am good for it" way. 

If you have a lot of relevant job history, you probably should use traditional / chronological resume where you just list all the jobs, since most of your careers you have been working toward this job you're applying for. 

But if you have very little experience (new grad? bootcamp?) or you are shifting careers, then you need to do a little more planning. You need to do a hybrid resume: a section about the skills and qualifications, THEN a section about education and work experiences. And guess which section goes first? Yep, skills and qualifications. 

If you are looking for a webdev position, and you listed a bunch of tech support jobs, you have to explain WHY those job experiences are relevant to a webdev position. Did you do tech support for a webdev company? For a webdev tool provider? Or did you just answer questions about Windows and printers and stuff unrelated to webdev? 

Let us consider an example. Let's say you are looking for a job as a junior webdev, mostly front-end static sites, nothing too fancy, no backend training.  (i.e. NOT full-stack) 

What are the skills that would be useful as a UI/UX front-end developer? List both the hard and soft skills. Go ahead, do it on paper. We'll wait for you. Give it five minutes. Just list as many as you can. 

It'd probably look something like this:

  • Hard / Tech: HTML5, CSS3, JavaScript ES6, React.js, Vue.js, Angular, SASS / LESS, jQuery, Bootstrap, Python, Selenium, Django, Jest, MySQL, MongoDB, PostgreSQL, ORM, Responsive Design, database, software development, Oracle... 
  • Soft: problem-solving, out-of-box thinking, customer engagement, verbal and written communications, project management, team collaboration, analytical, customer service, software engineering, multi-task, start-up environment, fast-paced... 
Okay, look like under Tech, there are 3 groups: web, Python, Database
  • Web: HTMl5, CSS3, JavaScript (ES6), Responsive Design, Bootstrap, jQuery, SASS / LESS, React.js, Vue.js, Angular, 
  • SQL: MySQL, MongoDB, ORM, Database, RDBMS, Oracle
  • Python: Selenium, Django, Flask
And Under Soft, there are three major groups: project management and problem-solving, communications, and misc. 

  • Problem-solving: out of box thinking, analytical mind, 
  • Communication: written, verbal, customer service, customer engagement
  • Project management: team collaboration, multi-task, startup environment, fast-paced
Okay, these are good starting points for a hybrid resume. But you have to create your OWN list, and only list skills that you ACTUALLY have. 

If you need some help coming up with a list of soft skills, just google "soft skills for (insert position)" and you would find them. Remember, pick only those you can PROVE you have, either through education or work experience. 

In the next part, we'll discuss how to rephrase your work experiences to fit your "story" or "branding statement" that you are indeed very suitable for the job. 

Comments

Post a Comment

Popular posts from this blog

Yet another take on recursion

Recursion is often one of the hardest things to "get" in programming, so when you have your "aha" moment, it's that much more amazing. Conceptually, it's not that hard to see, but how do you actually program one such?  First, realize that " recursion is a method of solving a problem where the solution depends on solutions to smaller instances of the same problem." Let us try something simple. Let's say... I want you to sum up the elements of an arbitrary array, let's call it arr. It can have any number of elements, and each element is an integer. For the purpose of this exercise, let's just say it's [1,2,3,4], but it can be any integer, and the array can be any valid size. And I want to you use recursion, not loop (no for or while or such statements).  Now, remember the definition: "solving a problem where the solution depends on the solutions to smaller instances of the same problem".  Let's call this function rsum (
Read more

How to Solve a Problem, with Examples

One of the fundamental tasks of a programmer is how to solve a programming problem, based on the specifications. Here is my attempt to solve such a problem, finally arriving at a validated answer.  If you've been on hackerrank.com, you may have seen this problem before. It's Fraudulent Activity Notifications .  TL;DR: given an array of arbitrary length (let's say it can go to 1x10^6). Each number in the array is expenditures for each day... It can range from 0 to 200 (and is always an integer). You are also given a number "d", that's the number of days you need to LOOK BACK to calculate the window. You need the median value of that window. If the next value is larger than or equal to twice the median, client is notified. Now, given arbitrary d, how many notifications had been generated, for a given array?  Example: you're given 6 4     10 20 30 40 50 60 6 is the size of the array: 6 entries. Window size is 4. First run, "10 20 30 40" Med
Read more

Problem Solving for Programmers: a Neglected Topic?

How often have you heard this story... it may be you, or someone you knew in class...  This person has no problem picking up syntax of a new programming language and even got the quirks of the language down. But when it comes time to write an actual program for an assignment, s/he has ZERO ideas about how to proceed. Just completely blanks out. Attempts to help with hints like "you need a loop", "you need a variable for X" results in one or two lines of code... and nothing else. Sounds familiar? This programmer never actually learned to problem-solve. S/he can learn things by rote, knew all the syntax, keywords, commands, etc. But has no actual understanding of the material. S/he would do great in a quiz or test, but fail completely on projects (or essay questions, if it's not programming). To badly paraphrase Sherlock Holmes' "You see but you do not observe", what we have here is a case if "you recall but you do not comprehend". I
Read more