Find Experts Worth Interviewing Without Famous Names

To find experts worth interviewing when you don't have famous ones, stop recruiting for reputation and start recruiting for proximity to the work. An expert worth interviewing is anyone who has personally done the thing recently, can describe a specific instance of it in detail, and is allowed to talk about it. By that definition, your support queue, your delivery team, your customers, and the operators one introduction away hold more publishable material than most keynote speakers — because the value of an interview is specifics, and specifics live with practitioners, not with personal brands.

Famous experts optimize for the opposite of what your article needs. They are rehearsed, which means their answers are already published; they are busy, which means you get thirty polished minutes; and they are careful, which means no real numbers, no named mistakes, no cleared screenshots. The unfamous practitioner who migrated the billing system in March will give you all three.

Who this is for

This is for content leads, writers, and founders who want interview-led articles — the kind with first-hand evidence that generic AI-written pages cannot supply — but who look at their contact list and conclude they have no experts to interview. The claim of this guide is that the conclusion is wrong, and the fix is a sourcing method, not better networking.

It assumes you know why the interview is worth running: Google's quality-rater guidelines treat first-hand experience as a core signal of page quality, and its helpful-content guidance asks whether content demonstrates the depth that comes from actually doing the thing. A practitioner interview is the cheapest honest way to put that experience on a page you did not live yourself.

What makes an expert worth interviewing?

An expert is worth interviewing when they personally did the work recently, can describe a specific instance of it, and are allowed to talk about it — score candidates against the reader's task, not against status. A candidate is worth interviewing when:

• The work is theirs. They executed it — not managed someone who managed it. One degree of separation costs most of the usable detail.
• The work is recent. Within roughly the last year for fast-moving topics. Memory of specifics decays; opinions calcify.
• They can produce a specific in sixty seconds. Ask about the last time they did the thing; if the first answer contains a number, a tool name, or a mistake, the interview will yield material.
• They have permission latitude. Someone must be able to clear quotes, examples, or screenshots. A brilliant source under total NDA produces an article you cannot publish — the clearance rules in quote permissions and fact-checking apply from the first email, not after the call.
• Their incentive is survivable. Vendors talking about their own product category need labeling and balance; that is manageable, but plan for it.

Notice what is absent: audience size, job title seniority, media experience. Those predict reach, not evidence.

Where do you find experts to interview for content?

Five pools, ranked by evidence quality: your own delivery people, your customers and users, operators one introduction away, practitioner communities, and cold outreach to visible practitioners. Work the pools in order — each step outward costs specificity and permission latitude.

1. Your own delivery people

Support, sales engineering, implementation, ops — whoever touches the real failure modes daily. They are the highest-yield pool: zero outreach cost, maximal permission latitude, and they already know which customer problems repeat. The same people power the workflow in turning sales and support questions into durable SEO pages; interviewing them is the evidence-capture version of that play.

2. Your customers and users

They have done the thing your readers are trying to do, with your product or without it. Recruit from support tickets that ended well, onboarding calls, and community posts. Expect to trade for their time: early access, a gift card, or simply the credit. Anonymization is often the unlock — many customers will describe the incident in detail if the company name stays out.

3. Operators one introduction away

Your investors' other founders, your teammates' former colleagues, your vendor's other customers. The warm intro matters less for trust than for triage: the introducer has already matched the person to the topic. Ask for "someone who has personally done X in the last year," not "an expert on X" — the phrasing filters out professional opinion-havers.

4. Practitioner communities

Niche Slack and Discord groups, subreddits, specialized forums. Look for the people answering questions with specifics, screenshots, and post-mortems — the ones already publishing evidence for free. Read their post history before outreach; it is a pre-completed screening call. Respect community norms about solicitation and take the conversation to DM or email early.

5. Cold outreach to visible practitioners

Authors of detailed blog post-mortems, conference lightning-talk speakers, maintainers of niche tools. This pool overlaps with "slightly famous," so apply the scorecard hard: you want the person whose talk was one migration story told well, not the circuit speaker with a slide library. Skip mass quote-request marketplaces; sourcing from them optimizes for people who want links, and the material arrives pre-flattened into quotable generalities.

The expert sourcing scorecard

The artifact on this page is the expert sourcing scorecard: score each candidate 0–2 on six criteria, from the sourcing pools above, before booking a full interview. Nine or more: book it. Six to eight: screen first. Under six: keep looking.

Criterion	0	1	2
Proximity	Observed or managed the work	Did the work with heavy support	Personally executed it
Recency	More than 2 years ago	Within 2 years	Within 12 months
Specificity on first ask	Talks in principles	Mixes principles and examples	Leads with an incident, number, or tool name
Permission latitude	NDA-bound, employer hostile to press	Clearable with effort or anonymization	Free to speak on the record
Incentive risk	Selling into the topic, undisclosable	Vendor-adjacent but labelable	No commercial stake in the answer
Reliability	Hard to schedule, vague replies	Responsive but hedging	Responsive and concrete in email

