Someone Just Asked for Your Resume in a Chat. Here's How to Send It

"Can you send me your resume?"

It arrives in a WhatsApp chat, a LinkedIn DM, or a Telegram group at 9pm. This is a small window of live attention, and it closes fast. What you send in the next two minutes decides whether it gets read tonight or forgotten by tomorrow.

Most people handle it badly, and not because they are lazy. They handle it badly because they treat it like a file transfer instead of a first impression.

What to actually send

Send something that opens in one tap and reads on the screen it lands on. The person asking is on their phone — that is where the message came from. Whatever you send should be legible there without pinching.

If you only have an A4 PDF, send it, but understand what happens: it opens shrunk to a quarter of readable size, they decide to look at it later, and later does not arrive. A link to a phone-readable version of the same resume solves exactly this, which is why the link is what you lead with when a human is on the other end.

What to say with it

Two lines. Not a cover letter, not a single bare file with no message.

Bad: the file, alone, no text.

Also bad: "Respected Sir, Please find attached herewith my curriculum vitae for your kind perusal and consideration."

Good: "Here you go — backend engineer, 3 years, mostly Node and Postgres. Happy to walk through the payments work if it's relevant."

That version does three things in one breath: it hands over the resume, it tells them what you are before they open anything, and it offers a next step. If they read nothing else, they know whether to keep going.

The four mistakes

1. Sending it as a document with a filename like resume_final_v3.pdf

They see the filename. Rahul_Sharma_Backend_Engineer.pdf costs you five seconds and reads like someone who is organised. resume final FINAL (2).pdf reads like the opposite.

2. Sending it as photos

Screenshots of a resume cannot be searched, cannot be forwarded cleanly, and cannot be uploaded to a form. It is the worst of both formats.

3. Sending a Google Drive link with restricted access

This is the most common self-inflicted wound. They tap, they hit a request-access screen, and now helping you requires them to send a request and wait for you to approve it. Half the time they simply do not. If you use Drive, set it to anyone-with-the-link and test it from a logged-out browser first.

4. Making them wait

"I'll send it tonight when I'm on my laptop" is where the opportunity leaks out. The moment someone asks is the moment they are thinking about you. If your resume only exists as a file on a laptop at home, you cannot answer while the window is open. Something you can send from your phone in ten seconds is worth more than a perfect document you send tomorrow.

The setup that makes this a non-event

Get your resume onto a link once. Then "send me your resume" is a ten-second reply from anywhere, on any device, and it lands readable.

That is what cvonphone.com does — you upload the PDF you already have, it becomes a page built for phone screens, and you send that address instead of an attachment. The A4 download stays on the page for whoever needs the file.

The point is not the tool. The point is that the request should never catch you unprepared, because a resume you can send instantly beats a better resume you send two days late.

A quick script you can reuse

Save this and change three words each time:

Here's my resume: [link]
Short version: [role], [years] years, mostly [two skills or domains].
Let me know if you want anything specific expanded.

That is the whole thing. Fast, specific, and easy to say yes to.