# Platform Hire

> Check an employer's hire for an external developer-platform role - API Product Manager, Platform Engineer/Architect,
> Partner Engineer, Integration Engineer. Answer a short interview and paste the draft posting, the outcomes, the loop
> and the sourcing channels; the browser checks who the role serves, flags build work stacked with outreach work and no
> headcount plan, plans the interview loop around the API-design split and the interviewer-hour budget, and checks the
> outcomes, sourcing and compensation. Metered runs write the role scorecard, and the loop, sourcing and compensation
> stance. Built on the SkillSafe skill @samber/developer-platform-hiring, from samber/developer-platform-skills (MIT),
> by Samuel Berthe.

https://platform-hire.skillsafe.ai/

## What is free
- The posting scan: outside-consumer language against internal-platform language; build, partner and outreach work; a headcount plan - and the scope-collapse verdict when build and outreach share one seat with no plan.
- The hire ranked (a dedicated search, a split across hires, or a fold into general backend or PM hiring), the competencies weighted for the track, and the loop planned per track - thinned for a one-off hire, stripped to the core under a low effort ceiling, fitted to the interviewer-hour budget.
- The gates: who the role serves, three to eight quantified outcomes, no build-plus-outreach stack, a loop that matches the track, apidays or general senior channels rather than PlatformCon, and pay anchored to the general ladder with a named, dated source. Plus a posting self-audit, a loop schedule CSV, the checks (.csv) and everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (scorecard or loop), `role`, `posting`, `carry` (loop only: the scorecard decisions) and `facts`.
- `scorecard` replies with `summary`, `calibration`, `mission`, `outcomes`, `competencies`, `shape`, `posting_fixes` and `caveats`.
- `loop` replies with `summary`, `stages`, `sourcing`, `avoid`, `comp` and `caveats`.
The page holds every reply to its own facts: an outside-developer calibration, quantified outcomes, the page's weights and the ranked hire, a split for a collapsed posting; the page's loop in order within the budget, apidays where it applies, PlatformCon avoided, and a dated ladder anchor.

The page also flags posting wording that screens on who a person is (age-coded, national-origin-coded or gendered terms) rather than the job. It is a structural check, not legal or employment advice.

## Links
- API tutorial: https://platform-hire.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/developer-platform-hiring