Questions › Guesstimate › LinkedIn
Estimate infrastructure or operational capacity needed for Company Pages
- Guesstimate
- Easy
- 10 min
Problem Statement Description
Product context: LinkedIn is Microsoft's professional network; its products include profiles, feed, jobs, recruiting, LinkedIn Learning, sales tools, messaging, and ads.
Estimate the infrastructure or operational capacity LinkedIn would need to support Company Pages, with particular attention to recruiter-driven use cases. Company Pages are the public professional identity for organizations on LinkedIn: recruiters and company admins maintain profiles, publish updates, showcase culture, post jobs, review analytics, and engage with followers, while members discover companies through search, feeds, job flows, ads, profiles, and recommendations.
Frame this as a guesstimate rather than a system design proposal. You are expected to define the scope, identify the main capacity drivers, make explicit assumptions, and calculate an order-of-magnitude estimate for the resources needed to keep the experience reliable and useful at LinkedIn scale.
The estimate may include technical infrastructure capacity, such as page views, feed impressions, storage, media handling, search/indexing load, notifications, analytics events, and API traffic, as well as operational capacity, such as page verification, abuse review, support, and content moderation. You do not need exact LinkedIn internal numbers; use reasonable assumptions and sanity checks.
The experience should consider:
- The unit of estimation: Company Pages, active admins/recruiters, member visits, page updates, job-related interactions, analytics events, or support/moderation workload.
- The relevant population: companies with pages, active recruiters/admins, LinkedIn members viewing or following companies, and job seekers interacting with company content.
- Usage frequency: how often pages are viewed, updated, searched, followed, shared, or used in recruiting workflows.
- Traffic patterns: daily average load versus peak events such as hiring campaigns, layoffs, major company announcements, or job posting spikes.
- Infrastructure components: read traffic, write traffic, media storage, search indexing, feed distribution, notifications, analytics logging, and caching.
- Operational components: company identity verification, duplicate page handling, spam/fraud prevention, recruiter/admin support, and policy review.
- Key assumptions and sensitivities: which variables most change the estimate, such as active company count, page-view frequency, media-heavy content, or recruiter adoption.
- Sanity checks: compare the estimate against plausible LinkedIn-scale member activity, B2B product usage, and professional network behavior.
Your goal is to produce a clear, defensible capacity estimate with transparent assumptions, logical segmentation, and enough sensitivity analysis to show which drivers matter most for LinkedIn Company Pages.
What this question tests
- Structured Estimation
- Numeracy
- Assumption Quality
- Sanity Checks
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Guesstimate questions
- Estimate the annual market size for Messaging among hiring managersLinkedIn · Guesstimate · Easy
- Estimate daily active usage of Jobs in a priority marketLinkedIn · Guesstimate · Easy
- Estimate how many creators could adopt Sales Navigator in one yearLinkedIn · Guesstimate · Easy
- Estimate the revenue opportunity if LinkedIn improves conversion in Creator ModeLinkedIn · Guesstimate · Easy
- Estimate the revenue opportunity if LinkedIn improves conversion in Creator Mode at global scaleLinkedIn · Guesstimate · Hard
- Estimate the annual market size for Feed among hiring managers at global scaleLinkedIn · Guesstimate · Hard
All Guesstimate questions · Product manager interview questions by skill area