How Workwise turns a job feed into useful pages

Current job inventory is supplied through Appcast in 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.

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.

Current search is deterministic. It compares the query with job titles, employers, supplied categories, and—when needed—description text; location searches compare supplied city, state, ZIP, and location labels. Text relevance leads the default order, followed by 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.