Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community!

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Getting a Job after studying at Treehouse

Hey everyone,

it's been quite some time since I last posted here. I just wanted to share with everyone that after about 2 months, and 4 interviews, I finally landed a front web developer position!

I've decided to share whatever advice I can give because I remember how it was for me when I first started seriously using Treehouse, perusing through the forums and reading all the amazing stories the site shares about going form 0 knowledge to being job ready and wondering If that were something I'd be able to do.

Moreover, (to the best of my knowledge) no one ever really shared the job hunt process in it's entirety. Treehouse will definitely give you the foundations necessary, but there's so much more involved in creating a career for yourself. So, I just wanted to create a discussion where other aspiring developers could ask me questions about how I was able to land a job and the job search process in general.

So feel free to ask as many questions as you like, and I'll do my best to answer them.

8 Answers

Martin Cornejo Saavedra
Martin Cornejo Saavedra
18,132 Points

First, congratulations on your new job!

Which tracks/courses did you do in order to learn front-end development?

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.

Congratulations on landing a job! Could you share with us some of the other things you did to help improve your skill set?

On a side note, I just visited your website. Imgur Is there something wrong or did you intend for the words "designer & front-end developer" to be darker than the rest of the text? It's barely visible.

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.

Congrats on the Job and thanks for the encouragement that you are sharing with me and others

jack AM
jack AM
2,618 Points

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

Outside of treehouse, what other resources did you use? How did you get to the point of getting comfortable making websites on your own?

Hey guys,

Sorry I'm a little late with my response time, I've been busy so bare with me.

Jack, as far as coding questions go it varies from position to position depending on what the company/agency needs at the moment & that's always changing so you wear a lot of hats. They'll ask you about the basics first like your background, what attracted you to the field, etc. Some have been really big on bootstrap and have quizzed me on css & html. Others have given me entire tests in JavaScript, html, css, and php (bombed that php part) that are timed & your first answer is the answer you have to go with. Not because they necessarily care about how long it takes you, but to see how you think under pressure. The most common test though, has been in 2nd or 3rd round interviews where you have to translate a design mockup to basic code in a certain amount of time.

Christian, please see my reply under Aarie's comment. I think it'll give you the insight your looking for

Also, sorry for any misspellings, poorly structured sentences that might not make sense. I'm writing this on my iPhone and im kind've in a rush.

Glad to see this post being of some use to you guys!

Happy coding!

I almost forgot to tell everyone thank you for all the wishes on the new job! Means a lot from me & I can't wait to return the sentiment when you guys land your gigs!

Erion Pali
Erion Pali
Full Stack JavaScript Techdegree Student 16,964 Points

Congratz James, are you able to tell us specifics on questions they asked during your interviews? How much depth they expect us to know in a given topic? Do they ask about the more complicated stuff such as design patterns and algorithms?

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.