I'm a developer and I recently saw a developer job posting with a headline I thought was fairly meaningless. I wrote a quick post recommending using a "job title, primary tech" format for headlines. A friend, who has been a professor of computing, disagreed and said that presenting the problem the job needs to solve rather than the tech used to solve it would make the headline more clickable for him. I understand that, but think it's really hard to describe many tech problems succinctly enough for a headline. Is the title and tech approach too boring? Is the "state the problem in 15 words or less" approach too difficult? What is the best way to write a headline for a job posting that will inspire devs to read it?
I told a recruiter recently that I responded to her specific post because I saw "C++" in the subject line. It was complete news to her, that naming the programming language would help.<p>A particular problem I see is that when I go looking for C++ jobs, the search form turns up javascript jobs that name C++ as a qualification.<p>The job title is not so important to me as the problem to be solved. Like "GUI, C++" would be good.
FWIW, this is the post: <a href="https://www.linkedin.com/pulse/one-weird-rule-job-post-headlines-greg-bulmash" rel="nofollow">https://www.linkedin.com/pulse/one-weird-rule-job-post-headl...</a>