Sapient Interview Experience for ASDE-1 (Off-Campus 2021)
Interview Experience
Round 1 (Online Coding Round)The first round was an online coding round where I had to solve 2 coding questions. The questions I got were both basic DP-based questions.1. ...
Full Details
Round 1 (Online Coding Round) The first round was an online coding round where I had to solve 2 coding questions. The questions I got were both basic DP-based questions. 1. Based on 0-1 knapsack problem 2. Based on Max Sum Path in a matrix from a given cell in the top row to a given cell in the bottom row. From a cell we could only move down, down left, downRight Round 2 (Domain Interview) This was a technical round that started with the introduction and project explanations. Then Basic CS fundamental questions related to:- CN - OSI Model and its layers OS - Process vs Thread, Multithreading OOP - 1. Encapsulation, Abstraction, Inheritance, and real-world examples of these. 2. Abstract classes and why did we need them when the inheritance was there? Others - What is DevOps, UML Diagrams.
Coding Question - Print all palindromic substrings of a given string SQL Query- A simple group by the query (There is a table with people and places traveled, I had to print the person with max distinct places traveled). At last, the interviewer asked if I had any questions - I asked a few (Always ask questions at the end of the interview) After one and a half hours I got a call for the
next round. Round 3 (Core Values Round) This was a short behavioral round of 25 mins which again started with introduction and project/internship explanations. Then he threw some situation based questions like - 1. If you and your peer have some conflict of thoughts, how have would you react and resolve it. 2. Tell me any real-life experience of yours where you had a conflict with your fellow-mate? How you resolved it? and some other questions which I don't remember exactly... At last, he asked if I had any questions so I asked a few (I remember at last I asked about location preference if selected to which he answered that he would be happy to have me at any location, which kinda gave me some idea that I would be selected : ) After 2 days I got a call from HR that I was selected : ) The only tip I would give is to keep your basics clear and BE CONFIDENT in giving answers, explaining projects and internships. They are looking for confident folks.
About This Question
This is a candidate experience report from a sapient interview for a sre role (intern level) during the phone screen round reported in 2021.
It covers the following topics: Oop, Strings, Dynamic Programming, Sql, Os, Matrix .
Difficulty rating: Easy
More Sapient Interview Questions
About Sapient Interview Reports
This question was reported by a candidate who interviewed at Sapient. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Sapient are the higher-signal extractions to take from this report.
For broader preparation context, the Sapient interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Sapient reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Sapient Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Sapient reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.