For people teams
Keep hiring organized. Keep candidate access deliberate.
Connect roles, candidates and interviews in a hiring app where access is granted around the hiring work each person actually owns.
Give the work a relational home
Start with connected tables. A shared name in two spreadsheets is not a relationship.
- Roles
- Keep team, hiring lead and role status in a shared record.
- Candidates
- Link a candidate's application to the role and its current stage.
- Interviews
- Relate interviews to the application and assigned interviewer.
Decide who sees what, before the first screen
Groups grant access per table, row, field and action. Every surface follows those rules.
- Recruiters
- Grant the recruitment group the applications it handles.
- Interviewers
- Grant access to assigned interviews and the fields needed to prepare.
- Private notes
- Set field access explicitly for compensation and private evaluation notes.
Different jobs deserve different screens
The Data grid is the starting point. Interface ideas can be described to the assistant and built over the same authorized data.
- Hiring pipeline
- A Data view grouped by application stage.
- Interview preparation
- A page with the authorized candidate details for one interview.
- Role overview
- An interface summarizing the recruitment work for a role.
Try this as your app brief
“Create a hiring app with Roles, Candidates and Interviews. Interviewers see assigned interviews. Compensation is available only to recruiters. Do not expose private evaluation notes to unrelated groups.”
This is an app design example, not a ready-made template. gtable is a work in progress and not open yet. Explore the product or other use cases.