|
|
|
|
|
|
by markfer
3299 days ago
|
|
|
Without spending too much time answering this - you're half right. Google is our top hiring partner by a long margin. The application requires a coding test, a technical interview (answering 3 questions with 15 minutes each), and a nontechnical interview. On average this takes 3-5 weeks.
We have tens of thousands of applications on a yearly basis, of which we accept 2-3%. The curriculum spends 9 weeks going through CSS, HTML, JS, and Ruby on Rails, of which an average week consists of 80-100 hours of coursework (no exaggeration here). Then 3 weeks for a final project of their choice, and prepping for job applications. The vast majority of our graduates will then have a job within 6 months of graduation. Yes, they interview at a lot of places and do better each time. Yes, it is incredibly difficult. Yes, they do get a job at Google when 6 months earlier they didn't know what a function was. Hope this helped. |
|
|
Doesn't your screening process basically require you to already know basic ruby? You don't have any idea how long it took an applicant to get to the point, so how can you have any idea if there are really people going from not knowing what a function is to job at Google in 6 months?
>which an average week consists of 80-100 hours of coursework (no exaggeration here).
I can't think of anything similar to this except maybe Resident Doctors, and they are performing a job, not learning for 100 hours a week. I'd really like to see some efficacy studies because I find it very hard to believe that learning for 12 hours a day for 9 weeks is effective.
After the whole thing is done, those that make it through are probably worth hiring because they made it through, not necessary because of what they learned during the process.
If anything It sounds like what you've really done is to create a multi month interview process that you've convinced people to pay for.