Sprinklr Interview Experience | Senior product engineer

sprinklr logo
sprinklr
Senior product engineer
June 15, 20254 reads

Summary

I experienced a two-round interview process for a Senior Product Engineer role at Sprinklr. The first round involved a Data Structures & Algorithms question, which I successfully solved, but I was unfortunately rejected after the second round, which focused on project discussions and system design concepts.

Full Experience

R1:


I was asked a DSA question. Similar to below:

https://leetcode.com/problems/task-scheduler/description/

Was able to solve it. Interviewer was very helping and was moved to next round.

R2:

Interviewer joined 5 min late. Started asking about projects I have done (He didn't even go through resume). Asked which db we use in our projects and why. I explained why we used PostgreSQL (for ACID compliance). Then asked what twitter might have used, I mentioned NoSql for scalability and performance. When asked about handling increased data loads, I suggested sharding as a solution. He asked on what param we should shard I mentioned time_stamps.Querying by user? Suggested composite indexing or hashing. Asked If I have used Message broker and I mentioned I have used ASB.

20 min interview, thats it. Just said thankyou and left the call and rejected. Unfortunately, some interviews are unpredictable, and despite preparation, the experience can feel unproductive due to unclear evaluation criteria.

PS: I received an invite on email for checking my availability just two days before interview. Also, I believe my profile was taken from Naukri, if that helps someone.

Interview Questions (4)

Q1
Task Scheduler
Data Structures & AlgorithmsMedium

I was asked a DSA question similar to LeetCode's Task Scheduler problem.

Q2
Project Discussion and Database Choices
System Design

The interviewer asked about my past projects, specifically inquiring which database we use and why. They then posed a hypothetical question about what database Twitter might use and the reasoning behind it.

Q3
Handling Increased Data Loads and Sharding
System Design

I was asked about strategies for handling increased data loads. When I suggested sharding, the interviewer asked what parameter I would use to shard and how I would handle querying by user.

Q4
Experience with Message Brokers
System Design

The interviewer asked if I had any experience using message brokers.

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!