Kivi Capital Interview Questions (May 2026)
1 experiences · 1p3a (1)
Top topics
Kivi Capital Quant Researcher Interview Experience Round 1
Interview Experience
I recently interviewed with
Kivi Capital for the
Quant Researcher role. The first round lasted around 60 minutes and consisted of one algorithmic problem followed by several conceptual computer science questions. --- ## Question 1 – Shipment Delivery Optimization You need to deliver
N shipments. For each shipment, you may hire either
Vendor X or
Vendor Y. * Vendor X delivery times: X = [x₁, x₂, …, xₙ] * Vendor Y delivery times: Y = [y₁, y₂, …, yₙ]
Constraints: *
Vendor X processes shipments sequentially → total time = sum of delivery times assigned to X *
Vendor Y processes shipments in parallel → total time = maximum delivery time among shipments assigned to Y Goal: Minimize the total completion time for delivering all shipments. Let: * Shipments assigned to X → indices (i₁, i₂, …) * Shipments assigned to Y → indices (j₁, j₂, …) Then: * Time taken by X = sum(x[i₁], x[i₂], …) = t₁ * Time taken by Y = max(y[j₁], y[j₂], …) = t₂ Total completion time: max(t₁, t₂) ---
Approach 1. If xᵢ > yᵢ, assigning that shipment to
Vendor Y is always beneficial since Y completes it faster. 2. For cases where xᵢ < yᵢ, the choice is non-trivial because: * Assigning to X increases the sequential sum * Assigning to Y increases the maximum parallel time 3. For such shipments, create pairs (yᵢ, xᵢ) and sort them by yᵢ. 4. Consider partition points in this sorted list: * Shipments up to index k are assigned to Vendor Y * Remaining shipments are assigned to Vendor X 5. Compute: * Vendor Y time = yₖ * Vendor X time = suffix sum of x-values after k 6. Track the minimum value of: max(yₖ, suffix_sum_x)
Time complexity:
O(N log N) due to sorting. --- ## Conceptual / CS Questions Asked After the algorithmic question, the interviewer asked several conceptual questions: * Difference between
Multithreading and Multiprocessing * What is a
Semaphore? * What is a
Mutex Lock? * Difference between
Semaphore and Mutex * Why do we need
Multithreading if we have Async/Await? (use cases) * Difference between
Virtual Memory and Physical Memory * What is a
Page Table?
Topics
Kivi Capital Interview Process Overview
The Kivi Capital interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show Kivi Capital runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Kivi Capital coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use Kivi Capital Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Kivi Capital updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in Kivi Capital reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Kivi Capital's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common Kivi Capital Interview Mistakes
Reports tagged "no hire" at Kivi Capital consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.