Publications, Patents and Conference Talks on a Resume

Deciding which document you are writing

Before formatting anything, settle which of the two you are producing, because the answer changes every subsequent decision. The CV versus resume guide covers the distinction in full; the short version for this section is below.

Anything in between — industrial research, clinical roles, R&D, science communication, policy — sits on a spectrum, and the reliable test is who reads the document first. If it is a departmental committee, write the CV. If it is a recruiter with sixty applications, write the resume.

Formatting a publication entry

Use whichever citation style your field uses — APA, MLA, Chicago, Vancouver, IEEE — and apply it identically to every entry. Which style you pick matters much less than the fact that you did not mix three of them, and inconsistency in this section is read as carelessness about the exact thing the section is meant to demonstrate. The Purdue OWL guidance on resumes and vitas is a reasonable reference for the underlying conventions.

• Mark your own name in bold or underline within each author list. Readers are scanning for your position in the ordering, and making them find it is an unnecessary tax.
• Keep author order intact. Never move yourself to the front. In fields where author position carries meaning, this is one of the most serious things you can get wrong.
• Include a DOI or a stable link where one exists, so the claim is verifiable in one click.
• Group by type once you have more than a handful: peer-reviewed articles, book chapters, conference papers, preprints, technical reports.
• Label the ones that are not peer-reviewed. Preprints, working papers and blog posts are legitimate outputs and are not the same as a journal article. Filing them together is the sort of blurring that a specialist reader will spot immediately.

What to say on a commercial resume

A citation on its own tells a non-specialist reader nothing except that a thing exists. What makes a publication useful outside academia is the clause you attach explaining what it demonstrates about you — usually depth in a topic, an ability to communicate it, or evidence that people in your field treat you as a source.

The same principle applies to industry writing that is not academic at all. A widely read technical blog post, a chapter in a practitioner handbook or a standards contribution can be more persuasive to a commercial employer than a journal article, and it belongs in the same section under a broader heading such as "Publications and Writing".

Patents

Patents are strong evidence and are frequently written too vaguely to be checkable. Four elements make an entry solid.

Title and number

The patent title as filed, with the number. For a granted US patent that is the grant number; for a pending one, the application publication number.

Status and jurisdiction

"Granted", "pending" or "published", and where — US, EP, WIPO. Status changes over time, so this is an entry to keep current.

Date

Grant date for granted patents, filing or publication date for pending ones. Say which you are giving.

Your role

Inventor or co-inventor, with the number of inventors where there were several. One clause on what the invention does is worth more than the formal title, which is usually written to be broad rather than clear.

Anyone can confirm a US patent number through the USPTO patent search tools in under a minute, which is exactly why the number belongs on the page: it turns a claim into something the reader can settle for themselves without asking you.

Conference talks and presentations

Speaking is under-listed on commercial resumes and over-listed on academic ones. The test is whether the event or the audience means something to the person reading. A keynote at a recognised industry conference is a strong signal about standing in a field; an internal lunch-and-learn is not, however good the talk was.

1. Talk title, event, location and year, in that order and identically every time.
2. Say what kind of slot it was. Keynote, invited talk, accepted conference paper, panel, workshop, poster. These are very different things and the difference is the information.
3. Give the audience size where it is impressive and known. "Approximately 600 attendees" is a fact; "a large audience" is not.
4. Note if it was peer-reviewed or competitively selected, since in many fields acceptance is the achievement rather than the delivery.
5. Link the recording or slides where they are public. A talk is the one output a reader can evaluate in two minutes.

Where you have a lot of talks and only some are notable, the same selection logic applies as for publications: three or four listed with detail, and a summary line covering the rest — "regular speaker at regional data engineering meetups, 2022–present" — which conveys the pattern without listing fourteen entries.

Common failures

• Pasting a full academic list into a two-page resume. It crowds out the experience section and signals that you did not adapt the document to the reader.
• Listing a paper you are a minor contributor to as though you led it. Author order is public and specialists read it first.
• "Manuscript in preparation". This means an unfinished draft and every academic reader knows it. "Under review at Journal" is a real status; "in preparation" is an aspiration.
• Undated entries. A publication list with no years cannot be assessed for currency, which is one of the main things it is being read for.
• Duplicating one output across sections. A conference paper that was also a talk is one entry with both facts, not two entries.
• Citation metrics on a commercial resume. An h-index means something specific to a search committee and nothing at all to a hiring manager, who may reasonably read it as jargon.

If the section is running long, that is usually a sign that you are writing a CV inside a resume. Decide which document you need, then let the layout follow — the template library includes longer academic-style layouts as well as the compact two-page ones, and choosing the right container solves most of the formatting arguments before they start.