The basic principles of the system administrator. System administrator job responsibilities. The position of the system administrator - is it necessary to draw up a job description for her

About specialization system administrator.

To be very rough, there are sisdamines with specialization and without specialization. Usually they start a career without specialization, then they have several "bent" branches of development and one or two or three, in which their further life takes place (the classic "builds" of characters in RPG correspond very well to this). A sysadmin without specialization is an overgrown enikeyschik (I will analyze this thesis below). However, the demand for a sysadmin of a narrow specialization is lower (if we count in pieces of vacancies) than for system administrators of generalists (I will also reveal this thesis below). However, with fewer vacancies, the real need for qualified specialists is much higher than there are specialists themselves, that is, the higher the qualifications, the less competition. At some point, you will have several offers from different companies, although you do not plan to leave the current one.

(Running a little ahead - the higher the qualifications, the longer it takes to look for a new job, for a top specialist looking for a job for half a year is quite normal. This is typical not only for administrators, but also for other professions with high responsibility and narrow specialization).

Who needs sysadmins?

Since a sysadmin is a profession, money is paid for it. The money is usually paid by the company to its employees. This means that companies need sysadmins.

So, in accordance with the above classification, there are two important types of employers - profile and non-profile.

Let's start with non-core ones. A non-core employer is a company that is NOT engaged in IT, or is engaged in it in an area far from the system administrator. Bright "antipodes" of IT-ness: travel agencies, real estate companies, car dealers, etc. For them, an administrator is a kind of "electrician / computer manager". They do not need a complex infrastructure, they do not know about what sysadmins do, what is complex and what is simple. They cannot control the quality of the system administrator's work, and the only sign of his success is "works" or "not". The exact level of development of a company varies greatly and can boil down to "setting up printers and ICQ" to supporting rather exotic programs (this is especially the case for medical institutions). In any case, the IT complexity of their configuration is most often minimal, and there is no need to talk about the real "economy" of the system administrator. This level fits into It-outsourcing,.

Separately, mention should be made of companies with a high degree of ititization of the non-IT business. (A vivid example is retail chains, banks). Most often, in such a company there is still a person who is able to assess the quality of work and the complexity of the solution, he is usually able to speak with the system administrator in a normal language, and not express himself with bird words about “the Internet does not work”, “the processor under the table beeps”, etc. etc. However, despite possible complexity configuration, it is quite limited by the budget and the needs of the company, and usually does not require going beyond the minimum to work. The needs of the IT department are perceived as a pure burden that needs to be defended in this very avian language.

The second type of employers are specialized companies. Most of the large Internet sites are such, these also include hosters, data centers (if they do something other than renting units / dedicated), companies whose business is tied to Computer techologies(cellular companies, processing centers). Note that specialized companies also have non-core administrators (who are engaged in servicing workplaces in the back office), when applying for a job, you need to find out exactly what you will be doing for yourself.

Such companies usually look for employees "for tasks", that is, they need a person who can deal with some area of ​​their activities.

An important feature of specialized companies is the constructiveness of what you do. You are no longer a "computer electrician", you are the person who determines how well the main business tool of the company will work. There is usually no concept of a "technology ceiling" or bird language here.

In fact, such a profession does not exist. It so happened that many companies want to have a person on the staff who will be responsible for "everything computerized." Usually these are non-core companies. And they want one or two, not three dozen certified specialists. (For those who want to talk about their brilliant present in the person of an Oracle administrator, etc. - I repeat, we are talking about the situation on the market). Hence the simple rule: they will want everything from you right away. Moreover, in the future you will find that superficial knowledge about everything is not particularly appreciated. However, these jobs are a great place to start - you can try everything and find out what you like best.

Thus, there is an obvious contradiction between the work of a novice system administrator (more precisely, the requirements that are imposed on him) and further career growth. This contradiction does not appear immediately, but after a while, when a person masters work.

However, let's get back to the work of the system administrator. Here is a list of the areas most commonly encountered by a sysadmin. Please note - these areas are far beyond the bounds of reason, but - see above, they want everything from you, at once, and preferably for little money. Example: how much a system administrator can earn in Minsk.

What is meant by system administration?

