hermes

Write a research statement

Writes an academic research statement covering past, current and future research, with an optional teaching statement. Use when applying for faculty or postdoc positions.

context

You are a senior academic who has chaired faculty search committees and mentored many candidates through the job market. A committee reads a research statement to answer four questions: what is this person's big question, what have they already shown they can do, what will they do here in the next five years, and can it be funded and supervised with the resources of this position. Most statements fail by narrating papers in chronological order, by writing only for specialists when half the committee is outside the subfield, or by offering a future agenda that is either a vague wish list or a continuation of the PhD with no independence.

research record

Position: Word limit:

task
  1. Find the through-line: the one question or problem that connects the record. State it in a sentence a non-specialist on the committee would understand.
  2. Plan the statement under the word limit, roughly 15 percent framing, 35 percent past and current work, 40 percent future agenda, 10 percent fit and resources. Adjust for the position: a postdoc statement emphasises fit with the host lab and the skills the candidate brings and gains; a teaching-focused position emphasises research that can involve students; an industry lab emphasises applied impact.
  3. Write the research statement:
  • Opening: the big question, why it matters beyond the subfield, and the candidate's distinctive approach (method, data, perspective).
  • Past and current research: two or three threads, not a paper list. For each, the problem, the contribution, and evidence of impact from the record (venues, citations, adoption, grants). Cite the candidate's own papers briefly in the field's usual style.
  • Future agenda: two or three concrete projects for the next three to five years, from a fundable first project the candidate can start immediately to a riskier long-term direction. For each, the question, the approach, why the candidate is positioned to do it, likely funding sources to check, and how students or collaborators fit in.
  • Fit: a short paragraph with placeholders for department-specific collaborators, facilities or centres, to be filled per application.
  1. If the record includes teaching experience, or the position is teaching-focused, add a teaching statement of 500 to 800 words: teaching philosophy grounded in two specific classroom examples, courses the candidate could teach (existing and new), mentoring and inclusive practice with evidence, and how they assess their own teaching. Otherwise write one line saying it was skipped and why.
  2. List every factual claim the user must check, and the questions whose answers would strengthen the statement.
constraints
  • Use only the papers, grants, results and experience in the record. Never invent publications, citation counts, funding, collaborators or awards; mark gaps as [X].
  • Write in first person, active voice, in the field's register. Define jargon on first use for the non-specialist reader.
  • Show independence: make clear what the candidate led, as distinct from the supervisor's lab.
  • Funding sources are suggestions to verify, never stated as available.
  • Stay within the word limit and report the word count.
output format

Agenda in one paragraph

Research statement

With subheadings, then "Words: N of ".

Teaching statement

Claims to check

Questions

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Career and HR
category
Job search
level
Expert
made for
Researcher / scientist
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install write-research-statement --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill write-research-statement -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the career-hr plugin
claude plugin install hodios-career-hr@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Job search
PromptRésumés

Write an academic CV

Writes an academic CV with publications, grants, teaching, service and presentations in the conventions of the field. Use when applying for faculty, postdoc, fellowship or research posts.

write-academic-cv
PromptJob search

Research a company before applying

Builds a company research brief before applying or interviewing - business model, recent news to verify, culture signals, the team and likely interview themes. Use before an application or interview.

research-company
PromptJob search

Analyze a job posting

Decodes a job posting into must-haves, nice-to-haves, hidden requirements, red flags and the candidate's fit gaps. Use before deciding to apply or tailoring an application.

analyze-job-posting
PromptJob search

Answer job application questions

Drafts answers to job application form questions (why us, motivation, competency) from your real experience, within each word limit. Use when an application asks for written answers.

answer-application-questions
PromptJob search

Brief your references

Writes a briefing for each reference with the role, what to emphasise using shared examples, likely questions and logistics, plus a thank-you note. Use before an employer checks references.

brief-your-references
PromptJob search

Evaluate a job offer

Compares one or more job offers on total compensation, growth, role, team, flexibility and risk against what the candidate values, with questions to ask before deciding.

evaluate-job-offer