Talent vs Operator experience
Two doors into Array HQ. The right one depends on who you are and what you're here to do.
The operational problem
A platform that serves both a VP of Operations and a warehouse picker can't show them the same screen. The VP needs cross-site performance, hiring throughput, and goal attainment. The picker needs to know their points, the next reward they can redeem, and where they stand on the leaderboard. Trying to combine those views creates a screen that works for neither.
How Array HQ solves it
Two distinct experiences share one identity layer:
- Operator experience — the web portal used by Owners, Admins, Operators, and Recruiters. Built for desk and floor work: rosters, jobs, goals, rewards configuration, and cross-site rollups.
- Talent experience — the mobile-first app used by Team Members. Built for someone holding a phone between shifts: points balance, redemption catalog, leaderboard, schedule visibility.
A person can move between them as their role changes — promoting a top picker to a shift lead is a role change, not a new account.
How it works
Operator portal
Web-based. Accessible at the operator URL provided in your welcome email. Read the docs sections Platform, //Recruiting, //Ops, and Administration for everything you can do here.
Talent app
Mobile-first (web works too). Branded for your organization. The Team Member sees only their own data, their organization's leaderboard, and the rewards available to them. Read the Talent and Team Members section for the talent-side experience.
Shared identity
Both surfaces share the same Array HQ identity. One person, one login, two views — chosen by role.
What you'll be able to do
- Send a new operator to the operator URL and a new picker to the Talent app, knowing each gets the right experience without configuration.
- Move someone from Team Member to Operator without rebuilding their history.
- Keep operational data and talent-facing data on the same backbone — no double entry, no reconciliation.