Hack Reactor is self-admittedly not a "0 to 60" course, it is instead a "20 to 120" course and expects successful applicants to have some background in coding (either professional or self-taught). Boasting a 98% graduate hiring rate, Hack Reactor places alumni in mid-to-senior level positions at companies in tech, including Google, Salesforce & Microsoft, with an average graduate salary of $104K.
On-Time Graduation Rate
180 Day Employment Breakdown:
Recent Hack Reactor News
- Episode 14: May 2017 Coding Bootcamp News Roundup Podcast
- Diversity & Inclusion at Hack Reactor
- Episode 13: April 2017 Coding Bootcamp News Roundup + Podcast
Recent Hack Reactor Reviews: Rating 4.51
- Around half of our students receive help in financing their Hack Reactor journey. We work with lending companies that understand the investment you are making in yourself. Pave, Skills Fund and Climb all offer pre-approvals, so that you can have a loan secured upon acceptance to the program. WeFinance is a crowdfunding platform with a dedicated page for our students.
- Payment Plan
- Deferral program available
- $1.3MM Hack Reactor Scholarship Fund - visit www.hackreactor.com/scholarships to apply!
- Minimum Skill Level
- Computer science and programming background required
- Placement Test
- Prep Work
- Approximately 30 hours
In PersonFull Time
In PersonFull Time
Hack Reactor Remote
- Payment Plan
- Applicants who would otherwise be unable to attend Hack Reactor may split their tuition into installments and finish paying a portion of tuition up to six months after graduation.
- Limited number of half-tuition scholarships
- Minimum Skill Level
- Some computer science and programming background suggested
In PersonFull Time
In PersonFull Time
New York City
- Around half of our students receive help in financing their Hack Reactor journey. We work with lending companies that understand the investment you are making in yourself. Pave, Skills Fund and Climb all offer pre-approvals, so that you can have a loan secured upon acceptance to the program. WeFinance is a crowdfunding platform with a dedicated page for our students.
- Payment Plan
- Deferral program available
- $1.3MM Hack Reactor Scholarship Fund - visit www.hackreactor.com/scholarships to apply!
- Minimum Skill Level
- Computer science and programming background required
- Placement Test
- Prep Work
- Approximately 30 hours
- Around half of our students receive help in financing their Hack Reactor journey. We work with lending companies that understand the investment you are making in yourself. Pave, Skills Fund and Climb all offer pre-approvals, so that you can have a loan secured upon acceptance to the program. WeFinance is a crowdfunding platform with a dedicated page for our students.
- Payment Plan
- Deferral program available
- $1.3MM Hack Reactor Scholarship Fund - visit www.hackreactor.com/scholarships to apply!
- Minimum Skill Level
- Computer science and programming background required
- Placement Test
- Prep Work
- Approximately 30 hours
- Payment Plan
- Deferral program available
- $1.3MM Hack Reactor Scholarship Fund - visit www.hackreactor.com/scholarships to apply!
- Minimum Skill Level
- Computer science and programming background required
- Placement Test
- Prep Work
- Approximately 30 hours
- Payment Plan
- Deferral program available
- $1.3MM Hack Reactor Scholarship Fund - visit www.hackreactor.com/scholarships to apply!
- Minimum Skill Level
- Computer science and programming background required
- Placement Test
- Prep Work
- Approximately 30 hours
In PersonFull Time
In PersonFull Time
In PersonFull Time
In PersonFull Time
Hack Reactor Reviews
138 reviews sorted by:
- Only Applicants, Students, and Graduates are permitted to leave reviews on Course Report.
- Post clear, valuable, and honest information that will be useful and informative to future coding bootcampers. Think about what your bootcamp excelled at and what might have been better.
- Be nice to others; don't attack others.
- Use good grammar and check your spelling.
- Don't post reviews on behalf of other students or impersonate any person, or falsely state or otherwise misrepresent your affiliation with a person or entity.
- Don't spam or post fake reviews intended to boost or lower ratings.
- Don't post or link to content that is sexually explicit.
- Don't post or link to content that is abusive or hateful or threatens or harasses others.
- Please do not submit duplicate or multiple reviews. These will be deleted. Email moderators to revise a review or click the link in the email you receive when submitting a review.
- Please note that we reserve the right to review and remove commentary that violates our policies.
My experience at Hack Reactor was fun, informative, hectic, engaging, depressing, rewarding, and a range of even more emotions. The 3 months 11 hour a day, 6 day a week immersive was everything I could've asked for and more. I wanted a program that would challenge me and it did that every step of the way. On top of that probably the best part of the experience was having a friendly and engaging community that was struggling at the same steps that I was.
Probably the most rewarding part of the experience was bouncing ideas off other students. I not only learned through my own progression but learn through other students progression as well. During the program, there wasn't an hour where I didn't learn something new by communicating with other engineers. And I think that's the great power of Hack Reactor. There are a wealth of technically strong and extremely helping engineers always around you. You still have to put in the work but it helps the motivation to be able to talk with other people around you with the same pain points as you and figuring out the solution together.
The program isn't for everybody, it's rigorous, technically challenging, and you have to work well with people. But I am forever grateful for my entire time at the program and wouldn't change my process of the program in a single way.
I came into Hack Reactor with no real professional software engineering experience. I came out in 1.5 months with a full-time position and a great salary.
I attended the Remote course and it was the most challenging few months of my life. In order to get the most out of this course you will have to set your comfort to the side. With that said, three months is a pretty short investment for the payoff.
Expect to be humbled in a big way. You probably won't be the most techincally apt person in the course and that's a good thing. You will be pushed and challenged more and get more value from the course if you have to struggle to stay afloat a bit.
I also weighed doing the on-site program with doing the remote program. For me, I had a set-up that worked well for the remote program. The only thing tough about the remote program is that it can be isolating if you don't make an effort to interact with your classmates. In that way, I think it could be even more challenging than the on-site program at times.
Like I said before, this course is extremely intense. For most Hack Reactor graduates, their job after will be much less demanding than the course itself. Understand this going in and you can set yourself up for great things in a short amount of time. Good luck!
Hack Reactor is a daunting undertaking, to say the least. My experience was probably similar to many people out there - the novice programmer, the excitement of building and creating slowly budding in my chest as I explored the surface of programming, growing more enthralled with each new step I took into this marvelous new land until I finally decided to make that dreaded 66/hr a week/3 month plunge. It was exciting, but utterly terrifying, and I had no idea whether I was really going to be able to do it or not.
I've been out of Hack Reactor for 8 months (wow, that's a lot longer than I thought!) at the time of writing this review, and I can honestly say it was the best decision I have ever made. I am happily working in my preferred field, with my preferred techs, and I'm loving every minute of it. And I wouldn't have been able to do it without Hack Reactor.
Now, the school is not exactly what some might think. Those 3 months are not about cramming as many technologies into your head as they can manage, though they certainly do that. It's not about teaching the fundamentals of programming, or design, or data structures. It's about making you a good programmer.
Well, what the heck does that mean, right? Isn't a good programmer someone who knows the technologies?
Oh, it's so much more than that. What Hack Reactor does, better than any other school I've seen, is teach you to learn on the fly. This isn't some Business degree, where you learn the tools you're going to need for the rest of your career, and the rest is up to your own ingenuity. No. Programming is constantly changing, remolding itself, producing new tools and technologies that you need to learn at lightning speed. Just the other day I was handed a project to work on using a technology I had never touched before. And I knew I could do it.
Hack Reactor gave me confidence in my ability to grow and expand in whatever role I was given. Their teaching methods are rough, to be sure. This is not a school that you can float through on minimal effort. And you're not going to be spending just 66 hours a week on this, to be sure - not if you're going to truly experience the course. But that forced work ethic, the speed of the course, the amount of work that is asked of you - it drowns you in the material you're being taught. And if you're really trying, then it's impossible to not absorb it.
You have to be willing to put in the time and effort. You cannot expect the school to do everything for you, though they do everything they can to make sure you have no choice but to immerse yourself. If the idea of spending every waking moment on coding and learning and problem solving is tiring to you, if you cannot stand to be separate from your family for extended periods of time, if you cannot miss your weekly double movie nights out with your friends - then this is not the course for you.
If you are willing to put forth that effort, then you will be rewarded with the staff's unyielding patience and support. Every step of the way, I had support from numerous staff members, who were always there to offer help when I asked for it, and truly seemed to care about my success in the course.
Now there is a fair chance that I was simply lucky in the staff that I got. Every person is different, and it's entirely possible that some of the staff is not up to the standards that I experienced. But I can only write this review based off of what I went through, and the people I was lucky enough to be involed with.
As for other pluses of the school, the community was incredible. You will know everyone in your cohort by week 6, and many of these friendships can stay far beyond. I've made several very close friendships from my cohort, and I know that I can turn to them anytime I need them. Many of us work with fellow grads, with companies that were impressed after hiring their first Hack Reactor student and who decided to keep hiring. The staff does a great job of building a fun culture, with regular events to help ease the stress of the workload.
I would also say that the technologies they teach are fantastic choices for making any student an enticing job candidate. My company was ecstatic at my React knowledge, compounded with the other techs I had to back up my strength there. They know that if they have a problem anywhere in the stack, there's a good chance I could help them with it.
Above all, they gave me an experience that translated well into my new job. It wasn't like back in college, where I came out of my biology studies with no idea what my work would actually look like. Every thing they do is catered to the kind of pattern you'll be following in your everyday life in your new career, and though the job search, and starting a new job, are still daunting, it was incredibly easy to settle into my new role.
This may have come off as an overlong love poem to the school, but I honestly believe I could not have gotten where I am now without Hack Reactor. The support was incredible, and extends to this day. And I know if I need them, they'll still be there to help me. Not because their obligated to, but because they care.
So take this for what it's worth. If you're willing to stick with it, if you're willing to throw your all into this program, it can change your life.
I recently graduated from Hack Reactor Remote. I will say, I didn’t expect to learn so much through the process. If I had known, I would have made the jump instead of letting life situations somewhat force me into it.
I was an Applied Math major at UC Berkeley, but ended up going down a more business oriented route. I got into online and mobiles games at an early stage and was able to progress pretty decently in my career through that. Still, I always had a passion for building things and if a few things had gone a bit differently would probably have ended up being an engineer down a different path.
Unfortunately that didn’t happen, but I kept wanting to make the switch. Of course I gave myself the same excuses; switching careers is a pretty big risk, I’m too old (mid 30’s), etc.
Fast forward many years, many things happen but I find myself in a position where I’m considering some bootcamps. After a lot of research, I narrowed down my choices to App Academy and Hack Reactor.
Why Hack Reactor
I got accepted to both App Academy and Hack Reactor Remote (didn’t actually finish the application to Hack Reactor onsite because of scheduling). Ultimately I chose Hack Reactor Remote for two reasons (keep in mind this is before starting the program). (1) It was remote and (2) six days a week.
I was initially concerned that I wouldn’t feel as connected with my cohort mates because it was remote, but Hack Reactor does a great job of providing an awesome space to build connections and friendships with others you’re learning with. Also for me personally I’m super open to moving away from the SF Bay Area in the future, so it’s nice to have built relationships with people in other regions.
On top of that, by being remote I saved a good 2 hours a day on commuting. Now, if you are moving to a new city to go do a bootcamp, this probably isn’t a concern for you but it was a realistic concern for me.
When I first heard that Hack Reactor was 6 days a week, I was honestly kind of turned off. As I thought more about it though, If I’m paying for this opportunity (and you are paying even with bootcamps that take a percentage later on), I best get the most out of it. The entire course is only 12 weeks long to begin with, that extra day per week does come in handy.
Material & Learning
Hack Reactor doesn’t just teach you how to code, but they teach you how to become a Software Engineer others want to hire and work with. With that, they teach how you mindsets and mentality needed to grow as a Software Engineer for now just your first job afterwards, but second, third, etc.
Hands down, you are going to learn so much.
This isn’t for everyone. Getting in itself a pretty decent challenge. Unless you already have a good backround, be prepared to put in work just to get in. Once you’re in, it continues to get hard. I’ve been in long hour, high stress work situations but nothing really compared to the mental challenge this program was. The plus side is when you come out of it, you know you can take anything on.
It isn’t for everyone. The only promise is you will get out of this what you put in. If you are not willing to put in the work before, during, AND after the program, it may not be for you. However if you are serious about moving into or leveling up your Software Engineering game then there is no better place.
Like you, I was extremely skeptical of attending a programming bootcamp. The thought of it just seemed way to good to be true, there had to be a catch, and there is one. The catch is hard work. The only way to achieve success at a bootcamp is the same way you achieve success anywhere else: putting in 100% effort and persevering. I was unsure of the remote experience and whether I would like the structure of the class or not, so I attended the remote prep program. The prep course was worth the money and gave me a great preview of what the Hack Reactor environment felt like and I loved it. I wasn't sure if the full program would be worth the money (spoiler alert it TOTALLY was) or that it would really be enough education to get me a job with zero experience. I read dozens of reviews from alumni saying that Hack Reactor was the best choice they ever made. Finally, I decided to go for it, got accepted, and never looked back.
I got an amazing job, thanks to the skills I picked up during my time at Hack Reactor. Some of these non-technical skills include writing a resume, how to ace job interviews, and tips on how to be effecting during the job search. I was able to get an amazing job, that I still love, at a very reputable company. Hack Reactor prepared me extremely well for the path that lay ahead after I left the program. I still tell everyone I meet how much I love Hack Reactor and what a great experience it was. The education that Hack Reactor provides is so impressive and it was doubly as apparent once I was on the job able to keep up with experienced engineers.
All of the team members and management I interact with at my current job are honestly quite amazed at the efficacy of the program and the amount I was able to learn in 3 months.
Hack Reactor is by and far an amazing overall experience, and I would go back and do it all over again if I could.
I was part of the Hack Reactor NYC campus cohort #5 (HRNYC5) that finished in March 2017. I think most people who will read this review are considering a career change on some level. I was in your shoes about a year ago. Whatever brought you to the point in life where you are looking at leaving your safe but unsatisfactory current circumstances and spending a LOT of money and time on an entirely new adventure. I have one thing to say to you. DO IT!
Before I left for NYC, I decided to apply to Hack Reactor for a throw-away practice application. I did, as expected, fail. Quite well, actually. But I was completely impressed with the HiR who handled my interview, and with his willingness to spend time with me, teach me, and encourage me even though I was so clearly not ready for a Hack Reactor bootcamp experience. While in NYC, I decided to take a second look and took a few tours at the then MakerSquare(made the name change to Hack Reactor around October 2016) campus. I also asked to sit in on a lecture and they said that was okay too. I tried that at FullStack and was told no I would disrupt the class.
The story was only beginning there. Hack Reactor is constantly working to improve their curriculum and nurture new learners, so they invited me to participate in multiple pilot programs. I was offered 4 weeks worth of mentoring sessions with an HiR, and also got the chance to participate in 2 phases of Intensive study groups that became the current remote prep program they now offer partially for free. All of this was at no cost to me, and gave me the opportunity to interact with many different people in different capacities. Never. One. Negative. Experience.
So it took some extra work and a little extra time, but I eventually found myself accepted to Hack Reactor NYC and started in December 2016.
The team at the NYC campus is fantastic. From Jeff the counselor, whose job it is to keep you from losing your mind while you work through the hardest 3 months of your life, to Joseph the supersmart primary instructor for the first half and John, the king of Tech Mentoring and then all the different HiRs along the way, every single person is helpful, willing to teach, supportive, and has your best interest at the heart of their decisions.
You don't spend 66+ hrs per week for 3 months with people without some drama and conflict along the way, but that turns into this crazy side benefit of the experience. You are working to change your life around entirely and along the way you make a group of friends who shared this intensity with you.
The Hack Reactor experience does not stop on graduation day. There is a very well-built out curriculum and program for supporting you throughout the job search. I have found the Outcomes Team to be every bit as concerned for me and what is best for me as everyone else. There are cynics out there who will not believe me and won't trust that HR's #1 motivation is the individual student, but I have zero evidence to the contrary.
I have a new career as a software developer! I will be starting my first full-time job in the next week or two, about 6 weeks after leaving the program. If you are thinking about it, look very hard at HRNYC and trust that these folks are the real deal.
Let’s begin by getting the dirty details out of the way to relieve some curiosity. I’m going to attempt to give those who are looking for an honest and insightful review a full understanding of my perspective, so they can possibly make an informed decision about their future. I’d first like to present some facts about me, since it seems to be relevant for the sake of context when reviewing the opinions, perspective, and respective nature of those providing reviews provided here or anywhere for that matter. My name is Richard Boothe, I attended Hack Reactor in Austin during the cohort of 2016 that went from February to May. During my time as a student I decided that I’d like to be a Technical Fellow/Hacker in Residence, and thus went on to do so at the New York campus from June to September of the same year. After my time at Hack Reactor it took me 5 weeks to find a job in web development, my salary is above the average of Hack Reactor graduates.
As of the writing of this review, I am working for both Ksquare Solutions Inc. and also the Boy Scouts of America in Irving,TX as a Senior UI Developer/Software Engineering Contractor respectively. I am 33 years old and before attending Hack Reactor was a bartender/bar manager for 10 years. Hopefully that’s enough info for you to find me on LinkedIn if you’d like to ask questions or just want to absolutely know I’m not a fake person like a majority of the anonymous one-star reviews seem to suggest.
My experience in regard to software and web development prior to Hack Reactor was limited entirely to Team Treehouse, Code Academy and Coderbyte. I had discovered that I really enjoyed the algorithmic nature of solving problems and was tired of my career behind the bar, so I began researching bootcamps and university options two years prior to my time as a student. The majority of programs at that time were advertising a 0-60 acceleration in learning, meaning having an absolutely zero amount of knowledge in the field of web development to knowing enough to get a junior level job. Meanwhile Hack Reactor advertised an education that would accelerate future web developers with a 20-120 acceleration, leaving their graduates at a mid to senior level upon entering job search. Furthermore, at the time none of these programs offered outcomes assistance besides Hack Reactor, which was a selling point for me for the obvious reason of avoiding retreating back to the bar scene after investing the admitted high cost of a bootcamp like program. I decided completely against the idea of investing in a University program upon realizing it would cost me a minimum of $80,000.
I decided on Hack Reactor for a seven reasons.
- First, I looked at the reviews on sites like Course Report and Google just as you are today.
- Secondly, I appreciated the honesty that was provided in regard to the level of understanding in coding/analytical thinking that was necessary to attend and succeed at their program, I will address this further later.
- Fourth, their is an emphasis on acquiring soft skills and learning to pair program. This skill has provided me with an enriched ability to communicate in an amicable and concise manner with my peers at work that has absolutely helped me advance quickly in my career.
- Fifth, the continued enrichment of the program keeps the topics fresh. I’ve read a few of these reviews that speak about how some of the instructional videos are old. Yet the concepts and the technology hasn’t changed in the last two years, at all. I'll discuss ES6 momentarily.
- Sixth, Hack Reactor enforces the basics first. This is the entire reason for the first six weeks.
- Seven and most importantly, Hack Reactor provides a community feel that inspires a drive to learn. This was crucial to my success during times when I felt overwhelmed or frustrated with my progress.
As a prospective student, an actual student, and later a Hacker In Residence, I never felt that any of those reasons were abandoned or less than what was originally presented.
Hack Reactor is *NOT* a bootcamp for students looking for an easy ride into a six-figure job, it never has been. Furthermore, it is not a program that one can easily jump into without prior experience and exit with a maximum gain. For this reason I warn anyone attempting to game the admissions program that you are doing yourself a huge disservice. If you review some of the poor reviews, you will notice a trend that most of those students providing 1 star reviews had failed the admissions program several times, or had ‘memorized the admissions requirements’ rather than take the time to learn the concepts that are recommended for admittance.
It took me a year to get to a point where I felt confident enough to take the admissions interview, and that was after performing self-study with the concepts of conditional statements, scope, closures and higher-order functions. For those that gamed the system and feel cheated, I feel sympathy for you but also wonder what you expected when time and again the expectations presented before admittance and during the cohort were that you needed to have a fundamental understanding to succeed. The reason Hack Reactor focuses so heavily on fundamentals to reinforce the understanding that students should already have is to insure that more advanced topics like frameworks, API creation and consumption, data manipulation, and database structures can be taught. FYI, the admissions system has been changed to avoid unknowingly allowing students into the program that are not yet ready. So while learning the concepts of higher order functions such as each/map/filter/reduce is great and will help you be a better developer, memorizing how to type those functions out without knowing the reason for the code will probably be a waste of time.
My thoughts on the program overall are great obviously, I rated everything five stars across the board for a reason right? The instructor Gilbert answered any and all questions I ever had about the content of the curriculum, and always did so humbly and with patience. My Technical Mentors/Hackers In Residence were always willing to help me reason about toy problems, or help me find break-throughs in my understanding. Of course there is the chance that I got lucky with a great group of folks as mentors and instructors, but given the nature of the Hack Reactor program, and my experiences at two separate campuses, I highly doubt it. Linden, my wonderful and amazing counselor was a godsend at times I felt overwhelmed and disheartened about my self-confidence in regard to my own progress. The support of a student counselor is one that is not mentioned very often in regard to the reviews on Hack Reactor and it should be, this role is crucial to the students having an ear to speak to and a voice to listen to. Shout out to Jeff in NYC for being equally amazing!
During my time as a student I decided I wanted to be a Hacker In Residence as I have always enjoyed teaching, and also wanted to enrich my understanding of more advanced concepts in web development. This decision, which frustratingly, insultingly, and inaccurately has been posted in prior reviews was not due to a lack of ability to acquire gainful employment, but rather a desire to teach and further my understanding in advanced topics related to web development. The Hacker in Residence program is something that students apply for during their time as students, not during their job search or after they "decide they can’t get a job". If you are reading this and decide to attend Hack Reactor, I highly encourage you to apply for this position as it is incredibly rewarding on so many levels, I’ll spare the details as that’s a different topic all together.
Lastly, the community that I still engage with today is one that continues to grow and flourish as I carry on with coding and my career. I am extremely grateful and proud of the accomplishments I have achieved because I am aware of how difficult the task was, and is. And with that I’d like you to keep that in mind when making an investment in Hack Reactor, as with any life changing decision for yourself. Most things worth doing of any magnitude are not simple, or easy, or quick. Don’t try to cheat the experience. If you really want to invest in something, attack the goal with a hundred percent. Please reach out to me if you’d like, and thanks for reading the novel ;)
I've now been employed as a Software Engineer for 1 month, and things are going better than expected...
A couple of months later after having been rejected previously for the Hack Reactor Immersive, I managed to get in with tons of codewars practice. It was a hard interview to pass but getting rejected/failing the first time helped me mentally prepare for success. Hack Reactor is big on this ideology.
On the second half of the program, theres a big focus on the job market and how to take software engineering interviews. The support is excellent and you get lots of practice. You also get support from a whole team dedicated to the job search after the program.
The atmosphere is great. The staff does a great job at trying to maintain a certain vibe which revolves around positivity. Because of the nature of having to constantly pair program, I was able to adapt better soft skills and communication.
Overall, if you're truly commited into changing your life 180 degrees be a software engineer, this course is for you. It helps to come in with empathy and an open mind. The cirricculum updates often as does the industry, and Hack Reactor does a great job and keeping up to date with industry standards.
I enrolled in the program looking for help in three areas, and Hack Reactor delivered.
Skill: the course teaches you through practice rather than memorization. The are lectures were mediocre, but I spent most of the time on code challenges and projects, which is where the real value lies. For the first half of the program, we completed a series of two-day "sprints" in which we finished incomplete programs until they passed all the tests. For the second part of the program, we built on a series of projects from the ground up. Throughout the program, we worked on a toy problem for about an hour every morning. In total, I spent over 450 hours coding.
Teamwork: During the first half of the program, I worked in pairs to solve programming challenges, which was exhausting but good practice for communication. During the last half of the program I worked on group projects, but these didn't feel like horrible group projects in school. Instead of working for a grade, we were just trying to learn and get stuff done. The group projects felt a lot like working in a real company.
Job Search: There's only one week at the end of the program for career coaching, but that we plenty. Even after 50+ rejected job applications, I wasn't discouraged because the outcomes team did a great job of setting expectations for how job searches usually work. I also couldn't have written my cover letter and resume without their help.
At Hack Reactor, I developed the skill and confidence I needed to find a job. A month an half after graduation, I accepted an offer and start working next Monday!
Huge Commitment: This program isn't a good fit for everyone. It costs ~$18,000 plus living expenses and consumes 60+ hours a week. I had to drop everything for 3 months. This worked out great for me because I have good credit and don't have children or a social life, but it's a lot more stressful for people in different circumstances.
Attendance: Their attendence policy is extremely annoying. You don't want to be late. Plan to arrive at least 30 minutes early every morning to account for traffic, parking, and exploding bicycle tires.
I've read my fair share of controversial opinions about Hack Reactor before joining. Having been through the ringer, I've come out firmly believing that the school has its priorities straight. I've spoken with staff at all levels, from the CEO to hackers in residence (temporary positions filled by recent graduates), and I have found the staff to be focused on their students' success and very far from the cynical, short term, take-the-money-and-run type of mentality that is sometimes associated with bootcamps at large.
The bottom line is that Hack Reactor delivered on its promise to help me transition to a software engineering career. Making this transition is difficult and requires enormous effort. Hack Reactor does not substitute for that effort, but it fosters an environment where students can put out their best work for a sustained period. Hack Reactor builds a community of like-minded risk-takers 100% focused on learning and changing their lives, and I can say with certainty that I would never have achieved this change so quickly if it weren't for Hack Reactor.
In terms of downsides, I found the sheer size of their larger campuses intimidating. These campuses are abuzz with energy. It's a regimented learning environment that results from the pressures of graduate output and a high bar in terms of desired skill sets. It's an intense environments to be in, day in day out, and might feel alienating to some.
It's important to realize that learning is only half the battle. While Hack Reactor provides some structure and support for the job search in the form of a career coach and advice building a resume / cover letter / online profile / set of job seeking tactics, the period after graduating is critical to a successful transition. Hack Reactor will not provide a job on a silver platter. That's just not where the job market is at right now. Prolonging the structure of Hack Reactor into your personal life after graduating and before starting a job is key to success.
At the end of the day, I was able to transition careers with an $18,500 investment and 9 months of my time (including 3+ at Hack Reactor). No college I know of can provide that. The value is hard to beat. If you're driven by making this change, Hack Reactor is a great launchpad to guide your efforts.
Hack Reactor is a unique educational opportunity. The intensity, cutting edge curriculum, and inspired staff made for an utterly transformative experience.
Hack Reactor have gone out of their way to discover exactly what it takes to take on the big bad world of Software Engineering. The team and curriculum department are clearly in-to-win-it and they only accept those with a similar spirit. They come from tech start-up culture and are guided by Silicon Valley tech talent. The education is non-stop, right down to their Outcomes program. I was caught off gaurd to know that beyond the code there is still more to know! Like, the real world concerns for Software Engineers while navigating the industry. It just goes to show, there's always so much to learn, and Hack Reactor never lets you forget that.
On a personal level, I am deeply moved by their mission: to create opportunities. I had no idea that an organization could be so dedicated to transforming individuals one person at a time. The staff is genuinely motivated by the reward of seeing the success of their students. What they do, what the students do is not easy, and that itself is the draw of the program.
I encourage anyone to discover the unique work at Hack Reactor. The investment is large and should be recommended on an individual basis, BUT do yourself a favor and inquire as to what's going on within the Hack Reactor walls. It is not typical by any standard, and I hope to see their model infect other fields. It's people-driven, and that's a sum-total win for everybody. Check out the Prep program. You will skill-up, but more importantly, you'll get a peek into what possible adventure could await you. Or better yet, ask around, because their community is growing, and I'm thrilled to be a part of it.
Oh, yeah -- and the tech stack is off the hook.
I attended Hack Reactor Remote from January to April 2016. I was a Hacker-in-Residence immediately following the program for three months. My experience with the remote program was different than those in my cohort. I participated in a pilot program, Remote Community, in Chicago. I attended classes with another student. I had the opportunity to speak with the other student, Mobile Maker students and instructors, and one of the founders of Hack Reactor. The founder helped immensely during the first six weeks.
Hack Reactor presents daily challenges. There is little to no hand holding. Prior to getting accepted to the program, I interviewed three times. Each time, I progressed a bit further than the previous attempt. After the interviews, I was given a list of concepts to study for the next time, but no example problems to test my knowledge against. It was my responsibility to keep improving and discover the gaps in my knowledge before trying again. The focus of the program is develop an engineer’s ability to be self-directed, autonomous, and unafraid to ask for help. These skills take time to learn and master. Throughout the 12 weeks, there are many opportunities to put these skills into practice during pair programming, toy problems and larger project work.
The instructional format was good for my learning style. I had tried watching videos with little success and retention. Combining video learning with “face-to-face” question and answer sessions helped solidify my understanding. I also benefited from having peers, of differing skills and backgrounds, going through the same challenges. We created a learning group to review content, which allowed us to share what we learned. Again, the focus is to develop an engineer’s ability to be self-directed and autonomous. You will truly get out what you put in. You must be willing to work with others, participate in knowledge transfers (in both the senior and junior roles) and ask for help when you need it.
Now, a year later, I am in a new city working in a brand new space. In my current role, I am working with Angular 2 and TypeScript. I believe that the instructional sprints helped me to get up to speed on working with two brand new technologies. Using a mix of tutorials, blogs, documentation, and videos, I was able to quickly learn the skills needed to contribute quickly. I have since become confident in providing input and taking responsibility for larger features. The autonomy I learned through the program prepared me to jump into a problem without feeling like I needed a senior dev to monitor my progress.
I highly recommend Hack Reactor. I do admit that it's not for everyone. The pressure is very high and the course load is heavy. However, if you are the kind of person who's really good at figuring things out on your own with the right resources, and will relentlessly work to keep yourself afloat, then this program is the right one for you. Make sure to be pro-active. Hack Reactor goes above and beyond with providing you with relevant material and successful ways to incorporate all of that knowledge into your toolbelt. They not only teach you a good broad range of knowledge for software engineering, but they also teach you how to absorb that material and apply it immediately.
Another spot that I think HR really shines is the outcomes program. After you graduate, they give you counselors, referrals, and general help to get you that job. The job hunt can be brutal, but it's nice that they at least don't send you out into that hunt without any tools.
I graduated in September from the Hack Reactor Remote program. Since then I’ve been an HiR doing personal tech coaching and interviews, and I recently accepted a fantastic offer from a really cool company.
I really can’t recommend HR enough. What really stood out to me early and often was the amount and quality of the career education and support. I attended a reasonably good 4-year public university and never received anything near the quality or quantity of fantastic career support as I have at Hack Reactor. Even early in the course, there are lectures going over the qualities that make a successful software engineer, what to expect, how to navigate the job market, how to market yourself, etc. Then, once you’ve graduated you’ll receive amazing continued job support. When I got my offer, I took it to my fantastic career coach and she helped me with the negotiation process. Negotiating is really hard for me, but she coached me through it, helping me script questions and responses so that my nerves wouldn’t overtake me during the negotiation. We did mock negotiations with role-playing so I could get used to phrasing the sentences correctly. Ultimately I negotiated an already great offer up a bit, and I was happy to accept at that point. I cannot put into words how valuable this is, what’s the good of learning the skills if you can’t get past the application process? Hack Reactor gets people’s butts in jobs, and that’s partly due to the fantastic career coaching and outcomes team who help you put the cherry on top.
They’ll also help you A LOT with resume writing. That’s also the bane of my existence, but with their coaching and help I produced a fantastic resume that got me in to a phone screen easily with several companies. I didn’t even need to attend the last week of the program (since I got a job :D) that goes really intensely over writing cover letters, resume review, job application support and white boarding practice.
Ok, aside from the job stuff, the quality of the course is amazing. You’re working on functioning code bases, mostly to add new features or implement required ones. You’re building web apps from day 1 (Ok, maybe not until day 7 when the sprints start). You are really plunged into the deep end from day one and forced to swim. Be warned: you must be an autonomous person who is goal oriented to take this course. Yes, there is guidance and structure, but it’s ultimately up to you to get what you need done to succeed in the course. There will invariably be extra work you need to do outside of class in order to keep up since it is so fast-paced.
I found the sprints challenging, but not overly-so. I found week 4 to be particularly challenging, and really doubted my skills, but the counseling and tech mentors helped me get where I needed to be. It seems crazy that 12 weeks is enough to get people all the skills they need to succeed, but I found that it was more than sufficient to get me into a job. I was even a bit over-prepared. I barely sent out applications; I applied for one, and was asked to interview for a second that I met at a job fair who had seen my resume. I received an offer from both, and ultimately went with the first one that I had applied to. I’m still completely astounded at how easy, painless and quick the job search was, but that’s because I was impeccably prepared and supported throughout (mix some dumb luck in there too). Granted, the jobs I applied for were both to startups, who value more practical skills to get you in the door. I didn’t have to do any white boarding or algorithm problems, just really practical stuff that I found (frankly) really easy.
By and large, your classmates will be fantastic. Hack Reactor goes to great lengths to make sure it admits people who are not only intellectually capable of the rigorous pace and difficult concepts, but those who will be enjoyable to collaborate with. I had so many helpful classmates that made a huge impact on my success in the course.
I would recommend that if you take the course, you set up after-hours study groups early and often. They were instrumental in helping me understand the material.
I’m a female in tech which isn’t always easy, but the support I received from Hack Reactor makes that much easier. I’ll be the first female engineer at my new job. If you’re wondering if you’ll be a good fit for Hack Reactor specifically because you’re a woman/unconfident about your skills or your ability, don’t worry. If you can get into Hack Reactor and get past the pre-course work, you’ve got what it takes to succeed in the program and on the job. You might be judged by dumb guys from time to time, but that just helps you build up a thick skin. For the most part everyone has been great.
This course is HARD and it will kick your ass. But (at least in my case) you might go from zero coding knowledge, to teaching yourself coding, to Hack Reactor, to an amazing job in less than a year. I can confidently say it was the absolute best decision I have ever made in my life, as well as the hardest thing I have ever done. I am incredibly grateful not only to the founders for starting the school, but to all the tech mentors, counselors, coordinators and cohort mates who put in so much hard work and care to make the program amazing.
If you have any questions, feel free to leave a comment and I’ll do my best to respond.
Unbeatable job support, insane value for the money, challenging but doable sprints, awesome cohort mates, fantastic tech and morale support/mentoring, insane outcomes (yes, those numbers are accurate). The most difficult thing I have ever done, and the best decision I have ever made. DOOO IIIT! IT WORKS! Regarding a few negative reviews I have read... really? 98% employment after 6 months is not impressive? Do you have any idea what the rate is for a 4 year college? I went to college and NEVER got a job in what I studied, let alone 6 months later.
And yes, there's a lot of self-teaching during the program -- they're trying not to set you up to need your hand held through every bit of code you have to work with. I've been working as professional frontend engineer for 6 months now, and I can say that the real world is very similar to how life feels at hack reactor -- you're thrown into an unfamiliar situation, without any expertise about the code, and you need to figure out how to find your way out of the problem. I'm grateful that they didn't hold my hand through the course-- it would have been a rude awakening to move into the job and suddenly have little support and no skills to figure things out by myself.
I went through the Hack Reactor Remote program last fall and it was by far the best educational experience I have ever had. It was a rigorous 12 weeks and took a good deal of preparation leading up to it but overall it was definitely worth it. Everyone I went through the program with along with all of the instructors and staff members went above and beyond to make the program the best that it could be. The job support team upon graduating was amazing as well and provided excellent resources to guide me through the job search. I was able to get an awesome job as a Full Stack Software Engineer within 4 weeks of graduating and I love what I do.
If you are willing to put in the work and love code, Hack Reactor is definitely worth the investment!
Hack Reactor is a results-driven curriculum, so I'm here to tell you if and how you can get the results you want. If you work your ass off and you have a decent education/resume, you shouldn't have too much of a problem getting your desired returns from Hack Reactor. I was formerly an attorney that was very frustrated with the legal market, so I pivoted to software and HR had the best reputation. It wasn't easy to get admitted, but if you get admitted to the San Francisco main campus, I'd definitely recommend going. It is important to keep in mind that it seems like the bubble for developers is growing, and it's not entirely certain whether there will be further forseeable growth in the market (although now that it's harder to get work visas, it might help). It's not a sure thing, I think a couple of people in my cohort had a tougher time finding a job, but most everyone found one. The curriculum is great, but it relies all on you to power your engine through it. No one is going to hold your hand through the learning process; be prepared to teach yourself. The BIGGEST asset that hack reactor has is that you will be surrounded by very driven, talented, and friendly individuals. My cohort (HR39) worked together and left no man behind, and we are very close even after the experience is over. If I could do it over again, I would do the exact same thing. After working about 75 hours a week at Hack Reactor, I received an offer for $120k base in San Jose in under a month. Again, it takes hard work though to achieve your dreams. I sent out almost 200 applications in the single month using angellist, hired, linkedin, ziprecruiter and application portals on websites. If you are smart, driven, and feel that you are being underutilized at your current job, I would highly recommend Hack Reactor. Be aware though that nothing is guaranteed no matter how gaudy the numbers were. Everyone works very hard to make it so, and the students, staff and Space Ops crew is amazing (despite underpaid). A handful of students seemed to have problems finding jobs. Most of them didn't apply to enough in my opinion, as it's a numbers game (i did 200 apps in a month and so can you). A handful, despite being good programmers, had pretty weak professional or academic resumes though, and seemed to find the market harder to break into. If you're talented, hard working, and having somewhat of a proven track record as a good human being, Hack Reactor is a vehicle that can help you successfully transition into web development.
In this age of refined open source and cost effective online materials you dont need Hack Reactor to teach you how to code.
Anyways the best way to learn is by using it in a project. Like you will best learn how to cook is by making your favorite dish and in the process you will google recipes, ingredients, best practice and then you will start putting them in place to make your super uber dish. First time it will not be great but will give you a base to improve upon until you get it right.
Apply the principles above to learning to code and make a portfolio of projects (not just tutorials but something actually most you have done yourself)
It will greatly enhance your experience if you find a friend or meetup to code along.
Boom, a couple of months of incremental progress leads to a solid skill you can take to your new job.
Hack Reactor is just a streamlined path of doing the above, and in no means a right of passage or even the best/right way of becoming a successful engineer. (I chuckle when they say Software Engineer. Even CS degree majors do not qualify as Engineers) but that is what you will want to become I am guessing in going to HR.
If this was 10-12 thousand dollars, it would have been worth it, probabily. 18-20 grand, common. Maybe 4 years ago when the best you could get online was a bunch of scrappy blogs. Someone can sue them for claiming to train Software Engineers, because that implies a lot more than going to a germ infested incubator of jam packed students puffed up with false hope after learning basic stuff about data structures, algorithms, a few libraries and frameworks, half of which are old redundant stuff. In the end even they will tell you not to mention HR in an interview, the real reason I will tell you after coming out on the other end is no one gives a c rp about HR, not because there is a bias which there is but because it is just bs that HR is teaching Software Engineering and any good engineer will hire you based on your skills, NOT coz you went to HR unless they are grads.
Staff are pretty awesome, building sucks, curriculum needs major over hawl not only because of old tech but also because for the first half you are learning mindlessly ie passing tests without knowing what the technology is or how its used. A better way would be that students implement a basic app after the two day sprints indivisibly. Fellow students are possibly the best thing about HR.
Seriously find friends who are doing the same thing and go through one of the online courses like the nano degree at udacity for 150 bucks or so is pretty good place, codeacadmy is a good place to start learning languages, freeBootCamp is a good one. Pick one, finish it. Boom Save 18000 bucks.
As far as the 105 grand salary, most people come to HR from strong CS back ground. Quarter have CS degrees, Quarter have some other engineering or relevant degrees, 10% are Berkley or similar grads. 30+% have significant prior experience from job as a developer and 10% have little background and take significant time to build up skills and get lower income spectrum jobs. Compounding all of this gives 105 grand average which is smart on their hand, only admit people who know how to code and this is what you get.
Good people. I would say that for sure. A lot of good iterative stuff going on. 10-12 thousand is a worth it experience.
I'm going to let you all know that I was 120% skeptical about the whole coding bootcamp experience. I mean, how can anyone expect to come out of a 3 month bootcamp with enough knowledge to be a mid or senior level software engineer? And how the heck did Hack Reactor skew their numbers to get such insane statistics?
Who I am:
- Business major in college coming from reputable and decent paying account manager type jobs
- Questioned if I was good at coding because I'd never done anything remotely technical besides some math, econ, and stats
The Bread and Butter of this Review:
- The remote experience requires intense self-discipline, but the curriculum is so well structured that you will definitely feel the pressure to be present and be on top of your game.
- Software engineering and programming is all about learning to be independent and figuring out creative solutions to the problem. I kid you not, I think i spent half the time during coding on Stack Overflow or becoming a pro Googler.
- Programming is not cookie cutter - it's like a language so sometimes you can express it in ways that aren't great, but still get the job done. Therefore, you will often find that the 2 day sprints in Hack Reactor don't necessarily explain solutions exactly in the way you want it. However, they really take a lot of time to explain methodology and do walkthroughs if you are struggling.
- You have to bust your butt every day. This is a unique time period in your life if you choose to follow through with the program. It's only 90 days long. Do whatever it takes and learn the material.
I got a job before my program even ended at an awesome company doing fullstack software development (senior to midlevel) and I didn't even know how to program a year ago:
Many of cohortmates have already gotten AWESOME software engineering jobs in line with Hack Reactor's statistics. If you are remotely competent and feel like you need someone to give you guidance and help boost your career towards something you really feel passionate about - DO HACK REACTOR.
I attended Hack Reactor (at the time still MakerSquare) from April to July of 2016. I then stayed on 3 months longer as a fellow, but this review will only focus on my student experience.
At first my research focused on traditional higher education. CS master's programs, mostly. However, I had little desire to do research or otherwise re-enter academia, so the value of a traditional graduate degree did not at all warrant the cost for me. Eventually, a serendipitous browse through alternative options led me to coding bootcamps, and eventually MakerSquare which had a campus conveniently located in my hometown. My honest first reaction to their claims (and the tuition) was “yeah, right.” I binged on all reviews, good and bad, before deciding to go the self-study route. Besides, I was already a developer. What could a costly 3-month program teach me that I can’t learn for free on the internet?
Fast-forward a year to early 2016, and I had barely gotten off the ground. I had more responsibilities at my old job and had little residual willpower to learn web on my own. Sure, I convinced myself a few nights a week to put in a couple extra hours and work through online tutorials, but it was a half-assed effort at best. At that point I realized I was missing a few key factors: accountability, structure, and a collaborative environment. I finally admitted to myself I'm the kind of person who needs the pressure to thrive and learn. That’s when I decided to go for it. After all, it's exactly that kind of environment HR seemed to be good at providing. Another major selling point for me was the networking potential. In my experience the tech industry is smaller than you think, and making many new connections can prove helpful in unexpected ways.
A recurring theme you’ll notice in coding bootcamp reviews is that you get out of it what you put in. This applies to Hack Reactor even more so because of the volume of information coming your way combined with the ambitious 3 month timeline.
I soon learned that head start was marginal, because the course hits the ground running with only a few intro lectures to get you acquainted with the staff, facilities, etc. After that you jump right into alternating between lectures and partnered assignments (sprints). In fact, the entire first half consists of sprints spanning a couple days each. Again, it’s easy to hit information overload in this time - your brain can only absorb so much - but building as solid a foundation as you can prior to starting can make all the difference in how well you understand the assignments. I used the help desk sparingly, but when I did need it I found it sometimes slowed me down more. I took the route of trying to figure it out myself unless I was truly desperate. But even when you do put in a ticket, there’s a chance your fellows (who just finished undergoing the program themselves) might not know the answer either. In the end, I always managed to find an answer either from fellows or others in my cohort. This wasn’t the case for everyone, though, and a common complaint is that fellows aren’t as knowledgeable as trained instructors. I didn’t share this frustration, because having a background in development has taught me that’s how the industry really is. You’ll sometimes get feedback on what to do, but it’s mostly up to you to figure out how. Overall, HR specializes in fostering this kind of “struggling" environment, and not necessarily one where answers are readily and conveniently available the moment you get stuck. As a result I learned how to form better questions to ask and where to find certain information, both essential skills in any highly technical position.
The second half of the course revolved entirely around group projects. What app to build was entirely up to us. HR did the grouping for us in an attempt to keep skills/proficiencies balanced across teams. It’s during this time I held the most grievances as a student, but mostly due to group/people dynamics which is largely out of HR's control. The silver lining is that learning to work with difficult people is in itself a valuable skill. Another grievance was that there was less structure/accountability in this half of the course. How much you can accomplish largely depends on how motivated/focused your group is, which can also stem from how exciting of a project you choose. As for choice of project, it was entirely up to us. It ended up working out for my groups, but I felt a little too much time was spent picking and scoping a project so that it was achievable in the given time. I wished they'd offered a list to choose from for groups who didn't necessarily have an idea off the bat. Finally, once we did choose a project, I felt there was little staff/instructor interaction. This wouldnt have been a problem except that I had to constantly split my time between project management and programming when I would have preferred to just do the latter.
The reason I didn’t dock any stars is the fact that the HR curriculum is not set in stone. It’s constantly evolving and adjusting based on student feedback, and it’s one of the reasons I admire the program so much. In the time I stayed on as a fellow, I personally saw all my grievances addressed along with any new ones raised by subsequent classes. Instructors (and even staff) began taking more of the project management role, freeing up the students to just code. Also, they began to provide a pre-defined list of projects for groups who didn't want to come up with their own. Regardless, I still came out of the second half having built complex apps from front to back that I could show off to employers and even study before coding interviews. In fact, it’s the proficiencies I gained working with the frameworks for those projects that helped me get hired quickly. So all in all, the group work was well worth it and a crucial part of the curriculum despite the few shortcomings.
Finally, I'd to mention the HR staff. Opinions vary wildly but in the end, I came out of the course feeling like every single person on staff would go miles out of their way to help me out, whether it be the instructors, administration, fellows or hiring team. I could tell they cared and believed in the program, so much so that they'd do their absolute best to ensure you get your money’s worth. But again, much of the work and learning is up to you in the end, and that can affect your perception. When I had grievances about the group projects, the administration took detailed notes and refined the structure for the next cohort. When I had difficult technical questions, the fellows would spend as much time as they could spare sharing what they knew, even if they didn’t have an answer on hand. When I needed general career advice, even the instructors would set up a 1v1 with me and spend hours of their time sharing their own experiences and suggestions. Then of course there’s hiring. I expected that making such a drastic career shift would mean I’d have to start over as a junior software engineer. Instead, I ended up being able to translate most of my experience from the hardware world with just a bit of careful wording on my resume. I was able to land an ideal position at my #1 choice within a couple of weeks of entering the job search. Some of that success was due to a lucky connection, and some due to the extended depth I gained from staying on 3 more months as a fellow. Regardless, the hiring team was in lockstep with me throughout each step of the interview process, helping me review what went well, what to communicate, and even how to negotiate an offer. I tend towards overcommunication as you can tell by the length of this review, yet they were more than patient with me. In short, there’s nothing I learned in the course that wasn’t relevant in the job interviews, and in fact I was able to blow my interviewers out of the water because there was little hesitation answering technical questions.
If you spent the time reading this whole thing, then I can only assume you’re on the fence about undergoing the program. While it’s easy to just say “go for it,” I’d rather suggest that you first separate the questions “do I want to be a software developer?” and “how do I become a web developer”? Hack Reactor will be a major asset in answering the latter, but the former is one you'll have to figure out on your own before you take the plunge.
Though at times imperfect, the HR curriculum continues to evolve, refine, and balance between employer and student needs. The elasticity of the program helps to ensure it’ll only get better in the long run. The first half is overwhelming and will spread you a mile wide and only an inch deep with the intent of providing comprehensive exposure. The second half, however, gives you the opportunity to dig deeper in a smaller set of topics and build practical resume fodder. And all the while, you have a motivated staff guiding you each step of the way.
Overall, the program worked as advertised for me. I put in my all and then some, so I feel like the value received in return exceeded my expectations. I’m now working at a wonderful company in the city I wanted to live in, at a better paying and more interesting position than I had under a year ago. I've successfully shifted my career and am way more excited about where it might take me. I also made numerous connections with both existing and future developers along the way, all who I’m better for having worked with and hope to work alongside again in the future. There isn’t a career goal I set that HR didn’t help me achieve, so it’s safe to say this investment paid off big time and will continue to do so for the foreseeable future.
I cannot recommend Hack Reactor more strongly to anyone who wants to get into full stack software engineering, but isn't quite ready to get a job yet. If you're able to get into the program, and willing to put in a lot of effort over three months, it's a terrific accelerator.
People may have been different levels in terms of background knowledge or familiarity with coding concepts, but one of my favorite things about the program was how smart and motivated my peers were. A lot of the work in the program is project-based work, in pairs or groups, so having really awesome peers was just as important to me as having great instructors.
I did the program over the summer, when it was still called MakerSquare, and then continued for another three months as a teaching assistant, during which time MakerSquare, owned by Hack Reactor, went through a re-brand process to bring MKS under the HR name.
As a graduating TA, my job search experience is a bit different than other students', since I have more experience (and a few months more of skills) under my belt, so you can take my comments on my job search with a grain of salt if you like :)
As a TA, you start work while the rest of your cohort goes into their "Career Week". Then at the end of your TA period, you join the Career Week of the cohort that's graduating at that time. During career week, you get a lot of help developing your resume, cover letter, practicing interviewing, discussing salary negotiation tactics, etc. Asif was our on-campus outcomes staff member, and he's awesome.
About half of my cohort (which graduated at the end of August) is employed by now. Maybe a bit more; I'm not sure exactly. Some folks get jobs right away, especially if they really hustle (one guy only had one month left on his visa, and got a job offer from a sponsoring company within that time). Of the four of we TAs who "graduated" a couple of weeks ago, I have an offer already, and another one of us is employed (by another one of our cohort-mates, actually).
I'll explain my ratings a bit:
- Overall Experience: It was really fun, challenging, and I came out of it able to build complex web applications from scratch. My job prospects are great. What more could I ask for?
- Instructors: Very smart, and very good at teaching.
- Curriculum: Top notch. The projects were very well designed to introduce us to important concepts we'd need to learn.
- Job Assistance: What I think HR does really well: Giving us guidance about our portfolio; helping prepare us for interviews. What could be better: Doing more to connect us to companies. I can't completely speak to this, though, because my job search so far has been so brief, and so hurried because I've had a very quick process with a couple of companies. I know HR does offer some resources, and I haven't had time to look into them and figure out how to use all those resources. I would have given a 5 score if the HR partnerships team had proactively reached out to me to try connecting me to partner companies.
I was surprised to learn that there are only a handful of Canadians that decided to attend Hack Reactor. I feel like a lot has been said about the general experience of the program so I thought I will write about my experience in hopes of helping those of you from out of the US whose thinking about attending.
I was very hesitant about choosing Hack Reactor at first and did extensive research before I decided it was the choice for me. I can't speak about other countries, but there were other coding bootcamps around the area I was living that was definitely a cheaper alternative. The reason why I picked HR over these other cheaper and closer alternatives is that the HR curriculum covered significantly more content in a shorter amount of time than any of its competitors (where I lived). If you are looking for a program that's there to push you to get the most done in the least amount of time, HR is the right place for you.
The second biggest thing that I was very worried about was whether the whole remote experience will live up to the onsite experience. Now that I have completed the remote program, I am really glad that I didn't decide to move to SF to attend the onsite class. Not only will you be saving a lot of money since you won't need to rent a place in SF but you will be working out of the comfort of your own home. For me, this was a big plus because I get to stay close to family and attending class just means rolling out of bed 10 minutes before class started! I also really enjoyed the recorded lecture because it allowed me to speed them up, rewind, and rewatch them anytime I wanted. But what about not actually seeing your classmates and instructors in real life? To be honest, I have made some amazing, life long friends that I didn't expect to make. I don't think that strong bonds between people are formed from just being in the same room together.
One thing I do have to admit is that being outside of the US, the amount of support you will be getting during the job search will not be as effective. You will most likely be facing a completely different job market and not everything you learn during job search will be applicable in your case. With that being said, I still believe that technically, HR prepares you very well to enter the job market, no matter where you are from. My biggest resource during the job search has been the HR alumni network, where you can get insight about your job market from HR grads who has gone through it before you.
This is just my prespective on the remote program and it might not be for everyone. I advise you to do your research before making your decision but don't be afraid to take the leap!
Tldr; Hack Reactor provides the curriculum and the right people (motivated and smart) for you to learn web development concepts in pairs and by yourself. I can only speak of the staff in the SF office, but they were both experienced and helpful, although anyone expecting to be a software engineer should get comfortable with directing their own learning (aka not leaning on staff to figure questions out unless you're really stuck).
Going into Hack Reactor (HR), I wanted to learn to code as quickly as possible and to try to get to a top tier company. I chose HR because I know I wanted an intense / all-day everyday experience, and looking on LinkedIn I found that HR had way more graduates at top tier companies (Uber, Google, Facebook, Airbnb, Stripe, etc.) than other bootcamps.
Within the first week of attending, I was very pleasantly surprised by the quality of my peers. They were more motivated and experienced than I expected, with several having graduated with Computer Science or Mechanical Engineering degress, and a couple having prior industry experience. Given that Hack Reactor is largely pair programming with your peers, they made a huge difference in how much I learned each day.
I was also pleasantly surprised by the quality of the curriculum. It provided some direction, while letting us figure out the key concepts via code. In my experience, the only way to really learn coding concepts is to code them yourself, and then recode them. After finishing the curriculum the right way, and reviewing the concepts you didn't understand (by recoding them), you should be able to do both.
When deciding on a bootcamp, it matters what your best alternative option is. I'll lay out the decision in my eyes from those perspectives as well.
1. Bootcamp or self-study?
After having gone through the program, I think that the people and curriculum in particular make a huge difference in the rate of learning. While it's conceivable that you could learn tht much on your own, you would need to be dedicated enough to work 10-12 hrs a day for 6 days a week, find your own curriculum to learn the key concepts, and to have smart and motivated peers to bounce your ideas off of every hour or two. If that sounds daunting, then Hack Reactor may be a good way to get the right structure to learn.
2. Hack Reactor or another bootcamp?
Several bootcamps suggest that they can help get you a job in software engineering. I read up on what the student experience was actually like, and saw that some of the bootcamps clearly had more intense experiences than others, which from my experience leads to more learning. Additionally, LinkedIn searches confirmed that only a couple of the bootcamps actually had graduates working in large numbers in software engineering.
Note: you should expect to get guidance on the job search, but realize that you will not be at the bootcamp for most of your job search, and will need to stay motivated / focused enough to find a job.
Overall, I enjoyed my experience at Hack Reactor. To give some background, I recently graduated with a mechanical engineering degree and I wanted to get into software engineering. I considered either getting a masters in CS or going to a bootcamp. I chose to go to a bootcamp because I wanted to be with a group of like-minded people during the learning process (+ get a job), rather than just finishing the courses required by my university. I think it was a good choice.
My favorite part of the experience was the people. In college, I had a lot of situations where studied on my own, because I couldn't find like-minded people with the same desire to learn/etc. This cause a lot of stress, exhaustion, and low accountability. At Hack Reactor I was learning with and from a group of encouraging, smart, and positive people for over 11 hours a day. This made the whole learning process stress free and maximized the number of hours that I was learning. I stayed until 10-11pm everyday because I wanted to keep learning. This was in contrast to college where I felt exhausted and stressed after a couple hours, took a lot of breaks, and wanted to be done ASAP.
I learned a lot, but I can't say that for everyone. You get what you put in during the time you are at the program. Hack Reactor can help you build the right community to be productive (there is some luck of the draw, since your cohort may/may not fit your vibes). But the amount of knowledge you acquire during that time is all up to you.
Hack Reactor was a truly unique experience and I can't think of a better way to get into programming if you had no background in CS. As a student, I stayed there past 10 PM almost every day because I just didn't want to leave. I was surrounded by very intelligent and motivated individuals and that really pushed me to work harder than I ever did.
If you are unsure about the program, you can message any of the grads on linkedIn and I'm sure they'd be willing to answer your questions. Or you can message me. I definitely don't think it's for everyone, but if you're the type of person that would enjoy going to (winning) a math competition or something, you'll love the place.
Our latest on Hack Reactor
Need an overview of coding bootcamp news in May? You’re in the right place! We’ve collected all the most important news in this blog post and podcast. This month, we read about a number of insightful surveys about employers, programming languages, and learners. We read advice about choosing a bootcamp, learned about efforts to encourage women and veterans to learn to code, and heard about student experiences at bootcamp. Plus, we added a bunch of interesting new schools to the Course Report school directory! Read below or listen to our latest Coding Bootcamp News Roundup Podcast.Continue Reading →
Looking around the Hack Reactor classrooms, Albrey Brown could see a lack of diversity. As the Director of Diversity and Inclusion, his team decided to do something about it, and started by auditing the demographics of past alumni and current students. After analyzing that data, Hack Reactor announced their “Vision2020” to graduate classes made up of 50/50 gender balance and 20% underrepresented people of color by Q1 of 2020. We speak with Albrey to learn more about how Hack Reactor will attract, engage, and retain diverse, technical talent. Plus, read tips on how other bootcamps can enhance their diversity and inclusion efforts!
Tell us about your role at Hack Reactor!
I’ve been the Director of Diversity and Inclusion at Hack Reactor for about four months now. I founded Telegraph Academy after graduating from Hack Reactor, and my team at Telegraph Academy did a very good job of sourcing students from underrepresented backgrounds. When Hack Reactor rebranded, our entire team was absorbed back into Hack Reactor to work on diversity and inclusion efforts and grow Telegraph Track (the revamped Telegraph Academy). I've been working with the leadership team and other employees to expand those efforts to the HR staff as well.
Telegraph Track’s first big project was working with Facebook on their F8 donation – Facebook just donated $250,000 to Hack Reactor's scholarship pool to be given out over the next year. That’s 14 full rides to Hack Reactor for underrepresented future engineers! The Hack Reactor scholarship program has been a really amazing source of underrepresented talent. We looked at how that's been converting to our student population and decided that our second project had to be figuring out whether we're improving or not.
What prompted Hack Reactor to conduct the diversity and inclusion report?
Our moment of obligation came a while ago. When I went to Hack Reactor in 2014, I was one of the only African-American students out of 160 people, which is unacceptable. As an organization, we’ve always been looking to improve, but we’ve invested most of our resources externally. There are seven bootcamps that we support in terms of curriculum, financial investment, and instructional support, and they are specifically geared towards underrepresented groups. We extend scholarships and curriculum help to many community partners, so externally, we've always been about promoting diversity and inclusion.
Once my team was back on site, we realized that we were overlooking more internal efforts and that's what prompted the diversity report itself. It was very easy to walk on campus and see that it wasn’t a very diverse environment. The anecdotal evidence was there – we needed the data to support that, because data is key to change.
Were the results what you expected? Better or worse?
We didn't start the survey with a clear expectation; we know that women and people of color are definitely underrepresented. When we compare ourselves to the bootcamp industry, we only had the Course Report Outcomes & Demographics study, which says that 43% of bootcamp grads are women. And in the tech industry, African-Americans and Latinos account for 1% to 3% of engineers, so I thought anecdotally that Hack Reactor would be consistent with those stats.
Our report found that 25.2% of Hack Reactor alumni are female, 4% are African-American and 6.9% are Latinx. I didn’t want to have preconceived notions about the findings based on the tech industry; we’re an education company, not just a tech company.
This may be obvious to some, but why is diversity & inclusion important at a coding bootcamp?
Hack Reactor is a new type of funnel to the tech industry. Tech organizations are looking to diversify, because no matter their size, being diverse is good – let's be honest – from a PR standpoint, but also good for the bottom line.
For Hack Reactor, there are two reasons why this is important to us. One, the coding bootcamp industry already lends itself to diversity, because the principles that we're built on is creating nontraditional engineers. So our students have a very diverse background and perspective compared to the regular CS degree grad. We've already developed internal practices in communities that foster diversity.
We also have a business opportunity here. In your report, 43% of bootcamps graduates are women, compared to 25.2% of our alumni. For us, that's an opportunity for growth and to get better. Obviously, I haven't heard anybody say that Hack Reactor is a place where women don't thrive, but we need to do a much better job of reaching out to spaces where women are looking for a tech community.
Why do you think that gender disparity exists?
It’s tough, because like I said earlier there are no indications that women at Hack Reactor don’t thrive. Since we started making a concerted effort toward diversity and inclusion, we’ve been getting tons of feedback from women in our community and no one has said they feel “bad” or particularly “marginalized”.
However, like with everything else success comes from a strategy. For whatever reason, our customer appeal is more male leaning. This was an eye-opening realization for us and now we are reimagining how we do things from the top down. Partnering with women-focused tech organizations, creating internal communities for women, and even making changes to our marketing that make us more appealing to women. These are some ways we’ve decided to close the gap and hopefully they work for us sooner rather than later.
Why will it take until 2020 to get to 50/50 gender parity and 20% underrepresented racial groups? How will you get there?
The first piece is tracking this data. We're going to be gathering data from each part of the pipeline to see when people fall out of the pipeline, what type of people parse out the different type experiences that different types of people have at Hack Reactor, and then we can start forming specific strategies around how to help them.
Once we've added gender and ethnicity questions to our admissions application, we can see the top of the funnel and then from there we can start tracking who gets admitted and who finishes Hack Reactor, making more informed decisions to get better at recruiting.
The next step is actually working on inclusion, which means making our environment welcoming to women, people of color, and those who are underrepresented. In our in-person interview, we're adding two cultural competency questions to show applicants that this is a priority for us. We’ll ask how willing they are to learn about diversity and inclusion, and how willing they are to advocate for it. We want to make Hack Reactor a place that not only fosters diversity and inclusion, but also fosters respect for other cultures.
We’re creating spaces for underrepresented students through our Telegraph Track, which provides mentorship programs and leadership development support.
We’re also creating Alumni Affinity Groups. Every large company has Employee Resource Groups (ERGs), and we’re replicating those with our alumni, so that they can create communities and networks outside of Hack Reactor.
Do you think that making the Hack Reactor classroom more diverse will benefit students?
People have lost jobs over not being culturally competent and I think it's important to highlight that. Not only is this a moral imperative that we should be invested in, but students should also be invested in it because, at the end of the day, the world is changing. This is going to be a conversation that almost every company goes through from now on. So you should invest time in thinking about these things.
After we filter out people who won't enjoy this type of thing, we also have to make it a part of our curriculum. We’re adding cultural competency education that's baked into our curriculum, which will expose the things that the majority population and the underrepresented population should be thinking about when it comes to their career as a software engineer, what it means to practice cultural competency, and also why it's important as part of your career.
Hack Reactor has always been known as the “Harvard of coding bootcamps.” Do you think that this exclusivity and perception of Hack Reactor’s low acceptance rate has contributed to the lack of diversity at the school?
I think you're right. There's a stigma around Hack Reactor that it can be very competitive and unattainable. In reality, only 5% to 10% of our students have a programming background before Hack Reactor.
One of the things that has definitely lowered that barrier to entry has been the Hack Reactor Prep Program. In January, we put out a free Hack Reactor Prep online coding module. It's basically 350 questions that tell you about everything we’re looking for in our interview process, and 85% of people who finish it pass our interview.
We can definitely change things in terms of the way we market ourselves to help us diversify the pipeline. The first thing we're going to do is ask all of our stakeholders, "What was your experience like before Hack Reactor and throughout Hack Reactor? What are the things that we need to tweak, change, and make better in order to demystify what it takes to be a Hack Reactor student?”
Telegraph Academy is reemerging as Telegraph Track – could you explain what Telegraph Track does for students and why someone from an underrepresented group needs that extra support?
To be clear, every Hack Reactor student gets the same technical training. All of the additional support through Telegraph Track is around community building. We meet 1.5 hours per week. Underrepresented students don't have the networks that the majority population does. We have people coming from so many different places – we have a student who moved here from Atlanta and didn't know anybody when he arrived. Having a network of people with a similar background, who are interested in his growth is huge for him.
Underrepresented folks also don't always have access to networks with industry knowledge. For example, they don't have a friend that they can ask for coffee and talk about working in tech. We intentionally pair those students with engineers to share that fountain of knowledge, and it gives them a leg up in terms of professional development. Next, we support their exposure. All of our Telegraph Track students write a technical blog post every week, so that they can build their brand. When you're trying to break into the tech industry, it's really important that you have a presence online to show that you can speak about yourself, particularly as an engineer.
Finally, we set up career support. We don't want this support to end at Telegraph Track, so we have an alumni community where we teach students how to be their own HR advocate. When you start your first job, how do you find the people who are going to be your mentors at your company? How do you break down biases and recognize privilege? How do you create allies? All of these things will help these students navigate the tech industry from the perspective of being underrepresented.
How are you working with employers to ensure that your graduates are being placed in diverse organizations?
We want to connect our students with companies that either have diverse teams or want to build diversity and inclusion programs. Tech organizations have been hiring from the same pool for a very long time. One of the reasons it's important that we do this at this moment in the industry, is that bootcamps are being taken seriously for one of the first times ever. For the first time, we’re hearing recruiters say, "my hiring manager told me to look for a bootcamper." Getting past that first layer of stigma was really important, because if you're an underrepresented bootcamper, then you have two layers of stigma that makes it difficult to get a job. Dissolving the first layer is awesome.
Our goal is to find those companies and audit them; ask how they’re fostering diverse environments and changing their practices. I was just on a panel at Lever, which is a really important company to me because they’re one of the first large companies to achieve 50/50 gender parity. I talk to hiring managers all the time, and I’m looking for employers who can change their perspectives on hiring. When you're looking for an experienced developer or a fresh CS grad, you’re looking for a certain skill set and for them to pass the “eye test.” They say that Silicon Valley is a meritocracy, but we all know that’s not true. We want to work with employers to create systems around applicants showing their work in a non-judgemental environment. That will go a long way towards diversifying and recruiting from other pipelines.
Do you have any advice for employers who want to expand their diversity and inclusion efforts?
First, make sure that you start with a coding challenge instead of a resume. It should be about being able to do the work. Instead of having somebody submit their resume, have them submit some code to you, look over the code and then see whether that is up to whatever standard of programming that you are looking to employ. If you want to hire bootcampers in general, I suggest you get a bootcamper from your company in on the hiring process.
Lastly, you should actually go to the places where bootcampers are, and to places where underrepresented groups are. You have to show up and be actually interested. Even when we vet companies, sometimes we are duped. We’ll go on a company tour and we can see that students can actually feel that this was just charity. As an employer, you have to be authentic about wanting the talent; not tokenizing the talent.
How can other bootcamps improve their diversity efforts?
Don't wait until you're at scale! Do it early and often. And of course, if a bootcamp wants to diversify, they should put out a diversity and inclusion report. Get a baseline of measurement first, because it’s the most important thing. (Rithm School offered a diversity and inclusion scholarship, even though they’ve only had 15 students. I admire the hell out of that.)
Secondly, it's all about engaging community partners. Coding bootcamps exist in the middle of two pipelines: between organizations and prospective engineers, and also in the education pipeline. You need some pre-knowledge to do any bootcamp. There are organizations that are already supporting and creating that pre-knowledge. Code Tenderloin is one example, which is an organization that we’re working with to build a bridge program to Hack Reactor. We need to invest our resources into those community partners, and tap into them to give our resources and share knowledge so that their students have a chance to go to Hack Reactor.
Finally, always get feedback from every group at your school. If you keep asking the same type of person whether they're enjoying the course, then you’re only going to get one point of view.
Missed out on coding bootcamp news in April? Never fear, Course Report is here! We’ve collected everything in this handy blog post and podcast. This month, we read about why outcomes reporting is useful for students, how a number of schools are working to boost their diversity with scholarships, we heard about student experiences at bootcamp, plus we added a bunch of interesting new schools to the Course Report school directory! Read below or listen to our latest Coding Bootcamp News Roundup Podcast.Continue Reading →
How do you get a job after coding bootcamp if you have no relevant, real-world work experience? Only 1.4% of bootcampers have worked as developers in the past, but most career-changers have little – if any– client experience when they start looking for a developer job. Some bootcamps help students overcome this hurdle by offering opportunities to work for the bootcamp itself, or with real clients through projects, internships, and apprenticeships. These opportunities can give students substantial experience to add to their portfolios and resumes, and kickstart the job hunt.Continue Reading →
How does a Financial Intelligence Analyst become a Software Engineer? For Dan Svorcan, it took thorough research, self-confidence, and a lot of prep work before he even started the Software Engineering Immersive at Hack Reactor. After being surrounded by engineers in Silicon Valley and realizing he wanted to pursue his childhood tech dreams, Dan enrolled in Hack Reactor Prep to start his journey. Learn about Dan’s ReactNative thesis application and how he prepared for Hack Reactor’s full-time Software Engineering Immersive.
What were you up to before you attended Hack Reactor?
I studied Competitive Intelligence and Music. My first job after college was here in San Francisco. I worked as a financial intelligence analyst at a bank not too far from Hack Reactor headquarters. I worked there for about a year and seven months before I started Hack Reactor.
How did you go from working in financial intelligence at a bank to then deciding that you wanted to learn how to code?
I’ve always wanted to work in technology. As a little kid, I was always more interested in opening up my battery-powered toys and seeing how they worked than actually playing with them. Putting them back together was also a fun challenge. I also spent some time coding in college. I took a Java class, and from that moment I knew I wanted to be a software engineer.
Since coming to San Francisco, I've met many software engineers. Their stories inspired me to pursue my passion for building software, so I started doing research on the best schools out there, and Hack Reactor kept reappearing. With my background in intelligence, I did thorough research to verify that Hack Reactor was the best option.
Did you try to start learning how to code on your own before Hack Reactor? What resources were you using?
Yes, definitely. I was using Code School, Codecademy, and FreeCodeCamp, among other things. My main segue into Hack Reactor was Fulcrum, an earlier version of Hack Reactor’s paid prep program. As I was finishing Fulcrum, Hack Reactor started offering the free Prep course and I enrolled to get more practice before my admissions interview. There were over 150 exercises to practice on along with great tutorials on how to prepare for the technical interview.
So you had already done prep work, why did you decide to take Hack Reactor Prep?
The main feature that drew me to Prep was a team of software engineers that reviewed every line of code I wrote for certain modules (chapters). I sent my code back and forth, up to five or six times until my formatting was correct, or until my code was small and modularized enough that it was easily reusable. These days, I still follow those rules when I write code.
Prep also offered mock interviews, which were amazing because nothing can truly replace the live interview experience. I think that having multiple mock interviews before my technical interview was very helpful, and made the entire process a lot less stressful.
To summarize, the human interaction and the mock interviews are the best parts of the prep program.
Since Hack Reactor Prep is online, how did you communicate with instructors and mentors?
There was a dedicated Slack channel for student/instructor communication. There was constant interaction with instructors, especially when we were learning about code formatting, readability, and modularity. For example, the main task would be to find the longest palindrome, but the solution would not be accepted until code was properly formatted, easy to read, etc.
What did you actually learn in the Prep course? How did Prep position you for the Software Engineering Immersive application and interview process? Do you think you would have gotten in without all of the prep work?
I learned a lot, but I think two most important things were how to better prepare for a technical interview and how to write clean code.
I truly believe that all the prep work (especially the mock interviews) had a great impact on my interview performance and admission into the Hack Reactor Software Engineering Immersive. The prep program was designed in such a unique way that every step of the way I felt more prepared for the interview.
How did Hack Reactor Prep prepare you for the actual Software Engineering Immersive?
I was offered admission into the software engineering immersive before I completed the prep course, so I had made a tremendous amount of progress even before the course was over. For example, I’m still using some of the skills I learned during the prep work (e.g. clean and modular code). Additionally, everything I learned in the prep program was later multiplied and enhanced during the software engineering immersive.
Tell us about a typical day in Hack Reactor’s full-time Software Engineering Immersive.
On a typical day, I get here around 8am, and I start doing either some quick coding problems or continue where I left off yesterday. At 9am, the day starts with a 15-minute kickoff and maybe a lecture, depending on the day. Usually, there’s a Toy Problem after the kickoff. Toy problems prepare students for technical interview problems during the job search.
How have you liked this bootcamp learning-style so far?
Hack Reactor is very different from any other school really. I was expecting something similar to college-style learning, where students attend a lecture, then learn more on their own before taking an exam. Hack Reactor doesn't work that way; it’s way more efficient.
During the first six weeks of the course (also known as Junior phase), we had lectures regularly– but instead of simply learning what was presented, we went beyond the lecture material and then applied it. Each lecture had a corresponding sprint, which is a technical challenge structured to reinforce a topic or technology (e.g. Angular, React, MySQL, etc).
During the second six weeks (Senior phase), there are fewer lectures. Instead, we work on projects that tie together everything we learned up to that point, and more. We focus on teamwork, larger scale of the applications, and efficient workflow.
Do you have a favorite project that you're working on now? Tell us about it!
Right now I'm working on my thesis application. My team and I are building an app for iOS and Android using React Native.
We're building PixPlorer, an interactive tour guide app designed to help travelers explore new cities. Let’s say you come to visit San Francisco; you’d probably want to see cable cars. Our app gives you a list of things to see or visit, so once you find a cable car, you have to take a photo of it and it will get checked off your list. The app uses image recognition to verify you took a photo of the cable car, and geolocation to determine which particular item needs to be marked as complete (e.g. California Street cable car vs Powell Street cable car). The app will be deployed soon so feel free to check out my GitHub page and the demo video. Some of the technologies we’re using for the app are React Native, Redux, Google Firebase, Google Vision, Amazon EC2, Amazon S3, MySQL, Bookshelf, MongoDB, Mongoose, Mocha, Chai, etc.
What’s your goal for after graduation? What types of jobs will you be looking for?
I’d like to focus on full stack software engineering roles after graduation. I’ve worked on every part of the stack, and I find it really exciting and rewarding to work on both front and back end.
What's been the biggest challenge for you on your journey to learn how to code?
My biggest roadblock was probably believing that this was possible. There are numerous articles about impostor syndrome in the tech industry where people who are really great engineers somehow still doubt themselves. Hack Reactor teaches not only technical skills but how to resolve all doubts and eliminate the impostor syndrome.
What advice do you have for people who are thinking about switching careers, and thinking about attending a coding bootcamp?
There are really talented people out there that never go to a program like Hack Reactor because they have doubts. Yes, you do have to quit your job, pay for school, be out of work for three months, and then spend some time on the job hunt after graduation. But doing something you're really passionate about is worth every risk. I'm excited to get to work every single day and I would recommend Hack Reactor 150%.
Here’s what we found ourselves reading and discussing in the Course Report office in February 2017! We found out the three most in-demand programming languages, we read about how coding could be the new blue collar job, and looked at how new schools are tweaking the bootcamp model to fit their communities. Plus, we hear about a cool app for NBA fans built by coding bootcamp graduates! Read below or listen to our latest Coding Bootcamp News Roundup Podcast.Continue Reading →
What were you up to before you applied for the Hack Reactor Scholarship?
Did you find that music and audio engineering was similar to programming?
Why did you decide that a coding bootcamp was your best option to learn programming? Did you consider getting another college degree?
I've been self-teaching for about a year, so this is something I thought about for a while. I briefly considered another degree, but I knew it would take too long. Plus, I felt jaded toward the university experience after getting my BS. To me, the risk to reward ratio of a coding bootcamp made sense – being pushed extremely hard while learning to code for 3 months and then getting the results that Hack Reactor publishes felt like a great deal. Originally, I thought I could work in a finance-related role at a tech company and horizontally pivot into a technical role, but I found I was getting burnt out coming home and learning for five to six hours, all while handling a day-job. I’m hoping my experience at Hack Reactor will fill in any knowledge gaps that I may have as I make a final push to get into an engineering role. Additionally, I realized that I needed the intangibles that a bootcamp could provide – the immersive structure, and the network of instructors and other passionate students who share the same objective as I do.
Did you research other coding bootcamps? What stood out about Hack Reactor?
I looked at General Assembly and CodeSmith. But I had a friend go through Hack Reactor who said good things about it and I watched him get placed at a company after he graduated, so I picked his brain. Plus, some of the prominent people that I follow on Twitter had been through the same track at Hack Reactor. After doing my research, I really felt that Hack Reactor was one of the top coding bootcamps for me, and if I was going to devote so much time and energy to this, I wanted to be around the best students and teachers.
In the beginning, I started with a few Udacity MOOCs, but as time progressed, I built a hybrid system that worked for me. I used pretty much anything if it was good. One thing I felt was helpful were written tutorials by developers on Medium. I followed knowledgeable engineers on Twitter. I found amazing resources on YouTube and would listen to the free classes provided by MIT on OpenCourseWare. Everyone learns differently, so I was just trying to be like Neo from The Matrix and “plug-in” to the tech community in a lot of different ways.
My local community was also extremely important. I went to several NodeSchool meetups and met people there who I'm still in touch with. Not to mention, meeting people at meetups helps you gauge your own competency, understand what level you’re on, and find areas where you can improve.
Did that self-teaching get you through your technical interview at Hack Reactor?
For the Hack Reactor scholarship, applicants have to make a two-minute video! What was yours about?
The point of that video is to teach something in a two-minute video. At first, I was going to teach my viewers something generic, like how to cook a recipe, but I felt that it wouldn’t fully tell my story. So instead, I gave a high-level overview on how to sample music. I spent two minutes explaining and demonstrating how to sample Crave You by Flight Facilities. I couldn’t go into as much detail as I would have liked, but I was able to briefly explain how sampled music is created. I tried to make my video educational, intriguing, and most importantly something that told my story.
When do you start your cohort?
I will be starting January 31st at the LA campus.
How have you started preparing for Hack Reactor?
I’ve also been letting my friends and family know that I’m starting Hack Reactor and it’s going to be taking a lot of my time for the next few months. But they’ve all been watching my journey and know how passionate I am about this, so I think they’ll understand when I go off the grid.
Do you have specific career goals after you graduate? Do you want to stay involved in music?
I’d like to work for a startup where I can get my hands dirty. I’m open to working for any company with a product that I’m passionate about. For example, Splice is a start-up based in Santa Monica, and they provide workflow tools for musicians and producers. I love the founder’s vision and what he does for the community. Stem is another startup that’s working on paying artists and producers their streaming music royalties using the blockchain; that looks interesting.
I’m passionate about music, but I have other interests as well! I went to school for finance, so ideally I’ll find a job that’s in my realm of interests or is a combination of the two.
Any advice for future bootcamp applicants?
Don't get discouraged! I can easily think of the many sleepless nights I had being frustrated as I dealt with all the new information. I knew where I wanted to be in my career, but it felt so daunting – I guess that’s what they call Imposter Syndrome – and I couldn't see the path to get to where I wanted to be. Tap into all of your resources; Twitter is the reason I found out about the Hack Reactor scholarship! Albrey Brown retweeted an announcement about the scholarship, and that's the reason I applied. Attend meetups and meet people; I’ve found the programming community to be extremely beginner friendly. It’s amazing how many resources are available at the click of a button or just by asking.
Also remember that learning is a lifelong process. I still have and will continue to have days where I get stuck, but as long as I'm getting better and progressing, I can feel content that I’m growing as a person and as a developer.
It’s that time again! A time to reflect on the year that is coming to an end, and a time to plan for what the New Year has in store. While it may be easy to beat yourself up about certain unmet goals, one thing is for sure: you made it through another year! And we bet you accomplished more than you think. Maybe you finished your first Codecademy class, made a 30-day Github commit streak, or maybe you even took a bootcamp prep course – so let’s cheers to that! But if learning to code is still at the top of your Resolutions List, then taking the plunge into a coding bootcamp may be the best way to officially cross it off. We’ve compiled a list of stellar schools offering full-time, part-time, and online courses with start dates at the top of the year. Five of these bootcamps even have scholarship money ready to dish out to aspiring coders like you.Continue Reading →
Welcome to our last monthly coding bootcamp news roundup of 2016! Each month, we look at all the happenings from the coding bootcamp world from new bootcamps to fundraising announcements, to interesting trends we’re talking about in the office. This December, we heard about a bootcamp scholarship from Uber, employers who are happily hiring bootcamp grads, investments from New York State and a Tokyo-based staffing firm, diversity in tech, and as usual, new coding schools, courses, and campuses!Continue Reading →
In our recent Student Outcomes survey, alumni reported that they were working in over 650 different companies! Of course, you may have read recent press citing companies like Google who apparently aren’t willing to invest in junior technical talent from coding bootcamps (we happen to know that coding bootcamp grads have been hired at Google and Salesforce, but that’s not the point)... Here we’re highlighting 8 forward-thinking companies who are psyched about the bootcamp alumni on their engineering teams. Each of these employers have hired multiple developers, and are seeing their investment pay off.Continue Reading →
Have you heard the news? MakerSquare and Telegraph Academy’s network of schools are rebranded as Hack Reactor Austin, Hack Reactor Los Angeles, Hack Reactor San Francisco and Hack Reactor New York City. But what exactly does this mean for MakerSquare and Telegraph Academy alumni, current students, staff, and future students? We asked the Hack Reactor team to answer our questions about how this merger will affect tuition, admissions, curriculum, culture, and reviews.Continue Reading →
Should I do a coding bootcamp? This is a question we hear all the time, and for good reason. As more coding bootcamps launch (not to mention the rising media coverage), you’re probably wondering, “should I jump on the bandwagon and learn to code?” A recent TechCrunch article implored you not to learn to code unless you’re ready to put in the work to be great, whereas President Obama wants every student to learn computer science in high school. So what types of people are opting for coding bootcamps? And should you be one of them?Continue Reading →
Cisco has hired a number of Hack Reactor grads (almost half of their CTAO engineering team are alumni), and finds that they are “so well prepared and ready to hit the ground running.” We spoke to Cisco Director of Experience Design Dustin Beltramo and Technical Leader Joe Sutton about what they look for in a new coding bootcamp hire, why skill set is more important than having a degree, and what stands out about Hack Reactor alumni compared to other candidates.
Tell us about Cisco and your roles there.
Dustin: I’m a Director of Experience Design in the Chief Technology and Architecture Office (CTAO) at Cisco. I manage a small team of visual designers and design strategists, and work closely with our lead engineer (Joe) to hire front-end and full-stack developers. As I’m sure you know, Cisco’s a large company with about 70,000 employees worldwide. The CTAO org is basically an innovation team, consisting of a bunch of architects and distinguished engineers from across Cisco who partner with customers to build proof of concepts for new technologies and products -- typically things like cloud service orchestration, security, analytics, IoT, and software-defined networking. When the POCs (POC = Proof of Concept) prove that there’s a market for a new product, we transition the project to the relevant mainline engineering team within Cisco to be productized. The Experience Design team supports the CTAO org by designing and implementing the front-ends for these co-innovation projects.
Joe: I’m a Technical Leader, my main role is to architect/lead the engineers on all the projects we implement. I work closely with the designers, various backend teams providing APIs, and when the time comes I work with the mainline engineering to transition the projects over.
How large is the development team?
11 engineers at the moment, four of whom are Hack Reactor grads.
How did you get connected with Hack Reactor as an employer?
Joe was recommended to Hack Reactor by a friend at his last company. While there, they had good success in finding top quality candidates. So when the time came to expand the engineering team, we decided to give Hack Reactor a try.
What types of roles have you hired Hack Reactor graduates for at Cisco?
Software engineer, primarily front-end and web-centric.
Other than Hack Reactor, how do you usually hire developers at Cisco? What are you looking for in a new hire?
There are a lot of coding bootcamp alumni looking for jobs now - of the Hack Reactor grads that you actually hired, what stood out about them?
It’s really their capabilities, the quality of their code, and their attitude. These days, most front-end and full-stack engineer resumes look the same, everyone lists the same set of frameworks and tools and whatnot. We’ve found the only way to really gauge a candidate is by the quality of the code they write. Since the Hack Reactor folks have their final projects and other work available on GitHub, it’s easy to get a sense for what type of developer they’re going to be. On top of that, the Hack Reactor program seems to prepare students exceptionally well, they have a good sense of what it’s like to work on a modern web development project.
I’m assuming that your hires from Hack Reactor went through a technical interview. How did they do?
Yes, definitely, there’s no other way to really guarantee that an engineer knows what they’re talking about. We do not modify our process for bootcamp grads. The partnership definitely makes things more efficient, by reducing some of the administrative overhead associated with the interview process.
Has it ever been a concern for you that these new developers don’t have a traditional computer science degree?
Not at all. We hire people based on their demonstrated skill set, not on any particular degree or certification.
Hack Reactor provides us with great support and consistently delivers a pool of candidates who are exceptionally well-prepared for the type of development work our team does.
How do you ensure that the new hires are supported as they continue to learn after they graduate from Hack Reactor? Do you have mentoring or apprenticeship programs in place?
Yes, the lead engineer provides ongoing mentoring, there are regular knowledge-sharing activities amongst the team, as well as providing opportunities to attend industry conferences and training. Oddly enough the Hack Reactor grads themselves can also act as mentors. Many of the teams we work with were trained as strictly backend engineers and so they are not up-to-date with the latest cloud-native web app techniques and technology. The work our Hack Reactor grads do with other teams helps to spread that knowledge more broadly within Cisco.
Are there any interesting stories about Hack Reactor hires that have advanced in their career?
We don’t have any particularly interesting stories, but we know that programs like Hack Reactor have had a very positive impact on most of the people that have gone through the programs. We’ve interviewed over thirty candidates and seen people from all walks of life, which you don’t always see from traditional new hire candidates. We’ve seen people with degrees in Computer Science, Law, Theater, Philosophy, History… the list goes on. Everyone we asked, why they joined Hack Reactor, all responded that they were looking to improve their quality of life, and were very happy they went through the program.
Do you have a feedback loop with Hack Reactor at all? Are you able to influence their curriculum if you notice your dev hires are underperforming in a certain area?
We provide feedback on every candidate we interview and hire. We haven’t really seen any systemic deficiencies. But the folks we work with at Hack Reactor are very open and responsive, I wouldn’t hesitate to approach them if we noticed an issue that needed to be addressed.
Will you hire from Hack Reactor in the future? Why or why not?
They are our first choice! The grads are so well-prepared, they come in and hit the ground running, that’s really what we’re looking for.
What is your advice to other employers who are thinking about hiring from a coding bootcamp or from Hack Reactor in particular?
First, not all coding boot camps are created equal. We would recommend talking to colleagues in the industry who have experience with the various programs. We wouldn’t hesitate to hire grads from the best boot camps, especially Hack Reactor. We find the students are highly motivated and excel in their work, and their training is top-notch. They may seem inexperienced on paper, comparatively, but the best coding bootcamps simulate a real world software development environment for their students, and that experience is incredibly valuable.
What is your advice to future Hack Reactor grads that are interested in opportunities at Cisco?
Please apply, we need you! Cisco is in the midst of an exciting transition from its hardware-centric roots to a future based on software and services. We need the skillset of Hack Reactor grads now more than ever. If you apply to a team that is fully embracing this cloud-centric future, your skills will be a huge asset, and you’ll have the chance to make a big impact, even on a company the size of Cisco.
Welcome to the August 2016 Course Report monthly coding bootcamp news roundup! Each month, we look at all the happenings from the coding bootcamp world from new bootcamps to big fundraising announcements, to interesting trends. This month the biggest news is the Department of Education's EQUIP pilot program to provide federal financial aid to some bootcamp students. Other trends include job placement outcomes, the gender imbalance in tech, acquisitions and investments, and paying for bootcamp. Read below or listen to our latest Coding Bootcamp News Roundup Podcast!Continue Reading →
Many competitive coding bootcamps require a certain level of coding knowledge or background in order to be accepted into their programs- whether they’re looking for past experience on your resume or require that you pass a coding challenge. For a beginner, it can be tough to get the experience that a selective bootcamp looks for in the application process. There are many ways to learn basic coding (including teaching yourself) but if you want to make sure you’re covering the right material and quickly, then a bootcamp prep program may be for you.Continue Reading →
While a number of coding bootcamps have published their own student outcomes, Reactor Core recently released SSOM, a methodology for calculating job placement outcomes that they’re encouraging other bootcamps to adopt. As the coding bootcamp industry grows, transparency in marketing practices becomes integral to the success of the industry, so we spoke to Reactor Core CCO Shawn Drost about their Standard Student Outcome Methodology (SSOM), the (un)importance of auditing outcomes, and how Reactor Core calculated Hack Reactor’s 98% Hiring Rate with an average starting salary of $104K.
Shawn, what’s your role at Reactor Core?
I'm a Co-Founder of Hack Reactor, the San Francisco bootcamp. In 2015, we also started Reactor Core, which is a network of coding bootcamps made up of Hack Reactor, MakerSquare, Telegraph Academy and others. Now my official title is Chief Commercial Officer of Reactor Core.
As part of Reactor Core’s efforts, you’ve now released the Standard Student Outcome Methodology (SSOM). Tell us what SSOM is about.
SSOM is a document that helps coding bootcamps calculate a placement rate. If a school is focused on helping people get jobs as developers, then it's very important to communicate that success to the public. Hack Reactor and our other Reactor Core schools have all communicated placement rates from Day One, but over time, it became important to formally document what that means and how we calculate that number.
So what does go into the Placement Rate? Isn’t it simply the number of graduates who get jobs as developers?
People think that number is really straightforward, but it turns out there are a lot of edge cases. We have to think about who counts in the numerator and in the denominator, how to deal with international students, and how to count graduates who the school employs afterward, etc. How do you deal with somebody who gets a short term, part time contract?
People can disagree about how all of these things work, and it's really important to be transparent. In its infancy, the bootcamp industry has not really done that. And to be fair, neither have law schools, which are now in their adulthood.
You've been running a coding bootcamp for three years- what are some of the challenges that you faced as a bootcamp founder in reporting outcomes?
It's not especially difficult for the coding bootcamp industry to keep track of student outcomes, and this conversation is broader than the bootcamp industry. It turns out, the entire higher ed system is bad at keeping track of student outcomes. When Reactor Core started building SSOM, the first thing we did is look at existing standards that are in place at law schools. It turns out the existing standards are very haphazard.
Did you look at College Scorecard when designing SSOM?
We did -- College Scorecard has a great approach that we can't implement on our own. The government basically pulls the tax records of students, so they have great salary data for all alumni. This is an approach we've recommended to the state of California, and they're looking at it.
So should there be different outcomes rubrics for different types of schools?
About 90% of coding bootcamps are organized on the promise of "you want a job as a developer. We'll get you there." And for any school that is set up like that, they should have the same basic principles that powers SSOM. It’s very strict in that it has a narrow view of what counts as success -- it only counts jobs with “engineer” in the title, and does not count edge cases like “what if I went back to my old job and did some coding”, or “what if I got a job like ‘product manager’ that’s tangentially related to coding.
But SSOM is not appropriate for a school that consciously decides it has different values. If Startup Institute, for instance, decides that they value a diversity of outcomes and they’re explicitly clear about that to students throughout the admissions process, then I think there's room for a different type of outcomes rubric.
How many schools in the US qualify to use SSOM to report outcomes?
Most of them. Any coding bootcamp that predominantly markets itself as "we can move you into software jobs" should take that as a principal that they count coding jobs as success, and they don't count jobs in other fields as success.
When designing SSOM, how important do you find auditing in the validity of success outcomes?
Zero percent. And we got our own Hack Reactor report audited through Frank, Rimerman Rimerman + Co. LLP; they did great work.
So you'd say transparency is more important than auditing?
I think that it's important to build consumer trust through as many mechanisms as possible. I think auditing is likely to catch only the very worst cases of outright fraud, and I don't think that audits are a very effective system for ensuring that students are being served well.
The problem is that there's an inherent conflict of interest when you have a bootcamp paying a supposedly independent third party who to hold that bootcamp accountable.
How about coding bootcamps that are “accredited” or “approved” by a government body (ie. the BPPE in California)? Does that mean anything about their outcomes?
The State would be the first to tell you that they don't have any means of tracking student outcomes in a rigorous way. We are in close touch with the California government, and when they asked for employment data and we started digging a little bit deeper, we found that the government knows that this is a complicated process. We had to write SSOM from scratch because there was no such document already.
They don't have any of the funding or the operational bandwidth to assess the validity of a school’s self-reported employment rate, so the state doesn’t validate it. They send out a data request and then publish what the schools send back. But look through that data- there are typos and numbers that don't add up when you page through the government’s list of vocational programs in California.
The government doesn’t have an accreditation process; they have a “permission to operate” process, where they determine whether or not you have the facilities and curriculum to run a coding bootcamp. Everyone I’ve spoken with is a dedicated public servant who really wants to do a good job, and I think they would also be the first to say that they have no idea whether or not a coding bootcamp curriculum is “good.” They’re looking at whether the school has the financial wherewithal to issue refunds, if the school has a fax machine, a library, etc.
So SSOM has been used to actually calculate and publish Hack Reactor and Hack Reactor Remote’s outcomes in the form of a Cohort Report. When will we see Cohort Reports for MakerSquare, Operation Spark, Telegraph Academy, etc?
We are on track for that- keep an eye out for announcements.
How long does it take a school to use SSOM in order to actually create the Cohort Report?
If your dataset is really neat and the number of students is pretty small, it could take as little as 5-10 hours.
How heavy is the burden of documentation on the school?
It's pretty substantial, because the documentation part of this assessment process is probably the hardest.
There's two phases for schools that adopt SSOM. This first report is published in “Onboarding Mode,” which basically means that the school is collecting all of the hard data (anything that a third party created or signed- for example, offer letters).
“Compliance Mode” is when the school is sending out confirmation surveys to students.
What is your advice to a new coding bootcamp who values outcomes and wants to start the process of reporting their student outcomes?
We designed SSOM specifically around the fact that a school will not necessarily have all the data required by a methodology that Reactor Core just wrote in the last year. Any school can start using SSOM today, and there's a grace period to get your operations in order. Reactor Core also has a standing offer on our website to help onboard any school with SSOM at cost, and that includes whatever kind of support we can offer in terms of assembling the actual report.
Have any schools taken you up on that offer?
We don't have any announcement about that yet.
Skills Fund is attempting to get schools to come to consensus on an outcomes methodology. From those early meetings, do you think that SSOM could potentially just be adopted by Skills Fund or by all schools?
What we want is for the industry to have good standards and for consumers to have access to apples to apple comparisons. The goal of the Skills Fund process is not to produce a document like SSOM- it is to produce a methodology minus the documentation standards.
SSOM is both a methodology for calculation and a set of documentation standards. I think it's correct for Skills Fund to first accomplish an easier set of standards given that they're trying to bring more coding bootcamps to the table.
Then would Hack Reactor theoretically also adopt that methodology if other schools agree on it?
Yeah. I'll say that if it is too flimsy for us to stand on, then we will try to kill it in committee. So far, though, the results are promising. Skills Fund is not our first or second methodology that we attempted to get adopted. I would love it if Skills Fund is successful and we will switch over.
Could an online school use SSOM?
Totally. An online school does use SSOM- Hack Reactor Remote!
Does it worry you that schools like DevMountain, NYCDA, and Hackbright Academy are now being acquired by for-profit education companies?
It is definitely two different worlds colliding. I don't really know yet. For-profit education companies certainly have a bad reputation, but I have a more nuanced view of that than others. And I think that generally, the safest person to trust with a responsibility is the person who just destroyed that thing. I'm at least curious to see what happens with the outcomes for those schools.
Why should students be concerned with seeing outcomes at coding bootcamps?
The first thing that a student should know is that we're in the early days of an industry that luckily is taking outcomes seriously. We care in a way that you don’t see even for other career-track programs like law schools. That’s lucky for students!
The bad news is that when it comes to bootcamp employment statistics, there's not an apples to apples comparison right now, and different schools are in varying stages of taking their personal responsibilities seriously. Students should look at how each school calculates its placement rates and you should continue to speak to alumni when you are making your decision process. I encourage students to put pressure on schools that are not explaining how they calculated their placement rates. Tell them that it matters to you.
If I were a student right now, I would almost abandon the attempt to get an apples to apples comparison and instead just look at the rigor of how specifically schools can answer questions and whether or not there is a document that explains it. That's a pretty meaningful signal.
To learn more about the Reactor Core network of schools, read Hack Reactor reviews, MakerSquare reviews, and Telegraph Academy reviews on Course Report. To check out Hack Reactor’s Student Outcomes, here is their 2015 report.
Welcome to the July 2016 Course Report monthly coding bootcamp news roundup! Each month we look at all the happenings from the coding bootcamp world from new bootcamps to big fundraising announcements, to interesting trends. This month the biggest trends this month are initiatives to increase the diversity in tech, some huge investments in various bootcamps, and more tech giants launching their own coding classes. Read below or listen to our latest Coding Bootcamp News Roundup Podcast!Continue Reading →
I heard you were recently at the White House talking about the New Orleans tech scene. Tell us what you were up to!
I was at the White House to talk at the Police Data Initiative event. A nonprofit coding school here in New Orleans called Operation Spark held a hackathon July 2015 focused on the White House Police Data Initiative. We worked alongside the New Orleans Police Department, City Hall Officials, and people from the community – developers and new coders. They released the police data and opened it to us, then we were able to hack on it, create applications, and do data visualizations.
Then we gave the police department feedback on how they could improve the data to be consumable by the public. They took our feedback and released the data in February this year. Representatives from police departments were there to discuss how we could do better in the future. Police departments from around the country agreed to the Police Data Initiative, and pledged to work hard to make their data open to the public.
Well done! What was your background before Hack Reactor Remote and before you even got into coding?
I'm from St. Louis, but I came to New Orleans in 2010 for college. I studied physics and math for two years at Loyola University. My original plan was to finish at Loyola University, with a degree in Math and Physics, and a degree in Engineering, then to go into software engineering. But I wasn't able to finish school for financial reasons.
I stayed in New Orleans and worked in sales for a couple of years and some other odd jobs. I've always been really interested in computers and learning how to code. When I was introduced to Operation Spark, my learning-to-code journey started.
Once you were at Operation Spark, what made you want to enroll in Hack Reactor?
When I got to Operation Spark- even before then- I was really excited about the opportunity. Then when I actually started learning how to code, I fell in love with it. I would be up really late working on projects. John Fraboni, the CEO and founder of Operation Spark, always tells a story about how he would get pings and notifications of me doing my work at 12am, 1am, 2am in the morning, just going at it. I fell in love with it and I didn't really know what next steps to take, but John told me about Hack Reactor and said that it was an awesome program. I just trusted in the process and went along with it.
What was the application and interview process like for the Hack Reactor Remote program?
When I did it, you had to apply online. There was a small coding challenge before you could apply, which encourages you to go Codecademy to teach yourself the basics. Then they give you materials to study in order to prepare for your interview. They set you up for an interview with their team over Skype. You’re asked a bunch of questions to test your knowledge and test how well you do on the spot with new problems.
Did you find that the class you did at Operation Spark really helped you with that application process?
Yeah, it helped a lot. Operation Spark gave me that initial drive and the initial idea that I could succeed in this field. You’re surrounded by people who are already software engineers in the city – their CEO John is actually a software engineer as well. Being in that environment gave me a lot of drive and excitement about what I could achieve because of who I was surrounded by.
What was the overall learning experience like while learning through Hack Reactor Remote?
It was crazy. I had to get used to working 11 hours a day and 6 days a week. People compare it to "drinking through a fire hose.” There's all this information in short, typically two-day sprints, which force you to learn at a rapid pace, and also not be distracted. You learn how to use your resources very, very wisely so that you can get to the end of each sprint. Once you get past the first two days, it's just craziness. In a good way, though!
And what was a typical day like when you were studying?
Typically there's a morning meeting, and then you have self-assessments every week. Then you pair, get your assignment, and it's solo reviewing of the sprint – what you're going to be doing, figuring out the basic requirements, and the time to start coding it. Afterwards you get with your partner and just pair all day long. In the evening, people do a short presentation on some type of technology. After that, you do more pair programming, and then obviously lunch and dinner are in there as well.
What kind of learning platform were you using? How do you stay on track?
A team from Hack Reactor- including full-time software engineers and students from the Hacker in Residence Program- built this platform called Bookstrap. It has the whole curriculum and everything else you need – resources, videos, and lectures.
Did you have just one instructor or were you interacting with a lot of different instructors?
There is a mixture of lab lectures and video lectures, so we had different instructors for the lab lectures and the video lectures. Then you have your technical mentors. There were two or three technical mentors who did town hall meetings during and after every sprint. Town Halls are 20-30 minute sessions where you can ask questions and clear the air on any confusion. We interacted regularly with different people, but they get familiar quickly because you are there all the time.
You were mentioning doing a lot of pairing. Were you paired up with the same person throughout or did you alternate?
No, you alternate. We had about 20 people in the class which gave room to pair with almost everybody over that time, and then towards the end of the class, you get to pick your own pair.
It sounds like you got to know the other people in your class quite well. Where were they from and what kind of backgrounds did they have?
They were from all over. One guy was from Poland. Our “shepherd” from the Hacker in Residence program, who made sure we were okay, was from Switzerland. I had classmates from Korea, and from all over the US. When I later went into The Hacker in Residence Program, that class had a guy in Brazil.
Some people find it easier to learn to code in-person, but Hack Reactor Remote sounds like it works even though you're far away from all the people you're learning with.
It works really well. The reason that it works is because you have to try a bit harder. The people aren't right next to you when you pair, so you have to work around their problems. Working with people who are in different time zones than you is a whole different problem to solve. Also, from the amount of time I spent in pair programming; I have close friends who I've never met in person. During Hack Reactor- especially during the job phase of Hacker in Residence- we talked all the time and shared notes. We still talk all the time in our Slack channels. I think in-person is an awesome experience, but I don't think anybody should rule out the remote experience either because it was great. We had a lot of fun.
How many hours per week were you spending on Hack Reactor work on top of the compulsory 11 hours a day?
During Hack Reactor, the first six weeks is the curriculum phase and then the next six weeks is the project phase. For me, being in Central Time Zone, class was from 11am to 10pm. During the curriculum phase, I would stay up for a couple hours after class, but I would try to get my sleep because this was new and I wanted to make sure I was functioning properly. Unless I was way behind on a sprint or something, then I would stay up. But during project phase and our thesis project, I was up all night. I would go home, and I'd be up working on my thesis project from about the time I got home around 11am to sometimes 4am.
Did you work on Hack Reactor Remote from home or did you find another space?
Since I was had done an in-person class at Operation Spark, they let me and six other people from Operation Spark do the Hack Reactor remote program together in a room. That was really awesome. In the very beginning they tried not to pair us together so we still had to have that remote experience.
I’m excited to take a look at your thesis project- could you share your screen now?
Yes, for sure. I worked on an actual company called Culturalyst. The idea was thought up before Hack Reactor by Sam Bowler, our CEO and founder. We then started building the project during the thesis phase in Hack Reactor and continued working on it. Our product now looks a lot different than our presentation did back then because we’ve been revamping it and building on that infrastructure. We’re going to release it to public, which I'm excited about!
Our team was Mykia Smith, Alice Green, Alon Robinson, Ryan Baskell, Brian Kustra, Victor York, and Sam Bowler, and our product is Culturalyst. Culturalyst is the LinkedIn for artists, where users can find artists they love and fans can directly support artists. Watch below:
That's such an awesome project. So you started working on this for your thesis project and you’ve continued working on it after you graduated?
Yes. It slowed down a bit because some people went into the job search and others were in the Hacker in Residence program, but now we have reassembled. We were actually all in New Orleans together at Operation Spark. We're looking at adding more team members so we can finish the functionality and release it to the public.
What technologies did you use?
We used Angular, Node Express, SQL for our database, and now we're migrating to PostgreSQL. It took about three to four weeks.
Looking back over your time at Hack Reactor Remote, what did you like best about Hack Reactor Remote?
Everything. The staff were awesome. The head of delivery, Liz Penny, is such a character. In our meetings we had “meow offs” where somebody begins meowing a song, and they have to keep meowing it until somebody guesses what the song is.
Because Liz is the head of delivery, her energy transfers to everyone else and makes it a really fun, supportive, and encouraging environment. All the people I met are just awesome. Also, I love Hack Reactor because they taught us how to learn. I don't know everything, but I'm confident that if I have a problem, I can find the resources and figure out how to solve it.
What was your first step when you graduated from Hack Reactor Remote?
I went into the Hacker in Residence program. Since I was part of Operation Spark, the in-person remote, they selected me to help pilot an experiment in Mountain View, California where we opened an onsite extension to the remote program. There were two Hackers in Residence, and a couple of students on site doing the remote program together.
We were called “shepherds” and were in charge of ensuring the success of the onsite and the remote students. We were figuring out if and how will this remote learning works, and reporting that back. We also got feedback from students on how they felt about the program.
After that, I came back to New Orleans in April, went to the White House, then really hunkered down in my job search. And this past Monday, I started working at GE Digital.
Congratulations! What are you doing at GE Digital?
I'm a front end developer. GE Digital is moving into the industrial internet of things. Have you seen a GE commercials lately? They're just making fun of how everybody thinks of GE as an appliance company. But they're trying to let the world know that they've entered the industrial revolution. I will be working on their industrial IOT platform, called Predicts, and building cool stuff on that.
Did Hack Reactor help you with that job search process to find this job?
Yeah. My outcomes coach was phenomenal. She had a lot of experience working with CEOs of companies. She brought that level of expertise to Hack Reactor and helped me in my overall confidence, my negotiation skills, presenting myself as who I am and the value that I'll bring to a company. That was really awesome to work with her and pinpoint those things.
She looked over my resume, and the emails I was sending to different companies. I could hit her up and say, “Hey, I'm about to reply to this company, I don't know what to say,” and she would make suggestions on my emails. It was an awesome experience working with her.
Now you're at GE, what's your day-to-day look like as a Front End Developer?
This is my first week! I’m one of only two front end devs on the team. I've been reading all day long just figuring out the platform, what it does, what it can be used for, and doing the tutorial and the introductions on it. Now, I'm finally getting into the seed application, and I can see how they built that out and see what it does. We're launching a brand new project on July 11th. It's awesome. I like it so far!
Yes. We'll be working with Angular and Polymer, and the back end at GE is built with Java. I'll definitely have to learn Java at some point. The cool thing about GE is that the company is so big that I will have the chance to touch everything. I’m starting on front end and then once I make a lot of progress on that, I can say, “Hey, I want to work on back end” and begin learning Java. Some of their back end is built in Go language, so I'm excited to learn that too. They're really big on getting you where you want to be in the company.
What advice do you have for people thinking about doing an online bootcamp?
I think a lot of people presume that doing an online course like this will give them the freedom that they desire as well. You can find that in some part-time or longer courses, but if you're thinking about going to Hack Reactor Remote, don't underestimate the time commitment because that is really important. You do have to put in a lot of work, and you will be able to work from home, but you can't use that as an excuse to slack off or anything because you will fall behind very quickly.
I had one of the best times of my life at Hack Reactor Remote. It was amazing, and the opportunity that I gained from it and the people that I met from Hack Reactor was completely worth all the hours that I put in. Now I'm employed as a full-time software developer at a very large company. If you're thinking about doing it, do it. Do it. I don't believe that you will regret the decision.
Welcome to the June Course Report monthly coding bootcamp news roundup! Each month we look at all the happenings from the coding bootcamp world, including new bootcamps, what we’re seeing in bootcamps internationally, outcomes, and paying for bootcamps. Plus, we released our big Bootcamp Market Sizing and Growth Report in June! Read below or listen to our latest Coding Bootcamp News Roundup Podcast!Continue Reading →
Welcome to the May 2016 Course Report monthly coding bootcamp news roundup! Each month we look at all the happenings from the coding bootcamp world, from acquisitions, to new bootcamps, to collaborations with universities, and also various reports and studies. Read below or listen to our latest Coding Bootcamp News Roundup podcast.Continue Reading →
After working as a software engineer for 15 years, Fred Zirdung joined Hack Reactor when it launched in San Francisco in 2012. And while he had always wanted to teach, he didn’t realize just how much he would learn by teaching at Hack Reactor. He’s now the Lead Instructor and in charge of developing the curriculum and lecture materials. Fred tells us about how he taught himself to code, what makes a great bootcamp instructor, and the recent additions of ES6 and React into the Hack Reactor curriculum.
Tell us about your background and experience.
I was an engineer for about 15 years before I joined Hack Reactor. I worked at a variety of companies, from Fortune 500 companies to little startups, in various capacities from individual contributor all the way up to key leadership roles.
I’ve been with Hack Reactor since the very first class in December 2012. I started out working part time as what we now call a Technical Mentor. On my weekends, I would help students with issues, questions, and bugs in their code. I joined Hack Reactor full time in July 2013.
How did you learn to code? Did you get a Computer Science degree?
I have an undergraduate degree in Computer Engineering, which is essentially a computer hardware degree. I didn’t really learn that much about software in my degree; most of my software skills are self-taught, through various industries and jobs that I’ve had. Back then I only had books to study from, and a lot of people who mentored me along the way.
How did you become aware of the coding bootcamp model and what did you think at first?
I thought it was an interesting take on education. I thought it was really cool and I wanted to be part of the experiment.
What drew you to teaching at Hack Reactor specifically?
I found about Hack Reactor through a friend of a friend. I’ve always been interested in teaching, but I’d never been interested in going back to college to get a masters degree or PhD – which is what you need to teach at college or university level. I didn’t think my teaching aspirations would ever come to fruition, but then I found out about Hack Reactor’s bootcamp model and decided to pursue it.
Did you have teaching experience prior to teaching at the bootcamp?
Not particularly. But as an experienced developer I would mentor younger and less experienced engineers who I worked with on a regular basis – and I really enjoyed that process.
What do you think is the most important quality for a bootcamp instructor? Is it better to have technical knowledge or be a good teacher?
So you need to have technical capability, but you also need to have a combination of other soft skills. You need empathy, to be able to put yourself in the shoes of a student. You need compassion – sometimes you have to tell students things they don’t want to hear or something at odds with their personal belief, but you have to do it in a way that doesn’t devastate the student. And you need to be able to hold a room and command attention while being approachable.
What does it mean to be Lead Instructor at Hack Reactor? What does your role include?
I teach a number of classes, and some of the lectures. I also oversee the development of our lecture materials and some of the curriculum, so I am the gatekeeper of the content that students see.
Tell me about the Hack Reactor curriculum and structure.
Our curriculum is structured in sprints, which mirror what you would see in a real life software engineering environment. You have sprints where you focus on a particular set of problems you’re trying to solve, so we mirror that same concept here, but on a shorter timeframe. Sprints happen once every two days, then we switch to a different topic. There are many topical based sprints, which focus around a particular core technology. However, often the goal in the sprints is not to teach a specific technology, but it’s about the bigger picture goal – for students to become autonomous learners and autonomous programmers. Hack Reactor bootcamp aims to teach students the ability to be autonomous in any terrain we put them into, rather than giving them strict recipes and paths to follow.
How do you keep the Hack Reactor curriculum up to date and relevant?
Because our curriculum is less focused on specific technologies and more focused on how you think about things, we don’t have to iterate as often on the actual technology components we use. We keep up with what’s going on in the industry; for example we recently added React and ES6. If we notice that a particular concept didn’t land, we will work out why it failed, then fix our lecture materials and content to plug that hole so future students don’t get caught up by the same issue.
Tell me about how you have recently incorporated ES6 and React into the curriculum.
We go through a review process, where we consider various changes, then implement them, and review them. However, our curriculum is pretty full so for us to introduce a new sprint like React, we have to decide what to take out. For React there was another technology we decided to remove, so that created a hole for us to add React. But if we were to consider adding Angular 2, there is already a spot to teach Angular in our course, so we would just replace that. Something completely new might mean restructuring the curriculum to make space for it.
What did you take out which allowed you to add React?
CoffeeScript, which was superseded by ES6. We spread ES6 throughout our entire curriculum, and a lot of features of coffeescript are contained in ES6, so those two technologies are rather duplicitous. While CoffeeScript is not going away anytime soon, it is now outdated.
What made you choose to teach both Angular and React?
We also teach Backbone. We teach Backbone, Angular and React from different perspectives. Sprints are focused around a particular piece of technology, but we are teaching people to think about programming, rather than the technology itself, so there are often secondary goals associated with each sprint. So Backbone, for example, is an extremely useful teaching tool for understanding the concept of decoupling modules in various ways. But Angular takes a completely different approach to dealing with dependencies, so it’s a fantastic technology to use when teaching dependency injection, which is another way you can deal with software dependencies.
There are a lot of popular frameworks out there, but we can’t teach all of them. We chose these ones because they have secondary pedagogical objectives.
How often do you make changes or updates to the curriculum?
Removing a sprint and adding a new sprint happens a few times a year, but our curriculum is changing every cycle – every single class gets a new version of the curriculum. We are in fact sometimes changing curriculum literally up to the day before students arrive because we are always aiming for the best possible experience. A lot of times there are hundreds of little tiny changes in there that are barely noticeable, but over the course of three years, there are vast differences as those little changes accumulate.
It’s one of the things I’m personally proud of that we are able to do. We’re really organized in term of our feedback cycle, getting feedback from our students and our observations on how curriculum landed in the past, so we just stay on top of that very regularly.
Do you ever make changes on the fly?
When appropriate yes. We try to avoid those scenarios because it can be confusing or frustrating for students.
What have you found is your personal teaching style? Are you hands on, do you like to lecture, do you let people get stuck and figure things on their own?
When I’m up lecturing I try to have a balance of all three. Sometimes there are concepts that warrant me just talking while students listen. There are other times when I like to let them struggle with a concept. Oftentimes I will play quizzes or games with the students to help identify dissonance in their thinking and problems with their mental model, and usually I find one person’s problematic thinking is reflective of many people in the room.
We’ve heard that some Hack Reactor lectures are delivered through video- why is that?
We have a small number of videos, but most of our lectures are delivered live. The ones that are delivered via video on site are solution demonstration videos. For each sprint challenge, we find it useful to give students the solution, or at least one possible ideal solution, so they can learn how an expert might approach a particular problem. We do that via video specifically because we want students to be able to go back and refer to the content on their own, in their own time.
What resources or meetups do you recommend for aspiring bootcampers?
Hack Reactor has a prep program, called Reactor Prep, that is aimed at beginners. It’s a really good way to get a taste of what the bootcamp is going to be like. We also have Fulcrum, which is for students who are more advanced and already have some of the knowledge covered in the Reactor Prep program. Both programs charge tuition but you can credit the cost of Fulcrum towards the Hack Reactor program.
To get a taste for programming in general there are a few things I recommend. Wherever you are, look for programming meetups in the language of your choice. There are tons in San Francisco and most of the metropolitan areas. It’s a great way to network, meet people in the industry, get tips, and see presentations on interesting programming topics.
What do you like best about teaching at Hack Reactor?
I love interacting with the students. In every cohort there are a bunch of new faces who come in with interesting stories and interesting backgrounds. It’s really great to interact with them, but also from a teaching perspective, every new cohort is a new challenge. Students challenge my thinking on concepts all the time, and that’s a fun way to learn new things.
Tyson had been an entrepreneur since the dot com bubble, starting and helming numerous tech companies for 14 years. In 2013, after watching the internet startup founder 'prototype' transition from an MBA to a software engineer, he decided to gain this skillset himself, so he enrolled at Hack Reactor to become a more effective entrepreneur. But Tyson’s goals changed. After graduating from Hack Reactor, he started a nonprofit to teach kids to code, and then became a senior software engineer at Nike. Tyson wasn’t expecting to fall in love with coding, but discovered he enjoys it as much as company building and product development.
What is your pre-bootcamp story? What was your previous career path and educational background?
Since 1999 I’ve been an entrepreneur and general manager of fast growing consumer, internet and mobile companies and products. My first company was a music discovery platform called Gigmania, providing live music content to Yahoo, AOL, and MTV. During the 2000 downturn we sold it to a big concert producer.
In the early 2000s, most digital company founders were Harvard and Stanford MBAs, so I decided to get an MBA. I went to INSEAD, an MBA program outside of Paris. After that I started an internet gaming company called Pixelfix, and then I joined a company in NYC called Bold Media, an early social network where I ran their games and business development units. Then I moved to the West Coast to run the internet development group of media company Future. After that I joined a social activity ad tech company called Appssavvy, where I ran the publisher side of the business.
In 2013, I had an idea for a new business. I talked to engineers who I’d worked with in the past and to Pivotal Labs in San Francisco. But ultimately Facebook's 'Hacker Way', which reflected the startup culture of the SF Bay Area, convinced me that to be a more successful, creative and agile entrepreneur I needed a deeper understanding of technology, and the skills to build prototypes myself. It was with that goal in mind that I went through Hack Reactor.
So you had been involved in managing and running all these companies, but had you been involved in building the products?
In all my roles I’d been deeply involved in product development, but I’d never written a line of code.
What made you want to be able to build those prototypes yourself and write code yourself?
For a couple of reasons. In 2001 when I got an MBA, most early stage company founders had MBAs. But by 2013, it was now engineers building their own prototypes. The market had shifted, so to be relevant in the industry, particularly in early stage companies, I was doing myself a disservice by not having a technical skillset. You can be a lot more agile and iterate more rapidly if you’re creating the product prototype yourself. It makes me more flexible, and on the management side it would make me more effective at working with engineers.
Did you try to learn on your own before you thought about a bootcamp or did you just dive into the bootcamp?
No, I pretty much decided I wanted to do this quickly. I should have started this process years ago, but I didn’t. So I quit my job and joined Hack Reactor. An immersive learning environment made a lot of sense. And I didn’t have time to go to back to college; there’s way too much slack in that traditional education path.
Did you research other bootcamps or just Hack Reactor?
Was your class diverse in terms of gender, race, life and career backgrounds?
It was pretty diverse- around 33% women. People had varied backgrounds, but I was the only one who had never done any coding before. I passed Hack Reactor’s admissions coding challenges, but everyone else had been writing in another language or knew another language. Some had done Dev Bootcamp and were now doing Hack Reactor, some had studied computer science in college. I had the least exposure to code, but I had a ton of relevant industry experience.
What was the age range in your cohort? We get a lot of questions about whether people in their late 30s or 40s should do a bootcamp, and whether they can get a job easily after graduating – what’s your take on that?
There were a few people in my cohort over 35, then there was one young person under 20. Everyone else was in the in 22 to 35 age bracket. Everything seemed to work out well for those in the older age bracket. I think one of the people in the older bracket is now a Hack Reactor instructor. But there is an age bias in Silicon Valley – it’s a cultural thing. I am currently a senior web engineer at Nike in Portland, Oregon, and I would say there’s no age bias here, and many of the engineers at Nike, perhaps half, are over 35. So I think it depends on the type of company you want to work for.
What was the learning experience like at your bootcamp — typical day and teaching style?
It was like being caught up in an information tsunami! We started at 9am, we would have a very light lecture, then you could choose to stay on for the second part of the lecture, or start the coding challenge. There was a lot of guided self learning, which was a very effective way to instill the discipline we would need on our own, or in a job to figure out how to solve problems. There was very little front-of-the-room lecture time. But tons of availability for advanced people to discuss advanced ideas, or for beginners to get help when they needed help.
What sort of projects did you work on?
My own personal project was called Yummy Show. It was an online cloud-based software for presentations, leveraging reactive data and data visualization. I thought learning D3 was really cool, and realized if I had known D3 when I was in business, my business presentations would have been much more effective. With Yummy Show I wanted to enable people to make their presentation data come to life without knowing how to code. The group project we worked on was a kids interactive game using the computer camera and HTML5, for face and object recognition.
Tell us about Mission Bit and what you did after graduating from Hack Reactor?
When I graduated from Hack Reactor in June 2013, I spent the summer building up Mission Bit, and launched the first classes at the end of summer. Mission Bit is a non profit providing computer science education pathway for public high school kids. The teachers are volunteer professional software engineers from top companies and startups in the Valley. We bring the kids to different companies to show them what they can do with coding skills. We try to convey to kids that this skillset is a booster for your life no matter what job you choose. You don’t have be a software engineer – if you were a farmer, you could write scripts to work out how weather is affecting your crop growth rates. Whatever job you choose to do, coding skills will help you do it better.
How were you using your programming skills at Mission Bit?
I built some software for our volunteers and students to use for class scheduling and for attendance tracking. I also built a text message management platform called Yummy Text. One challenge we had was communicating things to students across classes. Kids just don’t read their emails, and they didn’t want to download a Mission Bit app, but they all had cell phones so the most effective way to communicate was via text message.
When and why did you decide to start looking for engineering jobs?
While I was running Mission Bit, I set up a shell company where I could prototype different ideas, so I was building products all along the way. Initially I’d decided to learn to code to be a better entrepreneur and be more effective at iteratively making products. But I realized that I love the process of coding and I love the problems you have to solve. I love the scope of the knowledge, not just the end point of having the finished product. So that was when I decided I wanted to work and become a better engineer. So I started the search and took this role at Nike.
Tell us about your job at Nike.
What does a typical day look like for you these days?
We have stand ups at 9:15 am and 11 am, with sprint planning on Mondays. I deploy to production twice a week on Tuesdays and Thursdays. When I’m not in standups and sprint planning, I’m coding – it’s all coding all the time, and it’s awesome. I know I like coding my product ideas. Luckily, I like building other people’s products too!
How does your schedule and life compare to when you were working as an entrepreneur?
I work all the time anyways because I have all this other stuff. At Nike I put in about 40 hours a week, but I fly to Portland for work from San Francisco on Monday mornings and come back Friday night. I’m on a couple of different boards, and I’m always trying to learn new stuff. So I have entrepreneurs’ hours regardless. I don’t know how sustainable the lifestyle is, but it’s totally working for now and Nike is an awesome company. That was the main reason I wanted to do it.
What’s been the biggest challenge for you since you graduated from Hack Reactor?
Being a middle aged man figuring out what to do through a midlife pivot. Seeing the reflection of yourself in your kids makes it impossible to dodge things you’ve maybe tried to dodge in your life. That forced me to reevaluate what I was doing, what I was working on, and make sure I was focused on doing things I truly wanted to do. I would say working through all that was hardest thing. Hack Reactor was part of that process of changing myself.
What sorts of things are you doing to maintain/learn new skills?
Recently it’s been playing around with React and Redux and getting familiar with those frameworks, and getting familiar with Angular 2.
What advice do you have for people wanting to change their careers after a long career and take a bootcamp?
I kind of fell into the change. I wanted to use it as a propellant to what I was already doing, and just realized through that process that I liked building stuff with code. But my advice is to be clear about what you actually want after a bootcamp. Either you know you love being an engineer or you know this new skillset will help you attain or achieve your specific goals, because bootcamps are intense and you basically shut off your life to do it for three months. To get the most out of it you need to love the thing you want to be, whether it’s an engineer or CTO or a better entrepreneur.
Any final comments about Hack Reactor?
The Hack Reactor community is very special and I attribute that to the relationship among the founders, because those guys are really tight, and that permeates through the rest of the community. The community is solid, energetic, and really helpful, and the founders are super invested in nurturing and catalyzing that energy and possibility.
How long does the Hack Reactor application typically take? What are the steps applicants should expect?
The process is quick and relatively simple. Applicants first take a simple coding challenge to show that they have command of basic concepts. Once that is completed, they move on to a technical interview. And that’s it! Applicants typically receive a decision within 10 days of the technical interview.
Admissions Coding Challenge
Does everyone take the same coding challenge? Can you give us a sample question?
How long should it take? Is there a time limit?
How should a beginner prepare for the admissions challenge? Who is the right candidate for Hack Reactor Fulcrum vs. preparing on their own?
The best way to prepare is our Reactor Prep and Fulcrum courses. Prep is built for coders who have dabbled, but don’t feel comfortable building apps or interactive web pages. Many Prep students have gone on to be admitted into our 12-week program.
Fulcrum is for intermediate coders who want to get to the next level and have the optimal preparation for our immersive course. Fulcrum students are invited to a technical interview after completing the course, and may subtract their Fulcrum tuition from their immersive tuition.
While self-study can be a good way to introduce yourself to basic programming concepts, we’ve found that many people get lost in the resources and need more structured guidance in order to reach their software engineering goals.
What goes into the written application? Does Hack Reactor require a video submission?
Neither, actually. Students need only complete the coding challenge and technical interview.
Will interviewees need to walk through a technical problem during the interview?
Yes, the interviewer and interviewee will work on a technical problem together. The interview is not just a test, but a chance to learn and experience the Hack Reactor teaching method. Applicants are encouraged to examine the underlying logic of their code.
How do you evaluate an applicant’s future potential? What qualities are you looking for?
We look for students who respond well to challenge and uncertainty, and who are clear, empathic communicators. Some coding ability is important, but we are more concerned with students’ willingness and ability to learn, than with what they already know. Identifying these qualities has been a key element to our students successes.
Can applicants do the Hack Reactor interview in-person or are all interviews conducted online?
Applicants can do whichever is more convenient for them. Our online program, Hack Reactor Remote Beta, does online interviews. Like with the entire immersive course experience, Hack Reactor Remote Beta brings the full coding interview to an online format.
Are students accepted on a rolling basis?
What is the current acceptance rate at Hack Reactor? Is a low acceptance rate important to Hack Reactor?
A low admissions rate is an arbitrary benchmark, and is not important to us. What’s important is a high and consistent quality standard. We are exclusive, but not for exclusiveness’ sake: we require our students be hardworking, growth-oriented, and curious learners.
What types of backgrounds have successful Hack Reactor students had? Does everyone come from a technical background?
One comment we often get from employers is how refreshing it is that our candidates are from diverse backgrounds – culturally, academically, and in terms of work experience. Many students have technical backgrounds, but we also have many career-changers, and others who have been coding for weeks or months, not years. This is a result of our admissions process: we screen for communication skills and growth mentality as much as, or more than, coding chops.
Does Hack Reactor accept international students? Do international students get student visas/tourist visas to do the program?
We do accept international students. While we don’t offer official advice on visas, many students have made it work, and have found employment in the Bay Area or back in their home country.
It’s easy to apply to multiple schools at once, but each school makes their own decision. Applicants that apply to multiple schools have a better chance of getting into at least one program. However, we suggest that students do the research about the various schools in the network to choose two to three that fit their personal goals and learning style.
Can rejected applicants reapply? If so, how many times?
It is rare that we fully reject anyone. Generally, the worst case scenario is that we ask you to reinterview after more study. It is not uncommon for applicants to get in on their second or third try, sometimes after taking our Prep or Fulcrum courses.
Are Coding Bootcamps the new "replacement" for college degrees? Or are bootcamp grads missing out on valuable Computer Science theory by opting out of a traditional CS degree? As coding bootcamps rise in popularity, they face both praise and criticism- but what is the real difference between these two education paths? Join Course Report and our expert panel (seriously, these folks are running the best bootcamps in the world) to dive into this topic: CS Degrees vs Coding Bootcamps.
We're so excited about the panel joining us for this webinar:Continue Reading →
How much do coding bootcamps cost? From students looking for free coding bootcamps to those wondering if an $18,000 bootcamp is worth it, we understand that cost is important to future bootcampers! While the average full-time programming bootcamp in the US costs $11,451, bootcamp tuition can range from $9,000 to $21,000, and some coding bootcamps have deferred tuition. So how do you decide what to budget for? Here, we break down the costs of coding bootcamps from around the USA.
Welcome to the September News Roundup, your monthly news digest full of the most interesting articles and announcements in the bootcamp space. Do you want something considered for the next News Roundup? Submit announcements of new courses, scholarships, or open jobs at your school!
This Week on Course Report:
- Should you learn web or mobile development first? We dive into this question with advice from Atlanta's DigitalCrafts code school!
- Have you tried Thinkful's Workshops? Grae, the Head of Education at Thinkful, gives us the scoop on their newest offering for bootcamp grads and working engineers.
- Mechanical-Engineer-turned-Web-Developer Kacy Ebel talks about her career change and her experience at We Can Code It's women-only bootcamp.
Aquisitions, Fundraises & Regulation
- General Assembly announced their $70MM Series D. This reporter thinks about what the fundraise could mean for their London campus.
- Hack Reactor acquired Chicago-based Mobile Makers Academy, adding iOS to their offerings. They also announced "Hack Reactor Core," the umbrella under which each school will operate autonomously.
- Inside Higher Ed reported on General Assembly's journey through regulation and expansion. Education Dive provides a nice, brief summary of the article.
- The Huffington Post reported on a letter from Jeremy Shaki and Khurram Virani (Founders of Lighthouse Labs) to parliament on code literacy, outcome-based education, and Canadian innovation through technology.
New Campuses + Courses:
- Dev Bootcamp announced they will open doors in San Diego this November.
- Montana Code School's first cohort started class September 28. (Listen to Montana Public Radio's story on the bootcamp).
- ThoughtKite will teach their first Toronto iOS bootcamp in October.
- Code Fellows has overhauled and reorganized their courses (bye bye Dev Accelerators, hello Code 401!)
- Applications for Code Platoon, a Chicago bootcamp geared towards veterans, are now open.
- Global News Canada writes about Toronto's Bitmaker Labs.
- Fortune Magazine explores women in Coding Bootcamps.
- FCW finds that coding bootcamps are 'Very empowering, very transformational.'
- A LinkedIn researcher blogged about the types of jobs reported by bootcampers on the networking site.
- Delaware Online looks back on ZipCode Wilmington's first bootcamp cohort.
- Built in Chicago: How Designation is bringing the bootcamp model to design.
- Milwaukee Journal Sentinel: Milwaukee computer coding school expands as employers show interest.
- The Street: Future Code Monkeys May Skip College and Head to Boot Camp
Have a great October!
Are you planning on attending a coding bootcamp? Deciding between two bootcamps? We’ve scoured the net for alumni blogs from top coding bootcamps including Fullstack Academy, Dev Bootcamp, The Iron Yard, Coding Dojo, MakerSquare and Hack Reactor. From a CS major to an event planner, these bootcamp graduates give you a snapshot of what makes each coding school and experience unique.Continue Reading →
After a career in IT, Casey Garland realized his love for building and joined Hack Reactor's Remote class while living in Pittsburgh. We talk to Casey about the logistics of the remote course, the differences between Thinkful and Hack Reactor, and his advice to future Hack Reactor Remote applicants.
Tell me what you were doing before you started Hack Reactor.
I got a bachelors and masters degree from WGU which were both remote, online learning as well. My degree is in Information technology and my masters is in Information Security. I’ve been working in technology for about 10 years on the IT side of things, and then I managed a software development team and found out how much I liked building. Eventually, I decided to quit my job and I joined Hack Reactor.
Did you do Codecademy or other online programs to introduce yourself to programming before applying?
I’d been exposed to programming over the years but I really started this year, I started doing Codecademy but it wasn’t enough so I actually did Thinkful’s front-end developer program and that jump-started me.
So between your undergrad and Thinkful, you were confident in online remote learning beforehand?
Yeah, definitely. I was looking at Hack Reactor before they announced their remote program. I have a wife and a small baby in Pittsburgh; I couldn’t just go to San Francisco for three months on top of not working and paying tuition. The reviews and everything were so overwhelmingly positive I didn’t think it was possible for it not to work.
What was the application process like for you?
They’ve got a pre-interview technical challenge that we did but my understanding is that they don’t do that anymore. Then I had a technical interview with one of the Hackers in Residence and I found out about a week later that I was accepted.
Who were your instructors during the class?
Shawn Drost, who is one of the cofounders, was our main point of contact. Our lectures were primarily done via video. We would have a video of the onsite lectures and then we would follow up with Sean or somebody else afterwards if we had any questions.
Did you ever have live lectures or were they all recorded?
Well, we only had one live lecture. We had one live lecture where somebody actually that taught that lecture did it in person for us live. In the technical part we only had one. Once we had gotten to the hiring phase in the last couple of weeks, we had more live lectures.
Can you tell us how the recorded lectures work logistically?
They use Vimeo. The first half of the program was really scheduled out in advance and it was very clear what you were supposed to be doing in a given time. We experimented with different ways of asking questions during the video and things like that. I think what ended up working best was just freeform. We have a group chat that’s always active and people just pop in and ask questions.
Did you have lecture in the morning and then work on projects in the afternoon?
Yes- everything’s split into two-day sprints so you have a lecture then you go explore the problem then you have another lecture. Then you have the rest of that day and the beginning of the next day to work on the project for that lecture.
What was the second 6 weeks like?
The first 6 weeks are really hands-on technical learning. The second 6 weeks are project based; so the majority of it you’re just working on different projects.
Were you working on those as a team or individually?
As small teams.
So you were interacting with the other students in the remote program.
Yeah, it’s really interactive. You interact with the other remote students a ton.
Were there any hiccups with timing or issues like that?
Yeah, there were some. They weren’t as big of a deal as you would think. One of the guys was actually from Nigeria and he had all kinds of connection issues. I’m on the East Coast so I worked from 12pm-12am every day, which is kind of weird. You get used to it. That didn’t end up being as big of a deal as I thought it would be.
Were you all pair programming or doing Google Hangouts?
All the above. The first half was all pair programming and you were on Google Hangout at the same time. I probably got in a hangout with my group 4 or 5 times a day.
Do you feel like Hack Reactor adapted the program to what people needed, since this was the first cohort?
Yeah, definitely, within certain bounds that they’d established. I think they take that approach with the onsite as well. They really take an iterative approach to what they’re doing.
A few times we gave them specific feedback about something and the next week we were doing it a different way.
What were the differences between your experience with Thinkful and your experience with Hack Reactor remote?
They’re not even the same thing; they’re so different. For me, Thinkful was a way to see if I actually like writing code, if I could be any good at it. It’s relatively low cost and there’s no risk whereas Hack Reactor is so expensive and such a commitment that there’s a huge risk. And Hack Reactor was 12 hours a day. I probably did 12 hours a week for Thinkful. That being said, I would still highly recommend Thinkful.
Can you tell us about a project that you worked on during those 6 weeks that you were particularly proud of?
I have one big one and one small one I’ll tell you about. The big one was a group project that we did and we built a platform for a small businesses to mobile-enable their employees. So instead of filling out forms on paper in the field or filling out a spreadsheet, they go to backend out of Node and Mango and the Mobile Apps from Ionic and Angular that allows them to fill out forms on their mobile devices.
The other one was just a little side thing that I did to help me put together the best fancy football lineup. And I actually won a contest that had 14,000 entries in it this past weekend.
How has Hack Reactor layered in job placement?
I wouldn’t call it job placement. I think they do a really good job with the resume building and with preparing you for the interviews and preparing you mentally for the best approach at getting a job. I think they do an awesome, fantastic job on that.
We were the first remote program; they were trying to figure out how they can best actually help get in contact with the people. They have such a great presence in San Francisco and I think almost half of our class went to San Francisco to try and find a job there but five of us are still trying to find jobs back home or remotely. The contacts they have outside of San Francisco are not as plentiful, but they are working on that.
Did you meet with potential employers throughout the program? Were you given access to that network?
Not throughout the program. It’s pretty concentrated in the last week. We will have met with 5 employers by the end of the week.
Have you done interviews?
Yes, and I already have two offers. I didn’t apply to these jobs but I did update my resume on LinkedIn and Career Builder and I had several people call me last week and I set up interviews for this week and I got two offers out of it.
Are either of those jobs remote or are they in Pittsburgh?
They’re both in person, in Pittsburgh. I’m definitely open to something remote. I’m kind of freelancing now, too. I don’t know that I really care that much whether it’s remote or in person. I just want to like the people I work with and like what I’m working on.
Is there anything else you want to add about Hack Reactor that we didn’t touch on?
Overall, I’m super satisfied. I definitely would make the same decision again. I would recommend if the person was able to, go in person. I think you’d probably get a better experience in person, just judging from all the reviews I saw from the in person people.
After going through it, do you think that there’s a type of person who wouldn't do well or wouldn’t excel?
I feel like we had a lot of different personalities. We only had 10 people but still there were different personalities. You just have to be willing to do the work; especially the first 6 weeks. It’s so hands-on. The second half you have to be a bit more self-motivated. But if they can get into the program they will probably do just fine.
After working in animation for ten years, Chris Bradley was ready to head back to the East Coast and change careers. He was looking for a high-quality remote programming course, so he applied to Hack Reactor's newly announced Remote program. Check out our interview with Chris- it's full of useful information about the Hack Reactor admissions process, what to expect when learning online and how the Remote course compares to the in-person option!
What were you doing before you started at Hack Reactor?
I had attended an MFA program with an emphasis in computer animation. and then worked for about 10 years as a visual effects artist in Los Angeles. I created visual effects for commercials, television and film, finally ending up at DreamWorks Animation doing character effects.
What made you want to change careers?
Throughout my visual effects career, there was often some level of scripting involved. I wrote little tools to do certain things and worked with third party vendors to see what the current state of their technology was in order to decide between partnering up with them or writing something proprietary in-house.
So gradually, my career took me closer and closer to the development side of the industry. I never got to a point where I was actually a software engineer, but it seemed like a really neat space to be in.
So you were not a beginner when you started at Hack Reactor.
Probably not. I had done some scripting in Python, as well as MEL (Maya scripting language) and VEX (Houdini scripting language) but I always struggled to get good at scripting. I just never had the time to dedicate to the kind of thinking behind how to do it well.
When did you decide to start looking at bootcamps?
After being in L.A. for about 10 years or so, my wife and I decided we wanted to be closer to extended family back on the East Coast and I left DreamWorks without a concrete plan of what I was going to do. We ended up in Central New York, the flip side of picking a rural area being that there aren’t a lot of job prospects. I was looking at what the remote world had to offer wondering: “are there any viable career solutions or career opportunities?” I really felt that I could leverage a lot of my experience, interests and passions to create a good life for myself.
Did you look at other online bootcamps like Bloc and Thinkful?
Actually, I completed Bloc last year before joining Hack Reactor. As I did my preliminary search I looked at all the options and quickly honed in on the half a dozen or so that had credible reputations.
Did you look at any in-person boot camps?
No, I didn’t. I’m about three hours from New York City which at the time had the closest on site program. We had just gotten settled, so spending three months away from my family wasn’t really an option, and Bloc was the only boot camp that seemed to have a comprehensive offering that included some form of mentor or instruction, which I felt was important.
I spent some time on Treehouse and Code Academy and I think they’re great for getting introduced to programming, but you’ll never learn how to be a professional programmer through those sites. At the time, Bloc was the only one that offered one-on-one mentorship, which I think was a great initial support mechanism; there was someone you could actually ask questions and get a direct answer from.
The truth is, I picked Bloc because it was remote. Going to one of these places onsite for three months was kind of the opposite of what I wanted for myself and my family.
What was the application process like for Hack Reactor Remote?
Hack Reactor does its brand and its students a great service by being very selective with their admissions process. I’m going to speak about what I went through, although I think it’s changed a little bit since they’re constantly iterating based on feedback, which is really cool.
Once I submitted that, it opened up access to a chat application. They’ve got a chat bot, I think it’s on Firebase, that is just generating random chats and you basically have to interface with it using Ajax, JQuery and the like. It’s an exercise that’s intended to force you out of your comfort zone and to rely on your resourcefulness to get it done.
At the time, you weren’t even allowed to schedule a technical interview until you successfully completed that exercise.
After you successfully complete the chat bot you are allowed to schedule a technical interview. It’s probably a standard tech interview, about an hour long, with a few minutes of ‘why are you doing this?’ kind of thing and then it’s about 45 minutes of paired coding. It’s not for the faint of heart- it’s basically about getting very comfortable with anonymous functions and call-back functions and how to use functions as arguments to other functions.
Again, I think that by establishing that base level just to get in, they’re setting up their students for success in the long haul by accomplishing two things: setting the bar high from the get-go (last I checked, their acceptance rate was between 3 – 5%) and creating up a baseline that all students can start from.
This is important given that a lot of people with a wide variety of experience are going to be applying to the school. Some people come in with what I would call a moderate tech background, others with CS degrees, and others who were previously lawyers or whatever - with little experience in tech. Students come from all walks of life.
Other coding schools don’t really do this and consequently have to keep the curriculum down to the lowest common denominator, so you wind up spending a lot of time on basic fundamentals, which may not be appropriate for the entire class.
Was there anything that you were hesitant about or were you pretty much convinced during the interview and application process that Hack Reactor Remote would be a legit use of your money?
It’s a few hundred dollars shy of $18,000 which is the same price as the on-site program. That is psychologically different from most other coding boot camps that offer both onsite and online with a substantial discount for the online classes. In that case, the question becomes, why is the online version cheaper?
Once you get over the initial shock that it’s the same price, your expectations are that the experience is going to be as good as onsite. And once you start thinking about it that way, a more appropriate question to ask is, why are other places charging half as much for the online version? Is it half as much the experience? And if so, why are they doing it?
I think Hack Reactor, over the course of their two years, had opportunities for expansion. They could have gone to satellite locations and opened up offices, or almost franchised the school. They were very, very concerned about the quality control of the curriculum and they felt that it would be much easier to manage from one central location and distribute it over the web as opposed to opening up satellite branches. I think they had just as high expectations for the remote program as they do for the onsite program and based on that, they charge the same. It did take a little while to process that but at the end I think it makes total sense.
Everything’s going to be a leap of faith and I think a lot of it is tempered by their placement statistics. So you have that to offset any kind of the risk. You have to do your due diligence and make sure that you’re clear on what you’re getting out of it.
I want to talk about logistics for a bit- tell us how the remote classes work?
Hack reactor is 6 days a week, 11 hours a day of scheduled activity. That’s basically the minimum expectation, and you wind up spending, on average, a couple of hours more per day. Hack Reactor wants to make sure you never run out of stuff to do - they provide so much structure and so many opportunities for activities and stuff to work on that you could never finish it all.
Do they put a camera in the lecture room for you?
Initially, it was exclusively recorded lectures. What they’d been doing is recording the lectures from previous cohorts and giving us access to those. It’s an interesting format; we don’t get the benefit of actually being able to ask the instructor a question in live real time – but at the same time, we get the benefit as remote students of being able to pause, rewind and replay the video, which onsite students don’t have, so it’s a little bit of a trade-off.
What’s phenomenal about Hack Reactor in general is that they’ve taken an innovative iterative approach to teaching and their curriculum. Durring the first six weeks in the junior class, the 6 days of the week are broken up into three two-day long sprints. The first day in the morning, the topic will be introduced. You’d get a brief introduction lecture to a topic and then they’ll give you to a couple of hours to pore through the project documents and do some background research. Next, there’ll be a specific targeted lecture that’s kind of the meat of the project and then we pair up and hack away for the rest of the day.
At some point the following day there’s a solution lecture and then you have the rest of the day to finish up your project based on the best practices you learned about in the solution lecture.
This would be on a two-day cycle (called a “sprint”) that finishes with a sprint reflection that starts with about 5 or 10 minutes of just throwing out ideas on what you liked or didn’t like about the sprint. The class then votes on each topic to achieve consensus and pick 2-4 of them to discuss in detail.
And you were able to participate in that feedback?
Yes; this was done with the remote students just as it is with the onsite classes.
Would you use Google Hangout?
Yes. We heavily relied on Google Hangouts to come together and share a screen to have these kinds of dialogues. An amazing part of the class is that, if something was not working, Hack Reactor would come up with a fix within a few days. It was a very iterative process in that way.
As the course progressed, we started to get more access to instructors. There was some feedback saying we felt we were not getting the same experience as onsite so they would bring instructors in and give a lecture over Hangout. It was just really cool that they were able to adapt to our feedback immediately and import modifications to the program to address those concerns.
Were you ever able to interact with other students, remote or in-person?
There is a ton of interaction among your remote classmates and the Hack Reactor experience is completely built around the idea of pair programming, so there is very little time where you are doing anything by yourself.
So pair programming was an easy process even though you were remote?
I’d never done pair programming before and I feel like that whole experience translated very well to the web interface. We were using a really cool service called Floobits which basically allows you to synch up tech Sublime Text sessions. It’s a live code-sharing system so as you were typing, you see what the other person’s doing.
Once you have that combined with something like Skype and Google Hangouts, it really is just as good as sitting right next to somebody. So that experience translated incredibly well to the web.
How are the Bloc and the Hack Reactor remote programs different or similar?
I think you have to take a step back and look at the intent of each program. A year ago, Bloc positioned itself as “zero to web developer in 12 weeks.” I think they’ve reframed their expectations and now they say ‘learn the fundamentals of web development in 12 weeks.” Their intended results are just different.
Because the intended outcomes are different, the experiences are choreographed to be different. One of the ways Hack Reactor measures themselves is in their hiring placement statistics. They’re really making sure that they’re investing a lot in the program to develop those kinds of people. Since employability, for those immediately seeing jobs, is a big goal, they’re also concerned with recreating what it’s really like to work as a software engineer and recreating that experience. There’s an emphasis on pair programming, as well as thinking about the more theoretical aspects of application design like time complexity, algorithms and that kind of thing. I think they’re aiming for different results.
How were the instructors and how did you interact with them?
It’s the same instructors for the whole school. When we were watching the recorded lectures, they were recorded from the onsite presentations with the exact same instructors. I should mention as an aside, Hack Reactor probably has easily some of the best teachers I’ve ever encountered anywhere. They clearly have mastered the discipline and they have also mastered how to teach it. Even the recorded lectures far surpass most of the live lectures I’ve had in all my education up to that point.
I highly recommend that you go on YouTube or Google anything that Marcus Philips has presented and you will see what I mean; it’s incredible.
Hack Reactor also has one of the best Angular developers on staff, Scott Moss, who wrote the ngFX library. He’s onsite and actually came into our class to teach a live lecture over Google Hangouts when we had our Angular sprint. They’re very much experimenting with the format and trying to figure out which works the best. That’s really what they’re concerned about; providing the best experience possible.
You were saying the first 6 weeks is more lecture-heavy. Is the second week more project-based?
Yeah, I’d say there are more lectures in the first 6 weeks but you’d still have most of your time to spend hacking away. They’re basically done in the form of test-driven development. They give you a skeleton project with a bunch of failing tests and it’s up to you to look why the tests are failing and try to make them pass. Then you transition from the junior class to the senior class, which is the project phase of the course.
We did one solo project which was a two-day sprint and then a pair project which was another two-day sprint, then two more small group projects, about a week in length, and finally a large group project which took up three to three and a half weeks.
Can you tell us about one of the projects that you did that you’re particularly proud of?
One that I had a lot of investment in was a Spaced Repetition review app. Spaced Repetition is a method for studying and reviewing material. It’s essentially like flash cards on steroids with a really powerful method and a ton of data to back up its effectiveness.
The premise is basically that you get a flash card, it asks you a question which you answer, and then it reveals the answer and you rate how easy it was to recall the answer. Based on how well you rate yourself, the application has an algorithm that determines when the next time you’re going to see that card is. If you have a really hard time answering the card, it’s probably going to bring it back at a shorter interval. But as you get more confident and your ability to answer the questions becomes easier, it’s going to start staggering those intervals out to longer and longer intervals.
We did this project in Meteor, which was a ton of fun to work with. I got to implement the algorithm, which was really cool and hands-on.
There was another really cool project I didn’t get to work on but one of our other groups completed for their thesis project. We were using Google Hangouts for the whole class and it’s not the greatest. So they wrote their own Video Conferencing library Google Hangouts with much better video quality and much better audio quality and much more reliable in general. So there were some pretty cool projects.
How does the remote program incorporate job placement and job readiness?
I can speak to this to the extent that I’ve got experience with it but I should also say that I was invited to participate in the Hacker In Residence program, which pulls me out of the job hunt. It’s basically a post-graduate fellowship with the school. I’ll be doing that starting Monday. This last week is the actual week of the job hunt where they have a job day hold a hiring day. This is basically like a job fair where 30 or so companies come in onsite and each student interviews with about 6 companies. They’re currently setting up a similar hiring day experience for the remote students.
Leading up to the actual day when you’re face to face with prospective employers, all of the job preparation is identical to the onsite in that you get tons of experience doing mock interviews and help on how to craft your resume which includes an audit to ensure the most effective presentation of your personal story. Remote students received over two hours of live lecture time with a recruiter from Microsoft, getting real hands-on feedback on our presentation skills and how to pitch our selves. The experience is identical to what onsite students get.
You had mentioned a hiring day. How do they do that for the remote class?
I didn’t get to participate in that because I took the Hacker In Residence position but my understanding is that they’ve lined up five or six employers to do a series of hangouts throughout the day for the remote students, trying to replicate the onsite experience as much as possible. So they have an allotted time for the hangout with the particular employer; you talk to them and then you move on.
For your Hacker In Residence program, are you going to be working on the remote program specifically?
It’s basically part-time work directly for the school. In my case, I’ll be doing admissions work. The rest of the time we’re just expected to work on projects of your own desire and if it benefits the school and is something they wind up using, they’ll actually pay you for it. Hack Reactor’s only concern is that you’re working on something to continue your development as a software engineer. They’re very supportive and encouraging of personal projects and if it benefits the school, that’s fantastic and if not that’s also fantastic.
Once you’re done with the Hacker in Residence program, do you see yourself freelancing or being a remote employee?
I haven’t really thought about it in terms of what kind of employee I’m going to be. I’m more interested in working on projects – this sounds corny – that I’m passionate about. Personally, I’m not interested in working at a social media company coming up with another button to tell somebody that you like them. That’s not what I’m interested in.
Given where I am geographically, remote is probably going to be a big criteria.
After going through the program, have you noticed any traits that you’ve found you needed in order to really be successful in online learning?
I think that Hack Reactor has established a very good gating factor. Their application process is very selective in who they admit because they don’t want to waste anybody’s time. They don’t want to waste your time as a prospective student and they don’t want to waste their time as a school with accepting people who aren’t going to be a good fit.
What’s really interesting too is they put just as much emphasis in on being a culture fit as they do an aptitude fit. Not only do you have to be willing and able to do the work, you have to be willing and able to work with people. Also, you have to to be kind of comfortable with not knowing what you’re doing (and having confidence that you’ll figure out how to find the answer) because that’s a big part of software engineering.
Just from the schedule alone, it’s not for the faint of heart. I have three young kids and it was definitely incredibly difficult to see them for 15 minutes a day. I’d wake up and get them out the door for school because it is Hack Reactor is on a West Coast centric schedule. Being on the East Coast, my day would start at noon and not finish until midnight, one, or two in the morning. There’s nothing about the program that you do on your own time.
Is there anything else you’d like to add?
It was definitely the most challenging academic experience of my entire life but that being said, it was more than worth it just in terms of a sense of accomplishment. It’s just a very gratifying experience. If anybody’s looking for a challenge and they want to push themselves farther than they think they can go, Hack Reactor’s the place to be.
Shawn, what were you doing before you cofounded Hack Reactor and what convinced you that Hack Reactor was a viable business/education model to be involved with?
What does the Hiring Team do at Hack Reactor?
I have to give a shoutout to the Hiring Team, because they are incredibly hardworking and smart people, and they’ve built out a really unparallelled system for connecting grads with great companies. I’m seriously unaware of anything comparable… they make your college’s career services department look very sloppy, and they work harder and smarter and have more volume than any recruiter.
Here’s how it works: they collect all kinds of information about the open reqs at all of our hiring partners, then they really dig into how students should think about those companies and circulate information about them, the pros and cons and what kind of person should apply there. They then survey students and staff and feed this all into JobQuery -- this piece of software that we built because the team’s spreadsheets became too arcanely powerful and we grew fearful of them -- which does all this matchmaking and follow-up and tracking magic. It’s very beautiful to watch their meticulously-curated success metrics slope upwards.
On the other hand, they have kind of an easy job -- the students are great, and since word has gotten out about that, the companies are great (we can’t name most of them unfortunately), so they just get along well. OH at our last hiring event, from a CTO to a tech lead: “If you're hiring from anyone but Hack Reactor, you're doing it wrong.”
Does Hack Reactor require pre-work to make sure that students are on the same page? What does it consist of?
The precourse work is a pretty complicated piece of the puzzle. It has to be accessible to people that only recently started coding, but it has to be challenging to those well into a career, looking to update their skills or make a career switch, because we have a real mix of people coming into the class. It has to be hard, because we want to give everyone early perspective on how hard the class is (before they quit their jobs, etc) but it has to be easy enough that they can do it before they have the full support of staff. We’re constantly tweaking it and pushing content back into it from the course, to make room for other stuff. Right now, applicants rewrite some existing libraries, go through a bunch of self-guided instruction and test-driven stuff on the finer details of JS, and work through a bunch of git and HTML/CSS resources. It’s between 40 and 100 hours, depending on experience.
Hack Reactor is considered the "Harvard of Coding Schools." Did you and your team make conscious decisions to keep the quality of your school high?
Yeah, that was the plan from the start. It’s an easy plan to have (who doesn’t want that?) but making it a reality is harder. We’ve had to consciously decide to grow slower than others in the sector and turn away a lot of good applicants. We had to put a lot of work into making hires and have a lot of hard conversations when staff were doing a B+ job. More than anything, it’s the result of an insane amount of heart and energy from people at the school (most of whom never get any public recognition). So, it’s really rewarding to see that work implicitly recognized by stuff like this question (which is actually quoting Steve Newcomb, CEO of Famo.us, who’s hired several of the alumni) or the recent WSJ article that called us out as a counterpoint to the downward trend in bootcamp graduate outcomes.
I mentioned part of this earlier -- we were working at top companies, present at ground zero to witness a major trend in the web. The decision raised a few eyebrows at the time (my friends thought we were nuts for not teaching Ruby) but in the time since then, JS has clearly taken over (eg check the graph on this post) and we’ve seen some coding schools retool their entire curriculum to use JS instead of Ruby/Rails (eg Fullstack Academy has switched over completely).
Job placement may be one of the biggest variants between all of the coding schools. Explain Hack Reactor's approach to helping students and graduates find jobs.
We’re big on data-driven education, and student outcomes are our ultimate measure of the quality of our school. It’s the best way of measuring success, even for students that aren’t looking for a job: it’s the market saying “oh yeah, this place trains real engineers." So we pay close attention to student outcome statistics, and a lot of our power comes from the years of continuous revision that happens:
- Someone has trouble in the job search.
- We freak out and somehow solve the problem for that specific student if we can.
- We figure out what went wrong: Hole in the curriculum? Error in student progress reporting/followup?
- School levels up. So, that’s the meta-answer.
Here’re some specifics:
- We work really hard on admissions, and we have really good processes for determining how quickly people learn.
- The curriculum team is incredible, and they consider student questions or assessment failures as evidence of things that need to get fixed for next time.
- We cover the computer science fundamentals (data structures, algorithmic complexity) in great depth, both because they are fundamental engineering concepts as well as because they are the main subject matter of software interviews. This is kind of a luxury we get as a result of being a 20-120 program (vs a 0-60 program, which is what most coding schools are doing). We require that applicants learn a lot on their own, and then we have a longer course (more weeks, more hours per week). As a result, we have space for an hour a day of “toy problems” that challenge students to assess and improve the algorithmic complexity of solutions to small problems, just like they do during interviews.
- We have a lot of content throughout the course on blogging, portfolio management, resume review, conducting a successful job search, etc etc etc. All the curriculum is on github, so they have like 20 learning repos, plus a couple of big projects, which are often real projects for real clients/companies. When you google the students, they look like normal engineers.
- After the course ends, students use our software to track their interview pipeline, and we know whether they’re set up for success.
TLDR: no magic, just lots of hard work and iteration. Meat and potatoes stuff that somehow is not commonplace at any educational institution. I foresee a world (decades away) where we can’t say that any longer as education changes to be more data-driven and outcome-focused.
How is the job placement process structured? Does Hack Reactor get a referral/placement fee from companies? Does the student get a tuition refund once placed?
I answered the placement process question earlier. We get referral fees from hiring partners -- it pays the salaries of the several full-time people that do that work and overflows into the school’s general fund. We don’t do refunds when students accept a job at company X instead of company Y, and we have an organized process to encourage students to apply for jobs outside of our partner network. I find that refund model to be deeply weird: it offers soon-to-be-wealthy students a short-term, unimportant incentive for a decision that has critical long-term effects on the student. The alternative is a pay-it-forward model: every current student benefits from hiring program revenues equally (our staff:student ratio keeps going up while our tuition has not risen in two years) and if the student feels like a partner company is your best choice, they take that job (which probably pays six figures) and the school gets a bunch of money to reinvest.
What is the most current job placement rate? What goes into that rate? (ie. what's the denominator? do you only "count" students who indicate that they're looking for jobs?
This is a great question -- there aren’t clear standards in our industry for how these numbers are tracked, although we are working with other schools on this problem. Our current placement rate is 99% of job-seekers within three months of graduation. The denominator excludes the following groups:
- Students who enter the program with no intent to conduct a job search.
- International students.
- Entrepreneurs (eg the hedge fund profiled in Wired).
- People that enter the Hacker in Residence program (HIR -- it’s like grad school) are counted after their residency ends three months later.
The motivation here is to provide job-seeking students with the clearest picture possible of their likely outcome. We’d like to see better standards/transparency for the industry (eg cohort reports, third-party verification, total counts for different outcome categories, student-assessed outcomes, standard processes to establish prior job search intent) and we’re working to make this a reality as the industry grows up. It’s early days yet and we’ll see a lot of changes in this specific area.
How does Hack Reactor continue to help alumni after they've graduated and been placed in jobs?
We kicked off an incredible alumni program about three months ago. It’s only just beginning, but it’s already a source of pride, and is starting to draw people to the program through word-of-mouth. The long-term-vision is to build out the strongest network of brilliant engineers/CTOs/etc in the Bay Area and build out ongoing education programs. It’s already the best alumni network around (in my unbiased opinion) and we are really just getting started. Some awesome initiatives:
- We dedicated two different rooms at the school, exclusively for alumni. There’s a lounge/meetup space (pool table, giant TV, comfy couches) and there are several events every week (movie nights, side project Saturdays, the first-ever Tessel hackathon, etc). There's also a coworking space, where at least one startup is hacking on something world-changing.
- We’re collaborating on volunteering projects, like supporting Mission Bit (which was started by an alum) and building out an as-yet-unannounced learn-to-code program for prison inmates.
- If an alum decides to switch jobs, they come back to us and we loop them into the system for mock interviews, portfolio review, Hiring Day, etc -- same stuff we do for current students.
- We have a newsletter that informs alums of speaking opportunities, upcoming events, and so on.
- We’re launching an alumni mobile app soon that can tell alums who’s in the alumni lounge, or which alums are at which companies (if you need help on an API).
This is all paid for by the referral fees (although maybe only half of the alums that go through our process take jobs with our partners) so it’s long-term-viable and we have a budget to do all of this as well as the stuff we have planned in the future.
In your time at Hack Reactor, have you noticed that companies and hiring managers are getting more comfortable/confident in graduates of Hack Reactor and other boot camps?
We’ve definitely made a name for ourselves. The biggest factor is that alums act as a viral agent, either because their bosses are like “where can I get more of you” or because they end up in a role with hiring authority themselves.
I think coding schools as a whole have established that they’re putting out quality candidates, but that result varies by institution and within institutions (as with any educational sector). There’s still a long way to go towards educating engineers that went through a four-year program about how much you can accomplish if you structure a three-month program right. Word is getting out, but most engineers/hiring managers would still be surprised to compare the volume of coding experience of a coding school alumni vs CS degree-holders.
Where can we find Hack Reactor alumni today? Do you have any cool stories about students who landed a really neat job?
Oh man. Plenty. Our alumni can be found at pretty much any big-name company you care to name (Google, Adobe, Amazon, Uber, Beats Music, SalesForce, Pandora, Groupon) as well as the awesome startups that you might not have heard of unless you’re paying close attention (famo.us, NodePrime, Class Dojo, Backplane). One grad moved up to CTO in really short order at a really fantastic startup, Keychain Logistics -- kind of a savant. Another ended up rewriting a 70kloc front-end app (including selecting the framework) after six months at his startup, taking it all the way to successful launch.
It’s not all about jobs, either: I mentioned the alum that started Mission Bit, an incredibly inspiring non-profit to teach coding skills to high schoolers in public school. Another pair of alums went to France to work on meditation software with Thich Nhat Hanh. Ultimately, we’re not here to shuttle students into jobs, we want to empower them to have incredible lives and accomplish whatever they want.
Hack Reactor is renowned as a top programming bootcamp, and they just launched their Remote Beta Coding School. Applications are now open and the inaugural cohort begins July 21st. Course Report got the scoop from Shawn Drost, cofounder of Hack Reactor and the developer of the Remote Beta program.