Two candidates describe HockeyStack software engineering interviews that mix data-structure coding, SQL, JavaScript, system design and project discussion, followed by slow communication. Here is how to prepare for each stage.
$165K
Avg. Base Comp
$230K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Two candidates describe HockeyStack software engineering interviews, and their accounts differ in shape, so prepare for range rather than a fixed script. Neither ended in an offer, and the evidence is limited.
The candidate for a general software engineer role reports a screening call, then a first technical round of basic coding with hashmaps and other core data structures. A second technical round dug into one of their own projects, plus computer networks, operating systems and a puzzle. A final HR conversation asked for an introduction and why they wanted HockeyStack. They describe the interviewers as relaxed.
The senior candidate reports a heavier format: four rounds scheduled back-to-back on one day. They cover JavaScript and SQL questions, a system design discussion, a round on DSA and distributed systems, and a design-and-implementation problem. If you apply at a senior level, expect to be tested on breadth in a single sitting.
For preparation, practice hashmap-style problems, be ready to walk through a real project and the decisions behind it, and refresh networking and OS basics. Brush up on JavaScript and SQL, and rehearse a short answer on why you want to work at HockeyStack.
Both candidates mention slow follow-up. One heard nothing for a week or more, and the other waited almost three weeks before a rejection. Keep your other applications moving while you wait.
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 HockeyStack 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 HockeyStack
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Find the Missing Number | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Raining in Seattle | |
| Minimum Change | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Size of Joins | |
| The Brackets Problem | |
| Scrambled Tickets | |
| Weighted Keys | |
| Flight Records | |
| Rectangle Overlap | |
| Daily Retention Summary | |
| Project Pairs | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
One candidate for a software engineer role reports passing a screening call before the technical interviews were scheduled. The senior candidate says they were told they had been shortlisted before the interviews were arranged. Details of the screen's content were not reported.
The software engineer candidate reports basic coding problems on hashmaps and other core data structures. The senior candidate describes a similar opening stage of JavaScript and SQL questions, followed by system design. Expect fundamentals first, though the exact mix may vary by level.
One candidate reports a deep dive into one of their own projects, plus networks, operating systems and a puzzle. The senior candidate reports rounds on DSA and distributed systems, plus a design-and-implementation problem. Prepare to explain real work and core concepts in detail.
The software engineer candidate reports an HR round asking for a self-introduction and interest in HockeyStack. Both candidates report slow communication afterward: a week or more for one, almost three weeks for the other, ending in a rejection email. Timelines may vary.
