How not to write a job post

I commented on a similar post a couple of months ago but will re-paste it here.<p>A good job posting in my opinion must include:<p>- LOCATION or REMOTE. You can talk all about your great company, awesome team, great perks but if you don&#x27;t tell me where do I need to go, it is really not very useful.<p>- COMPANY NAME: I hate it when recruiters post &quot;Fortune 500 client&quot;. Really ? Could you be any more specific ? &lt;&#x2F;sarcasm&gt;<p>- SALARY RANGE: &quot;Market Rate Salary&quot;, &quot;Salary: Competitve&quot;, &quot;Salary: commensurate on experience&quot; is all bullshit. Give me a range. I understand that the exact salary could depend on how good you are but every employer has a range. Specifically big companies. Also, please make the range reasonable. 60K-150K is bullshit because then you are just throwing numbers for the sake of it. 60K-85K or 100K-130K is more reasonable.<p>- TEAM DESCRIPTION: Describe the team as much as possible without necessarily revealing personal info. I would rather like to read &quot;We are a team of 5 people spread across the globe where 2 of us do the back end dev in NYC.......&quot;. Don&#x27;t give me generics like &quot;Excellent motivated team working on world changing projects looking for the next ninja to join our awesome team&quot;. Really again ?<p>- WHY ARE YOU LOOKING TO HIRE: This is a must for me. Is this position open just because you have some cash to burn to show good to the management that you are &quot;growing&quot; the team or is there really a pain point that can be addressed by hiring. What problems are you facing currently that could be solved by this hire ? It is better to be needed than being a nice to have.<p>- BENEFITS: This one is a nice to have. But again be specific if you can. You offer 401K&#x2F;pension ? awesome. now tell me what the employer match percentage is. Or at least link to your HR benefits site if it is externally available. I am always surprised to see how little you know about benefits until you are hired. In the US, health insurance is a big deal. I want to know upfront what kinds of plans are offered which could impact my salary requirements as well.

Can I have a quick micro rant here: I don&#x27;t want to know about perks when I&#x27;m job hunting. Tell me about the type of work (not a wishlist of skills you want), the ball park pay (not a range), the location (I&#x27;m looking at you, agencies), the level (entry level vs management) and the type of hours (I&#x27;m the type of weirdo that has a life outside of work). I don&#x27;t care if you have free lunch or free t-shirts. I expect to work hard and get paid for it. P.S. Forget the marathon gauntlet interview with multiple skype calls; that&#x27;s why I send you a copy of my resume and give you references. OK, rant over. Please carry on. Nothing to see here.

There are a few things I want to know about when looking at job posts: tech stack, target salary, what the company is, and a small list of perks. This will give me an idea of what the office environment is like.<p>I hate it when job postings start listing out needed skills. I read one the other day listing 5+ years of HTML5 and CSS3 experience. When it comes to years of experience, you&#x27;re more likely looking for a particular level of knowledge and some people are going to get there in a year or less, and others will not get there no matter how many years of experience they have.

Apart from very confused about what an adjective it, this article nails it. Just because it&#x27;s &quot;ninja&quot; and &quot;rockstar&quot; instead of &quot;monetise&quot; and &quot;synergy&quot; doesn&#x27;t make it any less meaningless jargon.

Can&#x27;t access because the site is down, but I have a lot of feelings about this topic. Specifically, please never, <i>ever</i>, use one of these words to describe the developer you are hunting:<p>ninja, cowboy, rockstar, superstar, virtuoso, obsessed, &quot;lives and breathes code&quot;, knowledgeable about some arbitrary activity or hobby to show how quirky and social the team is...<p>It gets tiring, as a professional, to read these job postings that sound like they&#x27;re an ad for a teenage boy&#x27;s summer camp. Usually the non-programmer postings will read like, you know, jobs for adults. Also, when you&#x27;re asking for a &quot;virtuoso&quot; for your 60k junior dev spot, I don&#x27;t know whether that means you don&#x27;t know what that word means or you&#x27;re just delusional. Either way, it sounds like everyone definitely has a puffed up ego.

In my mind, a job posting, and the responses to it, are just intended to start a conversation.<p>Getting all worked up over what is or is not in the posting seem kind of silly to me. If you don&#x27;t like the way it was written, fine - don&#x27;t apply.<p>If you have questions, just apply. If they contact you, ask those questions. If they don&#x27;t contact you, the answers didn&#x27;t matter anyway.<p>Applying for a job is not a declaration that you want to work there. It is a statement that you are interested in discussing it more. All the real information gathering, in both directions, happens during the interview process.

If your job ad doesn&#x27;t give some indication of salary, then it&#x27;s literally useless to anyone worthwhile who might otherwise consider applying. Good candidates will only apply for jobs that they feel are worthy of them. If they can&#x27;t even tell whether you&#x27;re going offer $10k less than they&#x27;re already on, they&#x27;ll just move on to the next listing.

And site seems down :-)

Anyone have a mirror of this? It seems to be down...