Ask HN: Should I fret my GitHub activity when job hunting?

I think you're over thinking things. Tech hiring is so random that you could have the most impressive list of projects on github, but if you get asked a single data structure question that you stumble on they might pass. Similarly, you could ace the white boarding questions, but if they check out a project of yours on github that they don't enjoy for some reason they might pass.

I would stick to doing whatever will give you the most confidence when talking to companies. If that is studying data structures/algorithms then keep doing that. If its launching a side project focus on that instead.

Thanks for the feedback-- that's what my hunch was. I agree completely. I think hiring _is_ quite random and that is partially what puts me on edge. I want to prepare and give myself the upper hand but it's so random it's hard to prepare for.

I do think data structures and algorithms are a must and if I had to guess, stumbling on the whiteboard is probably the most common reason for a rejection which is why I think that is something that needs to be practiced.

The other things may just be gravy.

"the 'GitHub as a resume' hype, it worries me."

You shouldn't. If you have a github account with a couple repos that are not forks you're good.

Also, I don't think reading books on interviewing and solving interview problems is a good preparation. If the company doesn't focus on what you have done (like your own projects, which sound great) and instead gives you stupid interview problems on the whiteboard, run away.

Thanks--

In my experience most companies are the 'stupid' problems, I certainly wish more companies would stop all the bad habits but it's pretty wide spread :(

It's up to us to do our part and refuse to dance like puppets :)

There are plenty of great companies who are trying hard to improve the hiring process and move away from the whiteboard exercises and brain-teasers.

I systematically refuse to interview with people who ask me how many tennis balls would be required to fill up the empire state building.

Ditto on the first thought. If anyone is actually digging through your github, they're going to look at much more than just the activity graph, but the (non-forked) repos you have.

> Part of my preparation is reading books on interviewing...

Beyond interview prep, consider that your job search is similar to a sales process. A couple of books worth reading as you think through your approach to the market...

Gitomer's Little Red Book > http://www.goodreads.com/book/show/75890.Little_Red_Book_of_...

Perry's Guerilla Job Search> http://www.goodreads.com/book/show/9746430-guerrilla-marketi...

These are now on my book list, thanks!

Work on the commercial project. Even if it hasn't shipped, it is something worth talking about. What features did you implement, what were the challenges you faced along the way, what would you do differently next time?

Thanks for the feedback! It's a commercial SaaS product and it's feature complete (server written in Go). The client workflow is complete as well. I am in the last "10%" which is all styling, polish and making the experience feel great. This part takes a long time (at least for me).

I'd love to steer my interviews down this question line, it makes a lot more sense than, "Regurgitate how to perform a binary search", etc.

Don't believe the hype. A good resume, some confidence, and practice is all you need. Remember: You are not looking for everybody to hire you. Just one place. It doesn't matter if you 9 turn you down if #10 hires you. :)

Best of luck!

PS. If you need an test interview email me. I'll try and help.

Thanks! I may take you up on that offer :D

I think you're thinking too much about this, with all the things to worry about, your github profile should be far down on the priority list.

Thanks!