Verint software engineer candidates describe an HR or recruiter screen, technical conversations, basic coding and system design. Draws on three reports: one offer and two no-offer outcomes.
$118K
Avg. Base Comp
$135K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Three candidates describe Verint interviews at different levels, so the reports shouldn't be read as one fixed loop. The most detailed comes from a software engineer who reached an offer after four rounds: an HR screening call, a hiring manager conversation, a coding round with a tech lead, and a final round with the software engineering director.
In that account, the coding round was basic. The candidate chose JavaScript and was asked to reverse a string, check for a palindrome and implement a closure, and the tech lead cared about how they explained their approach. The URL shortener system design question came in the director round and was called the hardest part, touching on scalability, storage, collision handling and trade-offs.
A senior software engineer who did not receive an offer described a more backend-oriented process over two rounds. It covered Spring Boot, the equals and hashCode contract, how HashMap works internally, building a simple hash map, and REST versus SOAP or GraphQL. The second round reportedly added an Instagram-style application design with a reels API, REST scaling and basic SQL injection questions.
An intern got through a smooth recruiter screen, sent availability for the next round, and then never heard back despite following up for weeks. If you are applying, brush up on fundamentals in your strongest language, practice talking through design trade-offs aloud, and follow up politely if scheduling stalls.
Synthesized from 4 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 Verint process.
I had a promising start with my recruiter phone screen, which went smoothly enough that HR reached out to schedule the next round. I sent over my availability right away, but then... silence. I followed up multiple times over the next few weeks, but never heard back. It's tough because I genuinely don't know what happened—whether they found someone else, decided to move in a different direction, or just dropped the ball on communication. If the answer was no, I would've preferred they just say so. Getting ghosted after doing well in the first conversation felt frustrating and honestly unprofessional. It left me wondering what I could've done differently, even though intellectually I know sometimes these things are just about timing and how many candidates they're juggling.
Prep tip from this candidate
If you pass the recruiter screen, don't assume momentum—follow up proactively after a week and set clear expectations about timeline and next steps. Verint's process involves multiple HR touchpoints, so nail your initial phone screen and be prepared to demonstrate genuine interest in the company culture during behavioral rounds.
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 Verint
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records | |
| Prime to N | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Top 3 Users | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| First Touch Attribution | |
| Job Recommendation | |
| Over 100 Dollars | |
| Minimum Change | |
| Find the Missing Number | |
| Recurring Character |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial contact with HR or a recruiter. The software engineer who got an offer described a non-technical call about background, motivation and role expectations. The intern said the screen went well but scheduling then stalled, so following up is worthwhile if you hear nothing.
The software engineer who received an offer described a conversational round with the hiring manager about previous projects and technical experience, without live coding. The senior candidate instead reported a technical conversation early on, so the depth of this stage may vary by level.
In the offer report, the tech lead let the candidate pick a language (JavaScript) and asked for a string reversal, a palindrome check and a closure, valuing the explanation of the approach. The senior candidate reported Spring Boot, the equals and hashCode contract, HashMap internals, building a hash map and REST versus SOAP or GraphQL.
The software engineer who got an offer reported a final round with the engineering director, starting with personal questions and then a URL shortener design. The senior candidate reported an Instagram-style application and reels API design, REST scaling and basic SQL injection questions in a second round.
