it doesn't take much
TRANSCRIPT
Include a project
• Link to a specific GH repo you’re proud of• Zip of a current project• Link to a blog article explaining a project in
depth
DO NOT
• Send only a link to GH• “I have some code if you want to see it.”• “I can do a coding challenge if you have
one.”
Be Clear About Your Experience
• “I’ve been working with Ruby on Rails Professionally for 4 years”
• “I’ve worked on multiple projects using Backbone”
What it does not mean
• “10 years of web programming experience”
• “Thorough understanding of Ruby, Rails, jQuery, CSS/HTML”
Do you meet the requirements?• “You are looking for a person who is well
versed in TDD. I have 3 years practicing TDD”
• “Your posting said you were interested in EmberJS experience. I have not had the pleasure of working with Ember but I’m sure my prior experience in Backbone will allow me to quickly understand and master Ember”
Name Dropping is GREAT
• “I’ve worked with John Smith at meet ups before”
• “I spoke with one of your developers at a Conference, Steven was very friendly and he helped with an issue I was having.”
Sweat the details!
• Spell the employer name properly, using proper case
• Check for spelling errors• Ensure your call the person by the correct
name!
Any writings are really helpful
• Blog - ALL THE TIME• Writings help show you can communicate• Writings help show you understand your
tools