smallcase Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 26 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at smallcase.
smallcase
Software Development Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Behavioral Technical Coding
So the interview had four parts. First up was a quick 5-10 minute call with HR to chat about my background and why I was interested in this job. They also told me what to expect next. Then there was a technical interview covering JavaScript, React, HTML, and CSS, plus some problem-solving. After that, I had a machine coding round where I had to build a frontend feature. Lastly, there was a managerial round to see if I'd be a good fit for the team, talk about past projects, and discuss my career goals. All in all, it went pretty smoothly and felt well-organized.
Confirmed questions8 questions
- How would you run multiple promises at the same time?
- Can you explain the call, apply, and bind methods?
- What distinguishes .then/.catch from async/await?
smallcase
Software Development Engineer Intern
Intern Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding System Design
So the interview process for the SDE Intern (Backend) role back in 2021 was pretty streamlined, took about a week from the HR call to the offer. Applied through the website via referral. After my resume was probably shortlisted, I got a call from HR to set up the interview slots. It was a six-month internship, mostly remote. No coding tests, just two technical rounds. The first one focused on the technical skills I listed and general backend stuff. The second round was more about my resume projects, like how I could extend or change them, which I could answer since I knew my projects well. They were really friendly and helpful, and the questions were more general system design focused, not super specific to one language. So, if you've got a solid foundation in one tech stack, you should be fine. Definitely know your resume inside and out!
Confirmed questions8 questions
- Can you explain event loops in NodeJS?
- What are promises in NodeJS?
- How does async/await work in NodeJS?
smallcase
Software Engineer
Entry Easy Negative experience No offer 4 rounds
Interview process
Technical screen Take home Technical screen Panel Recruiter call Background check
Interview formats
Technical Coding Behavioral
It was a multi-stage interview process. We started with a technical round with basic questions. Then there was an assignment round, which had to be completed within 7 days. This was followed by another technical round focusing on concepts. The final round was with the CTO, which was more of an informal chat about my experience and projects. Honestly, the experience was not great. After I passed all technical rounds, the HR told me I was almost selected, as the last round was a 'cultural round' which is usually a pass for everyone. But then I was rejected, and when I asked for feedback, there was no response, which I feel is a bad corporate culture. It's a startup, so I'm not sure about their culture or benefits, but I've heard negative things. In one of the technical rounds, the interviewer kept interrupting me and didn't let me finish my answers.
Confirmed questions1 question
- Basic questions about APIs and HTTP methods, and how to make service calls
smallcase Software Engineer Interview Questions
Quoted word for word from smallcase interview reports.
“Can you find the subsequence of length 'n' with the largest sum in an array?”
Read reports →“What are the ES6 and non-ES6 ways to make a copy of an array?”
Read reports →“From a given 6-digit number, can you find two pairs that result in the smallest sum when added together?”
Read reports →“What are the common HTTP methods and what is the purpose of each?”
Read reports →“Which operator performs type checking in JS, == or ===? Both operators achieve this within the JS engine; consult the JS documentation for further details.”
Read report →“When looping over an array to return UI elements, why is it important to use a `key`?”
Read report →“What is the difference between HTTP and HTTPS, and can we discuss it?”
Read report →“Build a system that takes stock price changes every second and shows them on a webpage using a line graph.”
Read report →“Could you retrieve stock prices between two dates, aggregated daily, weekly, or monthly?”
Read report →Formats, difficulty and experience
Across all 26 smallcase interview reports.