= 27d567bc2d48d9f40e9ccc20ea370b15)
ChrisHallquist comments on Open Thread for February 11 - 17 - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (325)
Ignore what they say on the job posting, apply anyway with a resume that links to your Github, websites you've built, etc. Many will still reject you for lack of experience, but in many cases it will turn out the job posting was a very optimistic description of the candidate they were hoping to find, and they'll interview you anyway in spite of not meeting the qualifications on the job listing.
This is just a guess, but I think it might be helpful to include some screenshots (in color) of the programs, websites, etc. That would make them "more real" to the person who reads this. At least, save them some inconvenience. Of course, I assume that the programs and websites have a nice user interface.
It's also an opportunity for an interesting experiment: randomly send 10 resumes without the screenshorts, and 10 resumes with screenshots. Measure how many interview invitations you get from each group.
If you have a certificate from Udacity or other online university, mention that, too. Don't list is as a formal education, but somewhere in the "other courses and certificates" category.
I think ideally, you want your code running on a website where they can interact with it, but maybe a screenshot would help entice them to go to the website. Or help if you can't get the code on a website for some reason.
You want to signal a hacker mindset. Instead of focusing to include screenshots it might be more effective to write your resume in LaTeX.
It depends on your model of who will be reading your resume.
I realized that my implicit model is some half-IT-literate HR person or manager. Someone who doesn't know what LaTeX is, and who couldn't download and compile your project from Github. But they may look at a nice printed paper and say: "oh, shiny!" and choose you instead of some other candidate.