Dear (YC XX) recruiter, please include job location in your HN submission title
You're an amazing YC company looking for your N-th amazing hire, where N is an amazingly small number. The technology is fantastic, the team is fantastic, the benefits are fantastic, the potential upside is fantastic. It would be an honor for little old me to even be considered for a job interview. I'm not even worthy to have you read this message right now.
Yes, I get all that. But do you get that that's the same story for every YC company, all of which are really, really great opportunities?
So what three things separate one YC early-stage job opportunity from another? Location. Location. Location. No job perk is so great, and no problems you're solving are so tough and so interesting, that they'll make up for a lousy commute.
Let me know right away: WHERE IS THE JOB? Don't make me waste time figuring out where you are. Here's one that just got it right: "Meta (YC S13) is hiring 4 roles in the South Bay (Los Altos, CA)." And one that just got it wrong: "PagerDuty (YC S10) is seeking an exceptional Engineering Manager." The worst example I won't name, but it took me a few minutes to figure out where they were located--and their product was a hyper-location service!
So, recruiter, before posting make sure your title answer's this one question: What's the Location, Kenneth?
1 comment
[ 3.1 ms ] story [ 17.2 ms ] thread{company}, {location} ({yc season}) looking for {role}
Role should be the actual function title and if applicable mentioning the language-stack (i.e. RoR, node) the candidate should master.
hopefully PG sees it this time