Entry level

Now I don’t consider myself entry level, I’d consider myself Junior, but not entry level. I have around 5 years experience in IT. 1.5 years Helpdesk, 3 years Desktop Support and Network Admin.
Am I just completely off here, or can someone explain to me what ENTRY LEVEL is? I’ve always had this, I guess naive assumption, that entry level means NO experience and maybe some schooling. But I keep seeing positions that say entry level and then say 1 year experience, 1 – 2 years exp, I swear, even though I can’t remember where, that I saw one that said 3 - 5 years exp.
WTF?
Anyone out there, maybe those of you that run your own business, want to expand on this for me?
This is the post I most recently noticed.
http://philadelphia.craigslist.org/tch/814100655.html
Am I just completely off here, or can someone explain to me what ENTRY LEVEL is? I’ve always had this, I guess naive assumption, that entry level means NO experience and maybe some schooling. But I keep seeing positions that say entry level and then say 1 year experience, 1 – 2 years exp, I swear, even though I can’t remember where, that I saw one that said 3 - 5 years exp.
WTF?
Anyone out there, maybe those of you that run your own business, want to expand on this for me?
This is the post I most recently noticed.
http://philadelphia.craigslist.org/tch/814100655.html
Comments
Usually someones skill set grows with time but not always.
The Fiber Optic Association www.thefoa.org
Home Acoustics Alliance® http://www.homeacoustics.net/
Imaging Science Foundation http://www.imagingscience.com/
en·try-lev·el Audio Help /ˈɛntriˌlɛvəl/ Pronunciation Key - Show Spelled Pronunciation[en-tree-lev-uhl] Pronunciation Key - Show IPA Pronunciation
–adjective
of, pertaining to, or filling a low-level job in which an employee may gain experience or skills: This year's college graduates have a limited choice of entry-level jobs.
-relatively simple in design, limited in capability, and low in cost: entry-level home computers and word processors.
This sounds more like entry level IT than the first one
Keep in mind that, while helpdesk and network administration are related, they're not the same job. You were entry-level when you did helpdesk, and spent 1.5 years there, then you could probably have considered yourself mid-to-senior level. Once you stepped up to network admin, you're practically back to square one. You have the tech skills you learned as a helpdesk tech, as well as the experience working with end-users and vendors, but the job of network admin has different requirements and that prior experience will only be so much help.
Looking at your certs, looking at the time you've spent as a network admin, I'd say you're probably in the mid-range of experience, not necessarily a junior and not quite a senior. If you feel comfortable in your knowledge of the job, and you come to work without the fear of "oh god, what will I do if. . ." kinds of thoughts in your head, you can safely say that you're no longer an entry-level admin, but an experienced one.
Here's the breakdown, as I see it (in an ideal world, mind you):
Entry-level: No experience, limited or "canned" skills. (Certs and/or degree.)
Junior: Some experience, say 1 or 2 years, qualified for work that may be challenging, but not ready to fly solo on big projects. Still falls under the "technician" category, more focused on the equipment and less on the business of IT.
Mid-Level: Somewhere between 3 and 5 years experience, comfortable with the work, knows how to get things done without having to be supervised. Not necessarily a full-time projects type of person, but can handle integrating new technologies and performing tasks like rolling out new servers, routers, software, etc. Mentors, if not supervises, junior and entry-level IT staff, as well as has some involment with the business-aspects of IT, (recommending purchases, going to management meetings, etc).
Senior-level: This is the big guy, the expert, usually the boss. Heads up major projects, handles management responsibilities, supervises other admins and techs, and is usually the one that gets handed the newest, most untested equipment, and is told to "make it work". Gets paid in heaps, but the trade-off is that this admin has to KNOW EVERYTHING. Can often times be quite jaded, hidden behind a mountain of O'Reilly or Cisco Press books on his desk.
Free Microsoft Training: Microsoft Learn
Free PowerShell Resources: Top PowerShell Blogs
Free DevOps/Azure Resources: Visual Studio Dev Essentials
Let it never be said that I didn't do the very least I could do.
In that case I turned from newbie entry level administrator to season pro in the span of two weeks in this job. (Almost everything that could go wrong did go wrong in those 1st two weeks and almost sent me packing.)
I would agree with the concensus that entry level is more about the skill sets that you will be needing to acquire than the general IT experience you have. 10 years experience in help desk related activies and 0 years experience in administration duties = entry level administrator. I generally think that within 1 year though that a person breaks the entry level requirements. Depends upon the duties assigned. If the focus is too limited and narrow then even if the title is network administrator if all you ever do is create/delete user accounts and reset passwords then you're still entry level.
Very true, getting pigeon-holed is almost as bad as not working at all. If you're at a place that runs old NT4 servers for 10 years, you won't be capable of going out and touting yourself as a Sr. Systems Administrator now that Windows Server 2008 is out. Part of what makes this industry so difficult, is staying on top of the latest technology and best-practices.
Free Microsoft Training: Microsoft Learn
Free PowerShell Resources: Top PowerShell Blogs
Free DevOps/Azure Resources: Visual Studio Dev Essentials
Let it never be said that I didn't do the very least I could do.
Free Microsoft Training: Microsoft Learn
Free PowerShell Resources: Top PowerShell Blogs
Free DevOps/Azure Resources: Visual Studio Dev Essentials
Let it never be said that I didn't do the very least I could do.
I'd agree with undomiel,
I have broken and fixed more **** than I could ever imagine. Nothing like being thrown to the wolves.
Free Microsoft Training: Microsoft Learn
Free PowerShell Resources: Top PowerShell Blogs
Free DevOps/Azure Resources: Visual Studio Dev Essentials
Let it never be said that I didn't do the very least I could do.
Recent: 11/2019 - RHCSA (RHEL 7); 2/2019 - Updated VCP to 6.5 (just a few days before VMware discontinued the re-cert policy...)
Working on: RHCE/Ansible
Future: Probably continued Red Hat Immersion, Possibly VCAP Design, or maybe a completely different path. Depends on job demands...