Shared resumes were a dead end, so I gave them a preview card and a way back
Until this week, a resume someone shared from ResuHive showed up as a bare link in chats and on LinkedIn. It had no preview and no way for the person who opened it to find the tool.
Now public resume pages get a proper preview card, plus a small "Made with ResuHive" link back.
The same week I also stopped showing Chinese-style layouts on the English site by default, fixed US layouts that were still drawing ID photos, and added six US-style templates.
Honest status: I don't have data yet on whether shared pages bring anyone back. I'll report when I do.
If you've built a "made with" loop, did it pull its weight, or was it mostly vanity?
No "made with" data from me, but one thing from the other end of the resume pipeline that might change what you measure.
I build AI Applyd, which submits applications on employers' own hiring systems (Workday, Greenhouse, Lever and the rest). Every one of those systems wants a file, a PDF or a DOCX. None of them take a link. So when a recruiter or a hiring manager opens a shared resume page, their next real step is usually to get that resume into their own system.
Two things follow from that, I think:
A clean "Download PDF" on the public page may be the highest-intent action you have, and it's cheap to count. Someone who downloads is doing real work with it, not just glancing at a preview.
The people who open a shared resume are mostly hiring people, not job seekers, so they're a weak audience for a "Made with ResuHive" link. The job seeker's friends are a much better one, which fits your DM point: a friend asking "how did you make this?" is the loop that pays. It might be worth giving the person sharing a line they can forward, rather than relying on the recipient to click the badge.
Curious what the DM vs LinkedIn split shows once you have it.
How did you decide this was worth building in the first place?
How did you decide this was worth building in the first place?
Helpful post. How did you get your first bit of traction?
Solid lesson. Which channel has worked best for you so far?
Curious how long it took before you saw the first real results?
Interesting approach. What was the hardest part to get right?
Interesting approach. What was the hardest part to get right?
Curious how long it took before you saw the first real results?
The preview card as the conversion event is a sharp distinction. I’d also compare click-through by share context—DMs and LinkedIn likely create very different intent even with the same card.
Yep, splitting by context is next. A DM from a friend and a LinkedIn post are basically two different products.
Helpful post. How did you get your first bit of traction?
Curious how long it took before you saw the first real results?
Solid lesson. Which channel has worked best for you so far?
Interesting approach. What was the hardest part to get right?
Interesting approach. What was the hardest part to get right?
Curious how long it took before you saw the first real results?
Have recipients of shared resumes started taking a measurable next step into ResuHive, or is the “Made with” loop still unproven?
Still unproven. It shipped this week and I don't have numbers yet. I'll post them when there's enough to mean something.
That’s fair. What’s the first behavior you’ll watch to tell whether the “Made with” link is actually pulling recipients into ResuHive rather than just getting seen?
How did you decide this was worth building in the first place?
Did almost the exact same thing this week. Every team link on my site now gets its own preview image (e.g. "Celtics fans, the arena needs you"), because a bare URL in a DM or a reply just looked like spam.
Early signal: people actually click the card, the bare link got ignored. One gotcha if you use X: it caches a card the first time it sees a URL, including a failed one. One of my cards stayed broken until I added a version param to the image URL. Worth knowing before you debug for an hour like I did.
That X caching gotcha is gold, thanks. Our shares mostly land in LinkedIn and chat apps, and LinkedIn caches too, so I'll version the image URL before I spend an hour debugging a stale card. When you say people click the card, is that from your own analytics or just replies going up?
Love this angle, honestly. What made you look into it in the first place?
Helpful post. How did you get your first bit of traction?
Solid lesson. Which channel has worked best for you so far?
Interesting approach. What was the hardest part to get right?
Curious how long it took before you saw the first real results?
Interesting approach. What was the hardest part to get right?
Curious how long it took before you saw the first real results?
Interesting approach. What was the hardest part to get right?
Curious how long it took before you saw the first real results?
The Chinese-layout-on-English-site fix connects directly to the ID photo problem. Both are the same bug: a locale-sensitive feature rendering in the wrong context. We hit this running our site in seven languages — the fix is always the same shape: make the default match the viewer, not the creator.
On the “made with” loop: I don’t have data on ours because we haven’t built one, but the preview card matters more than the link. It determines whether anyone opens the shared page at all — without it, a resume link competes with every other bare URL in a chat window. The card IS the conversion event; the “made with” link is just the path after someone already decided to look.
Worth tracking once you have numbers: how many clicks come from LinkedIn shares versus direct messages. The channel shapes conversion more than the loop design.
"Default to the viewer, not the creator" is a cleaner way to say what I kept fixing one bug at a time. Agreed the card decides whether anyone opens the page. I'll tag share links by where they were posted so LinkedIn and DMs don't get lumped together.