Publicis Sapient Software Engineer candidates report DSA screening and technical interviews that may cover Java, system design, React, and detailed resume or project discussion.
$130K
Avg. Base Comp
$155K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Publicis Sapient Software Engineer reports describe technically focused processes, but not one fixed sequence. Candidates reported paths involving online assessments, case studies or assignments, technical interviews, and later manager, HR, client, or system-design discussions. Some candidates described three or four rounds, while another encountered a longer sequence that included multiple technical and client-facing stages.
Prepare to explain both your reasoning and your prior work. Reported coding topics include grouping anagrams, array problems, string modification, and other DSA-style questions. Java-oriented interviews covered OOP, SOLID principles, design patterns, collections, Stream API, multithreading, executors, and framework-specific questions, including discussion of a BDD-to-CI/CD workflow. Candidates also reported detailed questions about current projects, technical challenges, architecture choices, and technologies listed on their resumes.
The technical focus varied by stack. Backend and full-stack reports included Java, Scala, Apache Spark, Kafka, cloud topics, and system design. Front-end candidates encountered JavaScript, React, TypeScript, Webpack, responsive CSS, API integration, and framework optimization. Case-study work could also be substantial: one candidate was asked to build a booking-platform application with an in-memory database. Use the role and your own stack to guide preparation, practice standard coding patterns, and be ready to defend implementation choices in detail.
Synthesized from 8 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Publicis sapient process.
Time and effort waste, that was honestly my first impression by the end of it. I came in through a referral and the process dragged on for months with a lot of back and forth, changing communication, and very little clarity on what was next. The first step was a Codility-style online test, and after that I had a case study round where I had to build a booking platform application and even put together a working model of a booking service with an in-memory DB. That already felt heavier than a normal screening, but it was only the beginning.
After the case study, I went through a technical round that was scheduled for 2 hours but ran a bit over, then another in-person technical round at the Noida office that also went past the planned time. Later there was a client round, which was supposed to be 1 hour, and I was told there would be yet another round after that if I got selected. In the middle of all this, there were also rounds focused on Java fundamentals like OOP, SOLID principles, design patterns, collections, Stream API, and one DSA problem. On the frontend side, I also saw a separate path with a vanilla JS assessment followed by technical rounds on vanilla JS and React JS, including questions on JavaScript design patterns. Another review mentioned a long virtual Java round, a second technical round, an in-office round, and a system design round, so the process clearly leaned very technical and very drawn out.
What stood out most was not the difficulty of any single question, but the sheer number of rounds and the lack of consistency. The interviews themselves were mostly solid technical checks, but the process felt unprofessional and exhausting. I didn’t get an offer, and by the end I felt like the brand value was being stretched way too thin for the amount of time candidates were asked to invest.
Prep tip from this candidate
Be ready for a long process that can include an online assessment, a case study, Java fundamentals, one DSA problem, Stream API, and system design. If you’re interviewing for the frontend track, also drill vanilla JS, React JS, and JavaScript design patterns specifically.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Publicis sapient
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Groups of Anagrams | |
| Descending Alphanumeric Sorting | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Largest Salary by Department | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the Missing Number | |
| Comments Histogram | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Retailer Data Warehouse | |
| Size of Joins | |
| Minimum Change | |
| Upsell Transactions | |
| Lowest Paid | |
| Level Of Rain Water In 2D Terrain |
Synthesized from candidate reports. Individual experiences may vary.
Several Software Engineer reports begin with an online assessment. One candidate reported an online DSA test, while another described MCQs and coding questions. Practice solving familiar problems under time pressure and explaining the approach you choose.
Candidates reported technical conversations that combined resume-based questions with fundamentals. Java topics included OOP, SOLID principles, collections, Stream API, multithreading, executors, and framework choices. Expect follow-up on the technologies and projects you list.
One candidate reported a dedicated DSA interview after the online test and was asked to search a 2D matrix using binary search. Other Software Engineer reports mention array questions and a DSA problem, so rehearse reasoning aloud as well as writing correct code.
A reported three-round process ended with system design, including hashmap internals and a hashing-system design. Other later technical discussions covered Core Java or React component lifecycle. The exact focus can vary with the candidate's background and role track.
