Live data from Hacker News

Bootcamps vs. College

blog.triplebyte.com

71–80 of 449 posts

Re: Bootcamps vs. College

#71
post #47

How is this possible? I think one key aspect that is missing is that boot camp graduates aren't straight off the barista lineup. I took one at age 28 after having worked in a technical role in finance since undergrad. The average age of my class was probably 29. Beyond just time in the workforce, I had a double major in math and economics with a minor in applied statistics. Had I dropped "Behavioral Economics" and ta…

Good point. About 50% of the bootcamp folks we work with have some sort of technical background before the bootcamp. The other 50% do not, however, which is really interesting! (I have no idea how this compares to the bootcamp population as a whole. I would guess that folks with a tech background are overrepresented in the group that passes our screening step)

Definitely. I had a wide range of classmates. We had several people that were project managers looking to gain some technical knowledge/communication skills. They had no intention of becoming programmers. A good chunk were designers who had html/css knowledge that were looking to expand their reach. A couple were a drain on my education. My greatest criticism of the programs is that it's an educational boom, so there isn't a stronger filtering process in place yet.

Re: Bootcamps vs. College

#72
post #36

I'm in the process of hiring a junior position and have no bias towards college grads or bootcamp grads. The only negatives towards boot camp grads I've seen so far is: 1) One candidate had no idea what the terms "Class" or "OOP" even meant. I'm FINE with them not understanding stuff like sorts/advanced data structures, but he ACTUALLY had 0 idea what an int was. No lie! 2) I wish there wasn't such a heavy reliance o…

1) That's not really a "bootcamp" issue as it is with a candidate who can't be bothered to learn basic programming concepts or open a book on their own. Almost every book I've read on programming covers OOP in most languages. You can even hack it together in BASH (http://lab.madscience.nl/oo.sh.txt), not that you should.

2) LAMP stack is still probably the safest bet (substitute PHP for Python maybe), but yeah, just because it's the current hotness for a few startups doesn't mean it'll get you hired to know the most hyped tech.

3) Stop looking for candidates from Manhattan, or only hire those looking to move who have done just a little bit of research? CNN's COL calculator shows $100K in NYC is equal to about $54K in NJ so you don't seem too far off base for what you're looking for (http://money.cnn.com/calculator/pf/cost-of-living/). From personal experience their calculations were accurate when I made my move from the midwest to SF. Regardless, again that doesn't sound like a "bootcamp" issue so much as "candidates who can't be bothered to do basic googling/research issue."

Re: Bootcamps vs. College

#73
post #36

I'm in the process of hiring a junior position and have no bias towards college grads or bootcamp grads. The only negatives towards boot camp grads I've seen so far is: 1) One candidate had no idea what the terms "Class" or "OOP" even meant. I'm FINE with them not understanding stuff like sorts/advanced data structures, but he ACTUALLY had 0 idea what an int was. No lie! 2) I wish there wasn't such a heavy reliance o…

It really depends on which bootcamp. I finally picked up SQL while at App Academy and while we did use JSON, we spent no time working with NoSQL databases. Backend ended up being my strength and my primary role at my (full stack) jobs. The monetary worth as a junior developer is also very dependent on the bootcamp. A decent App Academy or Dev Bootcamp grad in NYC? 60k is a reasonable minimum IMO and a wage below that…

That's good to hear about the SQL. Honestly, we sort of didn't even bother with AA candidates because I went to the website to check it out, and first thing it says is "graduates earn an average of 89k in NYC". Instantly knew that whatever they were telling the students, we couldn't afford em.

On Indeed, we get a lot of crossover because of our proximity to NYC. I think we come up if you do a 50mi radius and search junior, not sure honestly. I totally get it, but it's getting to the point where we see NYC on the resume, we pass them aside cause we know we can't afford them. Probably better for both parties.

Re: Bootcamps vs. College

#74
post #36

