Find k closest values in a BST

Quick Overview

This interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Find k closest values in a BST states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Find k closest values in a BST

Company: LinkedIn

Role: Software Engineer

Category: Coding & Algorithms

Difficulty: medium

Interview Round: Technical Screen

Given a binary search tree with n nodes and a real target t, return k node values whose distances to t are smallest. Implement an algorithm with O(log n + k) expected time and O(h) extra space (h is tree height), using predecessor and successor iterators (e.g., two in-order stacks) or a recursive approach. Specify tie-breaking rules, handle k > n and duplicate values, and analyze correctness and complexity. Discuss how you would adapt the solution if the structure were a general binary tree (not a BST).

Quick Answer: This interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Find k closest values in a BST states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Solution

# Solution Alignment The prompt asks for an implementation-level answer. The safest way to present it is to define the state, maintain clear invariants, then walk through complexity and tests. ## Problem Restatement Given a binary search tree with n nodes and a real target t, return k node values whose distances to t are smallest. Implement an algorithm with O(log n + k) expected time and O(h) extra space (h is tree height), using predecessor and successor iterators (e.g., two in-order stacks) or a recursive approach. Specify tie-breaking rules, handle k > n and duplicate values, and analyze correctness and complexity. Discuss how you would adapt the solution if the structure were a general binary tree (not a BST). ## Recommended Approach Choose traversal based on the required output. DFS is natural for subtree computations, reconstruction, and range pruning; BFS is natural for level order or side views. Keep per-depth or per-position state when the output depends on columns, rows, or depths. ## Correctness The implementation should maintain an invariant after each loop or operation that directly matches the problem statement. At termination, that invariant implies the returned value has considered every valid candidate exactly once, or has preserved the required data-structure state after every API call. ## Complexity Most tree traversals are O(n) time and O(h) recursion stack for DFS or O(w) queue space for BFS, where h is height and w is maximum width. ## Edge Cases and Tests Empty tree, one node, skewed tree, duplicate values when reconstruction assumes uniqueness, deep recursion, and tie-breaking for same row/column nodes.
|Home/Coding & Algorithms/LinkedIn
LinkedIn logo
LinkedIn
Aug 10, 2025, 12:00 AM
mediumSoftware EngineerTechnical ScreenCoding & Algorithms
5
0

Find k closest values in a BST

Given a binary search tree with n nodes and a real target t, return k node values whose distances to t are smallest. Implement an algorithm with O(log n + k) expected time and O(h) extra space (h is tree height), using predecessor and successor iterators (e.g., two in-order stacks) or a recursive approach. Specify tie-breaking rules, handle k > n and duplicate values, and analyze correctness and complexity. Discuss how you would adapt the solution if the structure were a general binary tree (not a BST).

Clarifying Questions to Ask Guidance

  • Clarify input sizes, value ranges, mutability, return format, and tie-breaking.
  • State the target time and space complexity before coding.
  • Call out edge cases such as empty inputs, duplicates, invalid values, overflow, and boundary sizes.

What a Strong Answer Covers Guidance

  • A clear algorithm with the right data structures and enough pseudocode or code-level detail to implement it.
  • A correctness argument that explains why the algorithm covers all required cases.
  • Time and space complexity, plus at least one alternative approach when relevant.
  • Focused tests for normal cases, edge cases, and failure modes.

Follow-up Questions Guidance

  • How would the approach change if the input were streaming or too large for memory?
  • What invariants would you assert in production code?
  • Which tests would catch off-by-one, duplicate, or tie-breaking bugs?

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...