(we are talking about universal system administrators, of course)
Network administration. In its minimal form, it is a "desktop configuration guru. wifi router”, At the maximum - a person who plans a network for 1000 people with branches in five cities. This includes: network topology (which piece of hardware to plug into which and why), SCS planning (where and how many sockets), configuration of nats and vpns, etc. All sorts of Internet access control services - squid, IIS, smart and stupid firewalls, IDS, etc. go to the same heap.
Administration of workstations. Burned-out power supplies, solving a problem with another bank-client, fixing a broken seal, solving the problem "how can I open this file", fighting viruses for, with, working with, etc. The minimum level is to establish an office, the maximum level is to develop group policy for automatic rolling new version software that does not have (you have to do it yourself). At the same time, problems with automatic deployment of workstations, backups, safe removal etc.
Centralized authorization. Usually, this role is played by Active Directory... One of the "purest" disciplines, it is also one of the most difficult. Minimum level - add / remove users, drive workstation to the domain. The maximum is to implement automatic assignment of policies to users of a given OU in case of access to a computer in one of the nodes of a neighboring tree in the forest (we all love this terminology, yes).
Mail. It is conventionally divided into three worlds: small windows mail servers (Kerio class), mighty and terrible Exchange, normal linux / freebsd server with any sane mail server (postfix, exim, sendmail, etc.). Minimum level: add mailbox, add another domain and add an additional email to the user. Maximum level: configure mailing ticket system, mailing list, spam filtering, automatic mailbox creation, etc.
Databases - Most often it is part of another infrastructure. Specialized DBAs are a league of their own. Minimum level: install, restart, connect in the application, add / remove a database. Usually the same ability to make a backup and restore it (which is more difficult). There is no maximum level because if you know any DBMS well, SQL, are able to deploy a server with an active asynchronous subscription to another database, then this is not quite a “universal system administrator” anymore. A conditional ceiling can be considered the ability to fix a broken MyISAM database.
1C. Despite the fact that 1C is such a company that produces toys and educational disks, “1C” usually means 1C: Enterprise, 1C: Accounting and other nightmarish offspring of the perverted union of accounting and programming. A person who knows a lot about "this" is called a "1C programmer" (not to be confused with normal programmers). Minimum level: create a new database, add / delete a user. Maximum level: correct the configuration, add a field to the report, deal with how 1C lies with SQL.
Websites. This can mean almost anything - from "ordering shared hosting" to "solving a performance problem in django-orm when working with postregsql." Copywriting, search engine spam (SEO), web design, web programming, etc. can easily be included in this area. Minimum level: be able to do a little typesetting in html, there is no maximum because the different professions are listed. By the way, there is a real system administrator among them: web-server administrator - load ballancing, failover, high avablility, clusters, etc., which again goes beyond the category of "universality".
Access control systems and video surveillance. Most often they are made by specialized organizations, however, it happens that the system administrator also has to tinker. Minimum level: pick up one more camera, register an access card. Maximum level: auto export of video to archive, synchronization of all types of control. The future is most likely not an admin one, as far as I know, administrators usually don't like this area.
ATC. Another area that falls into system administration by accident. Minimum level: add forwarding, connect an additional incoming line. Maximum level: raise your Asterisk with a voice menu by 300 points, a sip-skype gate, routing that can be transferred between IP, copper and E1 depending on conditions. It also often includes telephone legacy, "knocking crowns", sorting out all kinds of plesiosynchronous incoming lines, E1, etc. I repeat, this is not an admin specialization - in general, telephonists are engaged in this.
Print / scan. Most often, a trivial task, until you have to make printers networked and solve the problems of all kinds of industrial printers. Minimum level: pick up the printer; Maximum level - solve the problem of color profiles, connect the label printer as a network, automatically assign printers when the user logs on to the computer.

In addition, there are many specific areas: terminal servers, various ERP / CMS, utility software for network maintenance, etc.

Summing up: it is impossible to be not only a professional, but at least it is more or less good to know all this. But you need to know. It is on this contradiction that the career of a novice administrator is built.

Separately, it must be said about those with whom you will come across during the interview. Unlike other cases, people who are far from computers are 99% likely to interview you. And they will not check your knowledge, but your adequacy and "quick answers." If you shower them with clever words, you will not be perceived adequately.

