Sprinklr | Product Engineering Intern | Gurugram | August 2022 [Offer]

This was on campus in IIT. Shortlisting was on basis of OA which had difficulty around Div2B/Div2C. Those who honestly cleared the test were rated around Expert on CF.

Rounds

There were 3 rounds of interviews: 2 Technical, 1 HR.

For technical rounds they allot you either DSA or ML based, by considering your profile/CV. I had DSA, and the interviewer was from backend team.

Round 1

The interviewer first had a short intro then asked how comfortable I was with DSA on a scale of 10. And then proceeded with questions. Just had to explain the approach and algorithm without coding as such. Some were standard questions/puzzles and some were harder versions of well known problems. Also asked basics of DSA and standard algorithms like sorting, dp, shortest path, Dijkstra etc.
To remember a few,

• https://leetcode.com/problems/contains-duplicate/
• https://codeforces.com/problemset/problem/1328/C
• https://leetcode.com/problems/single-number-ii/
• https://leetcode.com/problems/snakes-and-ladders/

Round 2

We had to solve 2 DSA problems in a Pair Programming format, but the platform was Google Meet for discussion and Google Docs for coding. Yes, plain Google Docs without any formatter or highlight, you have to take care of indentation and brackets and syntax yourself and make sure it is correct.
The interviewer started with a basic version of the problem and once you're done they'll extend and change constraints, so your code and approach has to be clean and explainable. The code won't be run, it'll be checked by logic. So if you're with the habit of running to check if it is working or not, it might be difficult.
To remember a few,

• https://leetcode.com/problems/sliding-window-maximum/ (some variation of this)
• https://leetcode.com/problems/linked-list-cycle-ii/
• https://leetcode.com/problems/lru-cache/

Round 3

This was the HR round. If you've made it till here you're almost in! The HR will first generally ask you about yourself, family hobbies etc. You can try to include stuff written in your CV for intro too.

• After that they'll ask some behavourial questions like your experience working in teams, or what do your teammates think about you.
• How has been your college life, and why you want to pick SDE out of all other career options
• What do you think of the work-life balance, as in WFH vs Office, flexible hours or 9-5 etc.
• Your dream company, apart from Sprinklr
• What do you think Sprinklr does? (I think the answer is supposed to be part of the PPT, otherwise do some research and tell what you find. Just make sure not to give a canned response)
• Which stack do you prefer, among
  • Backend (Java Spring with Mongo/Redis etc)
  • Frontend (JS/TS/React)
  • Mobile Dev (JS/React Native)
  • Machine Learning (Python)

There are supposed to be no wrong answers as such, so just be calm and just don't mess up

General Advice

• Eat well and sleep well before the interview. Try not to be sick. I remember having a really really bad cough throughout my round 1, had to take a break for a minute and ask for water.
• Dress formally and comfortably. If you're not comfortable with suit-tie just wear a proper shirt and pants/jeans.
• Be calm and attentive throughout the interview. Each minute of you should be fresh. The mental state you're in in this minute should not depend on what happened in the previous minutes. This applies to both getting excited or getting demotivated during the interview. Also there would probably more interviews scheduled on the same day, so you have to try to keep yourself mentally isolated and fresh for each.
• Remember, this is an interview not an audition. It is all about seeing the match between what they want and what you know. Think of the interviewer as a friend/future boss who wants to work with you too, not a judge in a talent show.
• Communication is key. Try to be geniune and don't fake anything. If you don't know something, tell them why, if you know something you can even tell them where you studied it. If you're not sure, try for a while - tell what you thought and ask if you should continue in this direction.
• Explaining your solution is more important than solving the problem. You need to be able to properly convey what you thought, and give both a high level and line-wise explaination of your solution. Ask the interviewer if they want a high level approach (as in Why you would do this), or a line-wise (how you would do this)