coreweave logo
Coreweave· Weights and Biases role

USA | CoreWeave | Technical Coding Onsite

Location
USA
Posted
30 Jan 2026
434 reads

Summary

I completed a technical coding onsite interview for a Weights and Biases role at CoreWeave, which involved designing and implementing a feature flagging system, followed by discussions on system optimization and scaling.

How it went

Completed technical coding onsite for Weights and Biases role.

Question

You are tasked with creating a feature flagging system

The system consists of channels, with each channel having:

  • a unique ID
  • a mapping of feature flags to boolean values
  • its parents (if any)

A channel can inherit features from other channels:

  • If a feature is defined in a channel, return the value for that feature
  • If a feature is not defined in a channel, it should inherit the value from its closest parent channel
  • If a feature is not defined in any parent channel, it should default to false

Implement the following functions for the feature flagging system:

  • create_channel(channel_id, features, parents)
  • get_feature(channel_id, feature_name)
  • set_feature(channel_id, feature_name, value)
  • delete_channel(channel_id)

Followups

  • Suppose we deploy this system in prod, we don't as much reads as writes. How would you optimize the reads?
  • What happens if you update a feature flag value for a channel. How do you ensure that the lookups work at scale?

Questions asked (3)

  1. 01

    Design and Implement a Feature Flagging System

    System Design

    You are tasked with creating a feature flagging system

    The system consists of channels, with each channel having:

    • a unique ID
    • a mapping of feature flags to boolean values
    • its parents (if any)

    A channel can inherit features from other channels:

    • If a feature is defined in a channel, return the value for that feature
    • If a feature is not defined in a channel, it should inherit the value from its closest parent channel
    • If a feature is not defined in any parent channel, it should default to false

    Implement the following functions for the feature flagging system:

    • create_channel(channel_id, features, parents)
    • get_feature(channel_id, feature_name)
    • set_feature(channel_id, feature_name, value)
    • delete_channel(channel_id)
  2. 02

    Optimize Reads for Feature Flagging System

    System Design

    Suppose we deploy this system in prod, we don't as much reads as writes. How would you optimize the reads?

  3. 03

    Scaling Feature Flag Updates and Lookups

    System Design

    What happens if you update a feature flag value for a channel. How do you ensure that the lookups work at scale?

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Coreweave recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!