A couple of months ago, after writing a few blog posts about hiring and job descriptions, I started working on an idea with Jim Kosem and Matt Webb. We called it Project Mordenite.
Here are some of the ideas we had:
- The importance of being specific: The more senior a role, the more tempting it is to use generic management jargon. When you use generic or vague descriptions, a smarter system would point that out for you and ask you to be more specific or add more context. For example, instead of saying a candidate would ‘manage a team’, it would ask you to be specific about how many people you would expect someone to manage and whether there are timezones that need to be considered. By being more specific, it lets people understand what’s expected of them early on and avoid new hire remorse. Being clear and more importantly, realistic, leads to better hires with more clarity about what they’re getting into and a better understanding for hirers and less disappointment.
- Treating job descriptions as a cultural touch point: For many prospective employees, your website and your hiring process is your front door, so let’s start treating JDs like an important cultural touchpoint instead of a listing for used furniture. A smarter system would take an existing JD you might have Frankensteined together, ingest it and tell you how boring it is. It would look at every other JD in its Small Language Model (SLM) and give you a ‘similarity rating’ so you can increase the differentiation and stand out more.
- Avoid bloating: A smarter system would challenge you when your JD is too long or starts to include too many elements from an entirely different job.This happens a lot in startups and SMEs where money is tight and everyone is looking for a unicorn. But the more cross-functional a JD, the more varied the applicant pool and the number of applications goes all the way up. By being prompted to notice the similarities with other professions, a hiring manager might review a job title and related expectations which would open the door to a completely different set of people.
- Improve access: A smarter system would tell you when you’re missing key elements that make your role attractive to the widest possible set of qualified candidates. Too many JDs we’ve seen fail to include salary information, holiday days or parental leave policies and whether visa sponsorship is available.
Whether this service works like a chatbot, or an advanced editing tool like (RIP) Poetica isn’t really the problem. The problem is helping someone make changes quickly because the opportunity cost of bad JDs (the wrong people apply) is largely invisible. If this is something you’d like to talk to us about, get in touch!