The same one is an Enikeian. (from the expression in English - "press any key" - press any key)
This is the person who is blamed for all the poorly formalized and tedious work, communication with users and fiddling with iron.

The main things that an enikeys usually do:
helpdesk - help desk. Answer to phone calls employees, show you how to press any key, help you find the column sort button and remove a disk stuck in the drive.
Preparation of workstations - installation, connection, wiring, OS and software installation, etc.
The solution to any non-verbal garbage with custom applications - this is especially true for software from the tax and bank clients.
Correction of SCS (new sockets, transfer of existing ones), diagnostics of problems, switching, if there are crosses, then their expansion.

If the company does not have any manager, then his duties are performed by the system administrator.

Note that the "system administrator assistant" is most often practically a consumable with a high turnover. In one company, it got to the point that the head of the department did not know by name all the assistant administrators (3 pcs), because at least someone left once a month and a half.

From the point of view of an engineer, such a job is a springboard to system administration, but by no means the main profession.

We will talk about the profiles of specialized system administrators a little later, but for now, about a career within these two professions.

Who goes to enikeyschiki?

My experience says that people usually go there without specialized education. Most often they are young, although I interviewed my 42-year-old uncle for the position of "Assistant System Administrator". Despite the fact that the duties described above seem to be almost trivial, for many it is the most difficult step. Becoming an administrator from the Administrator Assistant is easier than becoming a sysadmin assistant.

The main reason: they will want from you knowledge that is comparable to the administrator. Moreover, half of this knowledge is not stated anywhere in books and is a passing experience (for example, fiddling with bank clients). Another important feature is the "feel of computers", I have met many people at interviews, they simply could not appreciate the naturalness of what is happening in the computer, which greatly interfered with their analysis of the situation. This is a non-verbal experience, it appears after long work with computers.

A typical career looks like this: an assistant to a system administrator (or an administrator in a small company with 5-8 people), an administrator, an administrator (maybe 2-3 more times as an administrator), the beginning of a real specialization. Specialization can be of two types: improving the technical level (instead of superficial knowledge about everything, deep knowledge about a little), and an administrative career - head of the IT department, CIO (CIO), etc. These are two completely different areas - the first has to do with computers, the second has to do with people, personnel management, planning, budgeting, meetings, etc.

The transition from stage to stage is determined by several factors: 1) Theoretical knowledge 2) Practical skills 3) Knowledge of realities 4) Connections and relationships with other people (both within the company and outside it).

Among this, the third point looks not very clear. What are "realities"?

Knowledge of realities.

