John Jonas explains why job posts flop. Common mistakes: paying too little (like $200 a month for full-time work), writing vague job descriptions, listing too many requirements, or chasing skills so specialized almost nobody has them.
My job post didn't get enough applicants. What did I do wrong? This is a very common question that people ask when they make a mistake with a job post. The issue is one of two things. Usually either you made your salary too low, which is super common. Like I saw a job post the other day where someone said, oh, I didn't get, I only got three or four applicants and can you look at this? So I looked at it and was like, well, you offered $200 a month for full time work for someone who's really talented. That just doesn't cut it. That was good like 15 years ago. The other thing that I see often is that you didn't put any description in your job post. So they don't, people don't know what they're trying, what you expect them to do. They don't know what they're going to be working on. Or on the other end of it, you put too much. So this, that same person who asked for $200 a month also asked for a programmer and a writer and a designer. Like, well, that's not even a person, that's not even a thing. So I guess there's three things. Your salary is too low, you didn't put enough description in your job post, or you put too many requirements in your job post. I guess the last thing that could be is you're asking for a very, very specialty person. And if you're asking for a very specialty person, you're just not going to get as many applicants. It doesn't matter what you do, it doesn't matter how well you've written your job post is if there aren't that many people that can do your job, you're not going to get very many applicants.
Stop Being the Dispatcher, Start Being the CEO: How to Scale Your Field Operations 🛠️
