Get AI summaries of any video or article — Sign up free
The CV that got me my first university job [All the MISTAKES] thumbnail

The CV that got me my first university job [All the MISTAKES]

Andy Stapleton·
5 min read

Based on Andy Stapleton's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Tailor the CV’s opening section to the target job with specific, concrete alignment rather than vague statements.

Briefing

A PhD CV that lands a university postdoc isn’t about looking polished—it’s about putting the right evidence in the right order for the specific job. After finishing a PhD and spending a year in industry, Andy Stapleton says his first university role came from a curriculum vitae that matched the research focus of the position: transparent electrodes for solar cells. The core lesson is blunt: the most powerful section of a CV—career goals and how they connect to the target role—must be concrete and tailored, not generic or awkwardly broad.

Stapleton’s original academic CV is described as “ugly” but functional, and the details reveal where it worked and where it missed. He lists major sections such as personal details, career goals, qualifications, current employment, research experience, scholarships, publications, lab skills, computer skills, other skills, teaching experience, interests, and referees. The biggest weakness is the opening career-goals section: it begins with a vague line about having a “varied research history,” which he calls a bad first impression. He contrasts that with what should have been front-loaded instead—his specific background in colloid and surface chemistry and organic photovoltaic devices, plus a clear statement of how his chemical education and PhD work would help improve device performance and solve practical problems.

Beyond the opening, the CV’s structure follows a priority logic: qualifications and employment act as quick screening boxes, while research experience and publications do the heavy lifting for academic hiring. For research experience, he recommends keeping descriptions tight—typically a few sentences per project—naming what was done (e.g., refinement of a mini-emulsion process to yield colloidal nanoparticles, evaluation of morphology and surface interactions) and linking it to device improvement. For publications, he emphasizes that peer-reviewed journal articles and conference outputs matter most, and he notes a common temptation to include items that are “in press” or presentations that may not be strictly publication-grade. He also highlights that lab skills and technical tools (including software like Gaussian and Spartan, plus LaTeX and Microsoft Office) can strengthen credibility, especially when they map directly to the role.

Stapleton also argues that non-academic CVs require a different emphasis. When shifting toward science communication, the formatting becomes simpler and the content changes: professional experience and communication outputs move to the top, publications are summarized more broadly, and referees are chosen from relevant industry roles rather than academics. He cites science writing, video production, radio training, podcasting, and media appearances as the proof points that hiring managers in that space care about.

The closing guidance is practical for PhD students: track education, research interests, role-by-role responsibilities, awards, publications and talks, teaching, and a running list of skills (especially analytical, coding, and other transferable capabilities). He also advises preparing referees in advance and keeping them “warm” by notifying them after applying. The overall message is that a CV is a living document—tailor it to the job, lead with the most relevant evidence, and let everything else recede.

Cornell Notes

A successful PhD CV for academia isn’t about aesthetics; it’s about tailoring content to the target role and ordering information by relevance. Stapleton’s academic CV worked because his research experience and technical skills closely matched the postdoc focus on transparent electrodes for solar cells, even though the career-goals section was too vague. He recommends keeping research descriptions concise, prioritizing peer-reviewed publications and conference outputs, and listing lab/computational skills that directly support the job. When moving outside academia, the CV should be rebuilt around science communication evidence—media production, writing, radio/podcast work, and non-academic referees—rather than detailed academic output. The key is to track achievements during the PhD so the CV can be adapted quickly and credibly.

What should be the first thing a hiring committee reads on a PhD CV, and why does it matter?

The opening should connect the applicant’s background to the specific job in a concrete way. Stapleton criticizes his own vague line about having a “varied research history” and argues for a sharper lead such as a clear statement of expertise (e.g., colloid and surface chemistry and organic photovoltaic devices) plus how that expertise will improve the target area (transparent electrodes for solar cells). That alignment is what makes the CV feel immediately relevant rather than generic.

How should research experience be written for an academic postdoc application?

Keep it brief and role-relevant: a few sentences or a short paragraph per project, describing what was done and how it connects to device improvement. In his example, he lists work like refining a mini-emulsion process to produce colloidal nanoparticles, evaluating morphology and surface interactions, and incorporating strategies to improve device performance and rectify problems. The goal is to show competence without drowning the reader in detail.

What counts most in the publications section for academic hiring, and what pitfalls does he warn about?

Peer-reviewed journal articles and conference outputs are the primary credibility signals. He notes that including items that are “in press” can be tempting, and he also includes conference/presentation-related items that he later questions as potentially too informal. The practical takeaway: prioritize outputs that clearly demonstrate research impact and keep borderline items from distracting from the strongest record.

Why does a non-academic CV look fundamentally different from an academic one?

Non-academic hiring focuses on demonstrated communication and industry-relevant outputs, not just academic credentials. Stapleton’s science communication CV moves professional experience and communication work to the top, summarizes publications more generally (e.g., peer-reviewed papers and conference provocations), and highlights training and media production such as video production courses, radio introduction training, podcasting, and roles at outlets like ABC Radio National and science media organizations. Referees also shift to editors and industry leaders.

What should PhD students track during their program so they can build a strong CV later?

Track education, research interests, and what each role/project involved; record awards (even if applying is painful); maintain a running list of publications, conference presentations, and other speaking outputs; log teaching experience; and build a detailed skills inventory. He stresses transferable skills—analytical abilities and coding—because they “future proof” the CV for future employers.

How should applicants handle references and communication with them?

He recommends contacting referees beforehand to confirm they’re willing to act as references, since some may not want unexpected calls. After applying for a job, he suggests sending referees a heads-up email so they’re prepared for potential contact, creating a smoother, less surprising experience.

Review Questions

  1. If you were applying for a postdoc in a narrow technical area, what specific information would you move to the top of your CV, and what would you cut or shorten?
  2. How would you rewrite your research experience bullets to emphasize device impact rather than experimental detail?
  3. What evidence would you prioritize if you were switching from academia to science communication, and how would you choose referees accordingly?

Key Points

  1. 1

    Tailor the CV’s opening section to the target job with specific, concrete alignment rather than vague statements.

  2. 2

    In academia, prioritize research experience and peer-reviewed publications; treat other sections as faster screening items.

  3. 3

    Write research bullets concisely—describe what you did and how it connects to the role’s technical goals.

  4. 4

    List lab and computational skills that directly support the position, including relevant software and technical tools.

  5. 5

    When leaving academia, rebuild the CV around communication outputs and industry-relevant experience, and choose non-academic referees.

  6. 6

    During a PhD, maintain a running record of achievements: projects, responsibilities, awards, publications/talks, teaching, and transferable skills.

  7. 7

    Prepare referees in advance and notify them after applications so they’re ready for potential contact.

Highlights

A vague “varied research history” lead is a self-inflicted problem; the opening should immediately match the job’s technical focus.
Academic CV strength comes from research competence and publication credibility, not from formatting or length.
Switching to science communication requires moving communication evidence to the top and changing referees to industry figures.
The CV should be built from a live tracking system during the PhD—skills, outputs, awards, and teaching—so tailoring is fast and accurate.

Topics

Mentioned