Codesmith offers an extensive hiring support program that guides Residents through whiteboarding, advanced technical interview practice, resume and profile development, and interview and networking strategies. Support continues upon graduation with bi-weekly check-ins and, after offers, negotiation support. Overall, 25% of graduates receive offers for Senior Engineer positions and above, and about 70% receive offers for Mid-level Engineer roles.
Recent Codesmith Reviews: Rating 4.86
Recent Codesmith News
- Increasing the Visibility of Women in Tech after Codesmith
- What is AWS? A Guide to Amazon Web Services for Beginners
- New Year, New Career? Learning to Code in 2019!
- Start Date
- May 27, 2019
- Class size
- No deposit
- We offer tuition payment plans and many scholarships for the course.
- Tuition Plans
- We offer case by case payment plans, please reach out to firstname.lastname@example.org with questions!
- Refund / Guarantee
- If you pass the CS Prep assessment you are guaranteed a technical interview with our full time Codesmith Program. Refunds for the course are available and distributed on a case by case basis.
- We offer multiple scholarships to CS Prep, with many students paying no tuition at all. You can apply for the women in software engineering scholarship, Dean's scholarship, or minorities in tech scholarship.
- Minimum Skill Level
- Suitable for beginners who are ready to level up to intermediate and advanced material.
- Prep Work
- We recommend some familiarity with the content in the Precourse Unit on CSX - our free online learning platform - https://csx.codesmith.io/.
- Placement Test
More Start DatesMay 27, 2019 - OnlineApply by May 27, 2019June 24, 2019 - OnlineApply by June 24, 2019
CSX is Codesmith's free online learning platform, providing 100+ hours of curriculum and challenges, workshops and pair programming, video solutions for exercises, and an active Slack community.
- Start Date
- Rolling Start Date
- Class size
- Minimum Skill Level
- Placement Test
- Start Date
- Rolling Start Date
- Class size
- Online, New York City, Los Angeles
- Minimum Skill Level
- Beginner - Intermediate
- Placement Test
In PersonFull Time60 Hours/week12 Weeks
- Start Date
- June 3, 2019
- Class size
- New York City, Los Angeles
- We have financing partnerships available as well as case by case payment plans! Please email email@example.com with questions.
- Refund / Guarantee
- Refunds are distributed on a case by case basis but are available.
- Codesmith offers 4 types of scholarships -those to students underrepresented in the technology community, women in software engineering scholarship, Dean's scholarships, as well as scholarships to prior bootcamp grads.
- Minimum Skill Level
- Prior computer science and programming skills necessary - many applicants are self taught through our free weekly JS workshops/online prep course.
- Prep Work
- 4 weeks
- Placement Test
More Start DatesJune 3, 2019 - New York CityApply by June 3, 2019July 22, 2019 - New York CityApply by July 22, 2019September 9, 2019 - New York CityApply by September 9, 2019October 28, 2019 - New York CityApply by October 28, 2019December 16, 2019 - New York CityApply by December 16, 2019July 1, 2019 - Los AngelesApply by July 1, 2019August 19, 2019 - Los AngelesApply by August 19, 2019November 25, 2019 - Los AngelesApply by November 25, 2019
255 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.
Click here to log in or sign up and continue.
Before learning about Codesmith I was actively researching web development programs in NYC to see which seemed like the perfect fit for me. I applied and was admitted into some of the more familiar ones, but something about each didn’t quite fit what I was looking for.
While doing some research, I came across a comment on Quora that mentioned Codesmith. I wasn’t familiar so I did a quick Google search and read over their site. After going through the curriculum description, I was pulled in - it had everything the other programs seemed to be lacking. More so, the projects students were producing were tools made to solve real problems egineers face. Projects I could never fathom students producing in a 12-week bootcamp. I was hooked and decided to apply.
After going through two rounds of technical interviews, I was admitted to Codesmith’s April ’18 residency. It was challenging, but it was the best experience I could’ve asked for. I left with skills I never imagined myself having, and close friends I can’t imagine myself without. The curriculum is set up in a way to give you the training needed to hit the ground running day one on the job as a software engineer, and the community is built in a way so that you constantly feel surrounded by a group of peers who support you and, believe me when I say it, after a week together you'll consider some of your closest friends.
If you’re looking to accelerate your career from being a junior to mid/senior level engineer, or are coming from a different background entirely (like me), Codesmith is the place for you. In just 12 weeks you’ll leave with the experience qualifications of a seasoned engineer.
Feel free to contact me if you have any questions regarding the program, its curriculum or my personal experience at Codesmith.
Response From: Phillip Troutman of Codesmith
As someone trying to break into an engineering role, attending the JS Hardparts workshops has been invaluable to my growth as a programmer. Spending up to 2 hrs breaking down snippets of code line by line helped me understand why JS works the way it does. I could have read multiple articles on specific JS concepts but none of that would have been helpful if I didn't firmly grasp the fundamentals and truly understood how JS works underneath the hood. Spending the time digesting and truly breaking it down allowed me to see connections between specific JS features more clearly. What really makes Codesmith special it seems is the emphasis making engineers understand the why behind programming instead of just saying that's how JS works. Will is also an extremely engaging and passionate instructor, which makes the learning experience that much better. His teaching style and informal nature of the workshops is a big part of why I've repeatedly attended these events. Even though I am not a part of the CodeSmith program, I always feel welcomed and am extremely grateful and appreciative of the support Will and his team has given me!
Starting the journey
I first found Codesmith while looking for a great tech community in NYC. While there are many groups around and many people to meet, I found myself often dissapointed and frustrated for a variety of reasons. That is until I found Codesmith. The extended community around Codesmith is stellar and filled with people at all skill levels who are supportive of each other.
It was surprising, but I could see myself growing in Codesmith's residency, whereas the majority of schools on coursereport could offer me very little in terms of growth.
I found the application process very balanced, transparent, and fair. A person with little experience, but lots of aptitude can pass, while a person with lots of experience, but little aptitude would be challenged.
What drew me to Codesmith is their focus on excellence and quality. My first interaction with Codesmith staff was a message I received on meetup welcoming me to their meetup group. I replied with “This is probably a bot, but thank you for the welcome …”. The reply I received promptly summarizes my experience with Codesmith, “Alex, believe it or not, I’m not a bot. Here at Codesmtih, we do things right.”
The cohort sizes are smaller and the support from staff is tremendous. There is roughly 1 mentor for every 2 residents and the residents themselves are often quite astonishing in terms of technical ability, but also communication and working with team dynamics. The diversity of residents is a big plus and gives everyone a chance to struggle and learn. The teaching philosophy can be uncomfortable if you are not used to a strong focus on active learning, but, in my experience, is a phenomenal way to learn.
The experience is often uncomfortable and requires hard work and careful judgement in how you approach your growth and the growth of those around you. At the same time, the support is tremendous and the residents are carefully selected to thrive in such an environment. The general culture is one of “work hard, play hard” and does not get stifled by perfectionism.
Codesmith taught me new ways to communication, learn, present myself, problem solve, and put me in touch with an excellent growing community. I firmly believe that the trajectory of my growth has vastly improved for at least the next 5 years.
The hard parts
Every program has trade-offs. I think the major trade-off in Codesmith is that they put learning first and happiness as a close second. The people are wonderful and supportive, but the curriculum is not designed to make you happy. If anything, it’s designed to make you feel the stress and uncertainty of working in a production environment forcing you to develop consistent problem solving approaches with unfamiliar technologies. Watching your teammates struggle and figuring out how to constructively help can be difficult, but ultimately everyone seems to get through it.
On the other hand, it seems clear that this focus on real work is a key to Codesmith’s amazing outcomes.
I was a student from cohort 1 for the 3-week Deep Learning course. I dropped out after two days because it wasn't worth the time investment. I had already spent my money by that point (no refund). Since leaving around a month ago, no one from the program has reached out to me for why I left. I was hoping the stellar reviews here would carry over for the new Deep Learning program, but that was not the case. My main concerns are in the structure of the curriculum (as of July 2018).
It’s a 3-week course, but taught at the pace of a 12 week course. Tensorflow is not covered in the first week, let alone the first day. We spent the first two days on a very basic NN with no backpropagation. No backpropagation means weights were decided manually as an exercise. That’s like becoming an animator by adjusting individual pixels. Like learning astronomy by counting the stars. Attacking someone by hurling a gun at them. Rubbing two matchsticks together to create a fire.
I will say there is nothing fundamentally wrong, it was just executed poorly. The idea of an online Deep Learning course is a great one and I hope Codesmith does not give up on this. Here are my suggestions.
- There are many excellent free resources like Andrew Ng's Machine Learning course, Stanford Computer Vision course, and Fast AI. The curriculum of Codesmith was similar, but at a lower quality and they charge money. This is my biggest concern. I wish Code Smith followed my next point.
- Leverage how young the field is. Advances happen so quickly that many resources aren't available on the cutting edge. What is posterior collapse or KL Divergence? Are Sigmoid's still useful or should I only use RELUs? Goodfellow just released his code for his latest paper, but I can’t understand a line of code.
- Use abstraction. There are many libraries in Python that can make an image classifier with over 90% accuracy in a few lines of code. I agree that a basic understanding of Neural Networks would help increase performance. However, a significant amount of our time was spent on coding functions that are included in Numpy.
- Math isn’t needed. It doesn't take advanced math to understand the basics of a GAN. Yet many resources teach it poorly with a lot of mathematics. Adam gradient descent can be explained with a momentum metaphor. Feature space can be visualized with Google Deep Dream. To explain matrix multiplication is a waste of time for both math background and no math background students (1 lesson is not so effective). I would suggest to either choose to not need advanced math or limit the audience somehow.
- The instructor did not seem extremely experienced. I don’t mind this, but if that’s the case I would prefer the fate of the course in more than one person's hands. It seemed to be hinted that the instructor was the sole creator of the course material. What?! Give him some help! Unless he got a degree in this field or has direct work experience, he can’t take on AI by himself.
- Create a big picture, work towards a project. The majority of people would be very satisfied if they create something cool. An AI that beats me at chess, a model that can classify music into genres, an RNN that can write Shakespeare-like prose. We coded a Neural Network from scratch in the course, but this is covered by so many resources and has been done by thousands of people.
- Furthermore, I would suggest the precourse include setting up cloud computing (like Paperspace) on a local device. A laptop is pretty limited in what it can do. Also, Cloud computing setup is not so straightforward and people may need help. Any course that does not teach this is seems behind the times and limited in scope.
Response From: Will Sentance of Codesmith
The curriculum was designed by both the instructor Ryan Smith and Alex Zai, a machine learning engineer at Amazon responsible for building out Amazon’s MXNet machine learning framework.
The approach of Codesmith is to go under-the-hood of frameworks like Tensorflow so that you can think as an engineer. This was the goal of the deep learning program too - focusing on a first principles understanding rather than a lightweight use of tools where there are helpful youtube getting started guides available for free.
Understanding from first principles the intuitions of deep learning and specifically neural networks is what distinguishes machine learning engineers who really understand and can optimize the tools they use.
The team reached out to you a number of times after you stopped attending class. I know Ryan enjoyed the brief time you had working together in that first day and I hope you can keep in touch and keep cultivating your interest in deep learning techniques.
If there is one thing that I can really say that I got from my 12-weeks at Codesmith, it is the fact that I had developed an engineering mindset. Having the ability to decompose a problem and break it down to chewable / understandable parts and then formulate a solution while knowing the pros and cons of that approach and on top of that being self-aware of when to ask for help is something that will always be relevant in software engineering.
Life Before Codesmith
Due to my wonderful experience at Codesmith's Hard Parts Session and the high level of technical communication that I observed plus my further research that indicated that Codesmith residents will be making a developer tool to contribute to Open Source, it didn't take me too long to decide that I really wanted to go to Codesmith. Long story short, I got in as part of the first cohort of Codesmith NY.
The immersive (12 weeks) was grueling and yet had a "chill" environment. It's like "a work hard, chill hard" feel. Lol
The first six weeks was all about learning Codesmith material. I had a difficult time grasping them as we were going by fast and had to context switch every two days. In addition, I kind of felt the Imposter Syndrome as I often compare myself to other cohort mates who were breezing the two day modules, but thanks to Codesmith's warm, supportive, and reaffirming culture I was able to bounce back and eventually diverted all my energy to the task at hand (Developer Tool creation).
The second and final six weeks were all about our production projects (creating a developer tool as per each team's vision and MVP requirements). In this period, Codesmith gave us one week to brainstorm before each team submits their list of ideas. Once that process was complete, we spent the remainder of the last 6 weeks coding the tool out and beat bugs and solved technical challenges on our own.
Life After Codesmith (Job Search)
After graduation, I wasn't confident about the things I learned in Codesmith as I felt like they went over my head. In spite of that, I just followed the Job Search tasks that Codesmith gave us to do and it helped me immensely. I soon realized that I knew more than what I thought I did. It was just a matter of choosing the right terms and phrases to accurately articulate the knowledge that is already in my head.
Having said that, the Job Search process was filled with its ups and downs. From my experience, it took me a while (~4 months) before I gained traction ( getting an offer) in my job search but Codesmith staff was there to check up on me and offer feedback. Also, I know for a fact that Codesmith will never leave you alone after you graduated. I had a first hand encounter with that because two months after graduation I was seriously contemplating to go back to my prior field and it was at this time when Will Sentance, the CEO, called me personally and asked me how I was doing and then gave me pointers regarding my job search moving forward. So I tweaked my approach a bit, and kept on keeping on and eventually got an offer about 2 and a half months after the call.
To sum it all up, even after graduation, you’ll never stop being a part of Codesmith. One way or another, they will try to assist you and you will always be welcome to hang out/ set a base camp for your job search. Lastly, you may hear that on average, grads typically get a job in about 3 months. It's a fair estimate BUT should you ever find yourself exceeding the 3 months, PLEASE DO NOT CONSIDER YOURSELF AS A FAILURE. Just keep applying and learn from each interview that you have. Turn the grey squares to green. You'll get there.
Response From: Will Sentance of Codesmith
Thanks also for coming back for the alumni panel - your insights were excellent - of course
I have always had a love for technology and, after 17 years at the same company, decided to make a huge career change and jump into software development. After vetting several Southern California programs, I decided to move forward with Codesmith. After having competing offers, and accepting a senior level position, I don't know that I could have made a better decision.
In addition to the recommendation from a few hiring partners I knew prior to applying to the program, one of the more impressive factors in this decision was the overwhelmingly positive experiences and outcomes of alumni. I don't know that I have spoken to anyone since beginning the program that would not recommend it to a serious, hard working person looking to make a change, myself included.
I doubt I could say much more than most of the other reviewers have but will hit on a couple items I believe aided in my journey.
This is something they try to make everyone become competent in. It is such a valuable skill and they really ensure you are as clear and technical as you can be in order to fully communicate your ideas and thought process. Personally, as someone who initially struggled with this, all six of my interviewers (for the position I ended up in) commented on how proficient and clear my communication is.
Analytical problem solving:
By design, mentors will rarely give a straight answer. By guiding students to proper documentation or asking pointed questions, mentors are able to put students in a problem-solving mindset in which they are able to more adequately approach challenges and become independent, self-sufficient engineers, much like they would be in the wild. There are exceptions to this rule, however, the aim is to have students struggle and learn rather than go through a three-month tutorial.
Support and community:
Codesmith strives to create an inclusive and supportive environment which allows for an incredibly competitive culture in which everyone also wants to see each other succeed and grow as much as possible. This was very refreshing coming from an industry which maintained a dog-eat-dog, toxic mentality. Beyond this, you really do make your way in to a pretty powerful network of engineers, and a community of alumni which continue to maintain a presence after the programs conclusion.
If you have the opportunity, Codesmith is certainly one of the best programs you can go through. Be prepared for a lot of work, but the payoff is absolutely worth it.
# Course Report
Will is a passionate speaker and the community of people was very encouraging. I knew pretty much right away that I wanted to be part of this program. Even once the material of the lectures was less fruitful for me, I still loved attending for the pair-programming sessions and the random people I met.
One JSHP meetup night in particular that stuck out to me was when Schno stayed after with 3 of us as we were going through a coding challenge. We got as stuck as we could and when we reached out to him, instead of giving the answer right away, he subtly guided us down a path then sat back with a grin on his face. He could tell when we had figured out enough and just waited for us to put the dots together ourselves. You could tell that he really enjoyed "the a-ha moment" that comes from this type of work.
I ended up attending JSHP meetups about 10 times before attending the program.
Writing software never came easy for me, and it took me 3 attempts to even get into the program. Once in, the program was a struggle for me the entire time so, to keep up, I was coding all day and night ( minus ping-pong breaks of course :) ) and was practically sleeping at the computer. I expected the program to be intense, but just a warning... If you would prefer more hand-holding and a slower pace, this is NOT the program for you. If you like being pushed and going through intense growth as an engineer, then consider Codesmith.
1 month after the program I got a job offer in San Fransisco to work on Walmart's customer facing website. One of the biggest React apps in the wild and at $125k/year! I've made more than a few life-long friends, all of which are now working on exciting projects.
The Codesmith staff is a passionate and intelligent group of people. You really have all of the support you need to succeed as you got through their program. Erik Kirsten, Will Sentance, Haley, Shanda, Master Schno and all of the other instructors are incredible people.
There is no guarantee of success of course, but if you put in the dedication, Codesmith can be an incredible stepping stone in a software developer's journey.
Response From: Will Sentance of Codesmith
When I was researching avenues to enter the software engineering field, I was initially set on attending another school. I thought that every school was going to be similar. Boy, was I wrong.
Soon after that, I attended a Hard Parts in person and the vibe of the space, the CodeSmith team, and the attendees was really awesome. It seemed like a place/community that I want to be part of. It was really inviting, there's great diversity of people, and it feels cool and hip.
Needless to say, I eventually applied and was accepted.
Throughout the program these FIVE core tennets were reinforced.
- Technical communication
- Non-technical communication/Empathy
- Analytical problem-solving
- How to handle blocks...technical and non-technical
- Technical knowledge
Everyday was an opportunity to hone these skills, which are at the core for mid to senior level engineers.
There is not a lot of hand holding (just like on a real job), and you'll be pushed everyday. You're guaranteed to learn lots...whether its technology, working on a team, managing project scope, etc.
I won't talk too much about the course contents because that will evolve as technology changes. Having said that, during portions of the journey, you're free to explore and incorporate other technologies into your projects.
The team at Codesmith is super supportive, they really take care of things so that you can focus on learning. Also, lead technical mentors and fellows are there to help you think through your problems when you get stuck or to advise you on your Senior projects. No hand-holding...just a bump in the right direction.
Now for some other cool things about Codesmith (LA): There are lots of opportunities for fun...there's a Ping Pong table (during my cohort, there were lots of exciting matches), Venice beach is a few blocks away, Abbot Kinney is within walking distahnce, Codesmith organizes drinks after Hard Parts meetings, and more...
If you are up for a challenge and want to push yourself to the limits, Codesmith will change your life for many different reasons. You'll be honing your coding super powers (and can apply them to so many fields). You'll, forever, be part of a community and network of amazing individuals that share the same passion.
Response From: Phillip Troutman of Codesmith
They said it best, but I’ll add what I can
As hundreds of these reviews attest, Codesmith is an amazing, demanding, aggressively worthwhile program that turns excitement and ambition into engineering success. I’ll echo the highlights – a lasting community, self-directed projects, passionate instructors, consistent job-search support – but rather than focus on what makes the experience awesome in general, I want to touch on the stuff that I didn’t expect while addressing the concerns that I initially had. My intent here is to answer the questions that I was asking – and the ones I should have been asking – when I was considering Codesmith.
The Codesmith family – more than a bonus?
I sought out Codesmith because of the community – a network of friends and professionals really appealed to me, and I felt like I might mesh better with people who were drawn to this sort of environment. I was surprised to discover just how necessary this culture was, both during the program and after it ended. It didn’t just make the process more enjoyable – it consistently kept me around and learning new things hours after I would have left for the day. During the job search it was invaluable to have folks to meet up with for interview practice or to swap resources and encouragement.
Two heads better than one?
Pair programming is heavily emphasized for the first few weeks, and to be honest I was skeptical that the system would work for me. I felt like it would be intimidating and uncomfortable to problem-solve aloud in front of a stranger. What if all I did was slow my partner down, or visa versa? Turns out I was dead wrong – pair programming was a huge reason why I was able to join Google as a software engineer straight out of Codesmith. It not only builds your technical communication skills and makes you more introspective of your own thinking process, but also teaches you new ways to approach problems and diagram out solutions.
A program for all coding backgrounds
I’ll join the chorus here and say that Codesmith is an obvious choice for anyone with minimal programming experience but a willingness to put in the extra effort and a genuine interest in software development. But what about those – like me – who have technical degrees, or those who already have a few years of development experience? I was hesitant to commit to the program because I wasn’t sure that I’d get as much out of it. Again, I was dead wrong. As a comp sci major, I was able to build up knowledge of real-world technologies that complemented my theoretical foundation and market myself as a problem-solving generalist with relevant development experience. To a current software engineer, Codesmith is a place to transition into a more in-demand tech stack while building the communication skills of a senior-level developer.
For those who are wondering whether they’d be better off trying to pick up the technologies on their own – I can personally tell you that you’re being dumb. It’s worth the investment to learn them faster, better, and in context. No matter your background, I cannot recommend Codesmith highly enough. You’ll stagger across the finish line but wish there were more.
Response From: Will Sentance of Codesmith
Response From: Olivia of Codesmith
I have always had a passion for computers, hardware and software, but never had the training, encouragement, or courage to take the leap of faith in switching careers. I was looking at other schools in the LA area and was referred to Codesmith by a friend who had graduated and gone on to do very well. I feel blessed having gone in that way, as it helps to know beforehand that the program really works. It's incredibly demanding and it will make you doubt yourself at every turn -- overcoming those doubts is the very core of the program -- but with the support of passionate and caring mentors, you will come out the other end as the best software engineer you could possibly become in the time given. This crucible of overcoming blocks in understanding is one of many things that set Codesmith apart. It makes you a great software engineer able to tackle any stack you want to, and more importantly, engenders the technical communication and engineering empathy that makes you someone people want to work with. Codesmith is the Ivy League of bootcamps, and that means you'll do well when you graduate. It also means that you'll need to work hard to get in, so my advice on shooting for Codesmith is that there's no such thing as too much preparation. I went in without prior experience, but I put in many months of study beforehand, and I still struggled. It's all about the struggle. If you're looking for someone to hold your hand, walk you through "Your Very First Full Stack Application," pat you on the back at the end, and set you up with a nice, non-challenging Junior Developer role, then look elsewhere. If you want to become the kind of developer that other developers look up to, then go to Codesmith.
Codesmith was the best decision that I could have made for myself. I dropped out of NYU at 20 years old because I knew I could do what I wanted without paying $60K more for a degree. I wanted to be a software engineer. It didn't just teach me how to use frameworks and how to solve algorithms. It taught me how to learn efficiently. I left with a life long skill of adaptation.
I also left with really good friends, my cohort was like a big family. The whole team is such an amazing source of support. The instructors and the fellows don't give you the answer but they help guide you into figuring it out on your own. The environment just encourages support and learning together. I looked into a lot of programs that offered similar curriculum but I went to a hard parts and I knew that this was the place I wanted to spend my time learning. And I have no doubt that I made the right decsion.
I just graduated from the most recent April '18 cohort and had a really amazing experience at Codesmith.
Many reviews on here have described the amount of work that is demanded from Codesmith residents, to which I would say it's a given that if you're looking for a complete career change in three months, you're going to have to put in a lot of time and effort. That being said, the community and the support that you get from both staff and other students makes that process much, much easier. It's obviously possible to learn technologies like React and Redux on your own, but coding is a collaborative process. And that's not something you can learn sitting on your couch with a laptop. I remember all the time I spent on Codewars, FreeCodeCamp, and CodeAcademy prior to Codesmith, studying to get in. I learned a good amount studying on my own, and I'm sure I could have learned how to put together a website myself with a few more months. But the kind of work that you do in order to get accepted has almost nothing to do with what it's like to work on a team, which is what you'll have to do once you go out and get an engineering job. The projects that you build at Codesmith ingrain you with that collaborative process. Whether you like it or not, you'll have to work with people who are stronger than you, and people who are weaker than you. You'll have to decide how to break up a project into pieces so that someone can put together a SQL database while another person adds OAuth to your app. You'll also have to also learn how to merge two, three, four different peoples' work together into a single codebase and not break everything (which inevitably, it will) in the process. You'll learn to code with other people, and that's what companies want from engineers. Someone in my cohort had an interview a few days ago and was asked 'Tell me about a time someone on your team underperformed, how it affected the rest of the team, and how you responded'. That's a question you absolutely cannot answer if you've only ever coded by yourself. Codesmith prepares you to confidently answer questions like that, because you spent months working with other engineers, constantly facing blocks and having to overcome them. To bring this back to the amount of work that is demanded from students at Codesmith—yes, it's difficult, but most of that difficulty comes from learning to work with other people, and that's an invaluable skill to have as an engineer.
I was a resident and then a fellow at Codesmith so I think I can give some quick insights on the program. If you are about growth through technical challenge and embrace deliberate practice rather than easy wins, this is the place for you. If you want to be surrounded by determined and brilliant people who genuinely care about your learning experience, you've found it. But keep this in mind, no one will hold your hand and you have to come in with 110% of focus and self-determination to make it through. This is great opportunity to excel yourself as a mid-senior software engineer, so come and earn it.
A few months prior to joining Codesmith I had quit my job with the goal of learning coding on my own in order to switch careers and create a few projects I've had in my head but never been able to act on. (I come from a technical background, but on the Electrical side - so I wanted to get SW skills in order to be more full stack.)
About 2 months into my self-learning journey, I realized I could solve problems but always felt I was "hacking" the answer together instead of just being able to immediately solve them, which I felt slowed me own drastically.
I received all of the skills that I was looking for and can now immediately reason in my head when solving problems on my projects, as-opposed to having to stack overflow every question and 'hack' together answers.
In addition, the two things I think really set Codesmith apart are 1) the culture and 2) the projects.
1) A majority of the people that join Codesmith are already solid programmers or problem solvers with technical backgrounds, and they want to take their skills to the next level. This was what was really worth the price of admission, to me. Working on my own I would sometimes hit a wall of frustration and need a break; with the community you're working with at Codesmith, if you hit a wall there is surely someone around who is happy to sit down and troubleshoot it with you. And you're on your way forward in no time. (Not to mention the network of driven people you are now a part of)
2) I don't like how some schools force boring projects on you - I don't think that helps promote true learning because you're not passionately solving through your problems and can just go through the motions. Codesmith lets you choose your own projects (pretty much whatever you choose, as long as the concept is challenging enough and clearly described). This phase was where I really solidified my knowledge because I was working on projects I cared about and that allowed me to spend the extra time to really push through difficult problems, willingly.
TLDR: I'm very happy I made this decision as I now have the skills I was looking for, in only 3 months. Now I can solve challenging problems without help.
Note: It's not easy - be ready to put in the work.
Attended CodeSmith - August 2016 Cohort 9
Background - Chemical Engineering
Currently - Software Engineer (First Job landed after CodeSmith was Nike)
*Note* - One thing that Codesmith does well, is the support. I still get my resume reviewed from time to time and Codesmith does a great job in being responsive to their student needs in regards to Job Assistance.
I learned more about relevant technologies and code production at Codesmith than I did in college with a minor in computer science.
Overall it was a great experience. I developed some awesome friendships and am now working as a software engineer at a company that I love.
I do wish there was more back end in the curriculum. I takes extra effort and studying after Codesmith to land a backend position. But that is true for any bootcamp.
I come from a background in PR and Marketing, and transitioned into a role as a UX/UI developer. I wanted to build out the functionalities of these static wireframes and prototypes, but my scope of software engineering was so narrow that I didn’t know where or how to begin. I did a lot of research on bootcamps and immersive programmes, and the amount of polarising reviews put me off any further researching. I decided to try the whole “self-studying” thing, and found myself completing algorithm after algorithm, but not really implementing it to build anything useful.
During my time at Codesmith, the hardest part for me was to discipline myself in adjusting to a “new” way of learning. The lectures give you a solid high-level overview of a particular topic, but it’s up to you to put in the hard work to further research how it’s used and how all the pieces come together. Every two days, you’re learning a new concept/framework/protocol along with a unit challenge, and I definitely put in a lot of extra time during and after the programme to ensure that I’ve understood them. During the “senior” portion of the programme, Codesmith really pushes you to explore areas that might feel like impossible to build at first, but when you’re surrounded by such determined and ambitious talent, you pick up on their energy and push through together as a team. My team and I built a real-time text editor with end-to-end encryption - still can’t believe that we worked with encryption!
The last few weeks are dedicated to outcomes and building out your network, which was one of the most important areas of Codesmith. The Codesmith team put in a lot of effort in conducting resume workshops, mock interviews/white boarding sessions, and cover letter/follow-up strategies. You’re in this iterative and refinement phase that further strengthens your technical and presentational skills when it comes to hiring day. You’re equipped with an extensive network of Codesmith alumni that are scattered across major cities, and I definitely took advantage of that by reaching out to them and they were more than happy to meet with me for interview preps. Codesmith built a solid foundation for my career, and I accepted a great offer a few weeks after finishing up the programme!
Codesmith as a program really lives up to it's hype. I was skeptical at first, as having been a software engineer for 4/5 years back in the late 90's / early naughties I was well aware of how big an undertaking it is to become a competent developer. Having not programmed for 15 yrs, thereby missing the internet/cloud era I found myself drawn to bootcamps as a way to re-immerse myself in programming. I decided on Codesmith having attended JSHP and really liking the community Codesmith was developing. My instincts were correct. Codemith has developed an awesome community, where students, alumni and the Codesmith team, all support each other fantastically. This really proved helpful during the program, where people all stayed on beyond the required 12hr days to help each other overcome the struggles of learning to code. I feel like the base knowledge the program gives you, really instills an ability to go out and tackle any coding challenge. You come away having learned how to break the problem down, research what knowledge you need in an efficient manner and apply this to any given challenge. This ability coupled with the community, I could not have asked for more.
I'll keep it short since I can't say much more than the other reviewers have already said:
Codesmith was the right decision for me. I graduated with a Math/CS degree and was unsure about whether any of these coiding programs would be useful for me, but I eventually decided on attending Codesmith and I'm so glad I did! The vibe and energy from the people there was always positive, always friendly, and always collaborative. I was free to ask for help and work with others on what I had trouble with and at the same time other could always come to me with their questions as well. And that was important because the program was dense and without that kind of community, I couldn't learned what I did, and I wouldn't have been able to built what I did. It felt like we were all in this together and trying to raise each other up to become the best engineers possible.
My experience in the program was incredibly valuable and I would choose to do it again in a heartbeat!
When I joined Codesmith, I was a cs grad trying to reach for roles that are typically not possible to attain by people who are fresh out of college. I wanted to have the skills and the confidence to be taken seriously when applying for positions that aren't just entry level software engineering roles. I am passionate about engineering and knew that I could do better than performing mindless bug fixes and task/maintanence level engineering. I wanted to build new systems and apply cutting edge technology to real world applications.
The community aspect of Codesmith is one of the biggest contributors to the success of all the students that go through the program. You will be surrounded by highly motivated people and learn how to work in teams, mentor others, and work through difficult and interesting challenges together (just like in a real world environment!). AND you make a bunch of really cool friends throughout the program and beyond!
I have to say Codesmith helped me attain all the things I wanted in my career as a Software Engineer. The skills they teach allows you to be able to reach for higher roles solving actually interesting problems as well as have people take you more seriously as an engineer. You get to learn how to learn, how to design solid systems by building, pick up popularly used technologies, and create real projects. There are also various levels of soft skills that you will inadvertently pick up as well as lots of tools for doing well in interviews.
Coming out of Codesmith, in the interview process, I felt that I was taken more seriously than before. Interviewers got excited when I talked about the projects that I created at CodeSmith, especially the senior project that we built as a team (a realtime subscription system for GraphQL before it was even implemented officially in the GraphQL specification and before Apollo released such functionality!). Most of the offers I recieved after the program were well within and above the range of salaries offered to most Codesmith students.
One year later, I am confident in saying that I was able to apply pretty much everything I learned at Codesmith to excel and make a solid impact here at the company I currently work at. I have been an integral part of designing and creating several new backend systems, migrating our backend to microservices, developing an in house branded UI Component library using all the latest and greatest React tooling, and building lots of new features in our product.
Was it worth it? Hell yeah it was worth it! and it was LOADS of fun! It is important that you take this time to work hard and make the most of the experience. It's not magic where you just go through the program and you come out it being able to be treated like a senior engineer. Work hard, get sleep, eat well, read lots, and dive deep into the topics that you learn (and the topics you don't learn!). If you take the time to make the most out of your Codesmith experience, you will come out of it surprising EVERYONE you talk to. I was really inspired by the growth of all my peers at Codesmith who came from non-technical backgrounds. They worked hard, grew to be excellent engineers, and many of them are making waves at the places the landed afterwards.
Enrolling in Codesmith is one of the best investments I’ve made. I had some tech experience, but wanted to make a hard turn into software development. I didn’t want to spend a year in self-study or take a junior position where I wasn’t challenged to grow beyond my limits. This program challenged my limits everyday for three months and grew my knowledge and skill to the level I needed to pursue and make that hard turn into software development.
I came to Codesmith after several stints of personal projects and self-study. A night of self-study might have included me crouching over a computer in my living room for a few hours trying to get a web server to accept requests while pretending to watch the Bachelor with my girlfriend. The first successful response would lead to an audible, “Yes!,“ at which point I’d feel a sense of a accomplishment, shut the laptop as if it were an interruption to normal life, and get back to the Bachelor (don’t judge). Stack overflow articles and trial/error would have given me a concept of what was going on under the hood, but a lot of the learning actually comes after hacking together a solution. For three months Codesmith takes over your life. There are no interruptions to learning how to code - getting to the audible ‘Yes!’ becomes the first step of solving a problem instead of the last. Instead of closing the laptop, you take it with you to the classroom and start connecting the dots of why it worked like it did and digging deeper into the underlying architecture so the next project you’re focused on optimization as opposed to just getting something working.
The program is structured from a day-to-day perspective but retains a loose and agile feel to it - include its immersive aspect and you’re forced to make the program your own. Instead of simply experiencing a curriculum, you become part of the curriculum - on any given day you can be the student, the teacher, or even the intangible glue that holds your cohort together in times of stress. Looking back at the experience, this was incredibly motivating and helped drive everyone to keep their endurance and tenacity at the crazy levels needed to conquer each day’s/week’s goals. The Codesmith staff also did a great job of bringing the experience of many previous cohorts to bear in helping students navigate problem areas.
I’ll end the review like I started it - Codesmith is a great investment in yourself. That said, it’s not for the faint of heart. This investment is not only tuition and time but also the energy and dedication put into it. The program gives you all the tools and support to succeed - and really pushes you to make the most out of it. If you have a natural curiosity and urge to learn and legitimately give it 110%, you’ll grow enormously.
Initially, I was pretty skeptical - how could I learn the skills required to change careers in only a few months? Two weeks after my cohort finished, I had signed a six figure job offer, and within my first week I felt confident about the code I contributed to the team.
At Codesmith, you're surrounded by highly motivated people, and that environment encourages growth, exploration, and learning. You'll quickly become used to the minimum 12 hour days, but also find yourself frequently working even longer. The curriculum is modern, and is frequently being updated to cover the latest frameworks and libraries.
The Codesmith team works very hard to motivate and encourage you to work as hard as you can. This is especially true during the project phase, when they set strict stanardards for building a high quality open source project. To me, this is one of the key areas that makes Codesmith stand out from the rest- it encourages you to go deep into unique programming concepts and features, giving you the confidence to speak to these in depth during interviews.
Additionally, the team also works very hard with everyone to help you build a great resume to make you stand out, prepares you for the tech interview process, and at negotiating your best offer.
My one complaint, is that (in my opinion) some of the material is not taught well. This was especially frustrating for me after going from a series of very high quality lectures to some very poor ones- however, you quickly discover the real learning is not from the instructors or the lecture material, but from learning how to learn on your own and in the small groups you work in.
A large portion of Codesmith is focused around pair programming, which really teaches you visualize a problem before you blindly start coding. Technical communication is a term you will hear a lot, and after a few weeks into the program you will become very good and articulating your strategies. Through pair programming, you are exposed to lots of different ideas from your partners, which further expands the way you think about the problem you're facing.
If you are thinking about making the jump - be sure to seriously consider Codesmith. Yes, it's expensive, but for almost everyone it pays for itself within one year. I would recommend Codesmith to anyone I know looking to make the switch. Codesmith was one of the funnest and most productive three months of my life, and all of these reviews of it being a "life changing" experience are completely accurate.
I'm going to assume you've read some of the other reviews, and you know about Codesmith's curriculumn (<3 React), it's fantastic culture (I miss Thursday drinks), and it's inclusive community. I'll focus on my journey.
Spoilers: Codesmith transformed my life too. Today, I find myself thriving at a job that felt beyond my reach only a year ago. Software development can be a pain in the ass sometimes, but my experience at Codesmith helped me learn to approach every challenge as a learning opportunity to dive deeper into how things work instead of just patch them together to get them to work. Codesmith is not a traditional learning environment where you are fed all of the information you need to learn and your only job is to absorb and regurgitate it. In order to thrive there, you need to be willing to dive into the deep end, struggle a lot, and learn how to overcome many obstacles on your own. On the flip side, if you dedicate yourself wholly to the process for 3 months, it can change your life.
On-Time Graduation Rate
180 Day Employment Breakdown:
Notes & Caveats:
For transparency, here are the starting salary breakdowns of our graduates from 1/01/2018 - 6/30/2018:
- $110,000 - 119,999: 17.5%
- $120,000 - 129,999: 17.5%
- $130,000 - 139,999: 10%
- $140,000+ : 2.5%
Our latest on Codesmith
Alex was interested in coding throughout college but initially dismissed it, thinking that coding just wasn’t for her. But seeing the potential of technology while working for nonprofits, she decided to revisit software engineering, and loved it. Alex won the Edie Windsor Lesbians Who Tech Scholarship to attend Codesmith coding bootcamp in New York City, and now works on a team that values diversity. Alex tells us about her experience learning in Codesmith’s supportive environment, how she landed her new role as a Software Engineer, and why she’s happy to be increasing the visibility of women in tech.
Tell me about your career and education background – how did your path lead you to Codesmith?
My interest in engineering started when I was an undergrad studying Linguistics and International Studies. As part of my linguistics major, I worked on a project which involved building a website to document indigenous languages in the Oaxacan region of Mexico. That's where I learned that technology can be used in all these interesting ways, and there are all these interesting problems to solve.
After college, I had a hodgepodge of jobs, including jobs at nonprofits. In every job I had, I found ways to do engineering challenges, whether it be building small scripts and applications for a startup, or working with different content management systems.
I moved to New York and was feeling unfulfilled in my career, so I really decided to focus on software engineering. I was mostly self-taught at that point – I had only taken a couple of computer science classes in undergraduate, so I started teaching myself via online courses. I was just having so much fun with it.
How did you decide to go to Codesmith?
I started going to the workshops every week, and then I decided to apply to Codesmith’s immersive program and spend three months of my life devoted to learning. It ended up being one of the best decisions I've ever made.
Did you consider other options like other bootcamps, or going back to college?
I did, actually. I considered going back to college for a Master’s in Computational Linguistics. I also considered and tried some of the online learning platforms. But in terms of the learning environment that I wanted to be in, I know I learn better with people in a classroom or group environment, as opposed to learning online on the side with other jobs, or in the evenings. So I knew I wanted an immersive experience.
I did a paid, week-long prep course at one of the other bootcamps in New York. I liked it and doing that helped me decide that this path was right for me, instead of getting a Masters which is really expensive. Bootcamp programs aren't cheap, but compared to a two-year program, the bang for your buck in three months versus two years is pretty amazing.
When I went to Codesmith’s free workshops, I found the level of instruction was equal, if not at a higher level than the course I paid for. And so, I thought, "This is a no brainer, I'm definitely going to Codesmith." Also, I met such wonderful people at the meetups, and I was really impressed by Codesmith staff. It just felt right.
When you decided to go to Codesmith's bootcamp, what was your goal? Did you have a specific role or job or company in mind?
During the program, I was drawn to back end development. I'm not a very visual design-oriented person. I don't want to decide what a website should look like – I want to build it. Maybe I wouldn't have known that if I hadn't gone to Codesmith. Getting the chance to try out different parts of programming was really helpful for someone like me who was new to the professional side of the industry.
Congratulations on landing the Edie Windsor scholarship! Can you tell me about what the process was like to apply for that?
The Edie Windsor scholarship is a scholarship given by the Lesbians Who Tech organization, an organization which helps LGBT people, women, and underrepresented voices get into tech. They offer a really amazing scholarship which covers 50% off bootcamp tuition. For the application, I wrote two 500-word essays, then they sent me an email to say I was a finalist. The final email said, "Congrats, we've chosen you." So the process was really simple.
The scholarship is only one part of the work that Lesbians Who Tech does. They paid for my registration for the Lesbians Who Tech Summit in San Francisco, which was really exciting. I'd been to tech meetups, but it was my first full-blown tech conference and it was amazing. They do such incredible things for LGBT people and for women in tech. It's an awesome organization, and I feel incredibly grateful to not only have received the scholarship but also to be in this community of people. They have a Slack group, volunteer events – it's an incredibly impressive organization that I feel really grateful to have stumbled into.
Can you tell me about the Codesmith application and interview process?
It was not easy. It was definitely a little nerve-wracking. But the staff, the instructors, and Will Sentance, the CEO, were always incredibly supportive. That's a theme of Codesmith; everyone's incredibly supportive and is really rooting for you. It feels like a really positive space and energy.
I actually didn't pass my first technical interview. I was incredibly nervous because I hadn't taken a test since I was in college. I was being evaluated and it was really nerve-wracking, so I think I froze. They gave me feedback and let me come back for another interview a week later and I did a bit better. By that time, it felt more comfortable, and luckily they let me in! I got a call from the CEO, Will, who's a fantastic guy. He said I was ready to start in the April cohort, but I actually deferred to the June cohort, because I was so overwhelmed, and felt I needed to practice more. It was a good experience all around. Nerve-wracking, but ended up being good.
What was your Codesmith cohort like? How many people were there, and was it diverse in terms of gender, and race, age, and backgrounds?
It was definitely really diverse in a lot of different ways. There were 12 of us in my cohort. Four of us were women, which was great. It could have been better, but in the tech world, we take what we can get at the moment!
In terms of experience, there were some people who had been to a bootcamp previously, who decided to come to Codesmith because it was like the next level up. There were people who had never worked in the engineering industry, people who had worked in design or done some programming, people who had been going to hackathons for years, and others like me who had tinkered but never dived super deep into things. It was a great mix of people, which was really helpful because we were able to draw on each other's experiences. I met some of my best friends there!
How does that compare to the diversity at your job today?
I'm really lucky to work at a company that is trying to close the gender gap in their engineering team. The engineering team is about 30 people. Inside of that team, I’m in a group of four developers, two designers, a product owner, and a scrum master. I'm the only woman developer in my group, but we have at least 10 women developers in the whole team. But I can see the difference at this company, compared to places I interviewed where I would have been either the only woman engineer. So I feel really lucky to work for a company that is really committed to having an inclusive and diverse workspace.
Can you tell me about the learning experience at Codesmith?
There's a Junior Phase and a Senior Phase. During a typical day during your Junior Phase, you start with a daily warm-up exercise. Each learning module was organized in two-day sprints. So during the first day of a learning module, you have an intro lecture about a topic such as Node, React, or data structures. Then a big chunk of the day would be spent working on a problem set. On the second day of the module, you go over the answers to the problem sets with an instructor. Everything you do in your junior phase is with a pair programming partner, which I think is an awesome hallmark of Codesmith. It shows how much they invest in technical communication, to make sure that you're not just understanding the concepts, but you're also understanding them well enough to explain them to someone else.
The Senior Phase is the project portion when you build a developer tool. You're taking what you learned in your junior phase, and applying it to something that you think will be helpful to the developer community. People in my cohort built things like a Lambda orchestrator, a dev tool to help with GraphQL. I built an AWS metric visualizer, which was really cool.
How did Codesmith prepare you for the job hunt? What sort of career guidance did they give you?
The second part of the Senior Phase is the hiring phase. You work on your resume and do practice interviews. It's a whole other skill to learn and it's nerve-wracking, but definitely fun. You're working with people collaboratively, practicing out loud, doing mock interviews with your cohort-mates and alums. Then there's a hiring day where Codesmith brings in companies that really want to hire people. It's almost like speed dating. About 10 or 12 companies came to our hiring day, and we got to choose who we wanted to talk to. Then if they're interested, we could continue in their interview process. It's an amazing way to start to understand what kind of jobs are available and what people are looking for.
Can you tell me about your post-Codesmith experience and how you landed your current job?
I really hit the ground running after I graduated in September 2018. I spent about two and a half months applying for jobs nonstop. It was putting in the time and effort to follow up with the employers that I met on hiring day, reaching out to companies I was interested in, digging into my network, seeing who I could talk to, and going to networking events. My whole process lasted about two and a half months, where pretty much 9am to 5pm I was applying and interviewing.
What were your job interviews like? How did you do in the code challenges?
The interview process generally was a phone screen then a coding challenge with one of the company’s engineers. Then, depending on the company, there might be another coding challenge, or an onsite interview, where you would do a coding challenge, a culture interview, and meet different people who would be on your team.
It was a pretty grueling process. But I found it a lot of fun because I was also still trying to figure out what position would fit me best. So I really felt like I was interviewing them as much as they are interviewing me – and got to treat it as a fun conversation. My process with the company that I'm currently with included a phone screen, a technical interview, and an on-site interview. Then luckily, I was offered a job!
Congratulations! Can you tell me about your role and the projects you're working on?
My parents have no idea what I do, but I can tell them, "Go to that website, and click that button – I did that!" So that's kind of the fun side of web development. But then I'm also working with database queries, and different server-side problems, which has been really fun.
What’s been your biggest challenge or roadblock in your career change?
All things considered, things are going very well. But I think I do struggle with imposter syndrome. It's not that I didn't like math or consider myself interested in science or STEM topics in college. I put coding to the side as something that just wasn't for me a little too early on. Then I started to realize that coding is more about problem solving, finding patterns, and learning a new language. I wish that had stuck with me a little earlier. I'm glad I eventually got there. But I think the challenge has been my own confidence in myself, and thinking that "This stuff isn't for me, I haven't been doing this since I was 10 years old." And that's just not true.
While I'm definitely confident in my abilities, sometimes it can be really intimidating when an experienced colleague gets his tickets done much faster than I do, because he knows the code base better. There are days where I get frustrated with myself or frustrated that it's taking me longer to work out a problem. At the same time, I feel I'm able to hold my own in terms of learning new things. Luckily, I'm in a workspace where questions and collaboration are really encouraged. So I don't think I've ever felt like I couldn't ask someone if I get stuck. One of the best parts of my job is getting to work with my coworkers. This is an industry and a job where I'm constantly learning something new every day.
What is it like being a woman in tech now that you've graduated?
I'm still learning what it means to be a woman in tech. Again, I'm really lucky that the company I work for is cognizant and intentional about hiring women and diverse candidates. But it's always in the back of my mind, “Am I not speaking up because men are talking too much? Am I not speaking up because I need to learn a bit more?” I’m always thinking about the different power structures in the room and what effect that is having on me. I've made a conscious effort to speak at least once in every meeting to practice, so when I have something really important to say, I'll be used to speaking up.
Also, I'm part of a Women in Tech group at my company. It's about creating community, supporting people, and being visible. I'm really inspired, not only by some of the women in my company who've been there for a little bit longer, but also by the tech community in general. I'm always really excited when I see a woman speaking at an event. Visibility and representation are really important in all aspects for inclusion and diversity in tech.
Have your background and your college degree been useful in becoming a software developer?
The more relevant degree to coding is linguistics. Often when I say I studied linguistics, people will say, "Oh, that makes sense that you're a software engineer now,” because linguistics is focused on syntax, breaking down language into its smallest parts, and seeing how it fits together. And that's a lot of what coding is – logic, syntax, and how things fit together. So it makes sense that I found my way here because I enjoyed looking at and learning new languages.
But also, in the work that I did in the nonprofit world and the startup world, I learned how important communication is and how important it is to see the big picture. I'm really grateful for those experiences because that was where I learned how to work on a team, and communicate problems to people who might not be technical. I feel really grateful for having that experience, even if it wasn't directly engineering work.
Have you stayed involved with Codesmith?
Unfortunately, my job took me to a different city. I don't live in New York anymore, which is a bummer because I really miss all my friends from Codesmith in New York! But we do have group chats and there is an active alumni Slack channel – there’s a vast alumni network.
Anytime there's a call for grads to do mock interviews with current students, I like to do that because I remember how fun it was to talk to grads who returned to Codesmith. Anytime anyone is interested in talking to someone with a background like me, or interested in the Lesbians Who Tech scholarship, I'm happy to talk to people. I feel incredibly lucky to be part of the Codesmith community and know that there are smart, exciting, amazing people who are willing to help me and I'm willing to help them.
What advice do you have for other people, especially women, who are thinking about making a career change through a bootcamp like Codesmith?
You can do it. If you're waiting for someone to give you permission, here it is. Do it. It's hard to over exaggerate how much Codesmith changed my life. I never thought I'd be making as much money as I'm making now. I just never thought of myself as an engineer, even if I was doing things that were related. I met amazing people. It was really hard, it was really challenging, but it is the best thing that's ever happened to me. So if you want to do it, do it.
In today’s world, understanding the ecosystem beyond coding can be the difference between a junior and a senior software engineer. One part of that ecosystem is cloud computing infrastructure like Amazon Web Services (AWS). Schno Mozingo, Head of Curriculum at Codesmith, walks us through the basics of AWS, how companies and developers are using it, and why understanding AWS can help bootcampers land higher-level engineering positions. Listen to the podcast or read the article!Continue Reading →
Is learning to code on your 2019 New Year’s Resolutions List? It should be! The average coding bootcamp graduate gets a job in tech and sees a 49% salary lift. A coding bootcamp could be just what you need to make a fresh start in 2019 as a developer, so we’ve compiled a list of 18 full-time, part-time, in-person and online coding bootcamps which have upcoming cohorts starting in January and February 2019. Most of these coding courses have approaching application deadlines, so submit yours quickly if you want to get a head start in 2019!Continue Reading →
In the last week at Codesmith, students take part in Hiring Day, where employers visit the campus looking to hire new software engineers. Students interview with employers and show off their final projects. We visited Codesmith’s New York City campus and spoke to one student about his experience at Codesmith, what he built after 12 weeks, and how his ambitions have changed after Codesmith! Find out if Codesmith was worth it for Reynolds Colon.Continue Reading →
So you’re thinking about applying to a coding bootcamp. What should you expect in the application and interview process? And how do you ensure you get accepted to your dream coding bootcamp? We invited representatives from 7 coding bootcamps to ask all the tough questions about getting into coding school. In this live panel discussion, hear tips and advice about coding challenges, prep programs and more from Flatiron School, New York Code + Design Academy, Fullstack Academy, the Grace Hopper Program, Hack Reactor, Galvanize, and Codesmith! Watch the video, listen to the podcast, read the summary or transcript.Continue Reading →
Am I ready to apply to Codesmith? Do I need to have programming experience? What happens if I fail the technical interview? How do I improve my “technical communication?” Will Adamowicz just graduated from Codesmith’s 12-week Academy and spills the details about the application process (he’s now a Codesmith Fellow, so he knows the ins and outs). From basic steps to interview questions to preparation tips, Will answers all of your questions!
What are the steps of the Codesmith Application?
- Fill out an online application or attend a workshop at Codesmith to get a challenge code. That code sends you to a special application that guarantees you an interview.
- Attend a non-technical interview (can be done in person or over video call)
- Attend a technical interview (can be done in person of over video call)
How long does the Codesmith application process typically take? How long did it take you?
From the moment you apply to the moment you complete your non-technical and technical interviews can be as short as a one week. This is rare, though. Most students will plan several weeks – if not months – ahead to apply. In my case, I had a particular start date in mind and planned about two months ahead of that start date.
Codesmith accepts students on a rolling basis, though the process tends to depend on how much demand there is for a particular cohort. You’re definitely welcome to apply to a cohort several months in advance and you can also defer an acceptance up to three months.
What goes into the written application? Does Codesmith require a video submission?
The written application is fairly straightforward, just logistical info, a few essays about your background and passion for technology, and an optional coding challenge. There is no video submission required.
Can you give us a sample question from the non-technical interview?
One of the questions in my non-technical interview was: “What are your long term goals in software engineering? What do you want to do with it down the line?”
Is Codesmith looking for a specific technical background? What types of backgrounds have successful Codesmith students had?
About 50% of students at Codesmith come from engineering backgrounds and 50% come from non-technical backgrounds. Codesmith doesn’t look for any particular kind of background. I’ve seen everything from actors, school teachers, grad students, hotel managers, EMTs, and the list goes on. Having a technical background can help, of course, but there are so many factors that go into being a good engineer that it is not really a significant indicator of how successful you’ll be.
I had no coding background but studied logic and mathematics which definitely helped me in the admission process. Since I didn’t know anything about programming, I prepared for about three months before applying to Codesmith, doing three to four hours of study every single day. I had just come out of grad school writing long papers about analytic philosophy so I got accustomed to working alone and staying disciplined, but if this were a few years earlier I would have definitely signed myself up for a prep course to have some kind of accountability while studying.
Does every applicant get a Technical Interview?
Some candidates may not be a good fit for the program – in that case, they won’t get a technical interview. As a Codesmith Fellow, I interview candidates, and we generally look for excellent communicators who are also driven and passionate about wanting to become software engineers. We also want to accept team players. You’ll end up working very closely with a small team, so being able to work well with others is one of the biggest indicators of whether you’ll be a good candidate for Codesmith.
What can an applicant expect from the technical interview? Is there a coding challenge?
The technical interview involves answering a series of increasingly harder coding challenges. There is an endless list of challenges, so the goal is not to simply race through and try to get to the (imaginary) end. Much more important are things like technical communication and how you approach a problem that you don’t know how to do.
The engineer conducting the interview will stop after one hour and then send their notes off to the admissions team.
Can you give us a sample question from that technical interview?
Can I apply more than once if I fail the technical interview?
I think the current Codesmith acceptance is about 5% – I rarely see someone pass the technical interview on the first try. You can do the technical interview up to three times (if you fail the first and second). If you don’t pass, then the admissions team will give you feedback and resources to help get you up to speed. They’ll recommend a number of weeks for you to prepare until your next interview but you’re welcome to reinterview whenever you’re ready.
Most people fail the first interview, so don’t be discouraged if you don’t pass. Many people who fail their technical interview have even gone on to become Codesmith Fellows. More commonly than not, you’ll need to work on technical communication, so pair programming is one of the best ways to learn to talk through your ideas as you code them.
How do I get better at “technical communication?”
One thing that worked really well for me was recording myself doing algorithms and rewatching my problem solving. It was definitely painful at first but it helped me learn how to discuss a higher level strategy and talk about my implementation while going through a problem, which is an entirely separate skillset from the analytical thinking involved in solving a problem.
What resources do you suggest applicants use to really ace the technical interview?
The CSX platform (Codesmith’s online learning platform with instructional videos and coding challenges) is very good for preparing you to get in. Go to the Hard Parts weekly workshops or attend online – that’s one of the best ways to start working on technical communication. There is also a paid two week part-time online course called CS Prep that focuses on everything tested on the Codesmith technical interview and other qualities the admissions team looks for.
I would also recommend using websites like FreeCodeCamp or Codecademy to get the basics down, and to practice algorithms on coding challenge websites (Codewars, Leetcode, HackerRank). I’m also a big fan of this website, ReactiveX, for getting more accustomed to using higher order functions. It’s just a single tutorial but I found it very helpful in preparing me for the interview.
When do you think a Bootcamp Prep program is worth it?
Getting experience with pair programming is super helpful, so I would definitely recommend going to a prep program like Hard Parts or CS Prep if you think you’d have trouble sticking to a daily routine and want a little more guidance on the kinds of materials to study.
I was working in a kitchen in Kyoto in Japan when I started studying to get into Codesmith and soon realized I couldn’t get any productive work done after my shift, so I was getting up at 4:30am every day and practicing algorithms for a few hours every morning. I actually got my first opportunity to pair program by attending Hard Parts online and ended up being roommates during the program with my first pair programming partner. He was in China at the time while I was in Japan and next thing you know we were both in Venice, Los Angeles in the same cohort.
As a Codesmith Fellow, do you take part in the interviews? How do you evaluate an applicant’s future potential? What qualities are you looking for?
Does Codesmith accept international students? Do international students get student visas/tourist visas to do the program?
Yes, there have been several international students who have gone through the program with tourist/student visas.
Even after Brittany Miltenberger earned a bachelor’s degree in computer science and worked professionally in software (QA, Release Engineering, and Front End Web Development), she felt she needed to go to coding bootcamp to learn more advanced, full-stack web development skills and technologies. She chose Codesmith in Los Angeles, because she thought it would be a challenge and enrolled in the two-week Live Online CS Prep course to prepare for the technical interview. Find out how Brittany enjoyed learning remotely with others before she moved to LA, how difficult the Codesmith technical interview was, and her plans for the future!
Walk us through your career and education background. What did you do before Codesmith?
I have a bachelor's degree in Computer Science from Simmons College in Boston, Massachusetts. My interest in coding actually stemmed from my original major – music and audio production. Recording music with computers piqued my interest in software and UI/UX design. I found that I enjoyed deconstructing and building the software more than recording the music, so I switched my major to computer science.
After college, I became a Quality Assurance Engineer for a music production software company in Boston. It was a perfect fit and I was so fortunate. I was so thrilled to blend my interests in music and software. As a QA Engineer I was primarily conducting test scripts, then I got promoted to a Builds Release Engineer, a more technical role maintaining automated software builds, scripts, and creating installers.
Recently, I've been working professionally in front end and interactive web development. Over the past four years, I've built software for many aspects of learning – creating, developing, designing eLearning courses.
You had those technical skills and a computer science degree –why go to a coding bootcamp?
What made you choose Codesmith over other coding bootcamps?
I began by searching on Google, and comparing and contrasting different programs. I came across Course Report and read different reviews. Codesmith had stellar reviews; in particular, I liked that Codesmith prepared students for mid-to-senior level programming careers, which was exactly what I was looking for. I wanted to enroll in a program that would be challenging for me, where I would learn a lot.
In my last job as a Front End Web Developer, I worked remotely, so I wanted to do something in-person with other classmates. The two-week CS Prep program was remote and was excellent, but for the actual bootcamp, I wanted to do something in-person (Codesmith is 12-weeks, in-person). I live in Washington, DC now, but the Codesmith classroom is in New York and Los Angeles, but I was really eager to pursue Codesmith and relocate. I chose Los Angeles because I lived there a few years back, and it’s a great tech hub, especially in the Venice area and Silicon Beach.
Why did you decide to do Codesmith’s CS Prep program before applying for the 12-week coding bootcamp?
I enrolled in CS Prep to prepare for the Codesmith technical interview and to boost my confidence. I was so set on going to Codesmith, but since I wasn't in LA, I figured that enrolling in a prep course like CS Prep would be a great introduction – I could meet some of the fellows at Codesmith and other applicants. I was 99.9% sure I was going to enroll in the full program and CS Prep helped me confirm that.
I attended CS Prep from April 16th to 29th from DC, then interviewed for the full-time program in May. I flew to Los Angeles to do my interview and I got accepted. I start the full-time academy in LA on July 23rd. Right now, I’m starting a lot of pre-work and I'm so excited!
How was the application and interview process for the Codesmith CS Prep?
CS Prep does have a selective admissions process. At first, I thought, "am I even going to get in?" But actually, I found it to be a wonderful interview process. It was pretty stress-free. There were two parts to the application process. First I participated in a non-technical interview, to discuss my coding background and software engineering goals.
After that, I had the option of submitting short essays about my coding ambitions or completing a coding challenge. I chose the coding challenge. I’d been working through a lot of Codesmith's free online resources and I figured the challenge would be a good indicator of my readiness.
How did you feel about the prep course remote learning experience?
I did the live online CS Prep course alongside a group of other students. It was really cool because we used the video conferencing software Zoom, so for each class I could sign on and say hello to everyone – it was like I was in an actual classroom, but virtual. It wasn't a passive lecture learning experience – everyone could see each other and talk to each other so it was interactive. I always had to make sure I was listening and staying on track because, like in a classroom, I could get called on to answer questions. I found the whole experience to be so immersive. It was really like we were all there in person – it was awesome.
How many instructors helped you during the Codesmith CS Prep program?
We had four different instructors over two weeks, which was really cool. Some of them were Codesmith Fellows and had been through the program, so they could give us great guidance. It was nice to have a variety of instructors because everyone has different teaching styles. It kept the learning fresh and made it a rich learning experience.
Did the prep course teaching style match your learning style? What did a typical day look like?
It definitely did. Each of the instructors taught differently, but each was really excellent. I got so much out of each class. The overall class structure was very consistent, so that helped. We would start each class with a 30-minute coding challenge. It was a great way to warm up and get our gears rolling. Then we would go into a lecture on a new topic where the instructor would share a PDF and go through slides.
Another really cool aspect, and excellent virtual learning tool, was that we used iPads as whiteboards. In a lot of coding classes in real life, you'll have a whiteboard where the teacher writes some code on the board, and you walk through it together. But during our class, they would switch to the iPad view, and they draw with the stylus and walk through the code that way.
How difficult was the CS Prep Program?
It was honestly right in the middle of my expectations. It definitely wasn't easy. I put in several hours each day before class to review material. Although that wasn't required, I did it to keep on track. But at the same time, it wasn't crazy difficult, I wasn't beyond stressed and staying up all night studying. I felt like it was a really good middle ground.
I consciously resigned from my job, so I had the luxury of having time to study. But several students in the class were working nine to five jobs. If you are working nine to five, they have evening and weekend classes as well – so there's definitely a balance. You could go to a job all day and then go to CS prep, and I don't think it would be too overwhelming.
Can you tell me about the project that you built during the prep program?
The game’s source code is currently stored on our REPL account, but my team members and I are creating a shared GitHub account so we can actually publish it and share it.
Did you feel ready to apply to the full-time program at the end of CS Prep?
After the CS Prep program, my confidence level was boosted. Learning remotely can be intimidating because you may miss that sense of community. But one of the reasons I felt so prepared for the technical interview was because of the other students in CS Prep. We did so much pair programming, and that experience helped me with my technical communication. It's one thing to be able to code something yourself, but to be able to explain it and talk someone through it is of equal or greater importance. That was a big takeaway.
After you finished CS Prep, what was the admissions process like for Codesmith’s 12-week coding bootcamp?
It was a two-part process. The first part was a non-technical interview to assess my background and goals and to see if I was a good culture fit. It was definitely a longer interview and more in-depth than the CS Prep interview. We talked more about coding, my experience, and pair programming.
Part one wasn't stressful, but the second part was a technical interview, and I was definitely nervous. I did not need to fly to Los Angeles for that interview, but I wanted to check out the Codesmith headquarters in LA, and I felt that I may perform better in-person.
I coded each day for several weeks before the technical interview to make sure I was ready. That interview was challenging, and at some point, I hit a wall where I didn't know the answer. I had to take a deep breath, use technical communication (which I learned in CS Prep) and break down that problem, piece by piece. I had to show my knowledge, even if I didn't perfectly answer the question. Even though interviews can be stressful, Codesmith is really welcoming so I still found it to be a positive experience.
Could you have gotten into Codesmith without doing the CS Prep course?
I think I could have been accepted, but I would not have been as prepared for the technical interview. I would’ve been way more nervous. My experience with technical communication and pair programming at CS Prep built a really good foundation for a technical interview because I hadn't done a technical interview for a job in several years. CS Prep got me motivated and improved my confidence.
What are your plans after you graduate from Codesmith?
My familiarity and interests still lie within front end web development and design. But that could change as I work through the Codesmith curriculum. I'm really eager to learn more about full stack development, which is something I’ve never done professionally. For now, I just want a challenging job in a mid-to-senior level position.
I've worked for startups as well as huge corporations. I really dig the startup vibe and I’d like a job where my work has a direct impact. I'm trying to keep my options open when it comes to the industry I’d like to work in. I still have interests in music so it would be cool to combine art and code together again. I'm also aiming to work LA.
Do you keep in touch with anybody from the prep program? Is anyone going to the full-time program with you?
I've definitely kept in touch with several students from CS Prep. Some are interviewing and some have been accepted, which is awesome. Once CS Prep completed, we still did study groups a few times a week, and that was so valuable. Fortunately, we kept in touch.
When I went to LA a few weeks back, I met up with some of my prep cohort in person, so that was really nice. A huge part of the value I found in CS Prep was networking with other students who were applying, so I didn't feel so alone in the process.
What advice do you have for people thinking about attending a coding bootcamp? Do you recommend attending a coding bootcamp prep course?
I had a technical background before Codesmith, but for those who don't and are curious, I highly recommend a coding bootcamp. I was amazed with the other students – when I was pair programming and chatting with them about their lives and backgrounds, students who I thought had been coding for years, had just picked it up a few months ago. They learned fast! Computer science and programming can sound intimidating, but I've seen students excel so quickly. So if you are motivated, organized, and ambitious, it's totally doable.
Also, for those new to coding, it might be difficult to know what area of coding you want to go into because there are so many different sectors – back end, front end, full stack, etc. But there's a wealth of online resources for tutorials, so see what areas pique your interest. If you're still not sure, enroll in a bootcamp that can teach you various technical skills so you can figure it out.
In terms of Codesmith’s CS Prep, I highly recommend it. It was such a fantastic way to be welcomed into the Codesmith community. And there’s a great incentive where students who complete CS Prep get the tuition cost credited towards the full-time Codesmith tuition.
The Codesmith team understands that the best way for people to learn is alongside a community. So when they launched Codesmith CSX, a free online learning platform to prepare people for coding bootcamps, user interaction was front and center. Codesmith Senior Product Manager Haley Godtfredsen tells us all about the CSX curriculum, how to navigate the online platform, how users can take part in weekly pair programming sessions, and she gives us a demo of a CSX coding challenge!
What's your background and your role at Codesmith?
I'm a Senior Product Manager at Codesmith and I’m taking the lead on our new product – the CSX online learning platform. I've also been a Codesmith coach for about two years.
Can you tell us exactly what CSX is and why you are working on it?
Is CSX just for students thinking about applying to Codesmith or can anyone do it?
How long does it take to graduate from the CSX program?
It's different depending on what background you're coming in with, and how much time per week you're going to be putting toward learning. It's a completely free online program, and people can take it at their own pace. For someone who is less experienced, it could take them up to 60 hours. For someone who is more experienced, it would take less time than that.
Can you give me an overview of the CSX curriculum?
For those students taking the free version of CSX, do they work with instructors or is it mainly solo learning?
We really wanted to bring a community to the online space with CSX. Our weekly in-person workshops are focused on community. We make sure everyone feels comfortable and able to really put their best foot forward with learning because they're not worried about being competitive or asking a silly question.
All of our CSX videos are taught by our CEO Will Sentance, who is one of the top Front End Masters instructors. If you have questions while you're going through the free program, we have weekly half-hour office hours to ask a mentor or the CSX staff questions about the program itself or about a specific challenge.
If you have any questions, you can just shoot that into the general Slack channel and one of the mentors usually answers within a couple of hours. Other students also answer questions and help each other out on Slack, which is really exciting to see.
In addition to prepping for the Codesmith application process, what is the overall goal of CSX? What will students be able to build or do when they finish?
CSX is structured around a core Codesmith value: teaching students how to teach themselves. In this world of technology, things are always changing. The next thing is always right around the corner, and it doesn't help to get yourself in a very small hole by just being an expert in one technology. You need to know how to learn new technologies and new concepts. And that's what we want to bring to CSX as well.
There’s a lot more to being a software engineer than just understanding the technology. We also focus on technical communication and problem-solving, student pair program on a weekly basis to interact with other programmers and work on those skills. One way to understand a concept is by explaining that concept to someone else. We expect students to come out of CSX with a refined ability to tackle any type of problem, whether they've seen that problem before on CSX or not.
It’s cool that CSX students actually build a real project.
Yeah. We also award scholarship opportunities based on submissions of that Chrome Extension project. Recently, students had two weeks to build a Chrome Extension and our team awarded a 25% scholarship to Codesmith to the winner.
Okay, Haley – share your screen and show us what CSX looks like!
The CSX layout:
- Every unit is represented as a card on the main page.
- You’ll get an overview of which units are available, then pick and choose where to dive in.
- It's not necessarily a chronological course. If you have an understanding of one concept and you want to dive into another one, that's totally fine.
- You can watch our newly-released, professionally-shot video content and view the slides.
- Students are able to test their work from console logs. In the future, Codesmith will implement unit testing, so that students know immediately if their entries are correct.
Where should users start?
- The Overview of CSX is a great place to start out.
- The Codesmith technical interview tests certain core fundamentals – you can learn about those in sections 1 through 4 (up to the Recursion unit).
- If you’re prepping for other coding bootcamps, focus on Units 1 through 3.
- Depending on what you're using CSX for, you can pick and choose which units to attack or which concepts you really want to understand better. Once you're familiar with a concept, you can move on.
- Codesmith has plans for more content and will be releasing more features.
Watch the video to see Haley walk through the CSX unit about Variables.
It's awesome for people to be able to connect and work through problems with people around the world. Online learning can often be very solitary and it's hard to keep motivated when it's just you in your room alone. We do a lot of pair programming in our full program and in our in-person events, so we wanted to bring that to the online space.
How can students pair program on CSX?
- First you need to sign up and verify your email address. Then you can RSVP to a weekly pair programming workshop.
- You’ll rate your comfortability with the concept that will be covered in the workshop
- You’ll get a link to the challenge for that week's pair programming session. The email includes some instructions and best practices for pair programming. You’ll both go into the session knowing who the “driver” is and who the “navigator” is.
- During the pair programming session, you can use video + audio to talk to your partner.
What are “navigators” and “drivers” in pair programming?
- The navigator does the problem solving, working through how to get to the solution, and using their technical communication to relay that information to the Driver. In a navigator position, technical communication is very important. You need to know where you want to go with the problem so you can explain the steps to get there.
- It’s up to the pair to decide who wants to be the driver and who is the navigator.
- We encourage students to switch roles every 20 minutes, or every challenge so they can both get experience using the different skills that come from each position.
How is CSX different from other free online resources like Codecademy?
I'm a huge fan of Codecademy, but what we wanted to bring to our CSX is really hard learning. Hard learning isn't done best by yourself. It's easy to stop, hit a block, and not want to continue. We wanted to supplement that with live workshops that complement each unit that we have filmed live, as well as videos on CSX, weekly pair programming, and weekly office hours to give people that actual push.
If you have questions and you're struggling, you have other people to work with and you have mentors to ask questions. We think that you learn from hitting a block and working through it, as opposed to being walked through a programming tutorial like Codecademy.
How often do students actually get accepted into Codesmith (or other coding bootcamps) after going through CSX.
Since CSX is relatively new, we don't have any hard data on this. We have a lot of students in our most recent cohort who have been using it. And talking to them, it sounds like it was really helpful. I do think that it's helping our students start off on the right foot.
How else can students prepare for Codesmith?
We're releasing two new programs in March that are more structured, paid versions of CSX. The Live Online program is two weeks long, and is a version of the free program condensed into a two-week program, with three weeknights and one weekend day per week, with live instructors and office hours, and a focus on problem solving and technical communication.
Then we have a self-directed four-week program, which you can take as long as you want to finish. There's no focus on how far you get through it, but there are weekly personalized office hours, assessments, and pair programming with a mentor who can help you through if you're struggling. That course ends with a mock interview for Codesmith, to prepare you for the real thing.
There will be scholarships available for these programs. And if you are accepted into Codesmith, that tuition comes out of the full bootcamp tuition.
What's your advice for students who are considering this CSX program?
Set yourself up with goals and the achievable tasks to get to those goals. Make a plan and commit a certain number of hours per week, making sure that your schedule allows for that. Pair programming is important, and using to those office hours is super important too.
It's easy to stop when you’re learning online, so remember that there is a real community to take part in. Ask questions on Slack, meet other students on Slack, come to in-person events, or attend a live stream. Set yourself up with the expectation that it's not going to be easy. The CSX program is a really great path with a lot of support.
My best advice: be ready to hit blocks and then be ready to solve them.
What will your salary be after coding bootcamp? Coding bootcamps are judged almost entirely by their ability to find students high-paying jobs as software developers. Some schools release data about alumni jobs, others offer money-back job guarantees or deferred tuition, but how much are students earning when they graduate and how does their earning potential change as they gain experience? Every year, Course Report surveys real coding bootcamp graduates to better understand who is graduating from coding bootcamps and how successful they are in the workforce. In our second post of this series, we explore the lucrative data about salaries after a coding bootcamp.Continue Reading →
Tell us about your career and education background. How did your path lead you to Codesmith?
My college degree is actually in math and physics because at the time I thought I wanted to go into research or a PhD program in either math or physics. I wasn't totally convinced, so I decided to take time off from being in school to evaluate that pathway.
While I was taking that time off, I started substitute teaching just to pay the bills and ended up really liking teaching. I ended up teaching high school physics for about six years. Teach for America brought me to Los Angeles, where I taught for four years at a public school.
How did you become interested in programming?
The last school I taught at wanted to pilot a computer science course and I was the only person at the school who had any inkling of experience with programming, so they asked me to teach it. I had never taken a computer science class, but in my physics degree, we learned a little bit of programming for number crunching, large physics calculations, and simulations. I remembered liking that work, so the idea of teaching that computer science course was exciting. In the process of lesson-planning, I found myself wanting to spend my free time diving more deeply into it.
That experience is what really got me interested in programming and making the career switch into being a software developer.
What made you take the next step from teaching computer science at a school to actually changing careers and becoming a software developer?
My background is in technical fields – math and physics – and I found myself missing doing technical work myself. Spending time learning about computer science in order to be able to teach that course gave me the itch to do more technical work myself. That's what initially got me thinking about making a full-time career in software development.
Why was a coding bootcamp the best way to achieve that goal?
When I first started thinking about transitioning into software development as a career, I wasn't necessarily going to go down the coding bootcamp route. I started to consider coding bootcamps because even though I was a classroom teacher myself, I actually found it really difficult to be a student in the traditional classroom. I knew that if I wanted to go into software development, it would be really helpful to have some coaching or mentorship as I learned.
I wanted a place to learn with other people who were interested in programming as well, but I also wanted the transition to be faster than going through a traditional, multi-year master's degree. I knew that even if a coding bootcamp was difficult in the moment, I would be able to get a lot out of it very quickly and be able to start my career as a software engineer in a really good place. To be perfectly frank, I guess I was a little bit impatient!
How did you find Codesmith?
Having been a teacher in the classroom myself, I was really impressed with how hard Codesmith worked to build community, both with the students who are currently studying there and with the beginners who were coming to that free workshop every week.
Did you research other coding bootcamps? What stood out about Codesmith?
I did look at a few other coding bootcamps, but to me, community building is really Codesmith’s secret sauce. They work hard to create the kind of environment where everyone wants to learn at a really high level, wants to push themselves to the limit, and is 100% there to support every other person who's going through the process. It really allows you to push yourself and learn as much as you can without fear that you might fall behind – you've got 20 other people who are there with you to support you along that journey.
Was it a competitive application and interview process to get into Codesmith?
As a former teacher, what did you think of the Codesmith teaching style? Did it work with your learning style?
There are so many things that Codesmith does right, pedagogically speaking. Most impressively, their entire focus is where it needs to be: on the students’ learning. Students work on projects that are intended to help them learn a certain topic, and these projects are large in scope and open-ended; they're typically too large to be completed within the allotted time. The ultimate example of this is the Production project, where students spend the last six weeks of the program working on large, cutting-edge software project of their choice. My team and I decided to create a library for testing WebRTC applications, and as far as we know, we were the first people in the world to do so.
Since the projects are so large and open-ended, the point is that students dig into it and work as hard as they can. It’s not about finishing the project because, in the real world, you're never finished. Instead, it’s about taking away an enduring lesson. At Codesmith, learning is the most important part of the process. Instead of telling you how to solve a tough problem, the instructors gently nudge you in the right direction. In the moment, that can be frustrating, but you're really learning the most when you struggle. It's by fighting through confusion and overcoming barriers that we become stronger as software engineers. That's really what engineers do in their day-to-day work.
This style of learning was definitely cultivated at Codesmith and it's something that they emphasize and articulate as much as possible. Going through the program helped me to articulate those principles to myself more clearly. Working in education for the past several years, I had some frustrations with aspects of the traditional educational system because I felt it was too task-oriented and focused on the solution instead of the learning itself.
How did Codesmith prepare you for the job hunt?
The job search mostly happens within the last few weeks of Codesmith, and then during the next couple of months after you graduate. Codesmith does mock interviews, whiteboarding sessions, resume writing workshops, coached us on negotiating salaries, and exercises to build our confidence as we go off into the job market and start applying for jobs. There’s also a Hiring Day where they invite companies from the Los Angeles area to do interview speed dating with the graduating class. It's not uncommon for many students to get called back for onsite interviews due to Hiring Day. After graduation day, once we’re in the actual job search, Codesmith did regular check-ins to see how we’re doing on the search.
Codesmith was always very open and receptive. If I wanted to talk one-on-one to the Codesmith staff, they were very open to that as well.
How did your first technical interviews go for you?
I thought doing technical interviews was fun. It was a little nerve-racking at the time, but I always find that once I'm actually in the middle of the interview, talking about a programming problem or some technology or something about the company, that the fear goes away and I just start enjoying the conversation.
One of the things that was interesting about interviewing with several companies in a short timeframe was getting to talk to various people working in different environments. It was good to hear about the company cultures, and really get a sense for the type of environment I wanted to work in since I was so new to the tech world.
What have you been up to since graduating? Tell us about getting your first job!
I found the Codesmith alumni community to be really helpful and supportive in the job search. Now that Codesmith has been around for about 2 years, there’s a pretty significant alumni network. We have a very active alumni Slack channel and people are pretty frequently posting jobs on that saying, "Hey, my company is looking to hire a full stack engineer. Private message me if you're interested." That’s how I ended up getting my first job at MedCircle. I went for the interview and I really enjoyed the company and the team.
MedCircle is an online health education company in LA. It's a very small startup company – less than 10 people on the whole staff.
I worked at MedCircle for about 10 months and got to build the team workflows from the ground up, which was pretty cool. About two weeks ago, I started a new job at Google in San Francisco.
Congrats! What are you now working on at Google?
My official title at Google is Web Solutions Engineer. I'm primarily working on internal software tools that the sales and marketing organization use to do their jobs better. It's pretty exciting because, at MedCircle I worked on a small, agile, flexible team. My team at Google is similarly small and flexible, but it's within the context of the Google organization, so I have access to all of these resources and incredible world-class software engineering.
How did you make the move from MedCircle to Google? What was that process like growing into your next job?
I actually interviewed with Google back in December 2016, during my first job search after I graduated from Codesmith and before I was hired by MedCircle. Evidently, if you interview and they don't hire you but still like you, then Google keeps your name on their short list. In August, I got a message from a recruiter at Google saying that they had a Web Solutions Engineer position open up and asked me if I'd be interested in applying for it.
How do you feel you've grown as a developer? Where do you feel you are in your learning experience?
No matter where I am in my career, I always want to push to learn and grow more. One of the things that Codesmith does really well, more than just emphasizing learning one particular technology stack, is that they emphasize learning how to be confident technical problem solvers and engineers. Even straight out of Codesmith, I was pretty confident in my ability to solve difficult software problems, even if I wasn't necessarily familiar with all of the technologies being used.
Now, having been in the industry for a year, it's given me a lot more depth of knowledge in the kinds of tools, best practices, and higher level problem-solving techniques that it takes to really write high-quality software that is robust, that lasts, and that does its job well.
I’m also growing in different contexts. Google is such a large company; in order to accomplish anything, I have to learn a lot about the infrastructure of the company as a whole. It’s been pretty exciting to see how software engineering can really work at a massive scale.
What's been the biggest challenge in your journey to becoming a software developer?
What’s most challenging about software engineering is also what’s most exciting: there’s basically an infinitely deep pool of things to learn. In order to really be able to perform at the highest levels, you need to be willing to put in the time and effort to keep learning, whether you're on the job or not.
I've put a lot of hours and energy into trying to improve my skills even outside of work hours. But as I said, there's always interesting problems to work on, always new technologies to learn, and always new products to imagine. Because with software, anything that you can imagine you can create as long as you're willing to stretch your imagination and embrace the possibilities.
Would you advise other bootcampers to go into a small startup first like you did?
I think it was the right decision for me, but it depends a lot on the person and on the company. What’s more important than the size of the company is really understanding the company's culture during that interview process. For me, I like having a lot of flexibility in what I work on and being able to work on different projects, so I knew that working at a small company like MedCircle would give me that. Being forced out of necessity to wear different hats really made me into a more well-rounded engineer. I’m more confident when I have to tackle problems in a variety of different domains.
For your first job after a bootcamp, choose a company that will bring out the best in you and a place where you can continue to learn at the same rate that you were learning while at bootcamp. That can really vary a lot from company to company whether it's small or big, so feel out their company culture and choose based on that.
You have a background in Math and Physics – is it true that you need to be “good at math” in order to be a great software engineer?
I took Codesmith’s Machine Learning class after I graduated, and that topic was exciting for me because machine learning does involve a lot of math. My background in math gave me a good foundation to learn more in that area.
However, you definitely don't need to have a background in math in order to be good at software engineering. In order to be a strong software engineer, you need to be a strong problem solver. Being good at math is just one possible way to acquire those problem-solving skills. My background in math has definitely helped me, but I don't think it's the only way to get the skills needed for software engineering.
When you look back at the last two years, do you think you would have been able to get to this point by self-teaching or going back to a traditional school? What kind of role did Codesmith play in your journey?
I honestly doubt that I would’ve been able to make it to where I am today this quickly if I had gone down a different path. If I had done a master’s degree, I probably would’ve gone back to school in the evenings and continued teaching full-time, which would’ve drawn out the process and not allowed me to focus all of my attention on learning as much as I could. That would have made the career transition a lot more arduous.
When you teach yourself, it's easy to end up stuck in your own bad habits because you don't know best practices and how to get to the next level. Learning within a community of other people who are passionate about software engineering means that you can all help each other. You can push your thinking to the next level and get unstuck when you hit a roadblock in your learning. You always feel like the work that you're putting in is reaping benefits, because you can see the growth day by day and week by week. That rapid growth is really what allowed me to reach my goals so soon after deciding to make the transition into software engineering.
What advice do you have for our readers who are considering a coding bootcamp like Codesmith?
Your time at a coding bootcamp is very short, so it's important to really squeeze the most out of the experience that you possibly can. It's not enough to just go to class during the day and then go home. It's really important to get to know your classmates and help each other grow. It's rare that you're surrounded by so many other people who are this passionate about the same goals.
Codesmith works so hard to build community, not only between current students but also between professionals by hosting meetups for local software developers. If you can really take advantage of that community, then that's where you'll see the most incredible growth in yourself.
Everyone seems to be talking about Machine Learning. But what is Machine Learning, and do you really need a PhD in Math to master it? LA coding bootcamp Codesmith has recently added a machine learning unit to their core program, and will soon launch an entire Machine Learning Bootcamp. We asked Codesmith’s Director of Machine Learning, Weylin Wagnon, where to spot machine learning in everyday products, why knowledge of machine learning is useful for software developers, and what the job market is like for developers with machine learning skills.
- Machine learning is a subset of AI, where a computer uses data and previous experiences to predict outcomes
- Machine learning tasks include those which used to be done by humans such as fraud prediction and ad placement
- Any task that is currently tedious for humans but still requires some creative decision-making is a target for machine learning software.
- Codesmith is teaching machine learning with a code-first attitude, by introducing the concept to students as a new tool and a new library
- Software engineers who know how to interact with machine learning systems are future-proofing their skills
What’s your experience in machine learning?
I run a cryptocurrency mining farm, where we manage mining for our clients who want to invest in cryptocurrency. It’s very complicated to set up and do at scale, so we streamline the machine learning process.
What is machine learning?
In general, Machine Learning is equal parts math, statistics, computer science, and voodoo. Machine learning is very different from the traditional software engineering or programming paradigm. In computer science, you provide a set of rules and input data to make some kind of output. In machine learning, you switch that around. You input data and input the answer you want to see, and the machine figures out the rules required to get that answer. It is a little bit magical, it’s pretty challenging, but with a clear approach to understanding machine learning, it is possible to do extraordinary things with these tools.
How is machine learning different from artificial intelligence?
The standard general purpose computer is not intelligent. Artificial intelligence gives the machine some automated behavior that we consider “smart.” Machine learning is a subset of Artificial Intelligence and requires learning from previous data. As humans, we use our previous memories to influence our future behavior; machines can learn from previous data to do the same thing. Overall, AI doesn’t imply data alone, whereas machine learning is all about data.
Where do we see Machine Learning in the real world? Can you give us some examples?
Anything that is currently tedious to do for people but requires some kind of creative decision making is a target for machine learning software. Most of the cutting edge machine learning projects are coming from large companies that have huge data sets. For example:
- Google Photos and Apple Photos dynamically identifying faces in pictures and auto-tagging people.
- Shazam, which identifies songs, has been greatly enhanced through machine learning.
- Speech systems like Siri, Google Home, and Alexa, are all good examples of machine learning ability.
- Fraud reporting, which used to be done by humans perusing financial records, but is now accomplished with algorithms.
- Some core business uses have been around for a while – 10 years ago, machine learning was used to predict which advertisement a user would click on, and we still use advanced neural networks for the same task today.
How can machine learning be useful for a software developer?
Machine learning exists in an application ecosystem (like an API). So even if a developer doesn’t want to touch the whole backend of an application, they are still going to have to interact with some of these systems. Having at least an understanding of the concepts behind machine learning can be valuable in the long run when designing systems.
Any exposure to machine learning is a really good mark on your resume. Having interacted with such machine intelligence systems shows that you have a strong competency with current and future technologies.
Why has Codesmith decided to add Machine Learning to the curriculum?
Google I/O’s last conference (and every main stage) was fully focused on AI and machine learning at all times – it’s a significant trend.
You need to be able to work with large amounts of data, be a smart programmer, understand neural networks, and have machine learning skills if you want to build the next generation of tech products. And if you don’t, you’ll be left behind over the next 10 to 15 years. It’s hard to observe the future of jobs and not be scared of how machine learning is taking over; I think the best way to stem that tide is to get into the field yourself.
Tell us about the new machine learning unit at Codesmith and how you came up with the course.
We are now offering an entire unit within Codesmith’s core software engineering residency, plus a six-week stand-alone course for alumni and experienced coders. I just finished teaching the unit. It’s not a complete course, but it does give students all the tools they need to go forward in machine learning. We ran a beta-version of our six-week course for alumni, got a lot of feedback, and are iterating right now for our public course. It’s exciting to push software engineers on the right path. Machine learning is something that will be hard to avoid in the future so it’s really valuable to get into the space right now.
I spent a long time researching before writing the curriculum. I paired up with Kush Kumar, part of the USC Machine Learning Department, who is a stellar expert in the field. Combining his expertise with my teaching background, we forged the content together.
Can you really teach machine learning at a coding bootcamp? How do you fit such a vast topic into a short course?
We teach machine learning in the last quarter at Codesmith, so that students have the most experience and can gain the most from it. As we go through Codesmith, the pace of students’ comprehension accelerates, so they get used to picking up new information fast.
The core Codesmith unit is focused on teaching students about general machine learning ideas, providing a framework to think about machine learning, and defining terms that we’ll see a lot. We are focused on coding best practices first. Then, we’re fitting machine learning into the curriculum as a new tool and a new library, and not as a fundamentally alien concept.
We do a deep dive into re-engineering some machine learning algorithms so we can see it’s not just magic. But on this level, you don’t have to engineer everything yourself. We teach libraries like Pandas to enact a lot of complex behavior very quickly. The program is mainly project focused as we go through, and we also practice pair programming.
Students also learn some DevOps, neural networks, and Tensorflow. By the end of the unit, they’ll have covered the vast majority of the machine learning field and will be able to autonomously create projects.
What is the job demand like for machine learning skills?
In LA, job listings mentioning machine learning often offer salaries 10% to 30% higher than regular software engineering roles. The goal of our program is not to produce data scientists, data analysts, or data engineers – we’re aiming to graduate engineers who can build advanced programming products and meet the needs of a “machine learning software engineer” job listing. Companies are getting very competitive as the demand for machine learning engineers grows faster than the supply. The main source of machine learning talent comes from master’s degree or PhD programs, so it’s a challenge for companies to find enough engineers to rapidly prototype machine learning products. In addition to being in great demand, machine learning skills are a great accent to any software engineering role.
Is there anything you’ve had to leave out of the Codesmith machine learning curriculum?
We don’t cover neural network libraries in our Codesmith unit, but we can provide resources for students who are interested in learning more, and we highly encourage alumni to take the full machine learning course.
We always hear that you don’t have to be a math whiz to be a good programmer, but do you need math skills to do machine learning?
In the machine learning unit, we don’t focus a lot on math. People get the idea that machine learning is only about math because of Andrew Ng’s popular Machine Learning course from Stanford, which is all focused on the calculus derivation of different algorithms, and how to implement them. But that knowledge is not required to build machine learning projects – most of it is already wrapped up in libraries. So your math ability doesn’t impact your ability to implement machine learning systems.
However, at some point in your career, you may want to develop new machine learning processes, and then that math and algorithms research will help you. But in general, it’s not as big of a requirement as people think.
What’s an example of the sort of machine learning projects that students would work on at Codesmith?
At Codesmith, we mainly focus on portfolio projects. Having a significant portfolio of work is so important to getting hired in machine learning. Students work on projects which involve making graphs that convey information, getting insights from data, and then presenting the insights in a way that’s understandable for less technical people.
Who is teaching this new unit? How will you train your instructors to teach this new machine learning unit? Or will you hire new instructors?
So far I’ve been the sole instructor along with our advisory member Kushaan. I am hoping to continue contributing as long as I am able, plus we have some super talented engineers who have been studying machine learning on their own and have attended all of our machine learning courses. We like to take a multifaceted approach – we have really talented teachers, engineers, and people with math backgrounds, and it’s through all of us working together that we can make it work. It’s a community approach.
How often does the Codesmith team update or add new units to the curriculum like this?
We reevaluate the curriculum after every graduating class and talk about whether topics are still relevant, and whether we can improve. We add content often, like new lectures, or individual focuses, but rarely whole units. So this is exciting!
Can students in both LA and NYC campuses learn machine learning?
So far, we’ve only taught machine learning at the LA campus. Our first NYC cohort starts in two weeks, and we hope to also offer machine learning there eventually. Stay tuned for our separate machine learning course, which we are hoping to launch in the near future.
Are there resources or meetups you recommend for machine learning beginners?
The best machine learning resource for beginners is a YouTube channel called Welch Labs. He’s a fantastic teacher and makes the subject really dynamic. You can learn about the field and the core concepts behind it, without requiring advanced math.
There are also plenty of online courses and interactive online portals. I don’t particularly like those, but some people benefit from them as an introduction to concepts. Those online courses can make you feel like you’ve accomplished and learned a lot, but you have no autonomy, and having to define a task for yourself afterward can be really challenging. I think an interactive course where you build projects is the best option.
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 the October 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 fundraising announcements, to interesting trends. This month we are also covering our Women In Tech Snapchat takeover! Other trends include new developments in the industry, new outcomes reports and why those are important, new investments in bootcamps, and of course, new coding schools and campuses.Continue Reading →
Will Sentance is co-founder and CEO at Codesmith, a full stack coding bootcamp in Los Angeles that launched in fall 2015. Before that, he worked as a software engineer, and started his own e-commerce platform. Will says learning to code changed his life, and he wanted to pass that experience and knowledge on to others. Will explains the Codesmith curriculum, what Codesmith looks for in students, and how to prepare for the interview. Also find out what sort of jobs Codesmith graduates are getting!
What were you doing before you decided to found Codesmith bootcamp?
I worked as a Software Engineer at Gem, which is now a Hiring Partner at Codesmith. Before that, I was CEO and cofounder of Ownly, a social e-commerce platform I started while studying at Harvard. Gem is doing some really transformative work in the Bitcoin and Blockchain space for developers– we were finalists at Techcrunch Disrupt. It's a model for Codesmith graduates– exceptional technical talent yet great communicators. I loved the team there.
Why did you want to start a Los Angeles coding bootcamp?
Coding changed my life and the lives of significant people around me. It gave us the ability to build the ideas we dreamt up. People learn to code for many reasons from aspiring doctors who want to change medical document processes to people who love solving puzzles. I love getting to see all of these backgrounds come together to support each other in the program.
Many coding bootcamps these days have been founded by graduates of other bootcamps. After attending Hack Reactor, what did you think was important to keep about the bootcamp model and what did you iterate on?
There are distinct differences. At the end of the Codesmith program, we have our hiring event where companies from across the US come on site to interview graduates. This is very distinctive and is part of why the graduate outcomes are so strong.
The community of Codesmith Los Angeles is also extraordinarily tight-knit, with cohorts of 15 (two running at the same time) selected from over 300 applications. It plays out in the average leaving time each night– most people leave the campus close to midnight, six days a week!
What is the admission process like?
We look for people who have great potential in problem-solving and communication (both technical and non-technical). Before the admissions interview, there's a basic coding challenge online and special harder challenges given out at many of the free classes each week. If you complete these harder challenges, you're guaranteed to get an interview.
Your first interview looks at your interests and commitment to supporting others. This is followed by a technical interview. There you will work through various coding challenges, and we work with you as you navigate through. It's like a mini session of Codesmith.
How are graduates performing in the real world?
The graduates are doing remarkably well. They are doing everything from developing an organic grocery marketplace at Thrive Market, to a life-changing charitable platform at Omaze, to supporting 20m+ football fans at the NFL. By the end of the year, over 200 Codesmith grads will be out building great things with code. Graduates receive offers averaging $103.5k, with 92% hired within in 4 months– mostly in LA and SF. Companies like Whisper, Hautelook and others have hired multiple grads– that's a wonderful sign of the impact the grads are having at each company.
What types of final projects have Codesmith students built?
Students build a portfolio of four projects while at Codesmith– the final being the 'Production Project'. Students have built applications for clients including the Los Angeles School District and the University of Michigan Hospital.
Some of the most impactful projects have been tools and libraries for developers like React Monocle and React-D3 library. These developer projects have trended on Github and Hacker News and are now being used by thousands of developers including Hiring Partners of Codesmith.
Why is it so important for students to actually launch their apps in the real world?
Launching a project gives students production experience– handling user issues, bugs and requiring students to work as professional developers as opposed to working on artificial 'bootcamp' projects. It really makes the graduates stand out– it's a big part of why 95% of graduates join companies as mid-level developers or above.
What is the current class makeup in terms of gender, race, background? Is it diverse?
Students come from a wide range of backgrounds. While many have STEM experience or even Computer Science degrees, there are also students who were creative writing majors or didn't attend college at all!
We have scholarships for students from backgrounds that are underrepresented in technology, and we work closely with Girl Develop it and Women Who Code on free classes and curriculum to help show people that they can aspire to Codesmith whatever their background. But we have to do more.
How do you attract a diverse applicant pool to Codesmith– is that important to you as a founder?
It is crucial. In the coming years, more and more leaders of firms will come from a software engineering background. We have an opportunity to give people from all backgrounds that path to leadership. In November, we are starting a new Women in Technology Speaker Series and new scholarships in partnership with leading technology firms– to further attract a diversity of applications.
How should new students approach Codesmith?
We have high expectations for applicants in their interviews, but we also have an extraordinarily supportive community which is ready to help you reach your potential and prepare for your application. Join us for any of the classes in person or online– whether or not you end up at Codesmith, you'll find your partners in crime to code with.
How does the CodeSmith experience prepare students for job interviews?
Companies expect a lot from Codesmith graduates. They're going to be offering six-figure salaries so they expect people who are capable of solving problems without too much supervision.
The program is designed to prepare graduates for exactly these demands. To do this, the curriculum pushes you to perform at a level that impresses seasoned engineers, both through professional engineering best practices, and a structure that is heavily project-based. This makes you ready for deep technical discussions and challenges at interviews
The second half of the program moves into dedicated job-search preparation– through mock interviews, resume and online profile development– all culminating in Hiring Day.
Tell us about your employer partnerships.
We have a network of over 250 Hiring Partners who are required to have a strong engineering culture and who hire mid-level and above developers. A select group joins onsite for Hiring Day for multiple streamlined interviews. Nearly half of our graduates get offers from companies they met at Hiring Day.
Have you been through the regulatory process with the BPPE in California? Is it important that you become accredited?
The regulatory system is outdated for sure but efforts are being made to develop a new approach. In the meantime, we have begun the process of getting officially accredited by BPPE
What’s next for Codesmith? Are there plans to expand geographically, or to expand the curriculum?
I believe we've barely scratched the surface of the number of people we can bring the ability to code to, as well as the number of organizations and industries that can be transformed by engineers who can lead. I want our alumni to continue to develop as leaders in tech after they graduate. So we're working on new ways to give our alumni all the support they need to make that happen.
Many competitive coding bootcamps want you to have some programming knowledge 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 →
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,906, 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.
Move over tinsel town and make some space in the greater Los Angeles area for some of the finest coding programs in the country. While LA once paled in comparison to San Francisco when it came to the sheer quantity of bootcamps, we've seen a surge in LA coding bootcamps this year. There is a wide choice of code schools with campuses in LA's "Silicon Beach" that all bring a unique take on web development training.Continue Reading →
Welcome to the June 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!Continue Reading →