The recruiting QR story has two sides — most posts only cover one
Open most articles on this topic and you get the recruiter playbook: career fair attribution, ATS integration, employer brand. Useful, but half the picture. The other half is the candidate side — the engineer printing a QR on the resume that links to a GitHub repo, the designer whose business card carries a portfolio QR, the conference attendee whose badge holds a vCard QR for one-tap contact exchange.
Both sides use the same QR technology. Both are decisions someone is making this week. And both have specific best practices that depend on the destination, not the QR itself.
This guide covers both. The first half is for talent-acquisition leaders, in-house recruiters, agency recruiters, and employer-brand teams running QR for sourcing. The second half is for job-seekers, networkers, and anyone deciding whether a QR belongs on their next resume or business card. The recruiting industry page covers the deep TA-team workflow; this guide adds the candidate side and the bidirectional view.
A quick honest note: we built EZQR because we got tired of QR vendors with cancellation traps that kill printed codes after the subscription pauses. Recruiting is one of the verticals where that risk matters most — career-fair brochures circulate for months after the event, and quarterly TA budgets often go through pause-and-resume cycles. The vendor choice matters more here than it does for a one-shot restaurant menu.
Recruiter-side: the 5 QR placements that actually drive sourcing
There are dozens of places a recruiting team could put a QR. Five of them generate the bulk of attributable applications. The other twenty are decoration.
Career-fair booth signage. The single highest-volume sourcing QR for in-house TA teams. A 4-inch QR on the booth backdrop, a 2-inch version on table-top displays, both routing to a school-specific or event-specific job-board landing page. The booth-conversation pattern: recruiter says 'scan this for our engineering open roles' and the candidate has the careers page open before the conversation ends. See the events industry page for the booth-signage print discipline that applies equally to career fairs.
Campus recruiting handouts. Take-home assets from career fairs and university partnership events. The QR routes to a school-specific landing page ('careers at [company] for [school] graduates') with pre-filled application source. Per-school attribution captures applications submitted days or weeks post-event — usually 60% of the eventual application volume from a fair comes in the week after, not during.
Office signage for the employee referral funnel. Internal QRs on break room posters, all-hands deck slides, anniversary cards. Per-asset QRs route to the referral submission form pre-filled with the referrer's employee ID. The friction of email-to-form drops referral submission rates to 3-4%; the QR-on-poster pattern lifts the same channel to 10-12% in the teams that have measured it.
Job-posting print ads. Industry trade press, alumni magazines, niche industry publications. The QR routes to the job-posting URL with a per-publication UTM tag. Print recruiting ads have always been hard to attribute; the QR fixes the attribution problem. Worth running for senior roles where the audience reads print and the cost-per-hire justifies the spend.
Conference sponsorship banners. Booth backdrops and sponsored-session signage at industry conferences (RSA, AWS re:Invent, Gartner Symposium, HR Tech). Per-conference QRs surface which sponsorships actually drove hires versus which were brand impressions. The data informs the next-year sponsorship renewal conversation in a way that 'we sponsored, leads came in' never can.
Notice what's not on this list: QR codes on LinkedIn InMail signatures, QR codes on email signatures, QR codes on the company's own website. Those are not bad ideas; they're just not the placements that move the sourcing funnel. The five above do.
The ATS-deeplink pattern with source attribution
Most recruiting teams already have the data they need to measure QR-channel ROI. They just haven't wired it together.
The pattern is simple. The QR encodes a deeplink to the ATS job posting with a UTM source parameter:
https://boards.greenhouse.io/yourcompany/jobs/12345?utm_source=campus-fair-mit-spring-2026&utm_medium=qr&utm_campaign=eng-spring
The candidate scans, the URL opens in their phone browser, the ATS captures the UTM parameters into the application record, and the source-of-application field gets tagged 'campus-fair-mit-spring-2026' automatically. Subsequent stages (interview, offer, accepted) inherit the source attribution. End-of-quarter, the TA-channel ROI report can answer 'which fair drove the most hires' with hire data, not application data.
Greenhouse, Lever, Workday, Ashby, SmartRecruiters — all of them accept UTM parameters as source-of-application data. The mechanism is slightly different per platform (covered in the platform-fit table below), but the principle holds.
Dynamic QRs are the right choice here because the UTM scheme often evolves between recruiting cycles. The fall 2025 utm_campaign tag scheme might shift for spring 2026; with dynamic codes the destination URL updates without reprinting career-fair collateral. Static QRs lock the UTM scheme to print-time, which becomes a problem when the recruiting taxonomy changes mid-year.
For the broader dynamic-vs-static decision logic, see static vs dynamic QR codes. For the trackable-vendor comparison, see the best dynamic QR generator post.
The career-fair-to-application-completion funnel: real numbers
Career-fair booth ROI conversations get hand-wavy fast. Here is what the funnel actually looks like at a busy booth based on TA teams sharing data:
300 scans at a busy mid-size career fair booth over a single day. Lower at small regional events (40-80 scans), higher at large urban fairs with 2,000+ attendees (500-700 scans).
80 ATS clicks (27% scan-to-click). Not every scan results in a click — phones glitch, candidates scan to see what happens then back out, the venue WiFi struggles. The drop from scan to ATS-page-load is real.
25 application starts (8% scan-to-start, 31% click-to-start). Candidates land on the job posting, read the description, and start filling out the application form. The start rate depends heavily on form length; ATSes that ask for resume + LinkedIn + cover letter + screening questions lose half of starters at the second screen.
8 completed applications (3% scan-to-complete, 32% start-to-complete). The completed-application rate is the number the budget conversation cares about. Eight applications per booth-day is a reasonable expectation; the math from there is whatever the conversion-to-offer rate is at your company.
With those numbers, a TA team can budget against expected outcomes. A booth at a $5K fair that generates 8 applications and 2 interviews and 0.5 hires has a real cost-per-hire to compare against paid job boards. A booth at a $20K fair that generates 12 applications and 3 interviews and 1 hire is the more expensive but more proven channel. The data conversation becomes specific.
Without per-booth attribution, this analysis is impossible. With dynamic QRs and ATS-mapped UTMs, it is a 20-minute end-of-quarter report.
Employer-brand QR: 'scan to see what it's like to work here'
The candidate-side of the recruiter’s job is selling the company. Employer-brand QRs on conference booths, recruiting handouts, and office tour signage all serve the same function: shortening the distance between a candidate's curiosity and the content that builds conviction.
Employee-story video QR. A short video (60-90 seconds) of an engineer or designer talking about a specific project. Concrete, no scripted polish. Routes to a YouTube unlisted link or Vimeo embed on the careers page. Specific stories convert better than glossy brand reels; candidates can tell the difference within ten seconds.
Glassdoor-curated review QR. A QR linking to the company's Glassdoor profile filtered to a relevant tag (engineering, marketing, the specific function). Not every company is brave enough to do this; the ones that are tend to have the better candidate experience to back it up.
Day-in-the-life article QR. A blog post or LinkedIn article from an employee describing a typical workday. The content asset already exists for most companies; the QR makes it discoverable from print.
Instagram employer-brand feed. Particularly for design-forward and consumer-facing brands. QR routes to the @yourcompany Life Instagram handle. The handle name matters; many companies have an @yourcompanycareers handle that exists but is unmaintained and reflects poorly.
The employer-brand QR is a multi-URL pattern in many cases: one QR routing through a multi-URL QR destination page that offers candidates choices ('watch the engineering team video / read the design team blog / browse the open roles'). The intermediate page adds one click but raises engagement quality.
For the broader employer-brand-as-marketing crossover, see the marketing QR pillar guide and the marketing industry page.
Candidate-side: should you put a QR code on your resume?
This is the most contested question in the space. The honest answer: it depends entirely on the destination.
When a resume QR helps. The destination is content the resume cannot do justice. A strong portfolio site with recent project case studies. A GitHub profile with commits from the last 60 days and pinned repos that match the role. Published writing on a blog, Substack, or industry publication. A short video reel for designers, motion designers, video editors. A live demo of a side project. The QR earns its space on the resume when the destination shows something the recruiter could not see otherwise.
When a resume QR hurts. The destination is a LinkedIn profile that mirrors the resume. A personal site that hasn't been updated in two years. A 'portfolio' that is three placeholder boxes. A Calendly link before the recruiter has indicated interest. In each case the QR draws the recruiter's eye, the recruiter scans, the destination disappoints, and now the candidate has spent one of their few signal moments on something that subtracts confidence rather than adding it.
The honest test. Before adding a QR to a resume, scan it on a phone and watch the page load with fresh eyes. Imagine you are the recruiter, twenty seconds in, holding a stack of forty resumes. Does the destination earn the second thirty seconds? If yes, add the QR. If no, remove it and let the resume stand alone.
Format details if you do add one. Size: 0.5-0.75 inch square, top-right corner of the resume header. Format: black-on-white, error correction level Q minimum. See the error correction levels guide for the discipline. Label: 'Portfolio' or 'GitHub' or 'Project demo' adjacent. Avoid 'Scan to see more' — recruiters need the label to tell them whether to bother.
For the underlying QR generator, the URL QR code generator on EZQR is free for static codes, which is the right choice for a resume QR where the destination URL won't change.
The candidate's vCard QR: networking at conferences and meetups
The dying ritual of business card exchange at industry conferences has a clean replacement: a vCard QR. The candidate displays the QR on the back of a paper card or on a phone screen, the recruiter scans, the contact lands in the recruiter's phone with name, company, email, phone, and LinkedIn URL pre-populated.
Why this beats paper cards for candidates. Paper cards get thrown out; vCard scans land in the phone permanently. A recruiter who scanned eight vCards at a conference goes home with eight contacts in their phone; the paper cards never leave the conference bag.
Why this beats LinkedIn QR for candidates. LinkedIn's in-app QR opens the candidate's LinkedIn profile in LinkedIn — useful, but only if the recruiter wants to leave the moment to scroll a profile. A vCard QR adds the contact directly without requiring LinkedIn to be open. For the in-the-moment recruiter who plans to follow up later, the vCard wins.
The format details. Static vCard 3.0 format encoding full name, current company and title, email, phone, LinkedIn URL, and optionally portfolio URL. The static format is correct because the contact data does not change during the event and offline scanning (without venue WiFi) is reliable.
Display options. Print on the back of paper business cards (matte cardstock, 0.75-1 inch square). Save as a phone wallpaper or lock-screen image so the candidate can flash it during conversation. Add to LinkedIn cover-photo for online networking.
The vCard QR generator on EZQR handles the format encoding. For the broader business-card-QR design discipline, see the best QR code business card generators guide.
The portfolio QR pattern for designers, engineers, and writers
Specific destinations beat generic ones. A QR on a designer's resume linking to a portfolio with seven recent case studies converts the recruiter's curiosity into engagement; a QR linking to a generic 'designer who does design' personal site does not.
For designers. Portfolio QR links to a portfolio site with case-study-per-project (problem, process, outcome, role). Avoid Behance and Dribbble shotgun links unless the work shown is genuinely the best work; recruiters mostly skim those platforms looking for the same patterns. The candidate's own portfolio with curated work converts better.
For engineers. GitHub QR links to a GitHub profile with pinned repos relevant to the role applied to. Recent commits matter; a GitHub profile last touched in 2023 looks worse than no QR. Pin three to six repos that demonstrate the technologies the job description mentions.
For writers. Published-writing QR links to a single page that lists three to five published pieces with publication credits visible (Bloomberg, The Atlantic, the company blog). The 'about me' page on a personal site is less effective than the writing-samples page.
For photographers and videographers. Reel QR links to a 60-90 second cut of the strongest work, not the full portfolio. The full portfolio is a second click for the recruiter who wants more.
The destination-discipline rule. Before printing the QR on resumes, business cards, or networking handouts, scan it and time how long it takes the page to load on a cold mobile connection. Anything over four seconds loses the recruiter; the candidate has spent the QR signal on a destination that the recruiter never sees. Optimize the page weight before optimizing the QR.
ATS platform-fit table for QR attribution
Different ATSes handle source-of-application attribution differently. The table below covers the systems most TA teams use in 2026.
| ATS | UTM parameter support | Deeplink format | Candidate source field depth |
|---|---|---|---|
| Greenhouse | Full UTM source/medium/campaign/content/term | boards.greenhouse.io/company/jobs/JOBID?utm_source=... | Source, source category, plus custom fields |
| Lever | Full UTM source/medium/campaign/content | jobs.lever.co/company/JOBID?lever-source=... or UTM tags | Source, source category, application question |
| Workday | Source-of-application field via referral source query parameter | workday.com/company/jobs/JOBID?source=... | Source plus referral details and custom-field mapping |
| Ashby | Full UTM source/medium/campaign/content | jobs.ashbyhq.com/company/JOBID?utm_source=... | Source plus per-channel attribution and analytics dashboards |
| SmartRecruiters | Full UTM source/medium/campaign | jobs.smartrecruiters.com/company/JOBID?utm_source=... | Source plus campaign attribution and recruiter source notes |
| Recruitee | UTM source/medium/campaign | company.recruitee.com/o/JOBID?utm_source=... | Source plus pipeline source field |
| Workable | Source-of-application via referral parameter | apply.workable.com/company/j/JOBID?ref=... | Source plus campaign-attribution tracking |
Tips
- Greenhouse and Ashby have the deepest QR-channel reporting out of the box; Workday and Lever require a bit of custom-field mapping; SmartRecruiters and Recruitee are mid-tier.
- Whichever ATS you use, define the UTM taxonomy once at the start of the recruiting cycle and lock it. Mid-cycle taxonomy changes break per-cycle analytics comparisons.
- Test the full flow before printing collateral: generate the QR, scan it, complete the test application, verify the source field in the ATS admin view. Catching a taxonomy typo at print time costs nothing; catching it after 5,000 brochures circulate is expensive.
Static vs dynamic for recruiting
The static-vs-dynamic decision for recruiting follows the same logic as other verticals, with a few recruiting-specific notes.
Static QRs work for evergreen career-page links. The URL yourcompany.com/careers will not change for the foreseeable future. Static QRs on company business cards, office wayfinding for visitors, and permanent office signage can be static and printed once.
Dynamic QRs are required for job-specific QRs that rotate. The QR on a print job ad for 'Senior Software Engineer' will need to redirect somewhere different when the role closes or when the URL slug changes. Dynamic codes let the destination update without reprinting.
Dynamic QRs are required for campaign-specific UTM tracking. Source attribution often evolves between recruiting cycles. Dynamic codes let the UTM taxonomy update without breaking codes printed under the old scheme.
Dynamic QRs are required for per-event attribution. Career-fair-specific UTMs, campus-specific UTMs, conference-specific UTMs all require dynamic codes because the destination URL pattern includes the per-event tag.
For the broader logic, see the deep-dive in the static vs dynamic QR code guide.
The cancellation-timebomb for printed recruiting collateral
Recruiting collateral has a long tail. A career-fair brochure printed in February of a recruiting cycle circulates through the candidate's bag and onto a desk for weeks or months after the event. A campus recruiting poster on a university department bulletin board stays up until someone takes it down. A trade-press print ad runs in a magazine that gets reread on coffee tables for the rest of the issue cycle.
This is the cancellation-timebomb. Most TA budgets run on quarterly cycles; the recruiting QR vendor subscription often gets paused between hiring sprints to save the $5-$30 per month. If that vendor deactivates dynamic codes on cancellation, every brochure and poster and print ad still in circulation silently breaks.
We covered the vendor-by-vendor cancellation policy in the permanent QR code generator guide. The short version: Flowcode and QR Code Generator deactivate after cancellation; EZQR and QR Tiger keep codes redirecting indefinitely.
The practical TA-team workflow:
1. Verify the vendor's cancellation policy in writing before generating the QRs that go onto printed collateral.
2. Test the cancellation flow on a trial account. Generate a code, cancel, scan 35 days later, confirm it still redirects.
3. If the test code dies, switch vendors before printing the production batch.
4. As a cheaper alternative: keep the subscription active year-round on the lowest tier. $60 per year is meaningfully less than the reprint cost of one batch of damaged collateral.
Vendor comparison for TA teams
Recruiting teams have a few procurement nuances that consumer-grade QR vendor reviews miss. Monthly billing matters because TA budgets often roll quarterly. Bulk-generation matters because multi-event-organizer teams print dozens of per-event QRs in a single cycle. API access matters because larger TA teams want programmatic generation tied to the ATS workflow.
| Vendor | Monthly billing | Cancellation policy | Bulk QR generation | API access for ATS integration |
|---|---|---|---|---|
| EZQR | Yes, $5/mo Lite tier | Codes redirect indefinitely after cancel | CSV import on Pro tier | API on Pro ($10/mo) and Max ($20/mo) tiers |
| QR Tiger | Yes, ~$7/mo equivalent on monthly | Codes remain active per ToS | Bulk via paid plan | API on higher tiers |
| Flowcode | Annual billing pushed; monthly limited | Deactivates 30 days after cancel | Bulk on enterprise tier | API on enterprise |
| Beaconstac / Uniqode | Monthly available on some tiers | Codes remain active per current ToS | Bulk and CSV on Plus tier and above | API on Plus tier and above |
| QR Code Generator | Monthly available | Deactivates dynamic codes on cancellation per ToS | Bulk on paid tiers | API on higher tiers |
| Bitly QR | Monthly available | Retention policy varies by tier and history | Bulk on higher tiers | API on paid tiers |
Tips
- For TA teams in the 20-50 events-per-quarter range, the API-on-Pro tier is what unlocks programmatic generation tied to the recruiting calendar.
- For TA teams running 5-10 events per quarter, the Lite-tier monthly billing covers the dynamic-redirect need without overpaying for API access.
- For TA teams sponsoring large conferences with custom registration flows, verify the vendor exports per-scan data in a format the marketing-ops team can ingest into Salesforce or HubSpot.
The candidate-experience touchpoint use case
QR codes at candidate-experience touchpoints are small but high-signal. They communicate care from a company in moments where most companies do the bare minimum.
On the offer-letter envelope or PDF cover. A QR linking to a 60-second welcome video from the hiring manager and the immediate team. The cost is one afternoon of recording and editing; the signal it sends to the candidate during the offer-acceptance window is meaningful.
On the first-day onboarding paperwork. A QR linking to the team's Slack-invite landing page, the office wayfinding map, or the first-day-of-work agenda. Reduces the new-hire friction of asking 'where do I go and who do I talk to' at the front desk.
On the candidate-rejection email signature. A QR linking to a 'stay in touch' landing page with a one-field form. Rejected candidates today often become applicants two years from now; the touchpoint costs nothing and the long-tail pipeline value is real.
On the interview-feedback survey email. A QR linking to the candidate-experience survey. Email open rates drop fast post-interview; a QR on the printed interview-itinerary handout captures feedback in the in-office moment instead.
None of these are funnel-volume movers. All of them shape the candidate experience in a way that compounds the company's reputation over time. The recruiting industry page covers the broader candidate-experience workflow.
An execution checklist for a recruiting QR rollout
Both sides of the rollout in one checklist.
Recruiter-side: sourcing campaign setup.
1. Define the UTM taxonomy for the recruiting cycle. utm_source per channel (campus, career-fair, conference, referral, employer-brand). utm_campaign per event. utm_content per asset (booth-poster, handout, badge).
2. Generate per-event, per-asset dynamic QRs ahead of the recruiting cycle. Bulk-generate via CSV or API tied to the recruiting calendar.
3. Test the full flow end-to-end: scan, land on the ATS, complete a test application, verify the source field captured the right UTM. Catch typos before printing.
4. Print collateral with the QRs in place. Standard print-discipline applies: matte lamination, error correction level Q minimum, quiet zone of four module widths, label adjacent to the QR.
5. During each event, surface scan velocity to the recruiting team in real time. Per-booth scan counts inform mid-event decisions.
6. End of cycle, run the channel-ROI report: scans, ATS clicks, application starts, completed applications, hires-per-channel. The report informs next-cycle budget allocation.
7. Verify the vendor's cancellation policy. Keep the subscription active year-round on the cheapest tier if there's any risk of pause-and-resume cycles breaking residual print circulation.
Candidate-side: resume and networking decisions.
1. Decide whether a resume QR earns its space. The destination test: does the destination earn the recruiter's second thirty seconds? If yes, add it. If no, remove it.
2. If yes, generate the QR with the URL QR generator. Static is correct for a resume QR where the destination URL won't change.
3. Format the QR: 0.5-0.75 inch square, top-right header position, black-on-white, error correction level Q, descriptive label adjacent.
4. Scan the printed resume on a fresh phone to verify the destination loads cleanly and quickly.
5. For networking events, generate a vCard QR with full contact details. Save it as a phone wallpaper or print it on the back of paper business cards.
6. Test the vCard scan flow before the event. Confirm the contact lands in the phone with all the fields populated.
7. For the broader print-and-business-card discipline, see the QR business card guide.
The bottom line
Recruiting QR has two sides. Recruiters use QR for sourcing attribution; candidates use QR for differentiation. Both matter, and the practical discipline is similar enough that one playbook covers both.
For the recruiter side: five placements (career-fair booths, campus handouts, office referral signage, print job ads, conference sponsorships), dynamic codes routing through ATS deeplinks with per-channel UTM tagging, and a vendor whose cancellation policy doesn't kill residual print circulation. The recruiting industry page covers the deep TA-team workflow.
For the candidate side: the resume QR debate has a real answer, and the answer is the destination. A QR pointing at a strong portfolio, GitHub with recent commits, or published writing earns its space. A QR pointing at a stale LinkedIn profile or empty personal site subtracts from the resume. The destination is the test.
For the toolchain: EZQR handles both sides on monthly billing with codes that survive cancellation. Free for static codes (career-page QRs, vCards, resume QRs), Lite at $5/mo for dynamic recruiting QRs with per-channel attribution, Pro tier for API-based programmatic generation tied to the ATS workflow.
For the deep-dives on adjacent topics, see the events and conferences pillar, the registration pillar, and the call-to-action design guide.