I'm in the process of hiring a junior position and have no bias towards college grads or bootcamp grads. The only negatives towards boot camp grads I've seen so far is: 1) One candidate had no idea what the terms "Class" or "OOP" even meant. I'm FINE with them not understanding stuff like sorts/advanced data structures, but he ACTUALLY had 0 idea what an int was. No lie! 2) I wish there wasn't such a heavy reliance o…

1) That's not really a "bootcamp" issue as it is with a candidate who can't be bothered to learn basic programming concepts or open a book on their own. Almost every book I've read on programming covers OOP in most languages. You can even hack it together in BASH ( http://lab.madscience.nl/oo.sh.txt ), not that you should. 2) LAMP stack is still probably the safest bet (substitute PHP for Python maybe), but yeah, jus…

We're not looking, they are applying. Like I said, I understand why they aren't a good match COL/salary wise, just kinda of was writing about how I think it's interesting that they teach what salary they should be seeking minimum. That was never brought up in my BS degree.

Re: Bootcamps vs. College

#75

Earlier quoted context omitted.

How long is a well-run bootcamp? Getting a CS degree takes many, many hours of course work, plus typically a bunch of non-CS course work. I'd think a college grad would (should?) be much better rounded. That depends a lot on the quality of their CS program, obviously. What you describe college grads doing sounds more like a 1-semester high school CS class to me.

> How long is a well-run bootcamp? If I were put in charge, I would make it 6 months long. I could definitely teach people how to write coherently designed CRUD apps in 6 months (ie. 95% of all programming businesses in the wild).

In another comment I wrote that bootcamp-trained developers are learning to do jobs that will be automated soon. It's interesting that you mention teaching them to write coherently designed CRUD apps, because my company's product is a tool that writes a coherently designed CRUD app based on querying your database schema. Using my company's product, I can spend 15 minutes to do the job that you spent six months training someone to do.

It'll do the job better too; this isn't a simple Ruby-based admin app that gets generated. We generate a feature-rich enterprise-class system with both Windows desktop and web-based UIs, that could be deployed into production as soon as the code generation is complete. (Typically there's customization work done before deployment, but for a lot of tables that's not necessary.)

Re: Bootcamps vs. College

#76
post #11
post #2

I'm happy to answer any questions about this (I expect it to be controversial). When we started Triplebyte one year ago, I was pretty skeptical of bootcamps. Doing credential-blind interviews and seeing what some bootcamp grads can do, however, has won me over. Clearly there are a lot of bad bootcamp grads (and probably a lot of bad bootcamps). But the model is working really well at the top.

Great stuff Ammon and team! Can you discuss how you might test for bootcamps overfitting their curriculums to interviews? They definitely would seem financially incentivized to do just that. From a personal anecdote, someone I interviewed was able to code a solution for a problem, but then couldn't discuss how or why they did it that way at all, or solve a closely related problem, which made me strongly suspect that…

Interesting questions. Bootcamps are clearly incentivized to do this. However, they do not seem to be particularly good at it. Algorithms are over represented in interviews relative to most jobs, and yet (as our data shows) bootcamps are not very good at teaching this. Now, we are measuring algorithmic skill by asking candidates to actually implement non-trivial algorithms. We've observed that a lot of interviews involve what is essentially trivia about algorithms, and it's possible that the bootcamps are better at preparing students for this (we don't measure this skill so I am not sure). I think that this gets at the answer. If you make your interview go deep, it gets increasingly hard to specifically prepare for it, to that point where preparing is actually becoming a better programmer. Rather than a 30-minute question that covers knowledge of sorting algorithms (easily learnable), have your candidate spend an hour building a collision detection systems using a axis-sorted list of rectangles, and reason about maintaining this sort as objects move around. That's the theory. In practice there will always be some noise.

Re: Bootcamps vs. College

#77

I have a slightly more pessimistic view of the situation: Sure, bootcamp grads can write a web application just fine; after all, it's usually only CRUD. But what value are they bringing to an organization? Why would I pay them the same amount as a college graduate who undoubtedly has more total knowledge not only in CS, but in other areas as well? Ideally, a college should expose students to a diverse range of knowle…

Usually doing innovative independent work requires a whole lot of domain knowledge that can only be learned once you're in the business. (If not, I'd question the defensibility of the business...) Both a bootcamp grad and a recent CS college grad are completely unsuited for that. That's why they're junior developers; they need mentoring to understand the context of their work, the factors that need to enter into decisions, and the body of proprietary knowledge that the industry is built upon.

