4 ms·

I'm really not talking about something lengthy. But I get 100s of applications for every job post I publish. Most people who apply are frankly not qualified. If

I'm really not talking about something lengthy. But I get 100s of applications for every job post I publish. Most people who apply are frankly not qualified. If you are qualified, write a few sentences. "Hey, I saw your post for [...]. I thought this looked great for me because I have worked on [...] and I am super excited to learn more about [....]". I am not asking for paragraphs, but show me you are interested. I honestly spend hours writing and reviewing the jobs I post and it takes probably 100+ hours total from a team to hire a person. We want to hire you, but you've got to help us. :)

mdavid626 9y ago
I think hiring is completely broken. At least in IT. Developers don't understand HR people, and HR doesn't understand developers. For me "Hey, I saw your post for [...]. I thought this looked great for me because I have worked on [...] and I am super excited to learn more about [....]" means absolutely nothing. Frankly, I do NOT know you or your company and in a job description there is nothing about the team, culture etc. But I have no other option just to make something up, because otherwise no one'll hire me.
- nathantotten 9y ago
  Where I work, engineers hire engineers. You are right on some level that it is hard to know exactly what a company does, but for many jobs in software that isn't entirely true. Read the companies blog, look at their open source projects, use the product, and most importantly read the job posting. I really don't think you'll have to make something up if you really are a good fit for the role.
  - mdavid626 9y ago
    It's working really well when engineers hire engineers. I've no problem with that. They don't ask questions like "Why do you want to work for us" or "What are your strengths" or "Tell me about a situation where ...". Not every company has a blog, open source projects and many of them have no public products and are privately held. So, I can see the job description and the website. I don't know if you are an HR person or not. No offense. I'm not against them, but have very very very bad experience with them.

mdavid626 9y ago

I think hiring is completely broken. At least in IT. Developers don't understand HR people, and HR doesn't understand developers. For me "Hey, I saw your post for [...]. I thought this looked great for me because I have worked on [...] and I am super excited to learn more about [....]" means absolutely nothing. Frankly, I do NOT know you or your company and in a job description there is nothing about the team, culture etc. But I have no other option just to make something up, because otherwise no one'll hire me.

nathantotten 9y ago
Where I work, engineers hire engineers. You are right on some level that it is hard to know exactly what a company does, but for many jobs in software that isn't entirely true. Read the companies blog, look at their open source projects, use the product, and most importantly read the job posting. I really don't think you'll have to make something up if you really are a good fit for the role.
- mdavid626 9y ago
  It's working really well when engineers hire engineers. I've no problem with that. They don't ask questions like "Why do you want to work for us" or "What are your strengths" or "Tell me about a situation where ...". Not every company has a blog, open source projects and many of them have no public products and are privately held. So, I can see the job description and the website. I don't know if you are an HR person or not. No offense. I'm not against them, but have very very very bad experience with them.