Stack Builders logo

Stack Builders Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Stack Builders.

Showing 3 of 12
Stack Builders logo
Stack Builders

Software Developer

Engineering

Entry Average Negative experience No offer 7 rounds
Interview process
Recruiter call Technical screen Phone screen Onsite Technical screen Onsite Background check
Interview formats
Technical Coding Behavioral

I applied online and got an email for a technical assignment and to send my CV and Github. After a positive response, I had a phone screening with the recruiter to talk about cultural alignment, salary, and past experience. Then I had a second interview, focused on technical skills, where we reviewed my assignment and discussed Javascript, functional programming, object oriented design, and SOLID principles. After that, I was told the process was almost done. A couple days later, they scheduled a third interview with a senior developer for another technical assessment. This felt like an extra step, but I proceeded. After this, the recruiter mentioned it was the final step. A few days later, she called to say an Office Manager wanted to talk to me and they needed 3 professional references. This contradicted previous conversations, so I emailed for clarification. She insisted on the references, acting like she never said anything else. I started to doubt their intentions, especially asking for references so late and having an unscheduled interview. I called her, and she said they needed to talk to my references to ensure cultural alignment and interest, which seemed strange after multiple interviews and a code exercise. I decided to withdraw from the process, and they responded dismissively.

Confirmed questions3 questions
  • What is your knowledge of Haskell?
  • Could you explain the SOLID principles?
  • What can you tell us about strict typing?
Stack Builders logo
Stack Builders

Software Engineer Intern

Engineering

Intern Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Take home Phone screen Technical screen Technical screen
Interview formats
Technical Behavioral Technical

It's a bit of a long process. It starts with a phone call, then there's a take-home exercise that takes two days. After that, there's an interview with HR, followed by an easy theoretical interview, and then a more in-depth technical interview.

Confirmed questions4 questions
  • Can you list at least four HTTP methods?
  • What aspects of our company appeal to you?
  • What are your expectations regarding what our company should offer you?
Stack Builders logo
Stack Builders

Senior Software Engineer

Engineering

Senior Average Positive experience Accept offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Technical

Had a great chat with HR, they were super nice and gave me a lot of info. They asked about my skills and told me about the client I'd be working with as a consultant. It was also a good chance for me to ask questions about the tech stack.

Confirmed questions2 questions
  • Are you experienced with the required technology stack?
  • Have you worked on similar projects before?

Stack Builders Software Engineer Interview Questions

Quoted word for word from Stack Builders interview reports.

Solve an online coding challenge using a recursive algorithm.

Read reports

What are the best practices in object oriented programming?

Read reports

How would you build a web crawler using scraping techniques and implement filtering operations?

Read report

How important is Network Architecture in software development?

Read report

Do you know about encryption methods or libraries for them?

Read report

Formats, difficulty and experience

Across all 12 Stack Builders interview reports.

Interview formats

Technical 40.7%
Behavioral 29.6%
Coding 29.6%

Interview difficulty

Easy 16.7%
Average 58.3%
Difficult 25%

Candidate experience

Positive 50%
Negative 41.7%
Neutral 8.3%