Intellistack logo

Intellistack Software Engineer Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

3.8 Rounds average
Average Typical difficulty
62.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Intellistack.

Showing 3 of 8
Intellistack logo
Intellistack

Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Technical Coding Other

Process was divided into 4 meetings: 1. Screening 30 min 2. Engineering manager 30min 3. Offline coding task 105min 4. Final team interview 60 min. It's been over 2 weeks since final interview without any feedback. I've sent followup email which has been ignored. I've invested over 3.5h into your process, I've waisted a lot of time on your side and you couldn't send an automated email with decline? Im not mad that they hired other candidate, im mad that they could not send short decline email and ghosted my followup after final call. This is totally disrespectful, shame of you.

Confirmed questions3 questions
  • Describe the architectural considerations for the Woven coding task.
  • Discuss the coding implementation for the Woven task.
  • How would you approach the code review for the Woven task?
Intellistack logo
Intellistack

Junior Software Engineer

Engineering · more than a year ago

Entry Easy Negative experience No offer 4 rounds
Interview process
Phone screen Take home Group Technical screen
Interview formats
Coding Group Technical Behavioral

The interview process took over a month and had a few steps. First, there was a phone screen, then a technical take-home assignment where I had to build an app. After that, I had a group interview with some non-technical folks to see if I was a culture fit. Finally, I had an interview with the manager. It felt pretty easy, but it definitely took a while. They liked my app submission and said I was a good cultural fit. They told me it was a hard decision but they went with someone else who had a bit more experience with their specific tech stack. They even offered me a Support Engineer role. Looking back, it's probably a good thing I didn't get the job because they seemed to value specific tech stack experience over problem-solving skills and willingness to learn. I'm now a senior software engineer elsewhere and they saw my potential. It makes me wonder if they truly encourage engineers to innovate or grow.

Confirmed questions2 questions
  • Build a CRUD app.
  • What's your go-to karaoke song?
Intellistack logo
Intellistack

Software Engineer

Engineering · more than a year ago

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

About a week after applying they do a basic phone screen with the office manager, followed up with an "on-the-job project" email. They give you a week to complete a project using the Formstack API. You have to come up with the idea as well as implement it. At the end of the week there's a one-on-one interview with the dev team lead. We didn't hardly discuss the project at all as he was pretty positive about it. After about a week and a half they let me know they wanted to do a final interview. This interview was a group interview in three parts: met with 4 developers for a more technical part, met with three office people for the "culture" interview and finally met with the team lead and a VP. The culture portion was mostly random personality questions. I believe their interview process evaluates real-world skills better than the fact questions that other companies use.

Confirmed questions1 question
  • If you could be any animal, which one would you choose?

Intellistack Software Engineer Interview Questions

Quoted word for word from Intellistack interview reports.

Can you explain what refactoring means in your own words?

Read report

Describe the architectural considerations for the Woven coding task.

Read report

How would you approach the code review for the Woven task?

Read report

Formats, difficulty and experience

Across all 8 Intellistack interview reports.

Interview formats

Technical 34.8%
Behavioral 21.7%
Group 13%
Other 13%
Coding 13%

Interview difficulty

Easy 37.5%
Average 50%
Difficult 12.5%

Candidate experience

Positive 62.5%
Negative 37.5%