> if asked to provide code in an archive, don't splatter files inside my pwd
I think that displays the typical pickiness of people that do hiring. I mean, you could just type 'unzip -l' to check the contents of an archive. Similarly, the resume format. Practically every hirer requires a different format nowadays - pdf/txt/doc/odt/html - that simply maintaining a CV becomes a massive time sink.
Actually I specify tar.gz. This is actually a subtle test -- the job requires *NIX fluency and those who had ever compiled a few packages would have noticed the convention. That's my train of thought anyway.
As for resume format, it is an open source job and my main machines are all MS-free, so it is extra trouble (especially if it is docx). Just a preference, that's all. I didn't advertise otherwise.
Tip for maintaining multiple formats: asciidoc/markdown = text you can generate html with. And once you have html you can print to pdf from a browser. 3 formats for the price of one.
Bear in mind I wasn't trying to write a list that's canon -- just what I like to see. I'm not going to chuck applications simply because they missed a point in that list of recommendations.
I think that displays the typical pickiness of people that do hiring. I mean, you could just type 'unzip -l' to check the contents of an archive. Similarly, the resume format. Practically every hirer requires a different format nowadays - pdf/txt/doc/odt/html - that simply maintaining a CV becomes a massive time sink.