Hiring manager review portal for your open Ashby roles

Build an app my hiring managers can open instead of logging into Ashby. Most of them do not have an ATS login, and the ones who do are not going to dig through filter menus to get a status update on their own roles. Everything in this app is scoped to the person who is signed in.

Identity and access first, because this is the reason the app exists. On load, resolve the signed-in person's email address to an Ashby user with List Users. Then call List Jobs, which returns each job's status and hiring team, and keep only the open jobs where that user appears on the hiring team. Use List Application Hiring Team Roles to understand the role vocabulary so the app can tell a hiring manager apart from the assigned recruiter on a given application. This scoping must be enforced inside the server handlers, not by filtering in the browser, so a manager can never reach another team's requisitions. If the signed-in email does not match an Ashby user, show a clear empty state explaining that their address is not on any hiring team rather than failing silently.

The home view is a card per open requisition. Each card shows the age of the requisition in days since it opened, the count of active candidates broken down by stage, and a prominent "waiting on you" badge with the number of candidates whose current stage needs this manager's action, for example candidates sitting in a review or feedback stage they own. Order the cards so the roles with the most waiting candidates, and the oldest requisitions, come first. Clicking a card filters the queue to that role.

The queue view pulls every active application across those jobs with List Applications. One row per candidate, showing candidate name, role, current stage, how many days they have been waiting in that stage, and the assigned recruiter. Default the sort to days waiting, longest first, so the oldest stalled decisions surface at the top. Let the manager filter by role and by stage, but always keep days waiting as the default sort when the view loads.

Opening a candidate shows everything needed to make the call on one screen. Pull their interview feedback with List Application Feedback, including who submitted it and their recommendation. Pull the notes already on file with List Candidate Notes, newest first. Pull any upcoming interviews with List Interview Schedules, showing the time and the interviewers. Show the current stage and days waiting at the top so the urgency is visible while reading.

From the candidate view the manager can advance or reject in one click. Both actions open a small confirmation that requires a short written reason, and the submit button stays disabled until something is typed. This forced reason is the quality bar that makes the app better than the ATS itself, so it must never be skippable or optional. On submit, do three things in order: move the candidate with Change Application Stage, write the reason back to Ashby with Create Candidate Note recording the decision, the reason, and who made it, then notify the assigned recruiter with Slack Bot Send a Message.

For the Slack notification, resolve the assigned recruiter's email address to a Slack user with Look Up User by Email, then send them a direct message naming the candidate, the role, the decision, and the manager's reason verbatim. If the recruiter cannot be resolved in Slack, still complete the stage change and the note, and surface a non-blocking warning in the app that the notification did not send. The Ashby record is the source of truth and must never be left half-written because a message failed.

A few details to get right. Ashby list endpoints are cursor paginated, so page through until all results are collected before computing stage counts or the waiting badge, otherwise the numbers will be quietly wrong. Recompute the affected counts and remove the candidate from the queue immediately after a decision so the manager sees progress without a manual refresh. Show relative ages in plain language such as "12 days" rather than raw timestamps. Keep the whole app fast to scan, since the person using it is between meetings and wants to clear their queue in a few minutes.