QGenda software engineer candidates report a recruiter or HR screen followed by a HackerRank coding assessment, and sometimes cognitive and personality tests. All five reports here ended without an offer.
$105K
Avg. Base Comp
$135K
Avg. Total Comp
Not reported
Typical Rounds
1 month
Process Length
Across five candidate reports, the HackerRank coding assessment is the stage people mention most, and it is where several of them say the process stalled. Candidates describe an opening recruiter or HR conversation about their background and motivation, followed by an online test. Problem counts and time limits vary by report. One candidate describes three problems in a four-hour window, another a camera-on challenge with 4.5 hours, and a third was told partway through that a fourth problem was required.
Several candidates call the problems academic or competitive-programming style, and some say the statements were long and hard to parse. Practice reading dense prompts and pulling out the requirements before you code. One candidate reports spending about 30 minutes on a single problem just to work out what it asked. Another says the two medium data structure and algorithm questions were the bottleneck.
Some reports also include a timed cognitive test covering verbal, numerical and logical reasoning, plus a personality test. One candidate describes a second, hour-long HR call that went through their full work history and past projects before the hiring manager's review. One candidate reports a final technical interview that ranged across networking and other stacks beyond the C++ role they applied for, though other reports do not mention that stage.
Communication after assessments is a recurring complaint, with candidates describing weeks of silence or a delayed rejection. Treat the process as a time commitment, and keep applying elsewhere in parallel. Prepare for LeetCode-medium algorithms, be ready to walk through your own projects, and confirm the number of problems up front.
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 QGenda 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 QGenda
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Top 5 Turnover Risk | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N | |
| Comments Histogram | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Minimum Change | |
| Find the Missing Number | |
| Find the First Non-Repeating Character in a String | |
| Flight Records | |
| Upsell Transactions | |
| Download Facts | |
| P-value to a Layman | |
| First Touch Attribution | |
| Job Recommendation | |
| Daily Retention Summary | |
| Recurring Character | |
| Scrambled Tickets | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening phone or Teams call with a recruiter or HR contact about their background and why they are interested. One candidate was asked to show knowledge of the company and had to reschedule to prepare. Another reports several reschedules before connecting. Expect a conversational screen, though the focus may vary.
Candidates report three or more HackerRank problems, with windows of roughly four hours or more. Several describe academic, competitive-programming style questions with long statements. One reports a fourth problem added after submission, and another a camera-on session with one easy and two medium data structure problems. This stage appears to be the main filter.
One candidate describes a timed cognitive test with verbal, numerical and logical reasoning sections of about ten minutes each. Another describes a cognitive test with barely a minute per question, plus a personality test. A third mentions logic and personality tests alongside the technical one. Candidates call the pace tight, so it may help to practice timed reasoning questions beforehand.
One candidate reports a second HR call of about an hour covering their full work history and each project, which was then sent to the hiring manager before any technical interviews were scheduled. Another says discussions touched on problem-solving approaches, design patterns and projects they had led. Be ready to explain your past work in detail.
One candidate reports a final technical interview with questions on networking, frameworks and languages outside the role they applied for. Others report no interview rounds, ending in rejection or silence after assessments. All five reports ended without an offer, and waits of weeks with little feedback were common. Plan for uncertainty at this stage.
