Publicis Sapient Platform Engineer Interview Questions
& Process

I applied for an Associate Level 2 Java position at Sapient. This role requires about 4 years of experience and is pretty much the second-lowest permanent job there. The interview process has three stages: first, a 2-hour initial round, then an in-person interview at Sapient’s office with the same interviewer, and finally a managerial round. They record all interviews and have senior folks review them. If you get hired, you go straight to the bench and have to pass project-specific interviews. The interviewers seem to be evaluated on rejecting candidates to avoid any future blame, so they might pass you to the next stage with negative feedback, leaving the decision to reviewers. This way, the interviewer doesn't get blamed later.

The interview had two main parts: first, a 120-minute coding round where I had to build an application based on a case study, and second, a 145-minute technical discussion and pair programming session. The whole thing was scheduled from 9 AM to 11 AM with a panelist named Mukesh Singh. The JD focused on spring boot, MS, and modern tech. Honestly, the interviewer seemed uninterested. During the pair programming, he actually said, 'Etna time nahi de sakte code mein.' He was also very skeptical, asking very specific questions that required point-to-point answers instead of approach-based ones. He even questioned my knowledge of the 12-factor app for MS, saying, 'You don't know 12 factor app that's why I ask.' Publicis Sapient, working and interviewing are totally different skills. Please ensure your senior developers are punctual and professional when conducting interviews. I feel like I wasted a great opportunity and almost 5 hours in your interview process because of an interviewer like Mukesh Singh.

So basically it was a couple of rounds. The first was a recruiter call, then a technical phone screen. We did a coding question where I had to print 1-100 using threads, and I used atomicInteger for that. Then they asked me about ReentrantLock, effectively immutable, concurrentHashMap, fail-safe vs fail-fast, HashMap internal structure, and what happens if hashcode always returns 1. We also discussed CopyOnWriteArrayList, Liskov substitution, PUT vs POST, converting arrays to lists, UnsupportedException, ExecutionException, CompletableFuture vs ExecutorService, ForkJoinPool, microservice transactions, scope, profilers, extending Throwable, Docker, Kubernetes, ArrayList default size, Happens-Before, HTTP codes, JVM optimization, garbage collection, request flow, Kafka, and ordering.