I'm a bit late to this, but I'll give you my experience. It echoes what others have said to some extent. In every instance I've applied for a job, it began wit

I'm a bit late to this, but I'll give you my experience. It echoes what others have said to some extent. In every instance I've applied for a job, it began with my casually (but assertively) stating interest. Here is the process I go through (you could call it my job hunting "workflow"): 1. I read about an interesting company or meet/talk to someone with connections to an interesting company. 2. I learn what I can about them, researching for a few hours, deciding if I'd enjoy it (on a cursory level). 3. I contact people with decision making ability and politely but assertively state my interest. Note - I don't send a resume (you can, I don't). 4. Most cases, I've gotten through an entire hiring process without being asked for a resume. If they happen to ask, it generally suffices to show them my portfolio of prior work. This is in fact as simple as linking the list of projects I've authored on my blog with corresponding code. 5. Technical interview(s). Negotiation. Wrap up. Bam, you're done. I highly, highly suggest you read patio11's "Don't Call Yourself a Programmer"[1] and "Salary Negotiation"[2]. No, really, read both. Absorb every kernel of knowledge. The importance of a resume is grossly overestimated, as is the importance of a transcript. Don't show a piece of paper, show the knowledge that your education provided you with. Connections are important, and will field you the most significant leads in finding a job. [1]: http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/ http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pro... [2]: http://www.kalzumeus.com/2012/01/23/salary-negotiation/ http://www.kalzumeus.com/2012/01/23/salary-negotiation/