The ontology gap

The ontology gap is a thesis about representation: a short job title, skill label, or résumé field may omit the reasoning that made an engineer’s work valuable. A project account can supply that context. Whether a particular hiring system uses it is a separate empirical question.

What the evidence supports

Harvard Business School and Accenture’s 2021 study, Hidden Workers: Untapped Talent, examines how hiring processes and technology can exclude qualified workers. It supports concern about filtering and the choices built into recruitment processes. It does not establish a universal hardware-engineering blind spot or demonstrate that a personal doctrine site fixes screening outcomes.

There is also clear counterevidence to the claim that occupational vocabularies omit mechanical engineering. O*NET’s Mechanical Engineers occupation explicitly covers mechanical design, testing, failure investigation, and related work. That vocabulary’s existence does not show how every employer configures a screening system. It does rule out treating all such work as absent from occupational descriptions.

The narrower problem

MootMoat’s working hypothesis is that a category can describe an occupation while still failing to convey an individual’s decisions within it. A label such as “mechanical design” says little about which constraint changed a design, which alternative was rejected, or how the result was checked.

That is an argument for better evidence and clearer authoring. It is not a claim that every recruiter or automated system applies the same categories, ignores hardware expertise, or performs identity resolution before considering an application.

What “Round Zero” means here

“Round Zero” is a shorthand for the risk of being filtered or overlooked before a substantive conversation. It is a risk model, not a documented universal stage in hiring. It should not be used to infer why a particular person received no response.

To test that explanation in a specific setting, we would need evidence about the actual process, criteria, inputs, and outcomes. This project provides no such employer-specific visibility or active screening telemetry.

A practical response

Document one consequential decision using the workbook. Connect the claim to its source and project context. Use ordinary language for the domain, then explain the constraint and reasoning that a short label leaves out.

An analogy to another domain may help a reader, but it is not a substitute for the original engineering account. Explain where the comparison holds and where it fails.

What remains unproven

This site has not established that these records improve automated ranking, discovery, interviews, or hiring. A useful evaluation would define the audience and outcome, compare like cases, and report contrary results as well as favorable ones. Until then, the defensible claim is narrower: the method gives a reader more explicit material to assess.