Doing a CRUD web application is a good way to get a candidate into the door so that you can observe, first-hand, their response to learning that body of knowledge. Your business's competitive advantage may be based upon proprietary algorithms and deep domain knowledge, but sometimes you just need a webserver done. And the person who goes and builds that webserver will learn a lot about the domain knowledge needed to interface with it, and you'll learn a lot about how they approach challenges and seek out the information that they need but don't have.

All of this is independent of whether they learned to build that webserver in college or a bootcamp.

Re: Bootcamps vs. College

#78
Boot camps have their place, but they are not a replacement for a traditional CS degree. I have met good and bad programmers from both types of programs (some from well respected colleges who I still wonder how they exactly passed), but here's the thing, I don't care about practical skills. I care about the person being able to think.

All those concepts that they teach in CS isn't about knowing the name of an algorithm, it's about thinking abstractly. I honestly don't care if a recent grad knows how to use IDE x or even much about source control. I can easily teach them that. I can't easily teach a person how to understand pointers or pass functions as parameters. I don't need someone who can write code; I need someone who can look at a problem and realize that we can cut the amount of work we have to do by understanding programming concepts at an abstract level. It is very hard to achieve this in a 12 week course. Can some people do this? Sure, they may have the background from a previous career that aids them in this, but they are the exception and not the rule.

Re: Bootcamps vs. College

#79
post #2

I'm happy to answer any questions about this (I expect it to be controversial). When we started Triplebyte one year ago, I was pretty skeptical of bootcamps. Doing credential-blind interviews and seeing what some bootcamp grads can do, however, has won me over. Clearly there are a lot of bad bootcamp grads (and probably a lot of bad bootcamps). But the model is working really well at the top.

It's great to see some hard data on this!

Were you able to see any patterns in the backgrounds of the bootcamp students?

It doesn't seem too surprising that someone with a physics or finance or mechanical engineering background can learn enough programming skills in three months to be productive. But do students without as much prior experience in quantitative and analytical thinking have as much success?

Re: Bootcamps vs. College

#80
post #36

I'm in the process of hiring a junior position and have no bias towards college grads or bootcamp grads. The only negatives towards boot camp grads I've seen so far is: 1) One candidate had no idea what the terms "Class" or "OOP" even meant. I'm FINE with them not understanding stuff like sorts/advanced data structures, but he ACTUALLY had 0 idea what an int was. No lie! 2) I wish there wasn't such a heavy reliance o…

It really depends on which bootcamp. I finally picked up SQL while at App Academy and while we did use JSON, we spent no time working with NoSQL databases. Backend ended up being my strength and my primary role at my (full stack) jobs. The monetary worth as a junior developer is also very dependent on the bootcamp. A decent App Academy or Dev Bootcamp grad in NYC? 60k is a reasonable minimum IMO and a wage below that…

I know salaries are lower in NYC than SF, but even $80k/yr probably won't get you an App Academy graduate in SF. If it does get you an App Academy graduate, well, we actually talk to each other about compensation so they will almost certainly get poached after 6 months to a year.

The issue isn't what the bootcamp grad is worth. The issue is what the next best option is - spending more time job hunting and getting a position that values you better. An $80k/yr offer in SF isn't good enough to convince you to call a halt to the process, not when so many of your peers are accepting offers between $100k and $120k.

Post reply on HN