Consent-Based LinkedIn Profile Cards for Webex Meeting Participants

Quick Overview

A technical product question about showing participants' LinkedIn profile information inside Cisco Webex meetings. It tests consent-based identity linking, an architecture for fetching, caching and refreshing profile data, privacy and enterprise admin controls, and how the feature behaves at meeting scale and when things fail.

Consent-Based LinkedIn Profile Cards for Webex Meeting Participants

Company: Cisco

Role: Product Manager

Category: System Design

Difficulty: medium

Interview Round: Other

Design an integration that brings LinkedIn profile information into Cisco Webex, so that people in a meeting can see the professional profiles of the other participants. How would you build it? ```hint Start with whose profile it is Each profile belongs to a LinkedIn member, not to the meeting host or to Cisco. Work out how Webex can know with certainty which LinkedIn member a participant is, and what that person has agreed to share, before you design the panel itself. ``` ### Clarifying Questions - Who decides whether a profile is shown: the participant it belongs to, the meeting host, or the organization's administrator, and can each of them turn it off? - Which meetings matter most: external calls such as sales or recruiting meetings, large internal meetings, or webinars with thousands of attendees? - Which fields belong on the in-meeting card (photo, name, headline, current role and company, a link to the full profile), and how fresh must they be? - What access to LinkedIn data does Cisco have: only what any third-party app can get with a member's consent, or a partnership that grants more? ### What a Strong Answer Covers - The meeting situations where profile context helps and the user problem it solves - How a Webex participant is tied to a LinkedIn member through explicit consent, and why matching by name or email is unsafe - The integration architecture: authorization, profile fetch, storage, caching and refresh, and how cards reach clients during a meeting - Privacy and control: opt-in, revocation, host and enterprise admin settings, guests, data retention and the direction in which data flows - Behavior at scale and under failure, plus metrics for adoption, trust and system health ### Follow-up Questions - A participant unlinks their LinkedIn account in the middle of a meeting. What do the others see, and how fast must the card disappear? - How does the design change for a webinar with thousands of attendees? - A customer's security team wants the feature off for internal meetings but on for external sales calls. How do you support that?

Overview: A technical product question about showing participants' LinkedIn profile information inside Cisco Webex meetings. It tests consent-based identity linking, an architecture for fetching, caching and refreshing profile data, privacy and enterprise admin controls, and how the feature behaves at meeting scale and when things fail.

Cisco logo
Cisco
Nov 17, 2025
mediumProduct ManagerOtherSystem Design
0
0

Design an integration that brings LinkedIn profile information into Cisco Webex, so that people in a meeting can see the professional profiles of the other participants. How would you build it?

Clarifying Questions Guidance

  • Who decides whether a profile is shown: the participant it belongs to, the meeting host, or the organization's administrator, and can each of them turn it off?
  • Which meetings matter most: external calls such as sales or recruiting meetings, large internal meetings, or webinars with thousands of attendees?
  • Which fields belong on the in-meeting card (photo, name, headline, current role and company, a link to the full profile), and how fresh must they be?
  • What access to LinkedIn data does Cisco have: only what any third-party app can get with a member's consent, or a partnership that grants more?

What a Strong Answer Covers Guidance

  • The meeting situations where profile context helps and the user problem it solves
  • How a Webex participant is tied to a LinkedIn member through explicit consent, and why matching by name or email is unsafe
  • The integration architecture: authorization, profile fetch, storage, caching and refresh, and how cards reach clients during a meeting
  • Privacy and control: opt-in, revocation, host and enterprise admin settings, guests, data retention and the direction in which data flows
  • Behavior at scale and under failure, plus metrics for adoption, trust and system health

Follow-up Questions Guidance

  • A participant unlinks their LinkedIn account in the middle of a meeting. What do the others see, and how fast must the card disappear?
  • How does the design change for a webinar with thousands of attendees?
  • A customer's security team wants the feature off for internal meetings but on for external sales calls. How do you support that?