← Back to Directory

StackAdapt

Mid-sized

Screna has 6 StackAdapt interview write-ups. The most reported round is the technical phone screen (3).

6 interview notes · updated Jun 2026

StackAdapt·Software Engineer·Technical Phone Screen

May 2026
Stackadapt software engineering interview that got into some pretty meaty validation logic design. The coding portion built on domain classes from earlier in the session, which was a nice touch but also meant you were carrying context the whole time.
  • Given two domain classes from earlier in the interview, implement a validation function for each that collects all field errors without stopping at the first one, then discuss how the two validators could share code.

“This one took me a minute to get right.”

View Post

StackAdapt·Software Engineer·Executive / Final Round

Apr 2026
Final round for a Senior BI Engineer role at Stackadapt. Heavy on behavioral and situational questions, all orbiting around the ads industry, messy data problems, and working with non-technical stakeholders. Felt more like a case-study conversation than a traditional interview.
  • Tell me about a time you dealt with inconsistent metric definitions across teams. How did you resolve it?
  • How do you approach a requirements document that's vague or incomplete? Walk me through your process.
  • Describe a situation where you identified a data quality issue that was affecting business decisions. What did you do?
  • How do you explain a complex data problem or finding to a business stakeholder who isn't technical?
  • How do you design a data mart that's ready for reporting and can scale with changing business needs?
  • What's your understanding of how the programmatic advertising industry works, and how does that inform your BI work?

“This is the kind of question that sounds easy until you're mid-answer and realize you're describing a mess you never fully cleaned up.”

View Post

StackAdapt·Software Engineer·Technical Phone Screen

Apr 2026
Stackadapt software engineer interview focused on a pretty involved data structure problem with strict complexity requirements. The follow-up questions about Java internals caught me more off guard than the main problem itself.
  • Design a windowed key-value store where entries expire after a time window W. Implement Put(key, value, timestamp), Get(key, timestamp), and GetAverage(timestamp), with Put and Get guaranteed worst-case O(1), not amortized. ArrayDeque-based solutions are explicitly not accepted.
  • How do you handle hash collisions in your implementation, when do collisions actually occur, and what is the time complexity when collisions happen?
  • How does Java's HashMap handle rebalancing when collisions become frequent?

“The 'worst-case O(1), not amortized' constraint is the whole puzzle here.”

View Post

StackAdapt·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Stackadapt for a software engineering role. The question was a multi-part design problem building on prior validation work, and it got pretty deep into API semantics and concurrency pretty fast.
  • Using two validation functions you wrote earlier, design an update API for two classes. The API should accept an update payload, run the right validation, reject with all error messages if it fails, and apply the update atomically if it passes. Also discuss PATCH vs PUT semantics, optimistic locking for concurrency, and how you'd format error responses.

“This one had a lot of moving pieces.”

View Post

StackAdapt·Software Engineer·Technical Phone Screen

Apr 2026
Stackadapt software engineering interview that focused on graph traversal with a pretty specific real-world twist. The problem wasn't just BFS from a textbook, you had to think about two distinct entity types and how validation propagates across the whole graph including disconnected bits.
  • You have a graph where nodes are instances of two different entity types and edges connect related entities across types. You're given two separate neighbor-fetching functions, one per entity type. Implement a traversal that runs a validation function on every node in the graph. Walk through how you'd handle cycles, disconnected components, and memory constraints for large graphs.

“I started with BFS which felt right, but then got a bit tangled trying to explain the visited set.”

View Post

StackAdapt·Software Engineer·Take-home Assignment

Mar 2026
A take-home case study for a Senior BI Engineer role at Stackadapt, centered on ad spend data analysis in Excel. The bar was higher than I expected: they weren't just checking if you could write formulas, they wanted real business thinking around what the numbers actually mean.
  • Given a dataset of ad spend across multiple markets, analyze the data and produce a structured output covering data quality issues, trend analysis, top and bottom performing markets, assumptions made, and business recommendations.

“This felt like a lot more than a 'do some Excel' exercise.”

View Post