InterviewStack.io LogoInterviewStack.io

Data Structures and Complexity Questions

Comprehensive coverage of fundamental data structures, their operations, implementation trade offs, and algorithmic uses. Candidates should know arrays and strings including dynamic array amortized behavior and memory layout differences, linked lists, stacks, queues, hash tables and collision handling, sets, trees including binary search trees and balanced trees, tries, heaps as priority queues, and graph representations such as adjacency lists and adjacency matrices. Understand typical operations and costs for access, insertion, deletion, lookup, and traversal and be able to analyze asymptotic time and auxiliary space complexity using Big O notation including constant, logarithmic, linear, linearithmic, quadratic, and exponential classes as well as average case, worst case, and amortized behaviors. Be able to read code or pseudocode and derive time and space complexity, identify performance bottlenecks, and propose alternative data structures or algorithmic approaches to improve performance. Know common algorithmic patterns that interact with these structures such as traversal strategies, searching and sorting, two pointer and sliding window techniques, divide and conquer, recursion, dynamic programming, greedy methods, and priority processing, and when to combine structures for efficiency for example using a heap with a hash map for index tracking. Implementation focused skills include writing or partially implementing core operations, discussing language specific considerations such as contiguous versus non contiguous memory and pointer or manual memory management when applicable, and explaining space time trade offs and cache or memory behavior. Interview expectations vary by level from selecting and implementing appropriate structures for routine problems at junior levels to optimizing naive solutions, designing custom structures for constraints, and reasoning about amortized, average case, and concurrency implications at senior levels.

HardTechnical
0 practiced
Explain the Count-Min Sketch data structure: layout of the array of counters, update and query pseudocode, error bounds, and how to choose width and depth given memory and desired error epsilon/delta. Discuss application to counting high-frequency metrics in SRE systems and how sketches can be merged across workers.
HardTechnical
0 practiced
A third-party library uses singly linked lists for large in-memory queues and you observe latency spikes. Explain how contiguous memory (arrays) versus non-contiguous memory (linked lists) affects CPU cache behavior, branch prediction, and traversal latency. Propose alternative data structures (chunked arrays, deque, slab allocator) and analyze complexity and trade-offs for SRE workloads.
HardTechnical
0 practiced
Analyze lookup complexity in a typical Distributed Hash Table (for example Kademlia) and explain how node churn affects lookup latency and success probability. Propose data-structure and algorithm-level changes (replication, bucket refresh policies, caching) to improve stability and routing efficiency in a high-churn environment used by SRE tools.
EasyTechnical
0 practiced
Implement a function in Python that detects whether a directed graph (given as an adjacency list) contains a cycle. Use DFS (recursive or iterative) and explain time and space complexity when running this detection on large service graphs in an SRE environment.
HardTechnical
0 practiced
Design an algorithm to compute articulation points and bridges in a large service dependency graph to identify single points of failure. Provide the algorithmic approach, time and space complexity, and explain how you would support incremental updates as the graph changes frequently in an SRE environment.

Unlock Full Question Bank

Get access to hundreds of Data Structures and Complexity interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.