QR Codes on Resumes and Portfolios: What to Link, Where to Put It
A recruiter at a career fair holds your printed resume for about 90 seconds. A QR code in the corner can put your actual work on their phone before that time runs out, or it can dump them on a homepage where they tap around and give up. Which one happens is decided almost entirely by what you link, so start there, not with the design.
What deserves the scan
The code gets one destination, and it competes with a recruiter's patience. Link the thing that answers "can this person do the job" fastest:
| Destination | Verdict | Why |
|---|---|---|
| Curated portfolio (3 to 5 pieces) | Link it | Proof of work, immediately |
| Single case-study page | Link it | Strongest when tailored to one role |
| 60-second intro video | Link it | Works for sales, design, and client-facing roles |
| LinkedIn profile | Fine | Familiar ground for recruiters; keep it current |
| GitHub profile | Depends | Only with pinned, documented repos |
| PDF of the same resume | Skip | They are already holding it |
| Generic personal homepage | Skip | Forces navigation on a small screen |
The two "skip" rows are the most common real-world choices, which is why most resume QR codes get scanned once and never again. If LinkedIn is your best destination, a LinkedIn QR code generator turns your profile URL into a code in a minute; just make sure the profile shows the work, not only the job history.
Resist adding a second code, too. Two codes side by side split attention and make the page look like a flyer; pick one destination and let the printed URL beneath the code carry any backup.
The ATS reality
Applicant tracking systems parse resumes as text. A QR code is an image, and parsers ignore images entirely, so the code neither helps nor hurts your ranking. Keep it out of the middle of your text columns (unusual layouts are what actually trips parsers up) and it stays invisible to the software.
That means the code exists for exactly two humans: the interviewer holding your paper resume across a table, and the recruiter at a fair or networking event. Both are moments where "here, scan this" turns a conversation about your work into a look at your work. For the emailed PDF version, make the same URL a normal clickable link as well; nobody scans a QR code that is already on their screen.
Placement and size on the page
Put the code in the header block, next to your contact details, where a reader's eye already goes for links and email addresses. Avoid the footer: it is the first thing cropped by tight printer margins and the last thing anyone reads.
Size: 1.8 to 2 cm (about 0.75 inches) is the working minimum on an A4 or letter page. That is large enough for a phone to lock on from 25 to 30 cm away, roughly the distance between a seated interviewer and a resume lying on the table, and small enough to stay discreet. Leave a quiet zone of white space around it, keep the code dark on the white page, and print a short readable URL directly beneath it as a fallback for anyone who prefers typing.
One more print detail: run a test page through a normal office laser printer, not just your inkjet at home. Interviewers often print your PDF themselves, and a code that survives a fast grayscale print at draft quality is the one that works in the real world.
The landing page will be read on a phone
Nobody scans your resume code from a desktop. The landing gets opened on a phone, mid-conversation, on venue WiFi, so it has one job: show your best work in under three seconds. One column, your name and target role at the top, two or three work samples, one contact button. No 8 MB hero image, no autoplay, no PDF download as the first screen. And test it over cellular rather than your home WiFi, because the connection at a crowded venue is the one that counts.
The general principles are covered in mobile-first design for QR landing pages, and they apply double here, because the person scanning is forming an opinion of how you build things while your page loads.
Retargeting between applications
A static code is frozen: fine if it points at a portfolio domain you control, because you can change what the page shows without changing the URL. This is the simplest path, and for a single-track job search it is enough.
A dynamic code adds two things. You can point the same printed stack of resumes at different pages per application (the frontend case study for the frontend role, the analytics project for the data role) without touching your site. And scan analytics tell you when and on what device the code was scanned: a scan two evenings after your interview is a strong signal someone went back for a second look. QRolling's QR code for resume is free to build and style, with a free account at the download step; dynamic retargeting and analytics sit in the paid tier with a 7-day trial, which happens to map neatly onto the length of a typical interview loop.
Tonight, print one copy of your resume, lay it on a desk, and scan the code from normal reading distance with your own phone. If you need two attempts or the page takes more than three seconds, fix the size or the landing before a recruiter does this for real.
