Jobs
The roles you're hiring for and the locations they cover.
The operational problem
A job description written once and reused across every site treats a driver job in one corridor like a driver job in another, and a picker role in a cold-storage facility like a picker in dry goods. The reality on the floor is more specific. Screening that ignores this misses the applicants who match the actual role at the actual site.
How Array HQ solves it
A job in Array HQ combines a posting with the screening questions and target responses that will run for applicants applying to that specific job at that specific location. Recruiters approve the question set before screening goes live.
How it works
Defining a job
Each job captures:
- Role. Driver, picker, packer, crew member, shift lead — whatever your operation uses.
- Location. The single site the job runs for.
- Screening questions. SMS questions with target responses set by the recruiter. Questions can be agent-generated from the job description, edited, reordered, deleted, or written from scratch.
- Hiring need. How many people you're looking to hire.
Editing a job
Owners, Admins, and Recruiters can edit a job from the //Recruiting hub. Screening questions can be edited after applicants have started responding — existing responses are retained, and new questions apply moving forward. Ad copy can also be edited after the posting goes live; edits apply to subsequent distribution.
What you'll be able to do
- Stand up a job for a new site with role-specific screening questions.
- Update screening questions when the role or location context changes.
- Pause or close a job without losing the historical pipeline behind it.
Key terms
| Term | Meaning |
|---|---|
| Job | A role you're hiring for at a single location. |
| Screening question | An SMS question sent to applicants during screening, with a target response set by the recruiter. |