
Contentstack Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 52 interview experiences · FREE TO READ
Which role are you interviewing for?
20 roles · 52 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Contentstack.
Full Stack Developer
The interview process was pretty good and the difficulty was moderate. It lasted about an hour. I passed the online assessment and the first technical interview, but unfortunately didn't qualify after the second technical interview. Overall, it was a great experience.
- Questions were based on scenarios from your projects
- System design
- DSA
Senior QA Automation Engineer
I interviewed at Contentstack in Bengaluru for a Senior Automation QA position. All the interview stages, which included two technical rounds and one managerial discussion, were finished on the same day. I passed all of them, and they mentioned that the offer would be issued after the HR round the following day. However, after that, communication stopped entirely. Despite trying to follow up multiple times, I heard nothing back. Eventually, after three days, I called the HR department directly. To my shock, I was informed that they would not be moving forward with an offer because of a 'miscommunication' on their part concerning the CTC. It was really unprofessional and disheartening. The HR part seemed immature and badly handled. It's funny how they ask why candidates continue to have multiple offers – this is precisely the reason.
- Can you tell me about how your automation repositories were structured at your previous job?
- What were the testing processes you used at your last company?
Software Engineer
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.
- Can you tackle a random problem with some frequently changing requirements, where no out-of-the-box thinking is really needed?
Sales Engineer
The recruiter reached out about the role saying my background was interesting and asked if I wanted to schedule a call to talk more. But, during the call it was super obvious the recruiter hadn't even looked at my resume or LinkedIn, and didn't know anything about my experience. They even said, "Hmm, I don't know if you are a good fit, but I'll check with the team and get back to you." This was after they reached out to me. I never heard back. It was really rude and unprofessional.
- What makes you want to join Contentstack?
Contentstack Interview Questions
Quoted word for word from Contentstack interview reports.
“Can you check if two strings are anagrams?”
Read reports →“Can you check if a string is a palindrome?”
Read reports →“Could you write pseudocode to check if a string is a palindrome?”
Read reports →“What is the difference between an error and an exception?”
Read reports →“Can you provide pseudocode to determine if two strings are anagrams?”
Read report →“Can you sort an array with less time complexity?”
Read report →“When using TestNG, how can you re-run test cases that failed?”
Read report →“What is virtual DOM and how do bundlers work?”
Read report →“Describe the entire sequence of events when the 'like' button is clicked on Instagram.”
Read report →Formats, difficulty and experience
Across all 52 Contentstack interview reports.