Respond to a Review

Responses should answer questions and address concerns raised in the review or clarify information about your school. Once we authenticate that you are an official school representative, we will publish your response under the corresponding review. Each review is limited to one response, but you may submit a new response to replace the previous one. Please restrict comments to addressing the content of the review in question and refrain from including advertising/promotional material or unrelated exchanges. Official representatives will have the option to make a contact email available, but please avoid directing users from our site through other means.


Reviewer Name Review Body
Simon I discovered WeGotCoders by chance while browsing the internet and the course really peaked my interest. I was super fortunate that it was located only about a 20 minute drive from my house so when they announced they were doing an open day for potential new students I jumped at the chance to go meet the people at WGC and see what it was all about. I was super impressed by not only the location and the house but also by Dan (the owner and lead instructor at WGC). I did a code challenge and was offered a place on the course. I did the course with 5 other awesome people and had an amazing time. It was also one of the toughest 3 months of my life as you are basically learning and coding from 9am to 9pm (if not later each night), and is something I am really proud that I accomplished. You don't just learn how to code, you learn how to think as a developer, how to discuss and explain your code to others and also how to present your code properly to other developers. This is nerve racking at first, but after 2-3 days you settle in fine and this becomes the norm. A typical day at WGC looks like this: 9am-10am - 1-2 people will present their code from the previous day, explaining what they did, why the did it and then the group discuss any other approached they could have taken and any code improvements they could make. 10am-3pm - Dan or one of the other instructors will teach the days lesson which will teach you any new concepts, technologies etc. This is generally mixed up between lectures and code alongs. 3pm-Late - You are then given your daily coding challenge and you then split off into pairs or small groups to work on the challenge, which will you will then present the next day in the morning. Once you finish your course you have 2 weeks to make your final project which you will then present to CEO's, CTO's, startup founders etc who come along to see what all the fuss is about. As it happened there was a CEO at my presentation who I would eventually go and work for. While this does not always lead to a job, there have been members of WGC who were literally hired the same day as doing their presentation. Once I had finished the course I went for 4 interviews which were arranged by Dan. I was offered 3 out of the 4 jobs and after much deliberation accepted a job working for an awesome security startup. I worked for that company for 9 months until they unfortunately ran into some funding issues and I had to move on. As it happened Dan was looking for developers for a new project that was starting, and the CEO who I had presented to only 9 months earlier hired me to help build his Pharma startup. I was really pleased that Dan found me so many interviews for some really cool jobs almost immediately after the course. Dan will do his very best for you and try to get you interviews and a job after you graduate, but this does depends on if there are any opportunities available at the time, otherwise his hands will be tied and you may have to find something yourself. So would I recommend this course to anyone who wants to become a developer? Absolutely! You cannot go wrong with the course as long as your willing to put in the hard work that is required. The course will give you all the skills you will need to become a junior/mid level developer with skills that employers love. I don't know a single person who graduated from the course who didn't get a job as a developer, which in its self pretty much tells you as much as you need to know.