Should You Attach Your Resume to a Networking Email?

Attach your resume when the person receiving it can act on it today, and leave it off when what you actually want is a conversation. A recruiter, a hiring manager with an open role, or a contact who has already offered to refer you can all do something with a file, so send one. Someone you cold emailed for fifteen minutes of advice cannot, and the attachment quietly converts a request for help into a request for a job. That switch is what makes the email land badly, not the file itself.

Why does an attachment change the ask?

An email with no attachment reads as "can I ask you something." An email with a resume attached reads as "please consider me." Those are different favors, and the second one is much larger.

This is the part the forum arguments miss. People debate attaching versus not attaching as though it were a question of etiquette, when it is really a question of matching the file to the request. If you have asked a stranger for a short call about how they moved from consulting into product, a resume in that email is answering a question they did not ask. They now have to work out what you want from them, and ambiguity is the most reliable way to get no reply.

The inverse costs you just as much. If you write to a former colleague who has told you they will pass your name to their manager, and you make them come back and ask for the file, you have added a round trip to a favor they were already doing. Some of those round trips never happen.

When should you attach it?

Attach in these situations, and do it without apologizing for it:

• They asked. Obvious, but people still hedge here. Send it in the next reply, not after a paragraph of preamble.
• You are asking for a referral outright. A referral request without a resume is incomplete, since the person has to submit or forward something.
• You are writing to a recruiter, internal or agency. Their job is matching files to open roles. A resume is the unit of work.
• You are following up on an application you already submitted. The file is already in their system, so a second copy costs nothing and saves them a search.
• A mutual contact made an introduction and named a specific opening. The intro did the social work already. Attach and keep the note short.
• You are replying to a job posted in a group, a Slack channel, or an email thread. Public postings are open invitations.

The common thread: in each case someone downstream has a slot to fill, and your file is the thing that fills it.

When should you leave it off?

Leave it off when your email is a request for time or information:

• Cold outreach to someone at a company you admire, asking about their path
• Alumni outreach through a school directory
• Asking a former manager to catch up before you have told them you are looking
• Writing to someone senior who has no hiring authority over the roles you want
• Any first message where you are not yet sure the person is willing to help

In those emails, do this instead. Say in one sentence what you do and what you are moving toward, then close with "happy to send my resume if it is useful." That line does two jobs. It signals you have one ready, and it hands the decision to them. When they say yes, the resume arrives invited, which is a very different reading experience than arriving uninvited.

There is a middle option worth knowing about. A LinkedIn URL in your signature gives a curious reader somewhere to look without putting a file in front of them. It is not a substitute for a resume when someone needs to forward you, but for a first cold email it does the job. The differences between a profile and a resume matter here, because the profile is doing background work rather than making a case for one specific role.

Which version of your resume should you send?

Here is the problem none of the pages ranking for this question deal with: a networking email has no job description attached to it, and your resume is supposed to be tailored to one.

You have three real options and they are not interchangeable.

The master resume. Everything you have ever done, nothing cut. Send this to nobody. It is a source document, and reading it is work.

A target-role version. One clean resume aimed at the kind of job you want next, not at any particular posting. This is what a networking email should carry. It opens with a line that names the role you are going after, orders the relevant experience first, and carries a skills section built from the terms that keep recurring across the postings you have been reading rather than everything you have ever touched. If you have been pulling the language out of those postings, that vocabulary is exactly what belongs here.

A posting-specific version. Cut and reordered for one req. Right only when the email names that req, which is the referral and warm-intro case.

The mistake is sending the master file because it feels more complete, or sending last month's posting-specific version because it is the one sitting in your downloads folder. A contact reading a resume that was obviously written for a job at another company will read it as a resume for that other company.

If you are running enough conversations that keeping a target version current by hand starts to slip, LetMeApply's resume tailoring produces the per-posting versions from your master file, which leaves the target version as the one document you actually maintain.

What happens to your file after they forward it?

Assume every resume you send by email eventually gets forwarded, and assume at least one of those forwards ends inside an applicant tracking system.

That assumption changes three small decisions and one habit.

Format. Send a PDF unless the recipient asks for Word. PDFs hold their layout and modern parsers read them fine. Send Word only when a recruiter tells you their system needs an editable file, which some staffing firms still do.

Filename. Name it so it is findable in a stranger's downloads folder: priya-raman-data-analyst.pdf. Not resume.pdf, not resume_v4_final.pdf. Your contact may forward it three weeks later, and they will search for it by your name.

Parse safety. If the version you send keeps your contact details in a document header, uses two columns, or puts dates in a text box, it can look perfect to your contact and arrive at the ATS with fields missing. Running it through an ATS check once is worth the five minutes, because this is the file you will send many times rather than once.

One line in the body. Put a one sentence summary of what you do near the top of the email. If your contact forwards the whole message to a colleague, that sentence becomes your introduction. Without it, the colleague opens an attachment with no framing around it.

How do you write the email so the resume is not the point?

Short, specific, and easy to say yes to. The shape that works:

1. A subject line that names the connection. "Fellow Michigan grad, question about your move to Stripe" beats "Networking." It answers why you and why now before they open it.
2. One sentence on who you are. Role, focus, where you are heading.
3. One sentence on why them specifically. Something real: a talk they gave, a path they took, a team they built. Generic praise reads as a mail merge because it usually is one.
4. One clear ask with a floor under it. "Would you have fifteen minutes in the next couple of weeks" is answerable. "I would love to connect" is not.
5. The resume line. Either "I have attached my resume in case it helps with the referral" or "happy to send my resume if that is useful," depending on which of the two cases above you are in.

Five sentences. If you write these at volume, the same discipline that makes a cover letter fast to write applies here: the structure is reusable, and the only part you rewrite every time is that second sentence about them.

Skip the paragraph about how much you admire the company. They know.

What if they ask for your resume after the conversation?

This is the outcome you wanted, and it needs a same-day answer.

Send it within a few hours of the call, while the conversation is still warm. Reply on the existing thread rather than opening a new one. Add two lines that recall something specific they said, and if they named a team or a role, send the version aimed at that, not the one you would have attached to a first email.

Then say what you will do next, and do it. "I will apply through the careers page today and send you the req number" gives them something to act on internally without asking them for anything further. Referral programs generally attach the referral to an application that already exists, so the req number and the date you applied are the two things your contact needs from you.

Keep track of who has your resume and which version they got. When you are applying at volume, losing track of that is how you end up sending a fourth version to someone who is already advocating for the second one.

Frequently asked questions

Should I paste my resume into the email body instead of attaching it?

No. Pasted resumes lose their formatting, and a wall of unformatted text is harder to read than an attachment is to open. The one exception is an application address that explicitly says no attachments, which some government and older corporate systems still use. There, follow the instruction exactly.

PDF or Word?

PDF by default. It survives being opened on a phone, in a browser preview, and in whatever email client your contact's colleague happens to use. Switch to Word only when someone asks for it, which usually means their system needs to edit the file.

Is a LinkedIn link enough instead of a resume?

For a first cold email, usually yes. For a referral, no. Someone submitting you internally often needs a file to upload, and asking them to assemble one from your profile is asking them to do your work for you.

Should I attach a cover letter to a networking email too?

No. A cover letter is written for one posting and one hiring team, and in a networking email it reads like a form letter that wandered into the wrong inbox. Whatever you would have said in it belongs in the five sentences of the email itself.

They agreed to refer me. Do I still apply through the careers site?

Almost always. Referral programs are usually built to attach a referral to an application already on file, so someone has to submit one either way. Ask which order they prefer, apply, then send them the req number and the date.