A few things I noticed (through just a quick inspection):
1) Average training time is about 10 weeks;
2) 28 out of 50 teaches Ruby/Rails, 15 out of 50 teaches JavaScript, 5 teaches Python, 3 teaches iOS, and 3 teaches Android.
---
So, yeah, the curriculum is pretty practical. I doubt many of the curriculums cares about C.S. basics as long as it is enough to let them write Rails code.
I think one way to filter out the inept students is may be let them do some algorithm problems during interview? Also if your company does Ruby, then let a part of interview process be solving the bugs or issues on company's current project, and try to see how to approach the problem and whether can get it done. Understanding other people's code and reproducing/tracing/fixing bug is something very important. Also a big thing is when a bootcamp grad candidate say "you should do X in Rails", probably ask them why is a good idea. Do they do X just because their teachers say so, or there is a good reason for really doing so.
Disclaimer: don't have any experience with any bootcamp grad, but with experience working with X (place Rails, Django, etc. here) only guys.
> I think one way to filter out the inept students is may be let them do some algorithm problems during interview?
Depending on the goals of the interview, that can either be useful or a waste of time.
Bootcamp students may have never had a formal introduction to algorithms. Therefore, phrasing a question in terms of space / time Big O complexity is pointless.
However, if the interviewer is capable of posing an algorithm question in more generic terms it can certainly tease out an interviewee's approach to logic and problem solving.
I have come across a few that do teach algorithms, although I've never been. How deep can you get on algorithms when you only learn it for a week?
With that said, I'm not a CS grad and I've learnt time complexity through self learning.
Personally I don't think algorithms are really necessary for people working to be front end web developers. The bottleneck on speed is in the back end.
http://www.programmingisnothard.com/bootcamps
A few things I noticed (through just a quick inspection):
---So, yeah, the curriculum is pretty practical. I doubt many of the curriculums cares about C.S. basics as long as it is enough to let them write Rails code.
I think one way to filter out the inept students is may be let them do some algorithm problems during interview? Also if your company does Ruby, then let a part of interview process be solving the bugs or issues on company's current project, and try to see how to approach the problem and whether can get it done. Understanding other people's code and reproducing/tracing/fixing bug is something very important. Also a big thing is when a bootcamp grad candidate say "you should do X in Rails", probably ask them why is a good idea. Do they do X just because their teachers say so, or there is a good reason for really doing so.
Disclaimer: don't have any experience with any bootcamp grad, but with experience working with X (place Rails, Django, etc. here) only guys.