Sprinklr | Senior Lead | 5.5 YOE
- Result
- Offer
- Experience
- 5.5 years
- Posted
- 8 Dec 2025
Summary
I interviewed for the Senior Lead Product Engineer role at Sprinklr, which involved four rounds covering coding, technical discussion with system design, low-level design, and HR. I successfully received an offer.
How it went
Round 1 – Coding
I was presented with two Data Structures and Algorithms questions during this round.
Round 2 – Technical Discussion + Design
This round began with a discussion about my current project. Following that, I was given a system design question to tackle.
Round 3 – LLD
In this round, I was asked to design a web crawler with specific requirements, and they expected a working code implementation. The discussion also delved deeper into aspects like parallelizing the crawler, ensuring observability, and robust failure handling.
Round 4 – HR
The final round was a general HR discussion, where we talked about my career journey, my understanding of Sprinklr, and my motivations for wanting to join the company.
Verdict
I was selected for the position.
Questions asked (4)
- 01
Minimum Number of Platforms Required
Data Structures & Algorithms
Given the arrival and departure times of all trains that arrive at a railway station, determine the minimum number of platforms required for the railway station so that no train waits.
- 02
Frog Position After T Seconds
Data Structures & Algorithms
Open the problemGiven an undirected tree of
nnodes labeled from 1 ton, and an integert, a frog starts at node 1. For each second, the frog moves from its current node to a randomly chosen adjacent node. If the frog reaches a leaf node, it stays there. What is the probability that the frog is on a target nodetargetafter exactlytseconds? - 03
Design Live User Count for Streaming Platform
System Design
Design a system to efficiently track and display the live user count for a streaming platform similar to Hotstar.
- 04
Design an Error-Reporting Web Crawler
System Design
Design a web crawler that crawls URLs and outputs URLs which return errors. The expectation included providing working code. Further discussions covered parallelizing this crawler, ensuring observability, and handling various failure scenarios.