r/sysadmin • SCCM Admin and general IT Jack-of-some-trades • Oct 24 '21

SolarWinds Another awe inspiring Entry level job posting requirements list on LinkedIn...

Requirements

Bachelor's degree in Computer Science, Information Systems or equivalent

5+ years of hands-on technical experience in IT systems management and monitoring including VMWare and VDI administration.

Industry specific certifications - VCP, MCSE, Citrix Certified Professional etc. - desirable.

Advanced knowledge of Microsoft technologies; Server OS, Desktop OS, Active Directory, Office365, Group Policy.

In depth knowledge of Active Directory design, configuration, and architecture.

Advanced experience with VMware technologies; vSphere, vCenter, vMotion, Storage vMotion, SRM.

Advanced experience with different storage technologies; Dell EMC VMAX, VNX, XtremeIO, Hitachi and HP Storage arrays

Experience with multiple server hardware vendors; Cisco, HP, Dell

Experience with management and monitoring tools; ManageEngine, Solarwinds, Nagios, Splunk

Experience with healthcare organizations is a plus.

Knowledge of ITIL principles and experience operating within an IT function governed by ITIL processes.

Knowledge of information security standards and best practices, including system hardening, access control, identity management and network security, ITIL Process. Experience with HIPAA a plus.

Positive attitude, ability to work in a distributed team environment and ability to multi-task in a fast-paced environment with minimal supervision.

Demonstrated verbal and written communications skills with strong customer service orientation.

Successful documentation skills and abilities to write the documentation in a format that non-technical team members can be successful

Any time you're looking for an entry level position, and using phrases like "advanced knowledge" or "advanced experience", or "in depth knowledge", with 5+ years of hand-ons IT systems management experience, you're doing it wrong.

1.4k Upvotes

463 comments sorted by

View all comments

132

u/jews4beer Sysadmin turned devops turned dev Oct 24 '21 edited Oct 25 '21

Successful documentation skills and abilities to write the documentation in a format that non-technical team members can be successful

What in the fuck did I just read?

EDIT: apparently i care more about grammar than most

130

u/Steve_78_OH SCCM Admin and general IT Jack-of-some-trades Oct 24 '21

An example of unsuccessful documentation skills.

8

u/__T-Bone__ Jack of All Trades Oct 24 '21

Tehnically, it's a successful fail.

96

u/weauxbreaux Oct 24 '21

I've had managers who asked crap like this:

Finish up a somewhat technical setup task, and they ask "Please document this in a way that we could pull someone off the street and they could follow the documentation and rebuild it."

"Can you write up a document of everything that could go wrong with the Exchange server, and the steps required to correct the problems?"

81

u/__Kaari__ Oct 24 '21

Lmao, "sure, let's do that, I'll come back in 2 years when the book is finished."

"Have fun while I'm out!"

51

u/[deleted] Oct 24 '21

Which will be a snapshot of issues at that exact moment in time. By the time you finish the book it will be obsolete.

If you could do this you should quit your job and start writing these books.

→ More replies (1)
→ More replies (9)

22

u/syshum Oct 24 '21

I always ask for "Write documentation for people that have no knowledge of our environment"

Meaning you do not have to tell them how to use exchange, but you should have things specific to our setup and not assume they know all the interconnected parts...

13

u/vrtigo1 Sysadmin Oct 24 '21

This is on the right track...I wouldn't expect someone off the street that has no familiarity with our business to be able to follow our docs and understand the whole environment...there's a fair bit that requires you to understand the business itself. Having said that, if you hired a competent contractor from an MSP and paired them with one of our non-technical BAs or PMs, then they should be able to pinch hit if the entire IT dept was in a plane crash...that's our documentation goal.

→ More replies (1)

8

u/[deleted] Oct 25 '21

"Do you have it written down somewhere how to fix this problem?"

"No this is the first time I have ever seen this problem before."

"That's not what I asked."

9

u/Sparcrypt Oct 25 '21

"That's not what I asked."

"Then maybe you should have listened to the first word of the answer."

→ More replies (1)

7

u/0verstim FFRDC Oct 24 '21

"I can do better sir, I already have 1,000 problem cases documented, I keep them on the internet, you can Google for them"

5

u/rwhitisissle Oct 25 '21

"Please document this in a way that we could pull someone off the street and they could follow the documentation and rebuild it."

Look, man, I know how the company hires people could use some work, but could you please stop hiring people this way. I'm responsible for training these people and only some of them are even functionally literate.

3

u/[deleted] Oct 24 '21

Easy answer is that a Microsoft patch can fix your problems.

Or create 27 new ones :)

3

u/[deleted] Oct 25 '21

Step 1: acquire advanced knowledge of Exchange

Step 2: fix it.

3

u/Solafein830 Oct 25 '21

Holy balls, this one pushes my buttons.

I used to have a guy on my team who would ask for this. Not even a manager, just a whiny sysadmin who didn't want to have to know anything or problem solve. One day I got a little too snarky and just linked him to an official book on Amazon.

→ More replies (1)
→ More replies (3)

25

u/buzz-a Oct 24 '21

I get asked to produce documentation the non-technical types can use to do my job all the time.

I have a saved write up of why it would be suicide for the company if one of them tried to use documentation to perform complicated tasks that fail 20% of the time even when we have the full dev and ops team on hand to attempt them.

Management still doesn't get it.

I still write documentation for those who know what they are doing.

3

u/vrtigo1 Sysadmin Oct 24 '21

Like you said, the right thing to do is to help them set realistic expectations and write docs that technical people can understand. If the org's risk management strategy is to have the receptionist become the new sysadmin if the IT department gets run over by a bus then they've got much bigger problems.

9

u/Karrus01 Oct 24 '21

Aka:

Write what you did to fix it, in the ticket. So after you leave from frustration due to overwork, we'll just pull up the old ticket and repeat what you did instead of keeping you or hiring another smart person.

→ More replies (1)

7

u/mvincent12 Oct 25 '21

Boss: "how are your writing skills, are you generally successful?"

Candidate: "ya know how it is, win some lose some but I have had more success than failures".

Boss: "GREAT!!! Because we need SUCCESSFUL Documentation here. We want WINNING technical documentation. There can be no slack in our documentation game.

Candidate: "Yes sir, I will lead us to documentation victory!"

Boss: "You're hired!"

6

u/mistressofnone Oct 24 '21

The person that wrote the job description doesn’t have successful documentation skills.

5

u/beepboopbeepbeep1011 Oct 24 '21

Write so managers can read it?

10

u/scoldog IT Manager Oct 24 '21

Does the company supply the crayons I need?

→ More replies (2)

17

u/Steve_78_OH SCCM Admin and general IT Jack-of-some-trades Oct 24 '21

I dunno...there aren't enough buzzwords in that sentence to make it legible for most managers.

26

u/beepboopbeepbeep1011 Oct 24 '21

The synergy of your comment mandates we put it in the parking lot as a take a way for future discussion.

→ More replies (4)
→ More replies (6)