Turning your LinkedIn profile into a resume

LinkedIn will hand you a PDF of your own profile. What that file actually contains, the three things in it that are the wrong shape for a resume, and what to fix first after importing it.

Last reviewed

LinkedIn will give you a PDF of your own profile, and most people never find the button. It is worth finding: that file is the closest thing you have to a structured record of your career, and it is a much better starting point for a resume than a blank page or a five-year-old .docx you cannot find.

It is also not a resume, and the gap between the two is the useful part of this article.

Getting the file

Open your own profile — the page with your name on it, not the feed. Under your headline there is a More button; inside it, Save to PDF. LinkedIn builds the file server-side; on a computer your browser downloads it, usually as Profile.pdf, and in the LinkedIn app it is saved to your phone’s Files or Downloads.

Two things worth knowing. It is generated from your profile at the moment you ask for it, so it is always current. And it is generated from a template LinkedIn controls, which is why the file has a fixed structure — that is what makes it readable by a machine without guesswork, and it is the reason importing from it can be accurate in a way that importing from an arbitrary resume cannot.

What is in it

Laid out in two columns. A narrow left sidebar carries your contact details, your top skills, your languages, and certifications and awards if you have them. The wide right column carries your name, your headline, your location, your summary, then every role and every school.

Roles come with the employer, the title, a month-and-year date range, the location, and whatever description you wrote on LinkedIn. Education comes with the institution, the degree and field, and the years — years only, never months, because that is all LinkedIn stores.

What is not in it

  • Your photo. The export contains no image at all, not even a placeholder. If you want a portrait on your resume you are adding it separately, wherever you build it.
  • Most of your skills. The file gets your three Top Skills and nothing else. A profile listing forty skills exports three of them.
  • Recommendations, endorsements, follower counts, activity. None of it, which is correct — none of it belongs on a resume either.

Three things in it that are the wrong shape for a resume

This is where a straight copy-paste goes wrong, and it goes wrong quietly.

  • Grouped employers. When you have held several roles at one company, LinkedIn prints the company once, then a total tenure (“3 years 8 months”), then the roles underneath with no employer line of their own. Copied by hand — or read by a tool that does not know the pattern — the second and third roles end up attributed to whatever employer appeared last, and the tenure line can end up looking like a job title.
  • Two columns. Text comes out of a PDF in painting order, not reading order, so a naive copy interleaves your skills list into the middle of your job history. This is the same problem two-column resumes have with applicant tracking systems, and the same rules apply — see our guide on two-column resumes.
  • Descriptions written for a profile. LinkedIn descriptions tend to be a paragraph about the team or the product. Resume bullets are meant to be what you did and what changed because of it. This is the one thing an import cannot fix for you, because it needs facts the profile does not contain.

What to do after the import

Assume the structure is right and the content needs work. In order of how much it matters:

  1. Rewrite the descriptions as achievements. A line that says what the team owned becomes a line that says what you shipped and what it changed. Numbers where you have them, nothing invented where you do not.
  2. Put the skills back. Three is not a skills section. Add the ones the job posting actually asks for and that you can discuss.
  3. Cut what a resume does not need. A profile is cumulative and a resume is selective. School-level education under a completed degree, an internship from eight years ago, a two-month student society role — all reasonable on LinkedIn, all noise on one page.
  4. Rewrite the headline. “Engineering @Company” is a profile headline. A resume wants the role you are applying for.
  5. Check the dates. Education arrives as years, which is the right convention. Roles arrive with months. Both are worth a glance, because a gap you have explained in interviews for years is still a gap a screener sees for the first time.

Is the export itself a usable resume?

No, and it is worth being specific about why rather than just asserting it. The file is two columns with a coloured sidebar, its section headings are LinkedIn’s rather than the ones screeners scan for, it has no summary tuned to a role, it carries a tenure line under every grouped employer, and it will happily run to three pages. It is a faithful printout of a profile. It is not a document written to be read in eight seconds by someone with forty others on their desk.

Use it for what it is good for: it is the record. Everything factual about your career is in there, correctly dated, and re-typing all of that by hand is the part of writing a resume that nobody has ever enjoyed.

Related

  • What actually breaks resume parsing: a controlled experiment

    We took 33 resume templates, changed one CSS declaration at a time, and extracted the text back out of every render. Which formatting choices destroy text, which silently reorder it, and which turn out to be harmless.

  • What an ATS reads from your PDF

    The same resume, shown twice: the page as it prints, and the literal text a parser pulls out of it, in order. Four ways that text comes out wrong while the page looks perfect.

  • Are two-column resumes ATS-safe?

    Mostly yes, with one real cost nobody mentions. What decides whether a side column extracts in the right order, and what a column does to a two-page resume.

  • Fonts that break resume parsing

    A font can embed correctly, print perfectly, and still lose every digit in your dates. Three measured failures, including one that cost us a shipped typeface.

  • PDF or Word: which should you send?

    PDF, unless the posting says otherwise — and the reason is not the one usually given. What each format actually guarantees about the text a parser receives.