Experience complex with companies

Has anyone ever herd of volunteering or interning somewhere for experience in the exam type fields like admin? All the companies in my city require all IT to have at least 2 years experience in any field. Which tells me entry level stuff does not exist anymore, sad as that is.

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

ptilsen

Just ignore qualification requirements. What company would advertise a real position that needs no experience other than an internship? They don't really require what they say they require. Even with no experience, everyone in IT should have experience fixing friends' and family's problems. IT is not a catch-22; obviously people with no professional experience have to be able to find jobs. It's about being able to present yourself well and, again, blatantly ignoring job "requirements".

Ch@rl!3m0ng

kremit wrote: »

Has anyone ever herd of volunteering or interning somewhere for experience in the exam type fields like admin? All the companies in my city require all IT to have at least 2 years experience in any field. Which tells me entry level stuff does not exist anymore, sad as that is.

When I started off (After leaving the army) any of the jobs ads stated that you needed XY and Z and 2 years of experience.

I just applied for jobs anyway. If you dont want to volunteer then you could look at contracting to gain experience. Just remember that if your CV gets you a interview then the company thinks you can do the job all you have to do is prove it.

JDMurray

It's not your place to determine if you are qualified for a position. The hiring manager should have the oppertunity to decide to interview you based on what you currently have on your resume. If you start trying to second-guess what a hiring manager is really looking for in a job applicant, you'll probably second-guess yourself out of job. Submit your resume to every job requisition that interests you and let the hiring manager decide if you are a candidate for a first-round interview or not.

ptilsen

JDMurray wrote: »

It's not your place to determine if you are qualified for a position. The hiring manager should have the oppertunity to decide to interview you based on what you currently have on your resume. If you start trying to second-guess what a hiring manager is really looking for in a job applicant, you'll probably second-guess yourself out of job. Submit your resume to every job requisition that interests you and let the hiring manager decide if you are a candidate for a first-round interview or not.

I've never seen it phrased so perfectly. +1! No, +7!

Ch@rl!3m0ng

ptilsen wrote: »

I've never seen it phrased so perfectly. +1! No, +7!

+1 too. Just wish I was as Eloquent.

kremit

JDMurray wrote: »

It's not your place to determine if you are qualified for a position. The hiring manager should have the oppertunity to decide to interview you based on what you currently have on your resume. If you start trying to second-guess what a hiring manager is really looking for in a job applicant, you'll probably second-guess yourself out of job. Submit your resume to every job requisition that interests you and let the hiring manager decide if you are a candidate for a first-round interview or not.

See it's not me second guessing what the hiring manager, or specifically, HR is looking for. I am more concerned about meeting the requirements of the job. Good deal and thanks!

JDMurray

kremit wrote: »

I am more concerned about meeting the requirements of the job.

You can't possibly learn what the requirements really are until you have started the interview process. Even then, you don't really know what a job is like until you've worked there at least 2-8 weeks. Assume 50% of the information presented in the job description is "wishful thinking" by the employer and not factual for what you will really be doing most of the time.

kremit

JDMurray wrote: »

You can't possibly learn what the requirements really are until you have started the interview process. Even then, you don't really know what a job is like until you've worked there at least 2-8 weeks. Assume 50% of the information presented in the job description is "wishful thinking" by the employer and not factual for what you will really be doing most of the time.

Where the hell were you 1 year ago? I owe you a beer. On forth with my CCNA and N+

JDMurray

kremit wrote: »

I owe you a beer.

I would like to take you up on that one day, especially if it's 120F outside.

Lamini

Was in your shoes not long ago.

How could I land an IT job when all I had was my own entry level certs I paid out of pocket on my own (some employers saw this as initiative)? How can I get my feet wet in IT if I'm immediately turned down as I had no experience in it. The certs did help me get me a job(s) (mostly), but not alone. This with a good interview and its smiles. I got better as each interview went by (this means applying!), my confidence was based on relative job knowledge.