Build a recruiting requisition desk workflow backed by an applicant tracking system (such as Greenhouse or similar). The workflow is read-only: it reads recruiting data and never writes back or sends notifications. It has two audiences, triggered by authenticated HTTP webpage and API routes: Recruiter hub — a webpage restricted to members of the Recruiting space. It gives recruiters an overview of requisitions, pipeline stages, candidate movement across stages, and action alerts. Back it with a few API endpoints (also space-restricted) that pull the underlying data: the list of recruiters, the list of open requisitions, and the detail for a single requisition. The webpage renders immediately and fetches from these API routes rather than being fed data through an upstream step. Hiring manager pipeline — a separate webpage available to any authenticated tenant member (broader than the space), reached via a shared link that names a specific requisition (e.g. a job ID passed as a query parameter). It exposes only that one requisition's read-only pipeline overview, backed by its own tenant-scoped data endpoint using the same live ATS data. Pull recruiters, jobs, applications, interview stages, candidates, sources, and scorecards from the ATS. Use a connector for authentication rather than hardcoding credentials. Design the two webpages as polished, production-grade UIs. Tools used: Greenhouse