How to write about key skills in a resume?

Question

IT education

Questions for IT recruiters:
1) Is there a need to write unrelated key skills in resumes from other areas?
For example:
1. Resume for PHP or Front-end programmer, which indicates knowledge and proficiency in BPM systems or Bash scripting
2. Resume for System Administrator or Enikeyshchik, which indicates knowledge and proficiency in PHP, JS and 3D modeling
2) Worth it whether to write the level of ownership at all? If yes, then how to objectively evaluate, because different schools give different documents and often the same name (levels) are often not equal - to receive certificates from school gurus, such as the Linux Professional Institute and others?
3) Is there a need to write about the knowledge of programs that are lower on the level of what you are "targeting" or not related to at all? MS Office package and similar...

Answer 1

Don't forget that in addition to your portfolio you will need:
- work experience
- the ability to ask professional questions
- a reference
Sorted in order of guaranteed employment. Have a recommendation from someone close to the company? They will almost certainly take it.
There is not?
You will need to shift responsibility at the interview and ask questions to the interviewer so that he understands that you are asking questions that are already difficult for him to answer, and not vice versa. Or at least trying to do so. It makes no sense to ask a girl with the formation of an iron questions, " Do you yourself know what polymorphism is? So I know!"", ask questions in the style of" How do you conclude a cooperation agreement and what, besides programming, will be included in my duties? How can I improve my skills with you? How do programmers work for you? Can I talk to one of them?" There are lists with such questions on Habré.
Don't know how?
Earn experience and play a sincere person who knows how to do it, but it didn't work out with eloquence. There are chances, but meager
ps. my experience.
It was like there:
I had no experience - they didn’t hire me
I got experience - they said we don’t believe that you have it men
. "Here's a real man he owes..." - a real man doesn't owe anything, that's why he's real. So here too. All these requirements are written by programmers, and they will understand whether it is worth taking you or not. But no one checks these requirements before publication - as they wrote, they threw it. Unfortunately, you will have to convince a non-programmer that you understand. And this cannot be done by showing knowledge - she will get tired of listening to you, you will become boring and will not pass. This is theater in real life. Next.
"Do you know what Bootstrap is? Do you write in Backbone? Do you use the Restful API?" - the girl HR does not let up, with difficulty pronouncing the words.
Even if your head boils. Nobody even looks at it. The recruiter needs affirmative answers to the questions on the list. She doesn’t need any explanation, but I know with all my gut that you really want her to notice in you the zeal and desire to apply her knowledge, because I am the same.
One smart man on a pickup truck said:
I understood this for myself - if you take revenge, then to death (none - give a lesson, decided to take revenge - killed, sat down, so you better not take revenge), if you lie - so from beginning to end (friends, parents, enemies, lawyers - everyone), if you rejoice, then with all your heart (every second, every moment).
How many times have I not tried to prove that my knowledge is worth something - a girl from
HR ( Human Resources - the task is to find a specialist, bring and give )
is by no means a girl from
HPDC (Human Potential Development Center - the task is to find a specialist with low knowledge, dumb him down and prepare a new cog in the system, giving him motivation and kicks exactly when necessary, educate the employee, make him learn the things the company needs )
and she stupidly does not give a damn.
But if you manage to cheer her up and put her in a position in which she does not understand anything , you are a profit.

Answer 2

Have you ever gone fishing?
Here - the same thing: you need to give the fish the bait that it most expects.
If the sets overlap as much as possible, it is possible that the vacant place will be yours.
Good luck!

Answer 3

If I go to the vacancy of a Sysadmin / Enikey, then I'm unlikely to want to be pestered with PHP, JS and 3D and vice versa.
Also from personal experience - if you write that you know how to enik and program, then you will do both jobs for two, and receive only one salary (not for two).

Answer 4

And is this advice?
A couple of people wrote about how they wrote their own resumes, this does not mean that their resume is written correctly.
Do you think that if a web front-end programmer writes HTML in a resume, CSS is a plus for him? no, it’s a bold minus for him, he should be able to typeset by default, and HR looks at a whole pack of such resumes, you need to read everything and he doesn’t understand half of the terms.
Your template resumes came from the USSR, but there was no HR in the CCCP, they didn’t deal with personnel, and, as one person correctly noted, they kept personnel records.
The technical summary should be written in simple language in the format of a couple of lines for each item, in human language and without terms.

Answer 5

I would like to express my opinion on these issues, which I had before the creation of the topic and give a little explanation on the post again.
I turned to specific people - to IT recruitment managers, that is, to people who directly specialize in this, for whom nginx, iptables and Python are not an empty phrase. Not to "girls from HR". Why? With the latter, you either go through the specific requirements that they have written on a piece of paper, or not, but the fact that you know something related or better, universal does not concern anyone. Since they would not be able to assess the quality of the completed test task, they give tests that may not always reflect the level of your knowledge. Take more and charisma - you're accepted!
After reading the answers above, you can get confused - write specifically or not, what do you know for sure or by 10%? We need to act according to the situation. It all depends on the place where you send your resume. IT Giant - clearly and to the point. Not? Perhaps a resume written in a journalistic style will pass, as Alexander Litvinenko advises . In this matter, it is difficult to come to one thing. Here even HR themselves cannot decide. Take any of the studies, for example, "Should I call after the interview if they didn't call you, but promised?". Two camps: yes and no.
According to a survey conducted by the Research Center of the Superjob.ru recruiting portal among HR managers, almost half of recruiters (46%) believe that in the absence of feedback, the applicant may well call the company himself; another 14% believe that the candidate should write an email to the recruiter. “The activity of the applicant is a sure sign of interest in the job,” the respondents comment.
On the contrary, 38% of the personnel officers we surveyed think that the absence of a call or letter from a recruiter means a refusal, therefore, it is useless to cut off corporate phones. “If the employer is interested, he will call”; “There is no need to stop in your search, it is better to continue to actively attend interviews,” say HR managers.
Personally, I myself am not for or against templates, but for specifics, a clear confidence that it will "reach the addressee", and not immediately go into the back burner. How to do this is written in this topic.