Get a Better Developer Job

More interviews. More offers. More money.

If we haven’t met, my name is Philip Yurchuk and I’m a consulting CTO and dev community organizer. I put this material together from interviews with other hiring managers and developers, but also my personal experience as a developer, hiring manager, and even contingency recruiter.

That last one was an attempt to fix the hiring problem. I had a lot of encouragement from people on both sides to try it. What did I learn? The hiring problem can’t be fixed. Too much human nature.

However, through all of this I noticed some patterns. Patterns that few have seen and fewer talk about openly. I started documenting it and this is the result. I’ve also given this as a talk to hundreds of developers. Feedback everywhere has been positive, so I’ve repackaged it as an online book with no signup required. It won’t fix “the hiring problem” but will help you get hired.

Note: The link to the next chapter is at the bottom of each page because the book is meant to be read straight through.

What You’ll Learn

  • Career strategies that factor in the reality of today’s job market, including what it rewards and punishes:
    • should you specialize? and how?
    • choosing an employer
    • creating an action plan (or digging yourself out of a hole)
    • the truth about side projects
    • finding the perfect mentors
    • evaluating offers
    • certifications
  • Resume mistakes that keep you from getting hired and tips that get you noticed
  • Interview preparation, including a huge list of videos, courses, books, and sites to master coding interviews – most of it free. Plus what to ask, wear, do, etc. to get an edge.

Why am I doing this?

This was a lot of work. Many hours. So asking why it’s free is totally reasonable.

I know a lot of people in tech. Run the largest Java User Group in SoCal, used to run the biggest tech interview meetup here. Give tech talks. Belong to 40+ meetups. I have over 1,300 LI connections and I’ve met most of them. Lived in 7 countries. Bottom line, a lot of people come to me for career advice and I’m very happy to help. But there’s no time in a one-on-one to cover everything here and I’m sure to forget something. So like a good, Lazy programmer I’ve automated my advice giving. Any one-on-one happens after they’ve read this and covers the problem unique to that person.

I also wanted to learn marketing automation, so I created an email course in MailChimp. Was a good experiment, but now it makes more sense to just make it all public and get an SEO boost.

Finally, as a consulting CTO I help non-technical companies and founders get quality software products built very efficiently. A lot of my referrals for that work come from programmers who are asked to do the work, but don’t have the bandwidth or interest (perhaps for reasons listed in this book). And sometimes they want to do the coding, but not all the other management stuff, so we partner. So if you have a referral or a partnership makes sense, shoot me a message.

Help somebody's career:

Next chapter: Principles