Headcount approval flows
Every request to open or change a role now runs through a defined approval path in TeamOhana, with far more people able to see what is already in the system. The Slack scavenger hunt is gone.
“It used to take two weeks on average to hunt down an approval on headcount. Now, because we have approval flows and a lot more folks have visibility into what is in the system, it takes about 2 to 3 days.” — Amanda Tarkenton, Recruiting Operations, Vercel
Deliberate backfill decisions
When a role opens, TeamOhana surfaces the choice in real time: backfill it one-to-one, repurpose it, or do not backfill at all. That decision used to happen off to the side, if it was made at all.
“Before, those decisions happened informally and inconsistently, and sometimes the decision would never make it to me. Now it's structured and visible, which means we're making more deliberate choices about where we actually spend headcount budget.” — Amanda Tarkenton, Recruiting Operations, Vercel
Structured planning with required fields
Because levels, locations, and comp ranges are required fields in TeamOhana scenarios, leaders can no longer bring half-formed asks to the table. Planning gets rigorous by default.
“We used to not consistently gather levels, locations, and comp ranges up front. Because those are required fields in TeamOhana scenarios, it's forced a more rigorous planning motion. Leaders now come to the table with that context baked in.” — Amanda Tarkenton, Recruiting Operations, Vercel
Real-time visibility for hiring managers and recruiters
Hiring managers see their own headcount live and can submit a backfill or a change request in under two minutes. Recruiters are notified the moment a role is assigned to them, so no one sits in limbo waiting to hear what was approved.
Two-way sync with the ATS
Custom fields built in TeamOhana flow straight into Greenhouse and feed Vercel's reporting. The clean handoff between the two systems tightened data hygiene across the board.