A PI posts “we’re recruiting a postdoc, DM me if interested,” and gets forty replies, thirty-five of which don’t fit the work at all. This isn’t bad luck. It’s what a vague post reliably produces, and it costs more time to sort through than a specific post would have taken to write.
Vague language filters nobody
“Motivated individuals with a passion for research” describes every applicant who has ever applied to anything. It doesn’t tell a computational biologist whether the role needs Python or R, doesn’t tell a wet-lab postdoc whether the position involves mouse work, and doesn’t tell anyone whether funding exists yet or depends on a pending grant. A post that could describe any position in the field will attract applicants for any position in the field, and sorting through that pool is where a PI’s actual recruiting time goes.
What specificity looks like
Compare two versions of the same posting.
Vague: “The Martinez Lab is recruiting a postdoctoral researcher interested in cancer biology. Motivated candidates with a strong publication record should reach out.”
Specific: “The Martinez Lab is recruiting a postdoc to work on tumor microenvironment signaling in a mouse model of pancreatic cancer, using single-cell RNA sequencing and multiplex imaging. Experience with scRNA-seq analysis (Python or R) is required; wet-lab mouse experience is a plus but not required. Position is funded through 2029 via an active R01.”
The second version is longer, and it does more filtering in one paragraph than the first version does across forty replies. A candidate without sequencing experience self-selects out immediately, instead of applying and finding out three emails later that the fit isn’t there.
Say what a typical week looks like
Beyond the project description, a sentence on daily reality helps candidates self-select accurately. “This role is primarily wet-lab, with weekly lab meetings and monthly one-on-ones” tells a candidate who thrives on independent computational work that this isn’t their fit, before they spend a weekend writing a cover letter. This isn’t about talking the position down. It’s about giving an accurate picture instead of the generic optimism most recruiting posts default to.
Be direct about funding
“Position is funded through [year] via [mechanism]” or “funding is contingent on a pending grant decision expected in [month]” tells a candidate exactly what kind of risk they’re taking on. Leaving this vague doesn’t make the position more attractive. It means the funding conversation happens later, after both sides have already invested time, which is a worse outcome for everyone involved.
Where to post it
A recruiting post does more when it lives in more than one place. The lab website should have a dedicated, permanent page for open positions, not a line buried in the about section, since that’s the link a PI can send directly when someone asks. LinkedIn and X reach postdocs and more senior applicants already following labs in the field. Field-specific mailing lists, Slack groups, or forums often reach undergraduates and early PhD applicants who aren’t following individual labs on social media yet.
Posting the same specific language across all of these, rather than a different vague summary on each, keeps the filtering effect consistent no matter where a candidate finds it.
What this saves, in practice
The time spent writing a specific post is not new time. It’s time moved earlier, out of the forty-reply sorting process and into a single paragraph written once. A lab that does this well typically hears from fewer people and spends less total time getting to a good hire, since almost everyone who reaches out already knows the position is a real fit before they write the first email.
Common questions
Why do most lab recruiting posts get so many mismatched applicants?
Because they're written in language vague enough to fit anyone: 'motivated individuals with a passion for research.' That kind of post filters nobody, so it draws a wide, mismatched pool instead of a smaller pool of people who fit the work.
What should a good lab recruiting post include?
The specific project or system, the concrete skills needed, whether funding exists for the position, and what a typical week looks like. Specificity is what does the filtering work a vague post can't.
Where should a lab post when recruiting?
Wherever the lab already has a presence: LinkedIn and X reach postdocs and senior applicants, a dedicated page on the lab website gives a stable link to send people, and field-specific mailing lists or forums often reach undergraduates and early PhD applicants a general post misses.
How long should a recruiting post be?
Long enough to be specific, short enough that someone reads the whole thing. Three to five sentences covering the project, the skills, and how to apply usually does more than a long paragraph restating the lab's general mission.