Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

systems engineer-who should be called a system engineer

Status
Not open for further replies.

zebra1057

Technical User
Mar 31, 2001
39
US
For me, a systems engineer should be a person who has mastery in the following skills:

1) mastery in windows 2000, windows 9x, internet explorer, IIS, outlook client, clustering, exchange, terminal services

2) network security-- possess the skill to be a network de-
fender and network intruder

3) has intermediate knowledge of novell netware because they
are still in business

4) knowledge of unix because those As/400 and rs/6000's seems to be always there running aix

5) mastery of old dos because the command line
troubleshooting is always something like this

6) mastery of another language like VB so you can program
microsoft operating systems

7)mastery of cisco routers so you can connect your lans and
your company's different buildings

8) some knowledge of MS office because user's always ask
something about Word or Excel when you are under
the table . And if
you can't answer, they think you don't know anything.

9) mastery of A+ so you can build and troubleshoot your
multiprocessor servers. Includes the skills needed
for disaster recovery like broken hard drives,
motherboards, power supplies, printers,cd-roms
that reads only things it wants to read

The ability to answer the Tek-tip boards for these subjects
can be your performance monitor.

Just my 2 cent opinion adjusted after inflation.

roland
 
Roland,

You forgot the following abilities:

1. Arrive before everyone else otherwise the first person in will discover a dead server and will harp on about your uselessness for days.
2. Leave after everyone else or your mobile goes off while you are travelling home.
3. Work through lunch. If one person works through lunch in the company, IT should be doing so too.
4. Physical knowledge. Should know how to strip a printer, change the fuser, unclog the ripped paper they partially removed.
5. Company knowledge. Understand all the servers, how they link together, who is in which group / department. Know everyone by name. Know everyone's phone numbers off by heart.
6. Non-jobsworth. Should be proficient at moving tables, filing cabinets, fixing photocopiers, putting things on high shelves or removing them.
7. Patching. Should be able to repatch any individual to any position in the office in their sleep.
8. Payment. Should accept below market payment, appalling annual reviews and negligible pay rises.

And of course.

9. Should smile all the time.
 
The funny thing is, there were "systems engineers" long before DOS came on the scene (similar to electrical, mechanical, civil, etc engineers). Microsoft's cert title notwithstanding, I prefer the term network engineer (and before anyone responds that that could refer to the telecom guys, I'd note that I call them telecommunications engineers). That being said, yay, I fulfill eight and a half of Zebra's criteria (my *nix being too shaky to fully count) and would add a tenth - database skills, to include database admin, some simple scripting skills, and familiarity with reporting software such as Crystal Reports.

-Steve (MCSE+I, CNE4&5, CCA, A+(DOS/Win3.11), Network+, etc.)
 
Look everyone knows that ANYONE who works in an IT department knows everything. (Or at least everyone THINKS you do). I mean hey, I know Windows, DOS, UNIX(LINUX, AIX and SCO).I even know how to troubleshoot, PC's, Servers and Printers. Heck I can spell my name right most of the time. But D@#* it, all this "Knowledge" and I still cant set my VCR time. ;-) James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
My opinion..
A good start for a Jr.Systems / Network Engineer is the person everyone goes to for every little quark that Microsoft can throw at you.

1. "Hey, I can't log in" "Turn your caps lock off"
2. "Hey, I can't print" "Turn the printer on"
3. "Hey, where do I find this" "click on start, help"
4. "Hey, the internet in down" "The whole thing?"
5. "Hey, I can't seem to get to my favortive web-site to download my virus infected screensavers" "We blocked it"
6. "Hey, look, my e-mail is acting weird and sending mail to everyone" ....DAM
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top