Before You Try To Get A Tech Job, Build Stuff

It’s great to go through a coding school and learn the in’s and out’s of whatever code language is in question, but potential hirers want to see what you have built.  Often times, it does not have to be specific to what they do, they just want to see your ability to be creative and apply your knowledge.  In the best case scenario, you will be able to get a few freelance clients, which often leads to more and more conversation about you (assuming you do a good job).


One Project Leads to Another
Sometimes a client may subtly ask you questions that seem not to pertain to the current project you are working on. If you are smart about reading your client, you may begin to understand that he or she is feeling you out for a potential new project. When your client asks strange questions about other things, sit back and answer the questions carefully, and just assume that there may be other work in the future.

In addition, you may want to subtly mention to your client about something else you are building or working on—not because you want to scare him or her about your availability, but because it will increase his or her perception of your value.
Honestly, sometimes it just takes time. There are only so many large projects to be had out there, and only so many will fall into your particular skill set. Generally, it is a good idea to sync up with other developers or other people and work as a team so sometimes you get a piece of a big job you don’t have to get yourself.

If you would prefer to work alone, give it time and seek out large projects that fit you perfectly.

If you're looking for some serious preparation for your interviews, I'd recommend this book written by a lead Google interviewer. It has 189 programming questions and solutions:

Book Cover

Leave a Reply

Using Gravatars in the comments - get your own and be recognized!

XHTML: These are some of the tags you can use: <a href=""> <b> <blockquote> <code> <em> <i> <strike> <strong>