Five candidate reports across software, full stack, internship and QA roles describe Ness engineering interviews that are largely CV-driven, with technical questions on tools candidates have used. Round counts vary by role and client.
$90K
Avg. Base Comp
$120K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Across five candidate reports, Ness interviews for engineering roles lean conversational and tied to your CV rather than algorithm-heavy. One software engineer candidate had no HR screen and went straight to an engineer who walked through the technologies on their resume: Python, unit testing, Flask, pytest, MongoDB, PostgreSQL, REST APIs, Linux commands, CI/CD and S3. The same candidate faced a scenario question about a duplicate add-to-cart bug found on the last day of regression testing. The interviewer cared about who they would contact and why, not about a single correct answer.
The format varies by role. An internship candidate reported a technical round of about an hour with live SQL, plus JavaScript, database and object-oriented questions, followed by an HR round on behavioral topics. A full stack candidate described a short panel with a product manager, team leader and architect, then a simple written exam on AWS services and basic database code, and ended with a rejection. Another full stack candidate was asked to explain SLO versus SLI and discussed CI/CD and monitoring, and was told they lacked enough experience. A senior automation QA candidate described four rounds, including client-side technical and manager interviews, with Java questions such as interfaces versus abstract classes and HashTable versus ConcurrentHashMap.
In practice, prepare to explain every tool on your resume in depth. Rehearse a production-incident story that shows prioritization and communication. Refresh SQL and core language fundamentals. If the role is placed with a client, you may also need to learn that client's stack.
Synthesized from 5 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 Ness process.
I interviewed at Ness for a software engineering role and went through a structured multi-round process. The first round was a technical interview lasting about an hour, conducted directly with Ness. It covered database concepts, JavaScript, SQL, and object-oriented programming principles. The technical portion included live coding, where I had to write a SQL query to demonstrate my ability to work with databases. The interviewer also asked about my previous projects and professional experience to get a sense of my background. The conversation felt collaborative rather than adversarial — I didn't feel pressured, and the interviewer seemed genuinely interested in understanding how I approached problems. After the technical round passed, there was an HR round that ran close to an hour as well. The HR discussion focused on behavioral and situational questions, including topics like my greatest accomplishment in my career so far and how I'd handled challenges in past roles. The whole experience was surprisingly comfortable; the team was friendly and the process felt well-organized. I walked away feeling like they were trying to assess both technical competence and cultural fit rather than just drilling me on obscure algorithms.
Prep tip from this candidate
Brush up on SQL queries and JavaScript fundamentals, especially around database operations. Be ready to discuss your past projects and accomplishments in concrete terms — they'll ask about your career highlights and how you've tackled real problems.
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 Ness
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Over-Budget Projects | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| First Touch Attribution | |
| Employee Project Budgets | |
| The Brackets Problem | |
| Minimum Change | |
| Real-Time Transaction Streaming | |
| Repeated Category Purchase | |
| Get Top N Frequent Words | |
| SELECTive Wine Connoisseur | |
| Google Maps Improvement | |
| Find Duplicate Numbers in a List |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different openings. One full stack candidate began with an HR screening about background and domain exposure, and another began with a phone call with a product manager. A software engineer candidate reported no HR screen and went directly to a technical conversation. Expect to summarize your experience clearly either way.
Candidates describe a technical conversation anchored in the CV. Reported topics include Python, unit testing, Flask, pytest, databases, REST APIs, Linux, CI/CD and S3 for one candidate. Another reported Java fundamentals, and an internship candidate reported live SQL plus JavaScript and OOP. Depth on your own projects typically matters more than puzzle solving.
One candidate was given a pre-launch bug scenario and asked whom to contact and why. Another had a short panel with a team leader and architect, and a third talked with a local team manager about CI/CD and SLO versus SLI. These conversations seem to test reasoning, communication and reliability concepts, though that is an inference from a few reports.
Later stages differ. One full stack candidate got a simple exam on AWS services and basic database code. A senior QA candidate reported client technical and manager rounds before an HR round on compensation and logistics. An internship candidate had an HR round on behavioral questions. Candidates report outcomes within days to a few weeks, but timing is not consistent.
