Advice, please, for a new RecWorks recruiter
| From: | Miles D. |
| Sent on: | Wednesday, March 16, 2016, 8:55 AM |
It's important for a job description to be correct.
This may sound obvious, but terms like full-stack developer, devOps, and architect can mean different things in different organisations. "What" do these mean, if used in a job description.
Be honest in a job description. If developers are expected to support systems out-of-hours, then it should be in the job description.
Be succinct. Saying someone should have an appreciation of AWS is not great. AWS is complex, better to identify the core building blocks used.
I also think candidates need to clarify ambiguity in a job description. Developers are not always great communicators, but the ones who do contact you, make sure you get clear answers to questions, feedback, and update the job description.
For all of the above, please don't let none technical, internal HR departments lose the detail (and clarity), for a job spec. I have heard comments along the lines of "Java and Javascript sound similar" :-(
If I was was a civil engineer, building bridges, I would apply for jobs in this area. A developer deserves the same clarity.
Technical tests need to be clearly described. If you want a readme.md in a git repo, ask for that. If you expect someone to do a pairing session in an interview, please say that.
Must go as time to get off train.
Cheers
Miles.
People in this
group are also in:
-
DevOps Playground
5,078 Members
-
Agile London
5,457 Members
-
PyData London Meetup
13,995 data folk
-
JavaScript London
4,048 JavaScripters
-
GDG London
3,180 Members
-
London DevOps
10,504 DevOps Doves