# Platform Path

> Plan a developer-platform career from the candidate side - API Product Manager, Platform Engineer/Architect, Partner
> Engineer, Integration Engineer. Answer a short interview, paste the target posting and list your track record; the
> browser checks who the role serves (outside developers, or an internal developer platform, which is a different
> career), resolves the track and company archetype, audits the record, ranks the steps, plans the loop and checks an
> offer. Metered runs write the career plan, and the loop and offer prep. Built on the SkillSafe skill
> @samber/developer-platform-career, from samber/developer-platform-skills (MIT), by Samuel Berthe.

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

## What is free
- The posting scan: outside-developer language against internal-platform language (golden paths, Kubernetes, Backstage, internal teams) - and a stop when the role is an internal developer platform.
- The track and archetype, from your answers or read from the posting, with what a hire there is measured on.
- The record audit: each line read as an RFC or design doc, an API shipped, open-source history, partner integrations, product work, leadership, a certification (informational only) or talks and posts - against what the track is screened on, with the gaps named.
- The steps ranked from where you stand (the internal-API route labelled a hypothesis), re-ranked by deadline, mode and hours; the loop for the track around the API-design-versus-system-design split, each round with a drill; and the offer checked for a general-ladder benchmark with a dated source. Plus a self-check, the loop (.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` (plan or prep), `candidate`, `evidence`, `carry` (prep only: the plan decisions) and `facts`.
- `plan` replies with `summary`, `population`, `target` (track, archetype, why), `steps` (step, action, done_when, hypothesis), `portfolio` (kind, artefact, proves) and `caveats`.
- `prep` replies with `summary`, `rounds` (round, judges, drill), `practice`, `offer` (anchor, source, verdict) and `caveats`.
The page holds every reply to its own facts: both populations named, the page's track, archetype and steps, the internal route a hypothesis, an artefact per gap, no certification as a gate, no universal ladder; the page's rounds with drills, no coding for a PM, three practice prompts, the offer on the general ladder with a dated source, and no figure the input does not give.

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