Quote:
Originally Posted by Baltimore Jones
Very nice. Questions:
1. Most of these programs imply that starting Ruby jobs are $70K-$90K and that you're pretty close to guaranteed a job after completing the 2-3 month bootcamp. How realistic is that starting salary and how easy will the job market be for people who have gone through a bootcamp?
That range is very realistic *for SF*. 80k seemed to be the standard coming out of the brand-name bootcamps, though some go higher and lower and lately it seems like that number is creeping a bit higher. It'll be interesting to see the numbers as some of these get established in other cities and build awareness. Dev Bootcamp just opened a Chicago branch, App Academy a NYC one, and plus all the other assorted clones. I work with a guy that went to a different bootcamp and without fail one of us has stumbled upon a website for a new one every week. From my experience, outside of SF it's a tougher slog, both in terms of number of opportunities and salary.
Tougher to answer re: job market -- I had a fairly easy go of it, but I'm one of many who are watching all these bootcamps popping up and feeling pretty happy that I got in when I did, as at some point we'll hit saturation. I'd consider Dev Bootcamp, App Academy, and Hack Reactor (JavaScript-based) the premier programs at this point. If you go to any of those 3 and do well, you won't have much trouble in the job market.
These things aren't cheap, but it's important you also give yourself some financial runway for afterwards to make sure you find a good fit. I'd budget for 2 months after so you aren't overly rushed. If you do well you likely won't need that much time -- the market moves insanely quick at a lot of companies here, I went from intro phone call to offer in exactly 1 week. But I also saw multiple people who were definitely good enough to get 80k+ offers take lower-paying internships or lowball offers because they didn't have the ability to wait for something better. I ended up with a great offer at a company in a field I'm very interested in, but there was some waiting involved and I was lucky to be able to afford to do so.
While the market is great for developers in general, there are only so many junior positions to go around, and I'm not sure how kind the market is going to be for those who don't excel at these bootcamps in the future. I think it's extremely important to show up prepared. While the whole "Anyone can learn to code" and "Perfect for absolute beginners" stuff makes for great copy, the reality is you should be doing as much as possible on your own before you show up so that you can be near the top of your class and have a nice portfolio to show off when you hit the market. Which leads into your next question..
Have worked through the free online resources on your own. You'll show that A) you've actually done some coding and aren't just applying on a whim, and B) you've been able to grok some of this on your own. Have a compelling or at least logical story for why this is the right next step for you and why you think you're ready for it. For me it was the fact that I'd had that startup my last year of school, couldn't work very effectively with my developers, and realized in the process that I wanted to do the actual "making." I had 2 interviews, and after the first I emailed one of the staff saying, "Hey, I interviewed with so-and-so and they mentioned the prep material -- I'd love to get started on it, would you mind sending a list of the resources you recommend?" Show that you're a self-starter, a quick learner, but humble and coachable.
I'd recommend digging into Codecademy, Eloquent Ruby/Pickaxe book, Ruby documentation, and possibly even Rails guides to try to build something basic/Hartl tutorial, before applying. Then if you get in, put as much time as your circumstances permit into prep work. I remember being told that regardless of how much we did beforehand, we'd be either 0.1% or 1% of where we'd be at the end. Not sure how true that statement was, but if it was accurate that was one big-ass 0.9% of separation. There just isn't enough time to catch up to those who come in far ahead of you, plus the people who come in most prepared are going to be hardworking enough that they'll never give you the opportunity to outwork them to make up that ground. I wish I had come in more prepared, and most everyone feels that way. I went in having done the bare minimum that was given to us as prep material, whereas one of the top guys in my class had been focusing on learning full-time for 6 months before walking through the door on Day 1..needless to say we were on different levels when we left. Go in prepared.
Quote:
3. Any ideas on Plan B, for people who cannot get into one of the schools? Thanks!
Tough one. I'm very new to this (no technical background at all before DBC) so this is my only-somewhat informed take:
A) Think hard about if this is *really* what you want to do, as it will be a tough path. If so, your end goal should probably be to put together as good of a portfolio as possible. To that end:
-go through the online resources (Codecademy, Code School, Railscasts, etc.)
-read (Well Grounded Rubyist, Eloquent Ruby, Practical Object Oriented Design in Ruby, Pickaxe book, RSpec book, The Rails 3 (4?) Way, etc for starters)
-Don't be afraid of the documentation -- dig into the Ruby documentation and Rails guides/documentation
-Try to find a mentor and/or pay someone to periodically pair-program and/or review your code. One of the CEO's that came and talked to us mentioned he was learning to code by paying some college student that was a total whiz-kid like $40/hr. to teach him, just basic stuff, but definitely an affordable way to supplement self-learning and bridge gaps. If you can swing being in SF while you learn on your own, there are multiple Ruby meetups every week that are pretty beginner-friendly from what I understand, and someone there would be happy to help you hack on a project you're working on.
-Start building stuff you're interested in and lean heavily on Google and Stackoverflow for debugging errors and getting your questions answered. Try out different technologies and try to demonstrate proficiency with different technologies/focus on different aspects with each one, as one of the main things I've heard is employers want to see more than just a bunch of standard CRUD apps.
A couple blog posts I read last night and completely agree with, from guys who just finished the most recent DBC cohort:
http://eyeofthesquid.tumblr.com/post/49755884503/day-99
http://t.co/lW6lYCzucZ Eno is a baller. I actually haven't met him yet, but the guy finished up his Ph.D at Princeton just after finishing DBC and is now going to work at Pivotal Labs (top consultancy), following in the footsteps of another guy that did DBC in the summer.
Last edited by TomfooleryU; 05-06-2013 at 02:18 PM.