Stack Builders logo

Stack Builders Interview Questions
& Process

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

Based on 22 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
45.5% Positive experience

Which role are you interviewing for?

6 roles · 22 reports

Candidate interview experiences

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

Showing 4 of 22
Stack Builders logo
Stack Builders

Senior Python Developer

Engineering · more than a year ago

Senior Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Behavioral Technical Coding

I got an email from HR to set up the first meeting. Then had the first meeting with HR for about 45 min to 1 hour with 2 people from the Stack-builders team. After that, I had a technical interview for 1 hour with lots of Python and REST questions. Finally, I got an email saying I was not selected for the position and they did not provide any feedback. They said they are a leader in the industry. I feel like my time was wasted. In the first interview, they said they were hiring for their own team, not for a client, and the process would be very fast (max 1 week) and they wouldn't waste time.

Confirmed questions2 questions
  • Questions about Python
  • Questions about REST
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

Project Manager/Business Analyst

Product

Mid Average Positive experience No offer 7 rounds
Interview process
Recruiter call Group Take home Technical screen Panel Background check Offer
Interview formats
Behavioral Group Technical Presentation

First, there's a 30-minute phone call with HR. After that, a video interview where you'll meet two Project Managers and another candidate. Then, a Google Form exercise. If you get through those, you'll have a video interview with a senior PM/BA. The final stages include a video interview with the General Manager and another senior PM/BA, followed by a background check with previous supervisors (3 of them). If you pass all of that, you'll then talk with the CEO.

Confirmed questions2 questions
  • What are your expectations for the PM/BA role at Stack Builders?
  • How do you handle receiving feedback?
Stack Builders logo
Stack Builders

Project Coordinator and Business Analyst

Operations

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Background check Offer
Interview formats
Other

The interview process was surprisingly fast. However, throughout the entire experience, the recruiter was unresponsive to my emails. Despite reaching the final stages and investing significant time, including a 6-hour assessment, I was not selected. The rejection was communicated via a generic email with no feedback or explanation. My follow-up request for constructive feedback also went unanswered. Additionally, salary expectations were never discussed during the process.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Stack Builders Interview Questions

Quoted word for word from Stack Builders interview reports.

What are some common Linux commands you'd use to troubleshoot CPU and memory problems?

Read reports

Solve an online coding challenge using a recursive algorithm.

Read reports

What are the best practices in object oriented programming?

Read report

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 22 Stack Builders interview reports.

Interview formats

Technical 36.7%
Behavioral 32.7%
Coding 20.4%
Other 6.1%
Group 2%

Interview difficulty

Easy 9.1%
Average 77.3%
Difficult 13.6%

Candidate experience

Positive 45.5%
Negative 36.4%
Neutral 18.2%

Reports by job function

Engineering 15
Product 3
Operations 2
HR 2