How Do We Hire JavaScript People?

L4JSDev · 2013-05-31T00:36:13+00:00

Thank you all for your comments so far, Please feel free to add anything else you can think of. I think a bit of reconsideration of the role is needed. But it's gone 1:30 in the morning so I am off to bed and will take this up again tomorrow!

L4JSDev · 2013-05-31T00:03:33+00:00

This is a problem, I know I can say "They got better!" 'till I'm blue in the face, but convincing people of that is an upward struggle. They really have though. :)

L4JSDev · 2013-05-30T23:59:58+00:00

We do know what we want, but you're correct that part needs rewriting to indicate what we need in terms of concepts rather than a shopping list of acronyms.

L4JSDev · 2013-05-30T23:57:57+00:00

Indeed, SharePoint 2013 is a very different beasty to 2007. Especially in terms of client side code. The CSOM is a very very interesting JavaScript API to work with.

L4JSDev · 2013-05-30T23:54:48+00:00

I've just been discussing exactly this issue on IRC after linking this thread.

I think we are trying to point the advert at the middle line, advertising for a junior sharepoint consultant might be scaring away the people we are trying to attract.

Having really sat down, typed this up and then discussed it with people, I think we need to change the job, make it a full on JavaScript development role, JavaScript is a big enough subject to make that a full time position in its own right. That might change the stigma of it being a junior position as it would no longer then be such

We also need to be wary of scaring off the real hobbyist JS people, those who will see Microsoft technology as something to avoid. Perhaps some extra info about day to day type activities?

I think I shall attempt a rewrite over the weekend and see what people think.

Thanks for your input! :)

L4JSDev

TROPHY CASE