Contentstack logo

Contentstack Software Engineer Interview Questions
& Process

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

Based on 20 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Contentstack.

Showing 3 of 20
Contentstack logo
Contentstack

Software Engineer

Engineering · a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Recruiter call
Interview formats
Coding Technical System Design Behavioral

So first there was this online coding test to see if I could solve problems. Then, there were two really tough technical interviews where they really dug into data structures, algorithms, and system design. Each of those had a bunch of coding tasks, some optimization stuff, and questions about how I'd handle real situations. Lastly, I had an HR chat to check if I'd fit in, talk about my career plans, and see how I handle things, plus more behavioral and situational stuff.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Contentstack logo
Contentstack

Software Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Background check
Interview formats
Coding Technical System Design Behavioral

The interview process had 3 technical rounds. The first round involved problem-solving with two interviewers, where one seemed to be passively observing while the other referred to a sheet and asked questions, sometimes repeating previous ones. It was unclear if prior answers were considered. The second round focused on system design, presenting a problem statement for building a system. This was a good discussion point, but I wonder if the interviewer was open to alternative solutions beyond their own, as I presented optimal approaches like using a pub-sub pattern for notifications. It felt like the other engineer wasn't familiar with terms the first interviewer used. The third round was a managerial round to assess fitment.

Confirmed questions1 question
  • Can you tackle a random problem with some frequently changing requirements, where no out-of-the-box thinking is really needed?
Contentstack logo
Contentstack

Applications Developer

Engineering

Mid Average Positive experience Decline offer 2 rounds
Interview process
Technical screen Recruiter call Background check Offer
Interview formats
Technical Coding Behavioral

So, I first got in touch with Contentstack via a recruiter who set up my interviews. The first step was a Technical Round, which lasted about 1.5 hours and was a face-to-face with a Tech lead. They asked stuff about JavaScript, like the event loop, promise, async, and blocking/non-blocking operations, plus some React and Node questions. There was also a screen-sharing part where I had to build an interface for Set. It was a pretty good experience overall. After a week, the recruiter called to say I passed the tech round and they were moving forward. Next up was the HR round, which also went well. They asked general HR questions and we chatted about other things.

Confirmed questions4 questions
  • Regarding JSON.parse, is it blocking or not?
  • Can you explain the asynchronous behavior in JavaScript?
  • What is the Event loop and how does it work?

Contentstack Software Engineer Interview Questions

Quoted word for word from Contentstack interview reports.

Could you write pseudocode to check if a string is a palindrome?

Read reports

Can you provide pseudocode to determine if two strings are anagrams?

Read reports

Describe the entire sequence of events when the 'like' button is clicked on Instagram.

Read report

Can you explain the time complexity of a HashMap and the reasons behind it?

Read report

Formats, difficulty and experience

Across all 20 Contentstack interview reports.

Interview formats

Technical 38.6%
Coding 29.8%
Behavioral 24.6%
System Design 7%

Interview difficulty

Easy 15%
Average 65%
Difficult 20%

Candidate experience

Negative 20%
Positive 60%
Neutral 20%