R&D tax credit interview questions for engineering teams, with a records-depth block

Credit study interviews follow four steps: hypothesis, uncertainty, experiments and outcome. This question bank covers each step and adds a five-minute depth block that records how many years and systems of engineering decisions a client kept, the signal behind a permissioned SourceX licensing introduction.

When should you use this question bank?

Use it for the technical interviews in a credit study: the 30-to-60-minute conversations with engineers, product leads and quality managers that turn project files into a narrative of hypothesis, uncertainty, experiment and outcome. The questions below are written for the interviewer. A second, short block records how long and how well the team documented its decisions, which is the depth signal behind a permissioned licensing introduction.

Nothing here decides whether an activity qualifies for a credit. That judgment belongs to the engagement team applying the tax rules. This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

Core interview questions

Copy these into your interview guide. Each sits in a callout so it can be pasted as-is.

Opening and context

Hypothesis and uncertainty

Experiments and alternatives

Outcome and learning

Depth block: how well were decisions documented?

Ask these at the end, and write the answers in a separate section of your notes. They take five minutes and need no access to any file.

How to read the depth answers

What you heardWhat it suggestsNext action
Five or more years in connected tools, with named ownersDeep, exportable historyRun the fit screen; consider asking permission to introduce
Strong notes, but only in one or two toolsNarrow historyNote it; low priority
Older systems retired without exportsRecords may be goneAdvise preserving what remains before more is cut
Decisions made verbally, little writtenThin documentationCredit documentation risk; licensing not a fit
Key engineers left, notes in personal drivesFragile recordsNo introduction until the company can recover them

A company that scores well should also pass the baseline: 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license and an authorized sponsor. The company fit checker gives a non-binding preliminary screen.

Adapting the questions by client type

Client typeSwap inTypical record to ask about
ManufacturerTrial run and tooling questionsChange orders, inspection results
Engineering or A/E firmDesign-method and calculation questionsCalculation files, review markups
Software or AI teamExperiment and evaluation questionsPull requests, evaluation reports
Lab or process companyProtocol and batch questionsLab notebooks, batch records

For fuller context, see how this plays out for manufacturers, architecture and engineering firms and AI development projects.

What never to do with the interview notes

  • Never copy or describe confidential records to SourceX. Partners share basic fit information only.
  • Never promise payment, a price or a result to the client. Nothing is binding until the company agrees price and terms and signs.
  • Never type or quote reward amounts in client communications; the signed agreement and published terms set the economics.
  • Never mix the credit engagement with the referral in fees or engagement letters.
  • Never raise the topic without the client's permission.

How does a referral from an interview work, and what do rewards look like?

If the depth answers are strong and the owner is open, the steps are short. You share your referral link, or submit basic company details through the referral form. SourceX qualifies the company, the company completes its own data inventory, price and terms are agreed, buyers review, and the deal closes with delivery and payment. Partners earn 25% of the eligible platform fees SourceX actually collects, capped at $100,000 cumulative per referred company, and only after the buyer pays and SourceX receives its fee. No reward is guaranteed. Check your firm's independence policy and your state board first, and read the program terms.

Follow-up timing

Hold the licensing question until the credit study is delivered. Then raise it at the next planning meeting, within a few weeks, while the interview context is fresh. If the owner declines, note it and do not ask again in the same year. The accountants overview and the CAS growth guide explain how this fits a wider advisory practice.

Next step

Add the depth block to your standard interview guide for the next study. When a client scores well and agrees, register as a partner and make the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

How long should a technical credit interview take?

Plan on 30 to 60 minutes per project with the lead engineer, plus a short follow-up with finance. Shorter is fine for a single, well-documented project. The depth block adds about five minutes and needs no file access, so it does not extend the engagement.

Who should be interviewed besides the lead engineer?

Quality or test personnel, a project manager and, where relevant, a finance contact who can tie work to time records. Interviewing more than one person also shows whether decisions were written down or only remembered, which is itself a depth signal for later conversations.

Do interview notes ever go to SourceX?

No. Interview notes are your engagement workpapers. Only basic fit information, such as company name, contact, size, years in operation and system types, goes through a referral, and only after the client agrees. Confidential records are never described or sent by partners.

What if a key engineer has left the company?

Interview whoever remains and look for notes, tickets and review threads that preserve the reasoning. If the history is thin, the credit file may need more support, and the company is unlikely to be a licensing candidate until its records can be recovered and exported.

Can the same questions be used for non-engineering projects?

The structure of hypothesis, uncertainty, experiment and outcome works for most technical projects. Swap in vocabulary for the discipline. Projects without a technical uncertainty, such as routine customization, are a poor fit for the questions, and their records may also be less useful to AI buyers.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment