Employer-brand audio and video for job pages: cut time-to-hire and boost outreach responses
Titus Juenemann •
November 8, 2024
TL;DR
The Puck + Greenhouse integration brings employer-brand audio and video directly into job pages, outreach, and interview workflows so teams can tell their story where candidates decide. Suitable for enterprises, mid-market, and startups, the integration typically reduces time-to-hire by about 20% and increases outreach response rates by roughly 10%. Implementation usually takes 2–6 weeks including media production, and success relies on short, role-focused clips, consistent placement, and candidate-level analytics. To maximize ROI, follow the implementation checklist, track key metrics, and combine Puck storytelling with tools that accelerate resume review—such as ZYTHR—to create a faster, higher-quality hiring funnel.
The Puck integration for Greenhouse connects Puck’s people-first recruitment marketing content directly into your hiring workflow so candidate-facing audio and video clips appear where they matter most — job pages, outreach, interview prep, and career sites. This article explains how the integration works, who benefits (and why), measurable outcomes to expect, implementation steps, and practical best practices for maximizing candidate quality and time-to-hire improvements.
At a high level, Puck produces short audio and video clips that tell your team’s story; the integration pushes those clips into Greenhouse job pages and associated candidate flows so recruiting teams consistently surface employer-brand content to candidates and prospects. The result is improved outreach response rates, higher-caliber applicants, and measurable reductions in time to hire when employer messaging is embedded into the ATS workflow.
Who should consider the Puck + Greenhouse integration
- Enterprise and mid-market TA teams Teams hiring across many roles who need consistent employer messaging at scale — Puck helps standardize the candidate experience across hundreds of requisitions.
- Hiring managers focused on hard-to-fill roles Roles with low inbound interest benefit from Puck’s first-person audio that increases curiosity and response rates in outreach.
- Employer brand and recruitment marketing owners Teams responsible for career site conversion and content distribution will use Puck to centralize media assets and measure engagement at the candidate level.
- Small startups scaling hiring volume Companies under 1,000 employees can use Puck to build an authentic brand quickly without creating an in-house media team.
AI resume screener for Greenhouse
ZYTHR scores every applicant automatically and surfaces the strongest candidates based on your criteria.
- Automatically screens every inbound applicant.
- See clear scores and reasons for each candidate.
- Supports recruiter judgment instead of replacing it.
- Creates a shortlist so teams spend time where it matters.
| Name | Score | Stage |
|---|---|---|
| Oliver Elderberry |
9
|
Recruiter Screen |
| Isabella Honeydew |
8
|
Recruiter Screen |
| Cher Cherry |
7
|
Recruiter Screen |
| Sophia Date |
4
|
Not a fit |
| Emma Banana |
3
|
Not a fit |
| Liam Plum |
2
|
Not a fit |
Core Puck features delivered through the Greenhouse integration
| Feature | How it works in Greenhouse |
|---|---|
| Job page media embeds | Puck audio/video clips are embedded on Greenhouse job pages so candidates see team stories inline with role descriptions. |
| Content library | Recruiters access a searchable library of clips to attach to offer workflows, interview guides, and outbound messages. |
| Candidate-level engagement | Analytics show which candidates interacted with which clips, useful for outreach follow-ups and interview prep personalization. |
| Multi-language support | Assets can be delivered in supported languages (English, Spanish, French, Hebrew, Hindi) and published per-job or per-region. |
How the integration works technically: Puck exposes media and metadata through its content distribution APIs and plugs that content into Greenhouse job and candidate objects. When enabled, recruiters see Puck media selectors inside the Greenhouse UI and can choose clips to display on job posts or attach to candidate profiles. The integration also routes interaction events back to Puck analytics so you can track candidate-level engagement.
Implementation checklist
- Account setup Confirm Puck and Greenhouse admin accounts and permissions; agree on who will manage media publishing.
- Content strategy Map which roles and stages will use audio/video assets — job pages, outreach templates, interview prep, and campus events.
- Media production Schedule recordings with Puck’s Employer Brand Studio and approve final clips in the content library before distribution.
- Integration enablement Install the Puck app in Greenhouse, configure API keys, and test embedding media on a sample job posting.
- Analytics setup Enable candidate-level tracking and forward event data to your analytics owner for regular reporting.
Typical timeline and resource commitment: For most organizations the implementation takes 2–6 weeks. Production of an initial content library (10–30 short clips) usually requires 1–3 days of interviews and 1–2 weeks for editing and approvals. Integration configuration and testing in Greenhouse is generally a 1–5 day technical task with minor ongoing admin overhead for publishing new media.
Metrics to measure and realistic impact
| Metric | Typical change after deployment |
|---|---|
| Time-to-hire | ~20% faster when candidate-facing storytelling is embedded in job pages and outreach |
| Outreach response rate | ~10% increase due to personalized, humanized messaging |
| Candidate quality (hiring manager score) | Improvement varies; many customers report higher interview-to-offer ratios |
| Engagement tracking | Candidate-level insights available for targeted follow-ups and A/B testing |
Common questions about the integration
Q: Does Puck require a Greenhouse partner implementation fee?
A: No partner implementation fee is listed; implementation work is typically handled via configuration and content setup with Puck and Greenhouse admins.
Q: Which languages are supported for media assets?
A: Puck supports English, Spanish, French, Hebrew, and Hindi for produced clips; confirm availability for your region during onboarding.
Q: Can I measure which candidates listened to specific clips?
A: Yes — the integration provides candidate-level engagement data so recruiters can tailor follow-ups based on media interactions.
Best practices for using Puck content inside Greenhouse: keep clips short (30–90 seconds), align each clip to a single message (team culture, role expectations, growth stories), and include a clear call-to-action at the end of outreach clips. Use interview prep clips for hiring managers to standardize the candidate experience and reduce variability across interviewers.
Where to place Puck content for maximum effect
- Job description pages Embed a 45–60 second team story on the job posting to increase conversion and clarify role context.
- LinkedIn and social outreach Use short clips to upgrade outbound messages and posts—media increases response rates and social proof.
- Interview guides Attach clips to candidate interview kits so interviewers and candidates share the same narrative.
- Recruiter outreach templates Add links to clips in email sequences to boost reply rates and deliver authenticity at scale.
Privacy, data handling, and compliance considerations: Puck collects engagement events and may store anonymized candidate interaction data to support analytics. Organizations should review Puck’s privacy policy and map dataflows to their internal compliance standards. For Greenhouse-specific configuration, consult Greenhouse support pages to ensure data sharing settings and candidate consent flows align with regional regulations.
Operational details: regions, company sizes, and support
| Aspect | Details |
|---|---|
| Regions supported | North America, South America, APAC (Asia Pacific) — confirm region-specific distribution channels with Puck. |
| Company sizes | Designed to scale from startups (1-100) to large enterprises (1,001-10,000). |
| Languages | English, Spanish, French, Hebrew, Hindi (availability per engagement). |
| Partner implementation fee | No partner implementation fee listed in standard materials; confirm during procurement. |
Troubleshooting and support: If media does not appear on job pages verify API keys, content visibility flags in Puck, and Greenhouse job posting settings. Use the Puck privacy policy and Greenhouse support page to confirm consent and dataflow expectations. For developer assistance, contact Puck’s developer support to inspect logs and event delivery.
Quick ROI example and decision criteria
Q: If our average time-to-hire is 40 days, what is the impact of a 20% improvement?
A: A 20% reduction reduces time-to-hire to 32 days. This accelerates start dates, reduces vacancy costs, and can compound hiring velocity across teams.
Q: How to decide whether to invest in Puck integration?
A: Prioritize if you have recurring roles with low response rates, a need to standardize employer messaging, or if improving time-to-hire by even a few days yields measurable business value.
Speed up hiring and improve resume screening with ZYTHR
Use ZYTHR’s AI resume screening to automatically prioritize candidates who match your roles so recruiters spend less time sifting resumes and more time engaging candidates exposed to Puck’s employer-brand content. Start a free trial to see faster, more accurate shortlist creation that complements Puck + Greenhouse integrations.