Genesys software engineer interviews vary by team and level. Candidates report recruiter screens, coding and DSA rounds, a puzzle round, resume-driven technical questions, system design and HR conversations.
$115K
Avg. Base Comp
$134K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Genesys software engineering interviews as friendly in tone but uneven in format. One full-time candidate who received an offer reported an online technical test covering operating systems, networks, aptitude and a coding problem. Two coding rounds followed, one easier and one medium-to-hard, then a puzzle-solving round and an HR round. Another candidate reported an easy first coding round (Fibonacci and building a balanced BST from a sorted array). The second round then moved to system architecture, and that candidate did not advance.
Resume depth matters in several reports. An intern candidate said the online assessment's backtracking solution was revisited at length in the next interview. They were also asked about C++ pass-by-reference, linked lists and React, and given an eight-ball weighing puzzle. A test-intern candidate who received an offer described questions tailored to the CV, including JavaScript Observables, with no live coding. A test-engineer candidate was asked to automate at least six Playwright test cases and then discuss unit versus integration testing.
Behavioral questions appear in reports too, including a memorable failure and past internship roles. One candidate had to chase HR for a rejection and never received feedback. Preparation should cover DSA fundamentals, one system design refresher, and a clear account of every project on your resume. Expect the exact mix to depend on the team, and the evidence here is limited to a handful of candidates.
Synthesized from 7 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 Genesys process.
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 Genesys
The task is to write a function that takes a list of integers as input and returns the index at which the sum of the integers to the left of the index is equal to the sum of the integers to the right. If no such index exists, the function should return -1.
| Question | |
|---|---|
| Diagnosing Query Speed Degradation | |
| Decision Tree Evaluation | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Rolling Bank Transactions | |
| String Shift | |
| Top 3 Users | |
| Customer Orders | |
| Raining in Seattle | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String | |
| Minimum Change | |
| Largest Salary by Department | |
| Flight Records | |
| Prime to N | |
| Download Facts | |
| Upsell Transactions | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| First Touch Attribution | |
| P-value to a Layman | |
| Average Quantity | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a friendly recruiter call, in one case about 20 minutes, covering background and role details. Some candidates were asked to introduce themselves and discuss projects. It typically sets up the team conversations that follow.
One full-time candidate reported a non-live test covering operating systems, networks, aptitude, output-based questions and a coding problem. An intern candidate reported aptitude, core CS and a backtracking problem. This step may not apply to every team or level.
Candidates report easy-to-medium coding problems, with one reporting a medium-to-hard second coding round. Reported topics include Fibonacci, balanced BSTs, string subsequences and linked lists. Another candidate was asked about system architecture in a second round, and some interviewers gave hints.
One candidate reported a logic-puzzle round, and an intern candidate got an eight-ball weighing puzzle. A test-engineering candidate completed a Playwright automation exercise and discussed testing concepts. Role-specific content likely depends on the team.
Candidates report behavioral discussion of motivation, working style, past failures and prior experience. Feedback timing varied, and one candidate reported having to chase HR for a decision afterward.
