What people ops teams use Hops for
- Job description drafting: produce first drafts from the role brief and your existing JD templates
- Interview prep: summarize candidate background and prep questions from connected sourcing tools
- Onboarding plans: generate role-specific onboarding checklists from your playbooks
- Policy Q&A: answer employee questions from your policy docs with specific citations
- Offer letter prep: draft from templates with role-specific details filled in
- Cycle summaries: summarize performance or engagement survey results across teams
Example workflows
New hire onboardingCreate a Space for each new hire. Pin the onboarding plan, their role context, and key docs. The agent answers questions, surfaces relevant resources, and helps your team keep the onboarding consistent without starting from zero each time.Job description draft
Paste the hiring manager’s role brief. Ask the agent to draft a JD from your template. It uses the brief for specifics and your existing JDs (connected via Drive) for tone and structure. Review and refine.Policy question
An employee asks an HR question via Slack. Your HR agent searches your policy docs and returns the answer with the specific section cited. HR reviews before sharing.
Handling sensitive information
People ops involves highly sensitive data: compensation, performance, personal information. Be deliberate about what you connect and who has access.- Use invite-only Spaces for all people ops work
- Scope tool access carefully. Your HR tool data should not be visible to all agents
- Follow your company’s data handling policies when connecting HR systems
Hops accesses HR data with the same permissions as the account you authorize. It does not elevate access beyond what you grant.