“What was the moment this product clicked?” —
An in-house recruiter at a company of 100–1,000 people managing 5–15 open roles at any given time. Greenhouse is their operating system for hiring. They know it well. They also know all the ways their company uses it wrong — job stages that don't reflect reality, interviewers who don't submit scorecards, hiring managers who give verbal feedback in Slack instead of structured feedback in the system. They are the connective tissue of a hiring process held together by their own follow-up.
What are they trying to do? —
What do they produce? —
It's Wednesday. A strong candidate who interviewed Monday is expecting feedback. Three interviewers have submitted scorecards; one hasn't — and it's the hiring manager's scorecard that's missing. The candidate has a competing offer. The recruiter has sent two Slack reminders. The hiring manager is traveling. They need a decision to give the candidate today. They are drafting the third Slack message and deciding whether it should be more direct.
Manages 5–15 open requisitions across multiple departments. Uses Greenhouse daily — pipeline review, candidate communication, interview scheduling, scorecard review. Works closely with hiring managers who have varying levels of Greenhouse proficiency. Schedules interviews via Greenhouse's scheduling tools or a third-party integration. Sends offer letters through Greenhouse. Reports weekly pipeline metrics to the head of talent. Has customized interview plans for each role. Has not customized job stage names because that requires an admin.
Pairs with `hiring-manager` interviewer persona for the full candidate evaluation workflow. Contrast with `agency-recruiter` for the in-house vs. external recruiting workflow and incentive differences. Use with `first-time-job-seeker` UX persona for candidate experience design.