Upgrade your account to a Community Supporter account and remove most of the site ads.
Rocket your D&D 5E and Level Up: Advanced 5E games into space! Alpha Star Magazine Is Launching... Right Now!

Reply to thread

Message: <blockquote data-quote="Byrons_Ghost" data-source="post: 2184107" data-attributes="member: 7396">For general postings, and for cold application resumes, I'd agree. For active hiring in IT, I actually have gotten more interviews from online applications and e-resumes than from paper. It's just a question of how the field handles the technology, I think.For larger organizations, like the one RW is talking about, the system probably forwards the resume to some sort of recruiter or screener, who looks it over so see if it meets whatever list of qualifications were given to them. Said list was given to them by the hiring department, it's likely the screen doesn't have the foggiest idea what half the stuff on the resume is. (Side note on the "3 out of 5" qualifications thing- I think that's true if the department is doing the hiring directly. If they're using a screener like I'm talking about, the screener will apply pretty much all the criteria, since that's what they're job is. They might let stuff slide if there's not many applicants, but we all know that ain't the case these days).Anyhow, the resume has to go through a couple of steps to get in front of anyone who makes and sort of decision about it, so there's a good chance that it does get trashed for being a month short of required experience, or something equally petty. In this case, paper probably would be better- you at least force the recruiter to take the time to toss it in the bin, instead of just hitting the delete key on the keyboard.Is anyone here involved with the HR side of IT? I don't mean to give offense, but man- there needs to be some sort of standard for recruiting, or something. Most of the jobs I've interviewed for have had vague and wildly inaccurate specs or qualifications in the list. Often, even with prior research, I couldn't entirely figure out what they wanted. I had one prospect, for example, looked like it would be perfect- small company, entry level, close to where I lived. All they had advertised for a skillset was Java, so I just thought it'd be basic stuff like writing routine functions, supporting what the main designers were doing, etc. Then, at the interview, I found out that they didn't really use Java so much except as a shell to do a ton of networking and system connections stuff, that had packages in Java but also had their own entirely seperate skillsets. So, basically, they wanted someone who could do that, with a little bit of Java to hook it altogether.My last interview was for a university department in charge of multimedia tech, wiring up classrooms, that sort of thing. Which sounded cool, especially since I thought I was interviewing for what would basically be an AV support job, and it turned out that had all this innovative stuff to play with. The job specified a HS degree only (which was sort of odd for what they wanted, my guess is they were looking to keep the pay low), and I knew both people in the department and had a friend in the University HR who had submitted me for the job. I thought I was a shoe-in, but it still went to someone with tons of experience. The way things are, entry level jobs are out there, but you just can't compete with someone else who's lost their job of 12 years, and is also looking for an entry level job because it's all they can find.</blockquote>

Verification