Shared Review

• Tech Elevator

  Experience exceeded expectations, but..

  - 10/16/2020

  

  Brandon Murphy • Graduate • Course: .NET Coding Bootcamp • Campus: Columbus • Verified via LinkedIn
  Experience exceeded expectations, but..

  Overall Experience:

  Curriculum:

  Instructors:

  Job Assistance:
  I'm going to do a full breakdown below my review, because I wish someone had done that when I was researching Tech Elevator (TE). Here I'll just do a generic review: TE is incredible. Their process for admittance almost guarantees that if you are admitted, you're capable of completing the program. The instructors, pathway directors and anyone else you come into contact with are fully committed to your success. It's clear that it drives them from day one of the program. When you're in week 10 you'll think back to the questions you asked in week one and you'll be awed by how patient the instructors are, from start to finish. This is something you'll read over and over again, but it's true: the Pathway program is what separates TE. You can be the best developer in the world, but if you don't interview well, you're not going to get a job. This sentiment is important to remember, because when you start the program, most students (myself included) are so focused on learning code that the Pathway events tend to be an afterthought. This is fine for the first half of the cohort, but after that, your focus needs to shift. Which brings me to my "but..." part of the review: 
  
  I was surprised to find that many fellow students had at least a bachelor's degree. I did not. I received and accepted a job offer two months after graduating, but I believe it would have been quicker for me if I had a degree. One issue with COVID is that less companies are hiring; so while you will be happy for your classmates that find jobs, in some cases you'll be going after the same job. In those cases, everything else being equal, if I was a company I'd choose the student who also had a degree. Something to keep in mind and a reason to push yourself harder, especially with regard to Pathway. Someone without a degree may get less interviews, so knocking those interviews out of the park is critical.
  
  Overall going to TE was one of the best decisions I've ever made. The staff, fellow students, alumni and other partners (hiring and not hiring) are all amazing and all root for you to succeed. You come out of TE with a full blown starter kit for a tech career: technical skills, soft skills and a network. If you're thinking about doing it, do it - it was less work for me than the full time job that I left, and I got to learn new skills that I'm passionate about. The biggest determining factor for how the cohort will go for you is how quickly you "get it" - the instructors reference it early on, but some people can navigate the cohort successfully putting in 40 hours per week. Some need 60 hours per week. Some in between. The interesting thing is that you can struggle all cohort and feel like you're not getting it as fast as other people, and then it's possible to land a job immediately if you nail the interview, which is why Pathway is so critical. I cannot recommend Tech Elevator enough.
  
  
  
  Below I will break down the cohort from my perspective to give a better idea of what you may be getting into (note: the curriculum can change, so this is just what I experienced in the Summer 2020 cohort). If you do the bootcamp, I would recommend coming back and reading this breakdown again once it starts:
  
  It starts with attending a virtual (or in-person, without COVID) open house to learn a little about the program. From there you do a small assessment used to determine your aptitude for problem solving. If you pass that, next is a face to face interview, with a longer version of an aptitude test. If you pass those, you're in. Once accepted, you will be given some exercises to complete prior to the start of the cohort - the purpose for this is to make sure everyone starts the cohort on a level playing field (some people may have experience writing code, but most do not, so don't worry). These exercises just cover the basics. If you struggle with these, DO NOT worry - all of this is covered during the actual cohort. You will also get informed about the student book, which is a companion to the course. More on that below. You will also have a Google calendar shared with you for Pathway events and other miscellaneous events throughout the cohort.
  
  The first week introduces the basics of coding, either in C# or Java (I did C#). If you don't know which to pick, one nice tiebreaker could be going to LinkedIn and searching for "java developer" and ".NET developer" and seeing which has more open positions. Otherwise I would tell you .NET, but that's just me. You will have lecture from 9am to anywhere between 12pm-1pm, depending on what all needs to be covered that day. The morning starts with a review of the prior day, and a quiz for you to gauge where your understanding is (this quiz does NOT impact your actual grade, it's just so you and the instructor can see how you're doing). These quizzes were one of my favorite parts of the cohort because it allowed you test the knowledge that you just learned. After the quiz it's on to new material. For COVID, these lectures are in a classroom via Zoom and were recorded - however, I found taking notes the old fashioned way helped me retain the information. Why not type them? You will have a laptop and second monitor provided by TE if you need it (I used a TV for a second monitor). You'll want the lecture on one screen, where your instructor will be sharing their screen so that you can see what they're doing and how they're doing it. You'll also want to follow along with what they're doing on your screen at the same time, so that you can get used to doing what they're doing (and what you'll need to do for your homework). For me that meant handwriting notes in a notebook, which helps me retain information anyways. Other students typed notes. Some didn't take notes. Some followed along, some didn't. Following along AND taking notes helped me, and I generally picked up on things pretty quickly, so take that for what it's worth.
  
  Once class ends, you'll have a homework assignment and you'll want to check your calendar - there will usually be a Pathway event at 3pm. The homework assignment can take anywhere from 30 minutes to 4 hours - depends how quickly you picked up the material and how quickly you work. Once I had an assignment that took several hours, I began working on them the minute the lecture ended. One thing they caution you against is spending too much time in front of a computer - taking breaks can be good - I preferred to get everything done and then not work on anything until the next day, but I also have a 2 year old who I wanted to spend time with in the evenings. That worked for me; for others, multiple breaks helped them get through it. You'll have to figure out what works for you, and if it's in-person that probably further changes the conversation.
  
  Remember that student book? You should read the chapter tonight or tomorrow before class for what will be covered in tomorrow's class. It helps wrap your mind around some of the concepts. Tutorials also starting coming out, and for me a good habit was book the night before, tutorial before class, class, lunch, homework, Pathway, homework, done by 5pm on most days.

  This Review Is Helpful0

  Flag as inappropriate.

  Read More