← Cohere Interview Insights

Cohere·Software Engineer·Hiring Manager Screen·Intermediate

Intermediate
May 2026

Summary

45-minute live session with the hiring manager at Cohere for a data engineer role. The whole thing was a walkthrough of actual work, which felt more like a code review than a traditional interview.

Questions Asked (1)

Q1

You're filling missing values with 0 in your pipeline. Why not just drop those records entirely? And why not leave them as NULL rather than replacing them?

Technical Trade-offsData ModelingRoot Cause Analysis
Author's notes

This one got me more than it should have.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Acknowledge that the choice depends on the data semantics, downstream model requirements, and business context. Explain that dropping records can introduce bias and lose information, while leaving NULLs may break algorithms or metrics that don't handle missing values. Then justify why 0 might be appropriate for certain features (e.g., counts) but caution against it for others (e.g., measurements where 0 is a valid value).

Pro tip: Mention that you would first analyze the missingness pattern (MCAR, MAR, MNAR) and consider imputation strategies beyond zero, such as mean/median or model-based imputation, to avoid introducing bias. Also, note that the decision should be documented and validated with downstream metrics.

1. Clarify the goal

Start by asking what the pipeline is for: is it for training a model, generating reports, or feeding a real-time system? The purpose dictates the acceptable trade-offs.

2. Analyze missingness

Determine why values are missing and whether the missingness is random or systematic. This informs whether dropping or imputing is safe.

3. Evaluate dropping records

Discuss the risks: loss of data, potential bias if missingness is not random, and reduced statistical power. Mention that dropping is only safe if missingness is completely at random and the dataset is large enough.

4. Evaluate leaving NULLs

Explain that NULLs preserve the information that a value is missing, but many algorithms and aggregations cannot handle them directly. They may require special handling or imputation later.

5. Justify filling with 0

Argue that 0 is a valid and meaningful value for some features (e.g., counts, flags), but it can distort distributions and relationships for others. Suggest validating the choice with domain knowledge and experiments.

Key Points to Mention

  • Missing data mechanisms: MCAR, MAR, MNAR
  • Bias introduced by dropping records or imputing with 0
  • Impact on downstream models and metrics
  • Alternative imputation strategies (mean, median, model-based)
  • Domain knowledge to decide if 0 is semantically valid
  • Documentation and validation of the chosen approach

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.