Katkat

Company

StackAdapt interview questions

10 practice questions in the style of StackAdapt's interviews, covering Coding & Algorithms, Statistics & Math, Software Engineering Fundamentals, Machine Learning.

Questions10

5 easy5 medium0 hard

Your progress0/10

StackAdapt interview questions by the numbers

Last updated

Katkat has 10 StackAdapt interview questions. The largest topics are Coding & Algorithms (40%), Statistics & Math (40%) and Machine Learning (10%). By difficulty: 50% easy and 50% medium. The most common round is Onsite (40%). Frequent concepts include ad-tech, Algorithms, Data Streams and geometric-distribution.

Difficulty

  • Easy50% · 5
  • Medium50% · 5

Interview rounds

  • Onsite40% · 4
  • Technical Screen40% · 4
  • HR Screen20% · 2

Roles

  • Machine Learning Engineer60% · 6
  • Software Engineer40% · 4

Frequent concepts

  • ad-tech10% · 1
  • Algorithms10% · 1
  • Data Streams10% · 1
  • geometric-distribution10% · 1
  • Heaps10% · 1
  • math-derivation10% · 1

Showing 1–10 of 10 results

  • This question evaluates understanding of dictionary/hash table performance characteristics, covering hashing, collision-resolution strategies, load factor and resizing impacts, and the cost of iterating or copying keys into a dynamic-array-backed list within the Coding & Algorithms/data structures domain.

    StackAdaptSoftware EngineerCoding & AlgorithmsHR Screen
  • This question evaluates understanding of conditional probability and independence in simple probabilistic experiments. It belongs to the Statistics & Math domain, is commonly asked to assess foundational probabilistic reasoning used in statistical inference and algorithmic decision-making, and targets conceptual understanding with elementary practical computation.

    StackAdaptSoftware EngineerStatistics & MathHR Screen
  • Classic camel-and-bananas brainteaser: a camel that carries at most 1,000 bananas and eats one per kilometer must move 3,000 bananas to a market 1,000 km away. Find the maximum number that can arrive, testing piecewise cost reasoning, depot planning, and a proof of optimality.

    StackAdaptMachine Learning EngineerStatistics & MathOnsite
  • Design an object-oriented recipe service where nested dishes consume raw inventory and an order either succeeds atomically or changes nothing. The prompt tests typed references, cycle detection, quantity expansion, overflow handling, concurrent stock updates, immutable views, and explicit replacement and query semantics.

    StackAdaptSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's ability to design efficient data structures and algorithms for a time-windowed key-value store, focusing on expiration handling, update semantics, and maintaining aggregate metrics under memory constraints.

    StackAdaptSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Tests derivation and comparison of the expected value and median of a geometric distribution, explaining how right-skewness drives the mean above the median across different parameterizations.

    StackAdaptMachine Learning EngineerStatistics & MathTechnical Screen
  • Review a condensed end-to-end machine learning case study, from its goal and labels through normalization, evaluation, and deployment, and point out what is wrong with it. Tests systematic pipeline review, reasoning about what data each step uses, and ranking problems by how much they undermine the conclusions.

    StackAdaptMachine Learning EngineerMachine LearningOnsite
  • This problem tests your ability to maintain dynamic statistics in a data stream using efficient heap-based data structures.

    StackAdaptMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • Reconstruct a binary tree with distinct values from its preorder and inorder traversals and return it in level-order form with null markers. Tests how the two traversal orders pin down structure, careful index bookkeeping, and efficient handling of deep, skewed trees.

    StackAdaptMachine Learning EngineerCoding & AlgorithmsOnsite
  • Design a one-pass algorithm that keeps a uniform random sample of k items from a stream whose length is unknown in advance, using memory proportional to k. Tests the replacement rule, an inductive proof that every item is kept with equal probability, complexity, and edge cases.

    StackAdaptMachine Learning EngineerStatistics & MathOnsite

StackAdapt interview experiences

All 8 →
  • Stackadapt Software Engineer case study with unstable evaluation standardsStackadapt · Software Engineer · Take-home Project · Jun 2026

    My process started positively, but the final stage was deeply disappointing and left me uneasy about the evaluation standards. I was asked to complete what was presented as a case-study assignment for an enterprise agent solutions developer role. Although it was part of the interview, the work felt close to a real product and architecture project compressed into a short timeline. The most frustra…

  • Stackadapt Software Engineer three technical roundsStackadapt · Software Engineer · HR Screen · Jun 2026

    After a recruiter reached out and invited me to schedule, the process quickly became a sequence of conversations that felt somewhat shuffled compared with what I had been told. I completed an HR screen, then manager and culture-style interviews, followed by three technical rounds. Each technical round combined live coding with a system design prompt. What caught me off guard was that the intervie…

  • An OOP Recipe and Inventory Coding QuestionStackAdapt · Software Engineer · Technical Screen · Apr 2026
    Rejected

    This was more of an OOP-style question, and the problem itself wasn't hard. You're given two concepts. Recipe stores the dish name, how long it takes, and the ingredients it needs. Supply stores ingredients and their inventory counts. A dish can also appear as an ingredient — for example, one dish in Recipe can be used as an ingredient for another dish. Based on this, you implement a series of fu…

  • Stackadapt Software Engineer interview with four rounds and a three-hour sessionStackadapt · Software Engineer · Technical Screen · Mar 2026

    My interview felt intense from the beginning. I went through four rounds back to back, including one session that lasted around three hours. The questions were difficult. The interviewers were kind, but the pace and scope made it hard to give a complete answer. One technical round was especially rough. I had to complete both a LeetCode-style medium problem and a system design prompt within the sa…

  • Stackadapt Account Executive interview: three rounds with clear feedbackStackadapt · Account Executive · Other · Jan 2026

    The interview process felt unusually smooth and respectful to me. The recruiter communicated throughout, and the company’s values came through in how people treated me. I wasn’t ghosted, and the process was clear. I went through three rounds and spoke with five different people. Those conversations helped me learn about the role and how the team worked. Each one felt honest and grounded rather th…

More companies