Four stages, and what each one refuses to do

We pull the title, the responsibilities and every stated requirement out of the document. Nothing is matched or rewritten yet.

• Won't guess at requirements the posting doesn't state
• Won't infer seniority from tone — only from what's written

Every requirement is checked against your own words. A requirement counts as evidenced only when one of your bullets actually says it — otherwise it lands in partial or not evidenced.

• Won't treat a skills-list mention as evidence of doing the work
• Won't call the result an ATS score; it is requirement coverage, and no employer's system produced it

Your bullets are reordered, reworded and re-weighted against the posting, then rendered into every template your plan allows — eleven by default. Every generated line keeps a key back to the bullet you wrote.

• Won't invent a job, a number, a date or a tool
• Won't inflate a claim past the proficiency you set on your profile

We draw the questions this posting invites, grouped by family, and match what you can't evidence to a vetted course catalog.

• Won't pad an empty question family to make a tab look full
• Won't link a course we haven't checked — where we have nothing, we say so

The roadmap compiles the questions, bullets and courses this analysis already produced into one ordered checklist — nothing new is generated, so it's free and instant.

Job search, on your own plan, queries a small set of documented job-board APIs and ranks what comes back against your profile. We never scrape a site that doesn't offer an API.

• Won't tick a step for you — the roadmap tracks what you've done, it doesn't decide for you
• Won't invent a listing link — every result and every link comes from the job board's own API response

Whether you'll get an interview. Coverage measures how much of a posting your profile can evidence today — it isn't a prediction, and it says nothing about how a particular employer screens.