Open rub1e opened 9 years ago
Another one:
@rub1e so many (good) questions here. Might be worth splitting them out in case further discussion is required on any of them...
(Without any exaggeration) there are _thousands_ of "_tech_" recruiters in the world and we've met only a handful who know the difference between Java and JavaScript (and even then, a couple of them _memorised_ the answer) ... yes, its that bad! :cry:
Why is this the case? and is it a problem?
The objective of a recruiter is that of a sales person, they are focussed on the numbers and will sell the opportunity to the candidate using every trick in the book to pain it as the best 'opportunity" available in the marketplace ... and once they have "placed" you (locked in their commission), you are dead to them ...
Recruiters not understanding the technology is a problem because they will try to place people at the company that offers the highest commission not the one that will give the developer the best learning opportunities or interesting work.
Our _mission_ will be to find work for people based on what drives them: http://www.ted.com/talks/dan_pink_on_motivation somewhere they will be happy and thus more productive.
The duration of the initial agreement (4 months) is to not overwhelm anyone. We are fairly confident that we will find work for people beyond that initial timeframe but we don't want anyone thinking they are "locking themselves in" to anything.
Yes. We only want to work with people who want to work with us more than anything else. We know that will not be all 16 people in any cohort.
On the subject of people being "cr@p" ... We consider ourselves pretty good judges of character, so we expect to know long before the 16 week course has ended whether a person is going to be an "A Player" or not... A key point to note here is that the people who are fantastic at coding, might not be great team players; we will find them work somewhere they will learn teamwork...
Couple ofA few things: