NICE Systems Ltd. Interview Experience(On-Campus)
Interview Experience
Recently, NICE visited my campus with the role of Associate Software Engineer.Eligibility Criteria: Degree in CS/IT, Minimum Grade/Percentage – 60% and above or CGPA 6.5 t...
Full Details
Recently, NICE visited my campus with the role of Associate Software Engineer . Eligibility Criteria: Degree in CS/IT, Minimum Grade/Percentage – 60% and above or CGPA 6.5 throughout the academic career. 120 Students applied. Selection Process: Online Test Technical Interview Managerial Interview HR Interview Online Test: An Online test was conducted on the Interview Mocha “https://www.imocha.io/%E2%80%9D platform. The duration of the test was 100 minutes. There were 7 sections. The test had a negative marking . Quantitative Aptitude (5 MCQ's, 10mins.) Non-verbal ability (5 MCQ's, 10mins.) Software Engineering Fundamentals (8 MCQ's, 10mins.) Testing Knowledge (10 MCQ's, 20 mins.) DBMS (8 MCQ's, 10mins.) Data Structures Round (1 Code, 20 mins.) Calculate the no. of 1's by inverting the elements of an array of size n, which contains bits 0 and 1, by selecting a subarray. Math/String/Array Round (1 Code, 20 mins.) Calculate the Sum of Perfect Squares
Technical Interview Around 40 Students were shortlisted for this round. It had a panel of two interviewers. It had the following Questions: Tell me about yourself? Asked questions about one of my web development projects that was mentioned in my resume. Asked which language am I comfortable with. So I choose JAVA. Following questions were asked: OOPS concepts . Asked my favorite concept and dug deeper about it (In my case: Polymorphism) Gave me a code snippet and asked me for its output (It was moderate) What are JRE, JDK, and JVM? Write a code to Reverse a String (I gave 2 approaches to this problem and coded both of them) Write a code to Find duplicate numbers in an array (Directly gave the optimal approach and coded it) Then, It was the DBMS section. Following questions were asked: What are DDL and DML? What are the types of joins? And explain what is a self join? Query to find the employee who has the maximum salary. Puzzle: Man in the Elevator (The puzzle was quite weird but funny, the interviewer gave a lot of hints) This round lasted about an hour. The panelists were very friendly and gave hints throughout the process. It was more of a discussion than an interview. Managerial Interview: This round was with the Director of Engineering. Following questions were asked: Tell me about yourself? Asked me about my projects mentioned in my resume. What are my future plans? Am I interested in doing masters? Puzzle: 9 coins and 1 odd coin (I had done this previously, so, took a gap and told him my answer, the interviewer wanted to know my thought process) Which field am I interested in? (Data Analytics/AI/Frontend/Backend/Database) This round lasted about 20 mins. The interviewer was very friendly too. HR Interview: It had a panel of two interviewers. Both of them were very friendly. Following questions were asked: Questions on my past Internships and projects mentioned in my resume What technology stack did I use in my projects? Where do I live and other basic questions? The interview lasted about 15-20 mins. Both of them were very friendly too. Finally, they selected 8 students, and I was one of them. The interview process was very efficient and friendly. Important Tips: Be Honest with the interviewer. DO NOT lie in your resume. They ask about each and every project/internship. Let the interviewer know your thought process. (While coding, explain every line) Be Confident about whatever you say. If you don't know the answer, just say NO. Finally, I would love to thank GeeksforGeeks for such lovely content and for helping me throughout my career.
About This Question
This is a candidate experience report from a nice systems interview for a data science role (intern level) during the oa round reported in 2025.
It covers the following topics: Strings, Sql, Stack Queue, Arrays, Stack .
Difficulty rating: Easy
Topics
More Nice Systems Interview Questions
About Nice Systems Interview Reports
This question was reported by a candidate who interviewed at Nice Systems. 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 Nice Systems are the higher-signal extractions to take from this report.
For broader preparation context, the Nice Systems 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 Nice Systems reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Nice Systems 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 Nice Systems 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.