How to write a resume for a system administrator, or what did I write wrong?

Question

Computer networks

The question is rather for IT managers, although all the tips can be useful.
So, I am slowly looking for a job and created a resume on a well-known site. He indicated, as required, all the places where he worked before, and filled in the most important item - "Skills and abilities." I sent this same resume to various companies where system administrators were required, including where the most basic knowledge was required. But I didn't get an answer from anywhere.
At the same time, I guess that my real knowledge is somewhat above average, as proof of this, I observe how acquaintances, being more incompetent, get good positions.
In this regard, the question is - maybe I wrote something wrong or wrote a little? What is missing from my resume? I think that the question will be of interest to many. Thanks in advance.
PS: "skills and abilities" in my summary -
Knowledge of the principles of work of protocols of the OSI model, switching, routing. Construction and maintenance of networks built on Cisco, MicroTik, D-link equipment (VLAN, STP, ACL, NAT, OSPF, VPN). Network traffic analysis (Wireshark).
Work with Windows Server 2012 R2, FreeBSD, Avaya. IP telephony based on Elastix. Implementation of VMWare ESXi in the enterprise. Back-UP, anti-virus protection. Working with commercial equipment. MTX, Frontol, NCR, Shtrih-M, Mettler, Digi.
Extensive experience in technical user support, including remote. Outsourcing. Construction of a LAN from scratch, maintenance of office equipment, telephony, planning and purchase of equipment.
Construction of large video surveillance systems, implementation of access control systems at the enterprise, fire alarm system.

Answer 1

HR has such a term - overqualified. "Too smart."
You are rightfully not considered for a position with low requirements, fearing that you will not work for a long time - it will simply not be interesting for you.
From personal experience - create 2 (3-4) resumes "on a notorious site", dividing the areas of expertise - in one focus on the network, in the second on the server, in the third on the "all-rounder". Again, from personal experience - it works, the employer is not very interested in reading a multi-page resume.

Answer 2

"Specified, as required, all the places where he worked before, and filled in the most important item" Skills and abilities. "
The most important item is experience. Skills and abilities are great, but in them you write "I know how to set up a cisco", and in experience you write "maintenance of a cisco ASA, setting up OSPF, setting up site to site vpn. Feel the difference? Put more data in the work experience section.
In my resume, there are sections, in one of them there are regular tasks (accompanying this and that, doing this and that), projects (which indicate the project itself, my role in it, and what exactly I am in did it)
"At the same time, I guess that my real knowledge is somewhat above average, as proof of this, I observe how acquaintances, being more incompetent, get good jobs. "
Vanity is not good. If your less competent friends get good positions, then you are either in different areas (for example, you are conditionally a networker, and your friends are Windows and Linux users)
"In this regard, the question is - maybe I wrote something wrong, or I wrote not enough? What is missing in my resume? I think that the question will be of interest to many. Thanks in advance."
Describe in detail the experience, every little thing that you did at work - this time.
Depending on what position you want, optimize your resume for a specific position.
"PS: "skills" on my resume -
Knowledge of the principles of operation of protocols of the OSI model, switching, routing. Construction and maintenance of networks built on Cisco, MicroTik, D-link equipment (VLAN, STP, ACL, NAT, OSPF, VPN). Analysis of network traffic (Wireshark). "
Did you copy-paste this directly from the resume? You have a grammatical error there - recruiters do not like mistakes in the resume.
"Working with Windows Server 2012 R2, FreeBSD, Avaya."
Somehow everything is in a bunch. Break the OS separately, telephony separately. In the OS, write what exactly you can do there.
"Introduction of Vmware ESXi in the enterprise. "
Write it down better in experience.
" Back-UP, anti-virus protection. "
Any administrator solves the problems of data security and reliability. It is better to describe by what means you do this.
"Great experience in technical user support, including remote."
Well, confuse experience and skills. How much experience you have will be seen from the section above (where your notorious experience is actually described)
"Outsourcing."
Did you do this while working in a particular office? If yes, remove this item from the skills, and specify in the experience section. If not, then make a separate "place of work", such as "freelance sysadmin"
"Building a LAN from scratch, maintenance of office equipment, telephony,"
You repeat. It is above.
"planning and procurement of equipment."
Write it down better in work experience as one of the tasks.

Answer 3

1. I disagree with almost everything said above. It's like people who have never recruited are talking about how they think the people who make the decision think. Some set of superstitions.
2. Without seeing the entire summary, but only a piece of it, nothing can be said at all. Any leader and good HR for a resume first of all try to see a living person.
Author, please show your resume in full (you can in a personal) - I will comment.

Answer 4

Regarding the lack of response: I compare my experience of finding a job 4 years ago and now.
With passive search:
4 years ago - 2-3 interviews in two weeks.
This year - two a month. Or influxes, as it was before the May holidays and after March 8 (why it happened to me personally - who knows +))
And precisely silence in response to the sent resume, if you don’t call back yourself and don’t be interested in the fate of your response.
Regardless of your experience and the actual relevance of the resume, it is worth calling and asking.
PS Moscow

Answer 5

in the summer of 2014, we actively recruited people to the team, after reading such a resume, I would not invite ...
firstly, as for the resume as a whole on the "notorious site" - try to print it out. more than 2 sheets? think what to delete, it turns out less than 1 sheet? think what to add. for me personally, it was very convenient when a resume is 2 sheets long - the 1st sheet is contact details, a photo if any, information about education and a detailed description of the current (last) place of work (supported services, services, modernization / implementation projects, servers, networks, etc. equipment, team size, etc. etc.). 2nd sheet is a very brief summary of previous work experience, trite G-G / Company / Position and 2 lines of description, etc.
about what I see here -

Working with Windows Server 2012 R2, FreeBSD, Avaya

WS is there what? (infrastructure services, communications, support?) FreeBSD is similarly incomprehensible. AVAYA is a separate topic - did you have telephony or a network on this equipment? where is the description?

Implementing Vmware ESXi

- wonderful, but at least what version? 5 - 6 the difference is noticeable.

Back-UP, anti-virus protection

not Back-UP but backup, and even better is a backup system with support for versioned independent data storage on external media, again, which one? anti-virus protection in the same place - KSC and DrWES are different things ..
well, somehow my personal opinion, but just do a whole look at the summary, perhaps the opinion will change =)

Answer 6

Work experience not listed. Let's just say, working in a telecom operator, if you have not worked in providers, you will not be hired for a good position. Similarly with banks / insurance companies / integrators / software companies.
I can say that experienced network administrators generally do not indicate the words switching, routing, OSI in their work experience. It is considered self-understanding. They indicate more how many pieces of iron there were, what approximate network was, how many users are in it.
Your resume says that you know everything superficially, but nothing in detail. If I needed an assistant system administrator or an enikey worker (well, I still need to look at age, education, maybe a photo), I would invite you to an interview based on your resume. If you needed a network admin / win-admin / telephonist - no.

Answer 7

I'm not a sysadmin and can't appreciate the described skills... But maybe you're just asking for an inadequate salary for all this?
And not necessarily too much. Too low expectations with such a long list of skills can also scare the employer.

Answer 8

In any case, you need to lay out a complete resume. Why hide it if it is still on the open Internet?
Small general tips:
1) Add a photo. The recruiter is a real person. You will automatically turn from a jumbled text into a person in his imagination.
2) Sort the skills. FreeBSD and Avaya on the same list is a farce. The recruiter is forced to read the sections he doesn't need, but that's it. Let Avaya be in networking skills along with OSI and iptables, and FreeBSD in the OS list along with M$.