Stackline logo

Stackline Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 14 interview experiences · FREE TO READ

2.2 Rounds average
Average Typical difficulty
7.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Stackline.

Showing 3 of 14
Stackline logo
Stackline

Software Engineer

Engineering · a year ago

Mid Difficult Neutral experience No offer 4 rounds
Interview process
Recruiter call Take home Phone screen Technical screen
Interview formats
Coding Technical

It was meant to be a multi-stage interview process. This included a take-home assignment, a call with the recruiter, two interviews over Zoom, and then a three-part on-site interview. I only got through the first Zoom interview. I felt like I did well on it, but two days later, I got an email saying I wouldn't be moving on to the next one. I'm not really sure what went wrong or why. It would have been nice to have more transparency, especially since I put a lot of time into the take-home. Also, the recruiter mentioned it would be a Leetcode-style question in TypeScript, but the actual question wasn't like Leetcode at all (I also thought it was strange it had to be in TS). The interview questions themselves weren't that hard, but it feels like a pretty long process for a company that isn't very well-known, especially compared to FAANG or big tech companies. It seems more appropriate for a startup.

Confirmed questions1 question
  • Given a potentially nested data structure (object, array, or primitive) and a target value, can you write a function to determine if the target exists within the structure, returning true or false?
Stackline logo
Stackline

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Technical Coding

First, there was a phone call with a recruiter where we chatted about my background and the company. They also asked about my salary expectations and explained the interview steps. After that, I got an assessment. They said it would take about 2 hours, but honestly, it took way longer, though I did finish it. It was a React.JS and TypeScript task, and they didn't give much time to complete it. Once I submitted the code, I got an email saying they weren't moving forward. I thought there were supposed to be like 6 more rounds, including an in-person onsite, which sounds like a really long process. It wasn't a great experience, and when I asked for feedback, they didn't give any. They got back to me super fast, under a day, which makes me think they barely looked at my code. That felt pretty disrespectful.

Confirmed questions1 question
  • Build a React application with JavaScript or TypeScript that replicates a provided mock image.
Stackline logo
Stackline

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 2 rounds
Interview process
Take home Onsite
Interview formats
Coding Technical

I did a coding assessment first, and then an in-person interview which was pretty tough, with algorithm and design questions. The recruiter was easy to schedule with, and I liked doing the coding assessment on my own time rather than a phone screen during work hours.

Confirmed questions1 question
  • Can you solve a problem by creatively applying data structures?

Stackline Software Engineer Interview Questions

Quoted word for word from Stackline interview reports.

Given a potentially nested data structure (object, array, or primitive) and a target value, can you write a function to determine if the target exists within the structure, returning true or false?

Read reports

Build a React application with JavaScript or TypeScript that replicates a provided mock image.

Read reports

Describe how water flows in a 2D matrix, moving to smaller adjacent cells (not larger ones), and how to determine the tick at which water reaches each cell in a matrix, considering water moves one square in each cardinal direction per tick.

Read reports

Can you create a chart using the provided mock JSON data?

Read report

Can you solve a problem by creatively applying data structures?

Read report

In what ways has your experience with Java been beneficial to you as a programmer?

Read report

What is your experience with different frameworks or tools?

Read report

Formats, difficulty and experience

Across all 14 Stackline interview reports.

Interview formats

Coding 44.8%
Technical 41.4%
Behavioral 13.8%

Interview difficulty

Easy 7.1%
Average 78.6%
Difficult 14.3%

Candidate experience

Negative 64.3%
Neutral 28.6%
Positive 7.1%