Research Collaboration and Stakeholder Management Questions
Working across teams and the wider community: partnering with engineers, product, and academic collaborators, engaging stakeholders, prioritizing competing requests and hypotheses, and securing resources and support. Covers negotiating scope and timelines, keeping expectations calibrated through negative or inconclusive results, agreeing who owns what at handoffs, setting terms for joint work with outside labs, and re-planning or deciding when good enough is enough when competing work lands. Interviewers look for researchers who create leverage through collaboration rather than working in isolation. Excludes generic prioritization frameworks, stakeholder mapping on delivery projects, earning credibility with skeptical audiences, setting research-organization strategy, the mechanics of shipping a research prototype, and user-research study design.
You have five plausible research hypotheses and bandwidth for two. How do you decide which to pursue first, and how would you defend that call to a skeptical product partner?
Sample Answer
Direct answer
I would score the five hypotheses on the same few questions, pick the best two that fit the capacity, and show the scoring to the product partner so they can challenge the inputs rather than the conclusion. The questions are: how much value if it works, how likely it is to work, how much it costs, and what we learn even if it fails. I say what would change my pick.
Structured elaboration
- Write each hypothesis as a testable claim with the metric it should move and the cheapest test that could prove it wrong.
- Estimate value (if true), probability, and cost with the partner in the room for value, and engineers and peers for cost. Probabilities are rough guesses; the point is that they are written down and arguable.
- Compute expected value (value times probability) and compare with cost. A high-upside idea with a low chance can lose to a modest, likely one.
- Check dependencies and learning. If one hypothesis unlocks the data or tooling the others need, or a failure would still teach us something, adjust.
- Pick two and park three with explicit revisit conditions.
Worked example (illustrative scores)
Value is in arbitrary "value points" agreed with the product partner, cost is researcher-weeks, and the capacity is 8 weeks.
| Hypothesis | Value if it works | Probability | Expected value | Cost (weeks) |
|---|---|---|---|---|
| A | 8 | 0.50 | 4.0 | 3 |
| B | 10 | 0.25 | 2.5 | 5 |
| C | 4 | 0.60 | 2.4 | 2 |
| D | 9 | 0.30 | 2.7 | 6 |
| E | 6 | 0.50 | 3.0 | 4 |
The best pair that fits 8 weeks is A and E: expected value 4.0 + 3.0 = 7.0 for 3 + 4 = 7 weeks. The next best pair, A and D, gives 6.7 but needs 9 weeks and does not fit.
Defending it to a skeptical partner: B has the largest upside (10), and the partner will notice. My answer: at a 0.25 chance, its expected value is 2.5, below E at 3.0. Then I invite them to challenge the input. If they have evidence that B's probability is 0.4, its expected value becomes 4.0, and A plus B (4.0 + 4.0 = 8.0, cost 3 + 5 = 8 weeks) beats A plus E. I would happily change my pick on that evidence, and I would ask what that evidence is.
Trade-offs and pitfalls
- The numbers are structured guesses, not facts. Present them that way and the debate moves to the inputs, which is where it belongs.
- Do not hide the parked ideas; state when they would come back (new data, a failed first pick).
- Avoid picking by whichever stakeholder is loudest or by what is most intellectually exciting.
Product hands you a goal: lift 30-day retention by 5%. How do you turn that into a research scope you can commit to, and who do you need in the room to do it?
Sample Answer
Direct answer
I would not accept "lift 30-day retention by 5%" as a research scope until it is pinned down. I would sit with product, data and engineering to define the metric, the baseline, the population (which users the goal covers), the lever, and how we will measure success, then translate the goal into a scoped set of hypotheses and a commitment on what research can deliver by when. I would commit to the experiments and learning, and negotiate the outcome target separately.
Structured elaboration
- Clarify the goal. "5%" can mean different things. 30-day retention here means the share of new users who are still active 30 days after signing up. Ask: is the lift relative or absolute, which user group, which time window, and what is the current baseline?
- Check detectability. Detectability means whether a test can reliably tell a real lift from random noise. Can we even see an effect of that size with the traffic we have?
- Find the levers. A lever is something we can change that plausibly moves the metric. Break retention into where users drop off and which of those a model can influence (recommendations, notifications, onboarding), then pick hypotheses.
- Define what research commits to: a measured test of the top hypotheses by a date, not a guaranteed lift.
- Agree what "done" means and who acts on a success.
Worked example (illustrative numbers)
Say baseline 30-day retention is 40%. A 5% relative lift means 40% x 1.05 = 42%, a 2-point change. A 5-point absolute lift means 45%. The second is far harder. Which one product means changes the scope entirely.
The number also drives feasibility. Two terms first. Power of 80% means that if the lift is real, the test will detect it 80% of the time. 5% two-sided significance means we accept a 5% chance of calling a lift real when it is only noise. With those settings, the users needed per group (control and treatment) are:
n per group = (1.96 + 0.84)^2 x [p1(1-p1) + p2(1-p2)] / (p2 - p1)^2
Here 1.96 and 0.84 are the standard constants for 5% two-sided significance and 80% power, and p1, p2 are the two retention rates. The intuition: the smaller the gap, the more users you need, and the need grows with the square of how small the gap is.
- 40% versus 42%: (2.80)^2 = 7.84 (7.85 if the constants are left unrounded, the value used below). The spread term is 0.40 x 0.60 + 0.42 x 0.58 = 0.2400 + 0.2436 = 0.4836. The gap squared is 0.02^2 = 0.0004. So n = 7.85 x 0.4836 / 0.0004, about 9,500 per group, roughly 19,000 in total.
- 40% versus 45%: the spread term is 0.2400 + 0.2475 = 0.4875 and the gap squared is 0.05^2 = 0.0025. So n = 7.85 x 0.4875 / 0.0025, about 1,500 per group.
If the product only gets a few thousand new users in a test window, the 2-point lift cannot be detected in one test, and I say so before committing. Retention at day 30 also needs 30 days of follow-up per user, so the test cannot read out until 30 days after the last user enrolls; that waiting time belongs in the commitment too.
Who needs to be in the room
- Product manager: owns the goal, the definition of retention and what the lever could be.
- Data analyst or data scientist: owns the baseline and the metric pipeline.
- Engineers: own what can ship and the cost of the lever.
- Experimentation owner: owns test design and traffic allocation.
- Design or growth if onboarding or messaging is a lever.
Trade-offs and pitfalls
- Committing to the outcome lets luck decide whether the quarter was a success; commit to learning and a decision.
- A vague goal lets every stakeholder hear their own meaning of success.
- Check that the metric cannot be moved by something that harms the product, such as aggressive notifications. Add a guardrail.
What do you do early in research planning to make sure the product and engineering partners will actually adopt the result? Give an example where this changed what you built or how you defined done.
Sample Answer
Direct answer
Early in planning I define "adopted" with the partners who will have to use the result, before I choose methods. I ask them what they would need to see to put it into production, what constraints it has to fit, and who will own it afterward. Then I design to those answers. That conversation changes what gets built and gives the project a definition of done that includes the partners' needs, not only a model score.
Structured elaboration
Questions I ask in the first weeks:
- Decision and owner: what decision will this inform, and who owns the system afterward?
- Constraints: latency, cost per request, interpretability, data availability at serving time, review requirements.
- Evidence bar: what result would convince you to ship, and what would convince you not to?
- Integration: what format and interfaces do you need, and who will review them?
- Checkpoints: when do we look at an early version together?
I turn the answers into a short written definition of done shared by everyone.
Worked example (a story to adapt)
I was asked to improve a classifier that flags risky transactions. My plan was to maximize offline accuracy. In the first meeting the engineering lead told me the serving system (the live software that runs the model on each request) had a strict response-time budget (the maximum latency, meaning wait time per request, it allows; here 50 ms) and could not call the heavy features I intended to use, and the operations team said reviewers would only trust alerts that came with a reason (interpretability: a human-readable explanation of why each alert fired).
- I redefined done as: beats the current rules on the agreed review-precision measure (of the alerts the system raises, the share later confirmed as truly risky by investigators; the rules scored 55%), fits the 50 ms response-time budget, and gives a short reason code (a label such as "amount far above this account's usual") per alert.
- I dropped the most expensive features and built a smaller model, plus a simple explanation field.
- I shared an early version with the operations team after four weeks and changed the reason wording based on their feedback.
The offline score (review precision replayed on saved historical transactions with their confirmed outcomes, the agreed measure; it cannot show whether reviewers would trust the reason codes, so it is re-checked live in the reviewers' queue after launch) was somewhat lower than the bigger model's would have been (illustrative numbers: 62% review precision for the small model versus 66% for the big one, and about 35 ms versus 120 ms per request, so only the small model fit the 50 ms budget), and the engineers shipped it within one planning cycle because it already met their constraints. Had I built the larger model first, the likely result was a strong score that could not be deployed.
What changed in what I built: feature set, model size and an output the reviewers could use. What changed in done: from a score to a score, a latency fit and a reason code.
Trade-offs and pitfalls
- Asking partners for requirements is not enough; ask what would make them say no.
- Constraints discovered late are the usual reason strong research never ships.
- Keep room for the research question: partners can constrain the solution without defining the science.
You are negotiating a joint research agreement with a university lab that wants to publish freely, while the company needs some control over IP and timing. What are the points you would fight for, where would you give ground, and why?
Sample Answer
Direct answer
I would treat this as a trade, not a fight over principle. The university needs to publish and keep its students free to graduate. The company needs to protect confidential material, file patents before disclosure, and be able to use what it paid for. I would fight for (1) a bounded publication review process, (2) clear ownership and licence terms (covering both what each side brings in and what is created), and (3) protection of the company's confidential data and models. I would give ground on the right to publish, authorship by contribution, and student thesis freedom. I would involve the company's legal team and the university's technology transfer office (the office that handles its IP deals) early, because I am a researcher, not the signing authority.
Points to fight for
The four terms below make up the three headline items: publication review, ownership and licensing (background and foreground IP together) and protection of confidential data and models.
- Publication review, not veto. The lab sends drafts to the company a set time before submission. The company may only (a) require removal of the company's confidential information and (b) request a short delay so a patent application can be filed. It cannot block a paper because it dislikes the result.
- Background IP stays with its owner. Background IP means what each side brings in (code, data, pretrained models). The agreement should list what is included and say the other side gets only the licence it needs for the project.
- Foreground IP (new inventions made during the project): a default rule, for example inventions made by one side's staff belong to that side, jointly made ones are jointly owned, and the company gets a licence (written permission to use the invention) or an option (the first right to negotiate such a licence) limited to the field it cares about (its field of use, e.g. fraud detection, not every possible use). Decide this up front, because it is very hard to negotiate after something valuable exists.
- Confidential data and model weights (the trained numbers that make up a model, which can embody trade secrets such as confidential methods or data) the company supplies remain restricted: named people, named systems, no onward sharing, and deletion at the end.
Where I give ground
- The lab keeps the right to publish its results, with credit by contribution.
- Students are never held back from finishing a thesis: any delay has a hard cap (in the example below, 90 days in total, and a thesis can always be submitted and examined on time with the confidential parts handled in a restricted appendix).
- Non-core outputs (evaluation code, benchmarks, general methods) can be released openly.
- The university keeps a non-exclusive right (a right to use that does not stop the company or others from using it too) to use results for its own research and teaching.
Worked example (illustrative terms)
The company proposes a 90-day publication hold. The lab says 0. A workable middle: 30 days for confidentiality review, plus an extension of up to 60 more days only if the company states in writing that it is filing a patent application. Maximum delay: 30 + 60 = 90 days; typical delay: 30 days, and none of it is a veto. Note what the middle ground actually is: the ceiling equals the company's opening 90 days, but the company only reaches it by stating in writing that a patent application is coming, so the typical delay is a third of its ask (30 of 90 days) and the lab's 0 becomes a fixed, predictable 30-day window. In return, the company accepts that if the 30-day window passes in silence, the lab may submit. The company gains time for patents; the lab gets predictable deadlines for conference submissions.
Trade-offs and pitfalls
- A flat "no publication" demand makes the best labs walk away, and the project loses the reason for partnering.
- A fully open deal can leak unprotected inventions. Public disclosure before a patent filing can ruin patent rights in many jurisdictions, which is why the delay clause matters.
- Vague terms ("reasonable review") become disputes. Put days, who approves and what happens on silence into the text.
- What would change my call: if the work is exploratory and unlikely to produce patentable output, I would loosen the delay; if it uses highly sensitive company data, I would tighten data terms rather than publication terms.
Sample wording
Clause (illustrative): "Each party may submit a draft publication to the other at least 30 days before submission. Within those 30 days the reviewing party may require removal of its Confidential Information only. If it states in writing that it intends to file a patent application, submission may be delayed by up to 60 further days. If no written response is given within 30 days, the publishing party may proceed."
Opening line in the negotiation: "We want your project to succeed and your confidential material protected. Can we agree a fixed review window so neither side is surprised?"
Midway through a project, a competing paper appears that undercuts part of your approach. How do you decide whether to pivot, double down or merge ideas, and what evidence would change your mind?
Sample Answer
Direct answer
I would not decide on the day the paper appears. I would spend a short, fixed window (about a week) working out what exactly is undercut, then choose among three moves: pivot (change the question or method), double down (continue because your contribution still stands), or combine (incorporate their idea and keep your distinct piece). My default is combine or narrow when only part of the approach is hit, and pivot only when the core claim is gone and nothing distinctive remains.
How I decide
1. Classify the overlap. "Scooped" (someone publishes your result before you, so yours looks less new; a preprint is a paper posted publicly before peer review) is not one thing:
- Claim overlap: they show the same result you were about to show.
- Method overlap: they use a similar technique on a different problem.
- Counter-evidence: their results suggest your approach does not work, or works only in a narrower regime (a range of conditions, such as small models or one kind of data).
2. Test whether it really applies to you. Read it closely, then check setup differences (data, scale, metrics, baselines, compute). Reproduce their headline number (the single best result in their abstract) on one of your own settings if it is cheap. A competing paper often undercuts less than its abstract claims (a rule of thumb from experience, not a measured rate).
3. Ask what is still yours. Write one sentence for "what would be new after this paper exists". If you can write it, you have something to double down on or merge into.
4. Price the options in remaining time, cost already sunk (ignore it; only future cost matters) and value to the team's goals, not only to a publication.
Worked example (illustrative numbers)
A team is 5 months into a method for making fine-tuning cheaper and has 3 months left. A paper appears showing a similar technique matching full fine-tuning on one benchmark.
| Option | Remaining work | What stays distinctive | Call |
|---|---|---|---|
| Pivot | ~3 months to restart on a new question | Nothing carried over | Only if the core claim is gone |
| Double down | 3 months as planned | Your results on other tasks and a theory section | Fine if their setup is narrow |
| Merge | ~1 month to add their method as a baseline and component | Your analysis of when it fails plus combined method | Best if both ideas complement |
Suppose a one-week check (re-running their released code on your classification data, then on your long-form generation data, with your own baselines) shows their method works on classification but gives no gain on long-form generation, where you already see a gap. Decision: merge. Add their method as a baseline, narrow the claim to generation, and keep the schedule.
Be honest about how strong that week of evidence is. "No gain on long-form generation" from one run per setting could be noise, so run at least 3 seeds (different random starting points) per setting and compare the gap with the seed-to-seed spread: a difference smaller than the spread is "unproven", not "absent". The merge decision is cheap to reverse (about a month of work), which is why a modest amount of evidence is enough to act on, whereas a pivot (about 3 months, nothing carried over) deserves much stronger evidence.
Evidence that changes my mind
- Toward pivot: their result reproduces in your setting and beats yours with no regime where yours is better; a collaborator in the field confirms the community considers the question settled.
- Toward doubling down: your setting is outside their reported conditions, or their result fails to reproduce after you have matched their released configuration and ruled out a bug of your own (otherwise a failed reproduction tells you about your setup, not about their claim).
- Toward merge: ablations (experiments that remove one component at a time to see what each contributes) show their component and yours help in different places.
I would also tell my lead the decision and the evidence within the week, since a reframed project may change commitments.
Trade-offs and pitfalls
- Sunk cost: "we already spent five months" is not evidence.
- Panic pivoting: abandoning too fast wastes unique work; most overlap is partial.
- Ignoring it: reviewers will cite the paper, so not engaging with it weakens the work.
- Contacting the authors can open a collaboration, or lead to both papers citing each other as concurrent work (independent work done at the same time, so neither is treated as copying). Weigh that against revealing your unpublished details. Because concurrent work is commonly acknowledged openly, you can usually continue with a narrower claim instead of abandoning the project.
Unlock Full Question Bank
Get access to all 17 Research Collaboration and Stakeholder Management interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.