How can an engineer contribute to UX research with limited user access?

WHAT THIS TESTS: This question probes whether you view product discovery as a shared team responsibility or as a siloed UX function. Senior engineers are expected to close context gaps proactively, especially in B2B, healthcare, or other specialized domains where recruiting is expensive and slow. The interviewer wants to see resourcefulness, systems thinking, and cross-functional fluency, not just a willingness to sit in on a usability session.

A GOOD ANSWER COVERS: First, using engineering artifacts as proxy data, such as parsing application logs, support tickets, or error traces to reconstruct user workflows and pain points. Second, building lightweight research instruments, like rapid prototypes, fake-door tests, or in-app micro-surveys that generate behavioral signals without requiring full interview panels. Third, tapping into internal expertise by partnering with sales engineers, solutions architects, or support staff who speak the user's language and can facilitate warm introductions or contextual inquiry. Fourth, instrumenting analytics and funnel tracking so the team can quantify friction points and prioritize research questions before speaking to users. Fifth, offering to attend or shadow sessions when they do happen, and helping the researcher translate technical constraints into discussion guides.

COMMON WRONG ANSWERS: A red flag is saying the engineer should stay in their lane and wait for the researcher to deliver insights. Another weak pattern is suggesting you build the feature anyway and hope to iterate later, which ignores the premise of limited access. Proposing to interview random friends or generic users instead of seeking domain-relevant proxies also signals poor judgment.

LIKELY FOLLOW-UPS: The interviewer might ask how you would validate a hypothesis if you could only reach five users a quarter, or how you would balance research participation with sprint commitments. They may also probe whether you have ever instrumented telemetry that changed a product decision, or how you would handle a sales team that gatekeeps customer access.

ONE CONCRETE EXAMPLE: Suppose you are building an electronic health record integration for oncologists. Instead of waiting six months to recruit clinicians, you shadow your company's customer support team for two days, categorize the top ten integration errors from logs, and build a clickable prototype of a redesigned auth flow. You then ask the support lead to walk through it with one friendly clinic admin, recording the session for the UX researcher. This generates actionable feedback in two weeks rather than two months.

Source: dscout.com