Back to Menu |
Cut the fat. Application Form Filename Structure Posted By: Thomas Shaw, 1:18am Friday 27 November 2009 |
Tweet |
Back to Menu |
Australian HR Tech Report Published: 11:17am Monday 29 March 2010 |
Ask who? Ask Hugo Published: 1:30am Friday 05 June 2009 |
Don’t be a mule Published: 1:00am Thursday 20 August 2009 |
Sandwich Board = Job Published: 10:57am Tuesday 23 December 2008 |
Interview with Clayton Wehner from CapitalJobs.com.au Published: 4:57pm Monday 19 January 2009 |
Silly mistakes |
QR Codes in Print Job Ads |
I don't care that you have more LinkedIn connections than me. You can buy them for $5 |
More jobs than SEEK? |
Fail Whale. Phishing link love |
if(candidate.experience.contains(it)) ++bonusPoints |
For bonus points, apply using the API |
"Attaging" with QR Codes - The security threat for mobile recruitment |
SMS "Apply" to... |
Typo squatting and the doppelganger domain threat |
If you're going online - great - and take this opportunity to streamline the process, make it easier for the candidate and yourself. Take advice from your technology vendor as they will have implemented many systems and will be in a good position to advise you on how best to 'cut the fat' as Thomas put it. If you're not sure they are giving you the best advice, find someone else!
Do not follow or even ask your technology vendor for this type of recommendation - ask your most experienced recruiter.
Too often the technology advisor is mostly interested in implementing the system with as little change as possible & seeks to implement a singlrestandard version to keep costs lower.
I bet that's how most of these really awful "registration" processes get implemented. Screen after screen of required information before you are "permitted" to apply for the job. I've sat in on meetings where everyone but the recruiter ( that's me ) has said " well if they are too stupid or too lazy to fill out these 5 ( count them - 5 ) screens to register - we don't want them!