Define and measure article trending

Read the full interview experience this question came from →

Quick Overview

This question evaluates a software engineer's competency in analytics and experimentation, covering ranking-system design, signal engineering, data schema requirements, scoring frameworks, and evaluation metrics for article trending.

Define and measure article trending

Company: Figma

Role: Software Engineer

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Onsite

Define what “trending” means for articles and how to measure it. Specify the raw event schema you require (e.g., article_id, user_id, timestamp, action_type, dwell_time, referrer, device, locale). Propose a scoring formula that combines signals (impressions, clicks, dwell time, reactions, reshares) with recency decay, de-duplication, and spam/bot controls. Explain time windows (e.g., 5m, 1h, 24h), baseline normalization (e.g., by author follower count or historical traffic), category/locale segmentation, and cold-start handling. Outline offline evaluation (precision/recall against editorial ground truth, calibration) and online A/B tests, success metrics (CTR, dwell time uplift, save/share rates), and guardrails (session depth, bounce rate, creator fairness).

Overview: This question evaluates a software engineer's competency in analytics and experimentation, covering ranking-system design, signal engineering, data schema requirements, scoring frameworks, and evaluation metrics for article trending.

Read the full Figma Software Engineer interview experience this question came from

Figma logo
Figma
Sep 6, 2025
hardSoftware EngineerOnsiteAnalytics & Experimentation
30
0

Context

You are building a "Trending" ranking for an articles surface (e.g., home feed, explore). Define what “trending” means, what data you need, and how you would score, evaluate, and safely launch it.

Tasks

  1. Definition
    • Define “trending” for articles and how it differs from “popular” or “top”.
  2. Data Requirements
    • Specify the raw event schema you require (e.g., article_id, user_id, timestamp, action_type, dwell_time, referrer, device, locale).
  3. Scoring
    • Propose a scoring formula that combines signals (impressions, clicks, dwell time, reactions, reshares) with:
      • Recency decay
      • De-duplication (e.g., per user/session)
      • Spam/bot controls
  4. Time and Normalization
    • Explain time windows (e.g., 5m, 1h, 24h) and how to baseline-normalize (e.g., by author follower count, historical traffic).
    • Describe category/locale segmentation and cold-start handling for new items.
  5. Evaluation and Launch
    • Outline offline evaluation (e.g., precision/recall against editorial ground truth, calibration).
    • Outline online A/B tests, success metrics (CTR, dwell time uplift, save/share rates), and guardrails (session depth, bounce rate, creator fairness).