Score from evidence, not vibes: their forum posts, the introducer's answer to "what did they actually do," and their first email reply all count.

How do you screen an expert before booking a full interview?

Run a ten-minute screening call for candidates scoring 6–8: pitch the reader in one sentence, ask for the last time they did the thing, ask what went wrong, and map permission latitude — two specifics in ten minutes predicts a usable hour. The script:

1. One sentence on the article and the reader it serves.
2. "Walk me through the last time you did X." Listen for a story with a sequence.
3. "What went wrong that you didn't expect?" Listen for ownership of a mistake.
4. "Is there anything from that project you couldn't talk about publicly?" Maps permission latitude early.
5. Close: what attribution they would want, and whether their employer needs to sign off.

Two specifics in ten minutes predicts a usable hour. Zero specifics predicts a keynote — thank them and move on. Nielsen Norman Group's interviewing guidance makes the underlying point: what people say in the abstract diverges from what they did in the particular, so the screen asks only about particulars.

How do you get an expert to agree to an interview?

Pitch the specific incident rather than the topic, bound the ask to one hour, give them control of exposure, and offer the credit. Unfamous experts decline interviews mostly because they think they are not expert enough; the pitch has to dissolve that:

• Name the specific incident, not the topic. "I'd like to interview you about the warehouse migration you described in the community thread" beats "you seem knowledgeable about data infrastructure."
• Bound the ask. One hour, their choice of time, questions in advance if they want them.
• Give them control of exposure. Quote approval before publication, anonymization on request, employer sign-off accommodated. This is not just courtesy; it is the permission workflow starting early, per Reuters-style handling of attribution and quotation.
• Offer the credit. A byline-adjacent expert credit, a link to whatever they want linked, and a cleared draft they can show their boss.

The conversion rate on this pitch is high precisely because nobody else is asking these people. That is the whole arbitrage: famous experts are over-interviewed and under-specific; practitioners are the reverse.

Mistakes that produce famous-but-useless interviews

• Recruiting for the promotion, not the page. A big name shared to their audience is a distribution tactic; it rarely counts as evidence when the page later faces a keep-or-cut content audit.
• Accepting "thought leadership" as scope. If the candidate wants to discuss trends rather than incidents, the transcript will contain nothing your article can use.
• Skipping the permission conversation until after the call. You will interview someone whose best material is unclearable, then be tempted to paraphrase it anyway.
• Treating vendor experts as disqualified instead of labelable. A vendor engineer's migration war story is usable with disclosure; pretending they are neutral is the actual failure.
• Sourcing everyone from one pool. All-internal interviews drift into marketing; all-community interviews drift off your topic. Mix pools per cluster, and split rich conversations across articles with the interview splitting map.

FAQ

How do I find experts to interview for content if my network is small?

Start inside: your support, delivery, and sales-engineering colleagues are interviewable today, and your customers are one polite email away. A small network changes which pool you start with, not whether the method works — proximity to the work, not connections, is the scarce input.

Are unknown experts actually credible to readers and to Google?

Credibility on the page comes from what the interview produces: named context, specific incidents, verifiable details, and honest attribution. Google's quality-rater guidelines value demonstrated first-hand experience, which an unfamous practitioner supplies better than a rehearsed public figure. Fame adds recognition, not evidence.

Should I pay interview subjects?

Paying for time is legitimate for customers and community practitioners, and often fairer than not paying; disclose it if the arrangement could reasonably color the content. Do not pay for favorable claims, and never let payment substitute for the permission and fact-checking workflow.

What about services that broker expert quotes?

Quote-request marketplaces select for people seeking links, and the submissions arrive as polished generalities you could have generated. If you use them at all, treat responses as candidate discovery — then run the scorecard and a screening call before treating anyone as a source.

How many candidates do I need per article?

Plan two or three scored candidates per interview-led article: one primary, one backup, and optionally one whose role is a counter-position or edge case. Over-recruiting slightly costs less than discovering mid-draft that your only source cannot clear their best material.

Where this fits in the interview pipeline

Sourcing is step zero of the pipeline. Once a candidate is booked, scope the article with the expert interview content brief, run the call against the interview run sheet, clear the material through quote permissions, attribution, and fact-checking, and draft with the voice-preservation protocol so the specifics you recruited for survive to publication. For why practitioner evidence is the point at all, see what experience means in a blog post when you are not a famous expert.

Sources and last-reviewed notes

Last reviewed: 2026-09-14. Sources checked: Google's helpful-content guidance and search quality evaluator guidelines on first-hand experience, Nielsen Norman Group's user-interview guidance on eliciting particulars rather than abstractions, and Reuters' interview guidance on attribution and quotation handling. The sourcing pools, scorecard, screening script, and pitch structure are our own working methods; no real candidates, companies, or interviews are referenced.