Find Software engineers page describes results as Person and Place, not just list rows

Find Software engineers page describes results as Person and Place, not just list rows

Two of ProfileScribe's public discovery pages were updated in the latest check, and the interesting part is how differently they describe their contents. The Find Software engineers page is typed all the way down to individual entities: alongside the search-results and list structure, it declares Person and Place. Find Accountants is typed as a search results page with an item list and a search action, which is the shared scaffolding every profession page carries.

That distinction matters more than it sounds. When a page declares Person and Place, filters like location and current work behave like structured queries against real entities, not keyword guesses against page text. It also means the people listed are legible to outside systems as identifiable professionals attached to a place, which is the difference between appearing in a directory and being addressable in a search.

Working on this, my rule of thumb has become: describe what the page actually contains, at the smallest useful unit. Both pages promise search by credentials, specialties, and service area. The engineers page currently backs that promise with entity-level description, and that is the pattern I would want every profession page to converge on before we add more filters on top.