Appearance

A vague JD is usually trying to hide a vague operating system.

Paste the JD and get a hireability diagnostic, a founder memo, and the role signature packet you can actually hire against.

— paste the JD text below for instant analysis —

What this tool is actually checking

This tool checks your JD against the live GFE Skill System manifest generated from canonical levels, tasks, processes, KPIs, and teardown failure modes.

It is not a résumé keyword scanner. It tries to answer five questions instead:

  • What role are you actually trying to hire?
  • Which failure modes will make interviews drift?
  • What should be rewritten before you source candidates?
  • What proof should a real operator be able to show?
  • Can this brief be turned into a clean marketplace-ready role signature?

The output is meant for founders, hiring managers, and operators who need to know whether the JD is hireable, not just whether it contains the right buzzwords.

Analysing your JD against the live Skill System manifest...

Oops! Something went wrong. Please try again.

Here is the hiring read

Hireability Read

Founder Memo

What is broken now

    What to rewrite now

      Proof the candidate should show

        Role Signature

        Marketplace Packet

        This is the demand-side packet we would use to rewrite, score, and eventually source the role against the marketplace.

        Must-Have Tasks

          Required Processes

            ValuationOps Alignment

            Interview Pack

            DimensionWeightExpected LevelEvidence to Verify

            Interview Exercises

              Red Flags To Probe

                Underlying skill crosswalk

                Raw task matches are shown for auditability, not as the main hiring output.

                Task IDTaskDomainLevelCrosswalks

                Still not sure what this role should own?

                The fix is not prettier copy. It is a Growth Team Audit of people, process, and tools so you can hire into a system that can actually hold.

                Book Growth Team Audit →See JD teardown library →

                Hiring clarity

                Would this hire fix the problem, or become the new glue person?

                Use this when the role still feels like a blended wish list. The output reframes the brief into a hireability read, a founder memo, and a cleaner operator signature.

                Live manifestsynced to the Skill System
                Founder memoready to send to the poster
                • Most hiring mistakes start with role ambiguity, not candidate shortage.
                • Use the analyser before the interview loop turns a fuzzy role into a fuzzy hire.
                Leadership and team design visual used for hiring clarity

                A better JD is not prettier copy. It is a clearer signal about what the role actually owns.

                Turn this into a sharper hiring brief.

                ChatGPTClaudeGeminiPerplexity