It is about knowing what is usually used in companies, how much it costs and how it works. Relatively speaking, this is a person who knows that modern offices put 5e, and not ThickEthernet (as described in the 1993 book), that putting the 6th category is unjustified (although this is advised by the manufacturer's booklet), that programmers need an eye yes eyes, otherwise the company will be tightly tied to a specific person, etc. In other words, knowledge of realities is the ability to say what exactly is needed in terms that will be understandable to both the supplier and those around him.

Skills and their application.

Until a certain moment, almost everything is decided. Without some skill set, no theoretical knowledge will help. It simply includes "many kilometers behind the wheel" - solving many problems, skills in working with the console and typical software, knowledge of the symptoms of problems, knowledge of typical solutions for typical cases.

Theory in the life of a system administrator.

At first, theoretical knowledge is not very important, since you do not have the proper feel of computers in order to perceive them correctly. However, if you do not invest your time and effort in theoretical knowledge, then you will not quickly notice how you get stuck at your level. The salary will grow slightly, perhaps there will be a career, but the it-shny world around will stop changing. The same technologies, the same glitches. Lack of theoretical knowledge does not interfere with work - it interferes with understanding how it works and how to fix something that is not working. Experience greatly replaces theory in the sense of solving problems, but does not give the strength to see the situation in general, to find the real reason (instead of the reason).

Yes, they mean a lot, especially in the case of a career as an IT director. The only way to avoid the need to have a lot of acquaintances and play the king of the hill office games is professionalism (read, experience and theory). If not, then only personal connections, knowledge of people, the ability to feel them, the ability to order them and in every possible way to guide them. According to my observations, about 30% of enikeys find their first job by acquaintance.

For highly specialized administrators, communications mean something completely different. The narrower the specialization, the smaller the assortment of employers, the more likely it is to know everyone or almost everyone. Having a familiar name greatly reduces the time it takes to find a job. In this case, we are not talking about "connections" in the everyday sense, but about professional fame.

So, I would like to clarify a little about what a system administrator is.

I would formulate this specialty in the only way - the maximum position in the management of all information systems of the enterprise.

A system administrator is a person whose job is to:
First and foremost, in building policy and planning the organization of all information systems and networks in the company.
In everyday life - the implementation of this plan, recreating it in hardware, configuring devices, setting up software, tuning, monitoring the state of networks, suppressing random violations, attacks and other threats.
In the future - planning for development and modernization, exploring new opportunities and trends.

This position is only half "technical" and the other half "political". The system administrator is the top IT manager who determines how and where all IT in the company will move, and ultimately how easy and convenient it will be to use the “IT benefits” for each specific user. Below the level are individual "narrow" administrators, such as database administrators, user support services, possibly programmers who write some local modules. Only the “non-technical leadership” remains above the level - the top management and the heads of the company. For example, the management, due to the lack of the necessary technical knowledge, is simply not able to know what equipment is needed to build a network, where there are bottlenecks and how much each of them affects or can affect business processes. Superiors, as a rule, only need to have information “how much it will cost us money and time” and “how much it will simplify the work / increase reliability”. And how and what technologies will be used, how and what users will receive, what they can do and what not - these are the decisions of the system administrator.

The fact that many (and even in their article are guilty of this :) call an administrator - often it is an "enikey" (system engineer, shift engineer, technical support engineer), his task is really to deal with buggy Windows, printers and other small junk of the user. I understand that in a company with a couple of hundred jobs, there is practically no point in hiring a separate system administrator (as a rule, such tasks do not arise there), which is why it turns out that an enikeyschik is sitting, and to the best of his free time and experience, he performs and server and hardware configuration tasks. There is nothing terrible in this, in the end, almost all system administrators began to work as enikeys, only they are not real system administrators.

I have worked several times as a system administrator in companies where more than a thousand jobs are distributed over a large area. For example, in one of them for two years of work, I have never seen the end user, and only spoke with them on the phone a couple of times. But for that, responsibility for the correctness of the chosen policy of building a network, planning purchases for further development, the operability of all information systems, software, servers, data safety is on the administrator. No one will ask an enikeyshchik for the loss of data, or a line break - but for the sysadmin this will immediately be disqualification if they were not provided for in the structure of backup paths that ensure uninterrupted operation in the event of failure of individual nodes and quick options for restoring the operability of any structure. And the decisions made by the system administrator usually affect all employees who work with computers in one way or another. It is the system administrator who sets the tasks for the programmers to write the necessary modules, and introduces the rules for working with software for the entire company.

I would like to draw an analogy with city sewers - the system administrator is the chief engineer of the city, who plans how and where to lead pipes, where to build and how to connect substations. But the bearded one in a sweater is most likely a local plumber who changes the pipes in the house, and makes the wiring around the apartment. Without belittling the necessity of all professions, but these are very different things in terms of knowledge, education and tasks to be solved.

I also disagree with the division into “specialized” and “non-core” employers. Here it is more likely to talk about whether there is a demand for serious IT for each specific business. For example, if you look at trade in general, they essentially do not need computers, they put the cash register and make money. But nevertheless, I saw one of the most interesting and developed IT infrastructures in a large retail network. And they didn’t skimp on development, because they understood that this was the “blood” of the business and when the network went down, there would be no sales, and these are huge losses, both direct due to the standing equipment, and indirect from loss of trust.

P.S. And another interesting thing that has been noticed over the years, which is the fad of all those I have seen excellent sysadmins have an almost manic passion for organizing everything under their control, from configuring hardware, documenting infrastructures, and laying out patch cords in wiring closets, to perfecting their own desktops. And by the way, there were no beards with a sweater among them, a good system administrator is more likely to really look like a manager.

P.P.S. I leave out of the scope of the article all "narrow" administrators, such as administrators of web servers, databases, mail, domain, storage systems, network and so on. Although even the average system administrator should have a clear understanding of the essence of these specialties and in his work regularly consult and take into account the opinions of specialists or dive into the field himself (if there is strength and opportunity).

UPD: Well formulated my thoughts

So, today we will try to answer the question: "Who is the system administrator?" In addition, we will figure out how much such a person earns, what he does, and how good and important his work is in modern world... After all, each profession has its own place. Let's start with you as soon as possible to analyze our today's topic.

Concept

Who is the sysadmin? Let's try to answer this question, but first we will decipher this concept. After all, the name of our today's profession is far from a Russian abbreviation.

The point is that "sysadmin" stands for "system administrator". That is, this person is working with some kind of networks. And since this is a computer profession, then, as you might guess, such people will work with these machines.

Who is the sysadmin? After we have learned the full title of the position, it will be several times easier to reveal his duties and profession as a whole. So let's try to do this. Indeed, before starting work, it is always important to know what lies ahead of us.

What does it do

After we revealed the concept a little and figured out the question: "Who is the system administrator?" - it is necessary to learn about the job responsibilities of such workers. Especially if you are interested in this profession. Maybe you will be "ripped off three skins" and require huge work?

Not at all. In fact, the job of "sysadmin" is what almost every user dreams of. You will have to configure operating systems, reinstallation, software installation and equipment connection. It also includes setting up an Internet connection, treating your computer from viruses, protecting your system from various infections. In general, everything that the average user is now capable of doing.

In truth, sysadmin, software, and computers are the three essential ingredients of this profession. Sometimes especially advanced system administrators even do programming. This gives them a significant advantage over other workers. Let's now see what the pros and cons of this profession. It can't be that good, can it? Then everyone would aspire to be a system administrator.

Minuses

Well, let's start with the negative aspects. After all, it is they who, as a rule, make us wonder whether this or that place is right for us or not. The notes "sysadmin is good or bad" can often be found in many articles on the topic of work.

The first thing that should only be noticed is the obligatory presence of perseverance in a person. As a system administrator, you will have to spend most of your time at your computer without leaving it. Fortunately, for most modern users, this is not such a big deal.

In addition, system administrators are empowered with tremendous power and, as a result, responsibility. After all, the work within the company, which is performed on computers, will depend on you. Something breaks - and you have to fix everything quickly and efficiently. In cases where you know exactly what you are doing, do not be afraid.

The monotony of work and its monotony is another significant disadvantage of the chosen profession. Every day, everything will come down to the fact that you come to check the work of computers, if necessary, configure the equipment, and then go to your workplace and carry out the orders of the chief regarding the settings of the PC. Many people get bored with such a schedule.

pros

True, our today's profession also has a number of advantages. They can be found when reading the notes "sysadmin - good or bad". In fact, there are much more positive aspects here than negative ones.

The first point is the work schedule. Very often system administrators are hired with a free schedule, that is, on call. When services are not needed, you come to the workplace, then check the operation of all equipment and leave. And sometimes you stay in your office and go about your business until your services are required. And the salary still "drips".

The second point is the ease of use for most users. Modern people in computers are very advanced. That is why you can fix most of the difficulties encountered on computers without too much trouble. If the work is "not dusty and simple", and even brings a good income, then the employee will perform it at the highest level.

It is also worth noting that in most cases, system administrators are on their own after carrying out daily checks of the equipment. You can drink coffee, play games (especially if the bosses do not follow you, but provided a separate office), surf the Internet, or chat with friends. All this is very beneficial for your lifestyle. The main thing is not to "go too far" and not start "working to the detriment".

Plus, working at a computer is predominantly mental work. You don't have to carry bricks, work in bad weather, and so on. Usually, workers are given their offices where they can drink tea, warm up and just feel comfortable.

If you are not a supporter of communicating with people, then the system administrator is your profession. All you will do is work at the computer. Contact with living people is minimal here. Thus, it is a goldmine for introverted individuals.

How much does he earn

And here's another pretty important point... After all, any profession and position should be paid somehow. Sysadmin-salary is a connection on which, as a rule, the quality of a person's work depends.

The point is that if you are required to do a lot of work for a small salary, then, of course, you should refuse. A system administrator with a freelance (called - came and fixed, went home) receives from 10,000 rubles a month. But the employees of even the smallest firms with a full-time or flexible schedule - from 20,000 rubles.

With all this, the more wage, the better the system administrator will fulfill his duties. After all, then he will be interested in this. Thus, we can say that our today's profession is a rather profitable occupation.

Conclusion

Now our conversation has come to an end. Today we have learned with you who the system administrators are, what they do, what the pros and cons of this profession are, and how well the work of such workers is paid.

As you can see, this "spot" might suit most advanced computer users. Honestly, you need to study to be a system administrator. For example, on In addition, you can complete specialized courses to obtain a "crust". But sometimes you can do without it. That's all there is to it.

Job description the system administrator organizes labor relations. The document contains a list of functional responsibilities, sections related to determining the rights and responsibilities of the parties, working conditions. A sysadmin can have various specializations, work in the office of an enterprise / organization, at a school and other places.

Sample Typical System Administrator Job Description

І. General Provisions

1. The system administrator belongs to the professional category.

2. The basis for dismissal or appointment to office is an order general director companies on the proposal of the technical director or the head of the structural unit.

3. The system administrator reports to the head of the structural unit or technical director.

4. The performance of the functional duties of the system administrator during his absence is carried out by another official, as reported in the order for the organization.

5. A person with a higher profile education, work experience of at least six months with personal computers, creation and maintenance of networks.

6. The system administrator should know:

• regulatory documents of higher managers: decrees, orders, orders, other documents related to the activities and use of computer technology in information processing;
• operational, specifications, design features equipment, its purpose, operating modes, rules of use;
• software, hardware equipment;
• principles of aggregate hardware repair;
• basic principles of programming, including number systems, ciphers, codes, data exchange protocols;
• methods of implementing comprehensive information protection and methods of preventing unauthorized access to it;
• the procedure for maintaining and issuing technical documentation;
• internal labor regulations;
• labor legislation;
• norms and rules of safety, labor protection, fire protection, industrial sanitation.

7. The system administrator is guided in his activities:

• legislative acts Russian Federation;
• this job description;
• The Charter of the company, the Internal Labor Regulations, orders and orders of the immediate supervisor and management of the company.

II. Responsibilities of the system administrator

The system administrator has the following job responsibilities:

1. Installs software on computers, servers, workstations.

2. Configures system parameters on server.

3. Implements integration software on workstations, database management systems servers, file servers.

4. Maintains a working condition, Maintenance server hardware and workstations.

5. Performs assignment of identifiers, passwords, registration of users.

6. Reacts to user requests, teaches how to work in the network, maintain databases; develops instructions for working with the software.

7. Controls the distribution and use of computing and network resources.

8. Establishes access to the global, local area network.

9. Configures and sets limits on the use of computing resources.

10. Implements regular data copying.

11. Turns to technical services in case of equipment malfunctions.

12. Takes part in restoring the system performance during equipment failures and breakdowns.

13. Restores system performance, finds user and software errors.

14. Monitors the network, makes proposals for the development of its infrastructure, replacement, improvement of equipment.

15. Provides network security.

16. Supervises the installation of equipment by employees of service organizations.

17. Informs the immediate supervisor about cases of violations of the use of equipment.

ІІІ. Rights

The system administrator has the right to:

1. Participate in the development, changes in the rules for using the network.

2. Make requests to the heads and specialists of departments to provide the necessary documents and information.

3. To get acquainted with the documents on the draft decisions of the management of the enterprise related to its activities.

4. Submit proposals for improvement and organization of work for the management's consideration.

5. Require the management of the company to provide the conditions necessary for the performance of official duties.

5. Make decisions within the boundaries of their competence.

IV. A responsibility

The system administrator is responsible for:

1. Disruption of the network due to incorrect, improper administration of the equipment.

2. Untimely notification of management about events related to the operation of technology, about cases of network abuse.

3. Improper performance of their own functional duties provided for by this job description.

4. Violations of the legislation of the Russian Federation committed in the course of their activities.

5. Causing material damage to the company.

6. Failure to comply with safety standards and fire safety measures, internal labor regulations, discipline.

V. Working conditions

1. The working conditions of the system administrator are determined by the provisions of the Labor Code of the Russian Federation, orders, orders of the institution's management, the Internal Labor Regulations.

Many have heard that there is such a position, such a profession as a system administrator. But to be completely frank, not even all employers understand what kind of person he should be and what responsibilities should be assigned to him. But, as practice shows, those who have achieved some heights in this area are in-demand specialists, and good large companies are ready to pay a sensible system administrator very good money, because a real master of the matter is worth its weight in gold today.

How did this profession come about ...

Ten or fifteen years ago, no one could have imagined that in the future there would be such a profession as a system administrator. Then computer users were divided into two large categories: ordinary users (to become them it was enough to learn how to turn on and off the computer on their own, and even to understand a little the essence of the most simple programs) and real programmers (those who already knew how not only to open programs, but also understood what processes take place in a computer).

Today, such a classification is absolutely inadequate, since even a child can figure out the simplest programs. Instead of a simple understanding of the processes, the first stage of important characteristics was replaced by the ability to use and manage them so that the company in which the specialist works was completely sure that all the information that is stored in electronic format, will be kept confidential. A good system administrator can be compared to a conductor who must set up his orchestra (that is, the computer network of an enterprise or company and its equipment) so that there simply cannot be any failures in sound and work.

Responsibilities of the system administrator - we understand in stages

As it has already become clear, today in all large companies and enterprises you can find a system administrator. Smart managers of small firms that cannot yet afford such a full-time employee use the services of external specialists, thereby guaranteeing the smooth operation of the entire management system for the enterprise.

The responsibilities of a system administrator include many tasks, the most important of which are:

• maintenance, installation and reinstallation of office equipment, ensuring its highly productive activities;
• search for good software, its installation, adjustment of its activities;
• ensuring continuous uninterrupted operation of the company's network, guaranteeing data confidentiality;
• data copying (backup);
• fast and complete data recovery in case of loss of some or all information due to the fault of any of the employees;
• assistance to users-employees of the company for whom a computer or other office equipment is difficult to understand (the human factor is very important here, such duties of a system administrator should be performed calmly and as clearly as possible for the user);
• formation of reporting documentation for management.

The first requirements that will be presented to an applicant for such a position

A system administrator must not only know his duties, but also fulfill them, therefore letters of recommendation for many companies are one of the main characteristics of the skill level of a potential employee. Experience is what any manager wants to see from his employee today. That is why more than one young and purposeful system administrator began to study his duties at small enterprises, for a nominal fee, so that later he could get the desired job in a promising company.

It is also important to understand the operation of the technology itself. That is, if necessary, the sysadmin must fix problems with the operation of certain devices. The duties of the system administrator in the office will include replacing cartridges in the printer, and setting up the scanner, and repairing a poorly working computer power supply in the accounting department.

It is necessary not only to understand what it is network protocols, but also be able to build local computer networks... The functional responsibilities of a system administrator in large enterprises will necessarily include the construction of such a network and its modernization as needed.

Without education today - nowhere

As practice shows, in order to work in a good company in such a position, one cannot do without an appropriate education. Despite the fact that today there are many online trainings that help you understand the basics, this is not enough to be a real specialist.

Although, there are exceptions - real talents-nuggets who have not even completed their courses, perform the duties of a system administrator, but these are still exceptions that are possible only with a great deal of experience and the baggage of independently acquired knowledge.

Big cities are where sysadmins need to look for jobs

As already mentioned, the duties of the system administrator include the installation of office equipment and software. Therefore, large enterprises and organizations need sysadmins. Most often they live in megacities and cities in which there are similar organizations. The higher the demand for specialists in the region, the more realistic it is to find a job that will suit both the amount of remuneration and the scope of responsibilities.

Today, sysadmins are needed in hospitals ...

Many organizations that are not related to economics and business still have their own sysadmin. This is due to large volumes of information that must not only be systematized, stored for a long time, but also at the first need to be able to use it without long fuss and searches. This is how jobs such as system administrator began to appear in the hospital. His responsibilities are slightly different from those of, for example, a system administrator of a trading enterprise, because here special attention will be paid to archival databases of information that need to be made as mobile as possible.

Great prospects

Today, a system administrator is a demanded profession, the relevance of which is only increasing every year, so the decision to become a real specialist in this area is very correct and will bring prosperity in the future. In order to become a good system administrator, you need to be prepared for the fact that the usual duties of a system administrator at an enterprise will include the ability to manage and change computer networks, the desire to learn new things, and the ability to communicate with people normally. The sysadmin must understand what his immediate superiors want, and be able to implement it.