How Workwise turns a job feed into useful pages

Current job inventory is supplied through a structured external feed. Workwise uses the supplied title, employer, locations, posting date, description, category, job type, and destination data when those fields are present and usable.

Full descriptions are sanitized for safe display. Remote and employment-type labels are derived only from explicit wording in the supplied record; ambiguous records remain unlabeled. Workwise does not fill gaps with invented pay, benefits, qualifications, schedules, or closing dates.

Workwise reports active job families, not raw feed rows and not application clicks. A family is one supplied opening reference after its location variants have been consolidated into one canonical job page.

Collection and research counts use only job families that remain in the accepted active inventory and meet the public-page quality rules. A family can contribute to more than one location or industry when the supplied record explicitly represents more than one.

“Remote noted” means the supplied title or description contains an explicit remote-work signal. It does not mean Workwise has verified that the role can be performed from every location or jurisdiction.

Ambiguous listings remain unclassified. Candidates should confirm workplace expectations, residency limits, and any required office attendance on the original listing before applying.

Feed records that share the same job-family reference are grouped into one canonical job page. When that family has several locations, Workwise keeps the locations together while preserving a separate application destination for each supplied variant.

Workwise does not merge unrelated records merely because their titles or descriptions look similar. Separate records can therefore remain visible when the feed does not identify them as the same job family. That conservative rule avoids combining openings from different employers or application paths.

Production checks for a new feed snapshot on a recurring schedule. An empty snapshot, an unexpectedly large inventory collapse, or a generation time that moves backward is rejected instead of replacing the last accepted inventory. When a refresh cannot be accepted, the site may temporarily show the most recent accepted snapshot and label it as such.

A displayed posting date comes from the feed; it is not reset when a page is rendered. In durable storage, a job's change time advances when its stored content or lifecycle changes. Sitemaps use that content-change time when available, rather than pretending every page changed on every crawl.

When a job disappears from an accepted snapshot, it is marked expired as part of the same update that installs the new active inventory. It then leaves active search, directories, and job sitemaps, and its Workwise job page is no longer available.

Workwise hiring snapshots describe the inventory represented on this site during a stated observation period. They are not estimates of the entire U.S. labor market, total employer hiring, hires made, or unique vacancies outside the supplied feed.

Published reports use frozen aggregate artifacts and disclose their inventory timestamp, revision, methodology version, and limitations. Workwise does not publish market-growth claims until comparable aggregate snapshots exist for both periods. Browse the available reports in the Workwise research hub.

Current search is deterministic. It compares the query with job titles, employers, supplied categories, and—when needed—description text. Location searches recognize supplied states and use approximate straight-line distance for locally resolved U.S. cities and ZIP codes. City coordinates are averages of the city's postal-code coordinates. The default radius is 25 miles, with 5, 10, 50, and 100 mile choices. The named city remains included; the radius adds nearby localities. A bare city name shared by several states stays an exact-name search until a state is selected. “New York” means the city; use “NY” or “New York State” for the statewide search. Text relevance leads the default order, followed by location closeness when relevant, supplied posting date, and stable tie-breakers. Visitors can also sort by newest or title.

Results are not personalized from a résumé, candidate profile, or account because the current service has none. A result's position is not an endorsement of the employer or a prediction that the role is a good fit.

City and ZIP location data: GeoNames, licensed under CC BY 4.0. City and ZIP matching are approximate and happen against this bundled index; Workwise does not send a visitor's location query to GeoNames. Confirm the job location on the destination listing before applying.