Résumé tailoring for engineers, where the stack list is a liability

The four failures specific to engineering résumés

• Stack claimsThe common failure is not a new line in the skills list — it is a technology name inserted into an existing true sentence, which is harder to spot and just as indefensible in a technical interview.
• Scope inflation'Postgres' becoming 'distributed Postgres'. 'A service' becoming 'microservices'. 'Evaluated' becoming 'fine-tuned'. A prototype becoming a production system.
• Invented metricsLatency, throughput, cost and model accuracy are the figures AI tools invent most freely, because they sound like the kind of thing an engineering résumé contains.
• Ownership driftA team project becoming yours. 'One of three engineers' vanishing. An internal tool becoming a platform.

Test with two postings, not one

A backend posting is dense and specific — a language, a framework, a datastore, a queue, a cloud. The failure there is the skills list quietly acquiring an item.

An ML or AI posting is vaguer and mixed: some research vocabulary, some infrastructure, some product. The failure there is scope inflation, because the posting gives the model more room to be vague.

A tool that handles the backend posting cleanly can still fail the ML one. Run both.

What SchoolWhool blocks mechanically

• Every edit must quote your résuméA suggested edit has to quote an exact, unique passage of the file you uploaded. If the quoted original is not found verbatim, or is found twice, the edit is discarded before you ever see it — which removes the whole class of edits that invent a new bullet point.
• Invented figures are strippedA replacement may not introduce a number that was not already in the passage it replaces. Percentages, headcounts, latency and cost figures that appeared from nowhere are dropped mechanically, not by asking the model nicely.
• No overlapping rewritesIf two suggestions touch the same sentence, applying both would produce a sentence neither proposed. The overlap is dropped, so an accepted edit means what it said it meant.
• Your original is never rewrittenThe file you uploaded stays as you uploaded it. You approve edits one at a time, and changing your profile details invalidates an earlier approval so a stale review cannot follow new facts.

And what it does not

A technology name added inside a sentence you did write survives these checks: the edit quotes a real passage and adds no digits. 'Built the ingestion service' becoming 'Built the ingestion service in Kafka' is anchored and number-free.

That is why edits are presented one at a time against the exact sentence they replace, rather than applied. On an engineering résumé, read the stack words specifically.

Export and check the result too. Engineering résumés carry monospaced technology lists, nested bullets and a projects section that does not fit a template's model of a résumé.

Roles to tailor against

SchoolWhool's catalogue is crawled from 285 companies' own career boards through the public APIs of Greenhouse, Ashby, Lever, SmartRecruiters, Workable and Recruitee. There is no HTML scraping and no aggregator anywhere in the chain.

That sourcing skews toward technology employers, which for this audience is the point: the backend, ML, data and infrastructure roles in the catalogue are those companies' current postings, with direct links to their own application pages. Browsing is free and needs no account.