By Jon Saints - 16 Dec 2013
I recently went through a job search and compiled some notes on what worked and what did not. This is me searching for software engineering work in Colorado in late 2013.
I presented this to the Lafayette Tech Meetup. Here are the slides.
I am not sure why companies even bother posting jobs on their web sites! Only one out of many got in touch with me later. I am not the only one with this experience. (Perhaps I just wasn’t qualified for 99% of the jobs I applied for… )
I found my github profile page to more important than my resume. I am not exaggerating. If you are looking for a developer position today, your resume is secondary. Start curating your github page today. My Github profile started many many more real conversations with potential employers. (In fact Google called me out of the blue saying “hey we noticed you have been committing a lot of Python code, do you want to chat?”. I did not get the job in the end, but did get a couple of real conversations in interviews.)
Ways you can create a profile worth looking at:
Too busy to write full working code for you Github profile… try README Driven Development!
Just create detailed readme of your idea with complete install steps and documentation. Show example of how the user will use your code to solve a problem. The community might just start a discussion… my Improvements for Git got to #5 on hackernews.
Clear READMEs can quickly show off an innovative solution to a complex problem. They also make a great spec for when you do start coding.
Here are examples of a couple of my README Driven Development projects:
You are selling your time and talent. Two of your most valuable possessions! Fight for them.
The interview is not just for you to impress them. They need to impress you.
Some questions that I asked:
Look for interesting companies
Find a way to understand deeply what they do… grab coffee with an employee… find an in through your network
Propose a role. Tell them how you can help them most.