PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/Data Manipulation (SQL/Python)/LinkedIn

Compute each member’s current notification status

Last updated: Mar 29, 2026

Quick Overview

This question evaluates temporal data handling, record consolidation, and merging of baseline and event-driven records using SQL/Python to determine current entity state from historical actions.

  • easy
  • LinkedIn
  • Data Manipulation (SQL/Python)
  • Data Scientist

Compute each member’s current notification status

Company: LinkedIn

Role: Data Scientist

Category: Data Manipulation (SQL/Python)

Difficulty: easy

Interview Round: Technical Screen

You have two tables describing LinkedIn members’ push notification settings. ### Tables `status` — each member’s **latest setting as of 2020-01-31** - `member_id` INT (PK) - `status` VARCHAR — values: `'on'` or `'off'` `actions` — all setting change actions during **Feb 2020** - `member_id` INT - `date_sk` DATE - `action` VARCHAR — values: `'turn_on'` or `'turn_off'` Assumptions: - A member performs **at most one action per day**. - `actions` may include **new members not present** in `status` (e.g., a member created after 2020-01-31). ### Task Return each member’s **current notification status as of 2020-02-29**. - Include **all members who appear in either table**. - If a member has at least one action in Feb, their status is determined by their **latest action** in Feb. - If a member has no Feb action, their status remains their `status` value from 2020-01-31. Output: - `member_id` - `current_status` ### Follow-up How would you handle it if the `actions` table did **not** have `date_sk` (i.e., you had no reliable way to order actions)? Specify what additional data/assumptions are required to make the problem solvable.

Quick Answer: This question evaluates temporal data handling, record consolidation, and merging of baseline and event-driven records using SQL/Python to determine current entity state from historical actions.

Related Interview Questions

  • Write SQL for rankings, state, and aggregations - LinkedIn (easy)
  • Analyze member video posting behavior by country - LinkedIn (easy)
  • Compute article-type diversity per user and histogram - LinkedIn (easy)
  • Find top countries by population per continent - LinkedIn (easy)
  • Count Article Types Viewed - LinkedIn (medium)
LinkedIn logo
LinkedIn
Feb 1, 2026, 5:10 AM
Data Scientist
Technical Screen
Data Manipulation (SQL/Python)
4
0

You have two tables describing LinkedIn members’ push notification settings.

Tables

status — each member’s latest setting as of 2020-01-31

  • member_id INT (PK)
  • status VARCHAR — values: 'on' or 'off'

actions — all setting change actions during Feb 2020

  • member_id INT
  • date_sk DATE
  • action VARCHAR — values: 'turn_on' or 'turn_off'

Assumptions:

  • A member performs at most one action per day .
  • actions may include new members not present in status (e.g., a member created after 2020-01-31).

Task

Return each member’s current notification status as of 2020-02-29.

  • Include all members who appear in either table .
  • If a member has at least one action in Feb, their status is determined by their latest action in Feb.
  • If a member has no Feb action, their status remains their status value from 2020-01-31.

Output:

  • member_id
  • current_status

Follow-up

How would you handle it if the actions table did not have date_sk (i.e., you had no reliable way to order actions)? Specify what additional data/assumptions are required to make the problem solvable.

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More Data Manipulation (SQL/Python)•More LinkedIn•More Data Scientist•LinkedIn Data Scientist•LinkedIn Data Manipulation (SQL/Python)•Data Scientist Data Manipulation (SQL/Python)
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.