Getting a Job after studying at Treehouse

Hey Martin,

Thanks! I used the Front-End Web Development, Web Design, & Full Stack Javascript Tracks, as well as a few other courses here and there. I'm pretty sure you can just click on my profile to get each and every course, workshop I've done.

Hey Aarie, The black text on a black bg was done on purpose for a few reasons:

1. As an experiment to see how different people react to it. So far it's been like a 51/49 where those more concerned with function hate it make up about & those that are more artsy love taking the risk.

2. I love black on black, so I'm constantly experimenting with the concept on the web. Also, whenever I meet new in people in the industry, it gives me the opportunity to get feed back on how to get better use out of things like inset shadows, and other cool css features. However, it can become very hard to read & is obviously not a best practice.

As far as other things I did to build out my skill set:

1. Don't just complete the courses for points and badges. You have to practice & implement what you learned. Personally I like to complete a course then go back over it multiple times until everything really sticks, then try out doing it completely on your own, then adding your own twist to things here and there.

2. Side projects/ freelance opportunities outside of treehouse where you are forced to learn on the fly and in a hurry. Because if you don't, it's your reputation on the line. If you have an idea, go for it with what you have at your disposal at the moment, skills at wise.. Then learn as you need to.

3. Google, stackoverflow, github are my best friends

4. In the tech space, you never stop learning, so there's never a right time to start looking AND applying to jobs. You just never know. More importantly. The skill requirements listed on job postings will give you a better understanding of what you need to learn, and what companies consider priorities versus bonus skill sets.

5. Building up my confidence. <---- this is just as important as everything else I've said so far if not more important. No one is going to think your good enough, if you don't think your good enough. For me, I had to get over that "fear" hurdle of "am I ready? Will I get in over my head? And then get fired after like a day on the job. But the way I built my confidence up is just by taking a leap of faith and getting out into the real world. Going on intereviews & getting rejected. You learn a lot about where you are and where you need to be from those situations. I was able to even land a mentorship from a great developer at company that ended up going with someone else. And the things I've learned from that guy in just a few hours time, has sped up my development flow 20 fold. But again, that would never happen for me if I didn't put myself out there.

Firstly, GRATZ! But would you mind sharing with us, what kind of coding questions you were asked?

Hey Erion,

I guess the best way to answer your question is to say the questions you get asked will really depend on what kind of developer you want to be/role you're applying for. I wanted a front-end/design sort of role, so I didn't have any questions necessarily involving things such as algorithms. Mine were more so along the line of: "Here's a layout one of our designers created, now make it function", "What's your IDE look like?", "Here's some code, can you tell us what's wrong with it, or how you would improve it." I even had one interview where a company asked me to recreate a custom subscription page on an e-commerce website with a layout that accounted for 9 items instead of 3 for one of their multi-million-dollar clients. Truthfully, every company's going to be somewhat different in their requirements and the questions will reflect that.