Spinny Software Engineer interview typically runs 4-6 rounds: phone screen, online assessment, technical interviews, HR. The process usually takes a few days to a few weeks and is notably fast-paced and technical.
$1300K
Avg. Base Comp
$2220K
Avg. Total Comp
6
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Spinny is looking for engineers who can move fast without getting sloppy. The recurring pattern is not just algorithmic difficulty, but the way interviewers keep pushing until they see the cleanest underlying approach. One candidate described starting with a brute-force idea on a missing-positive problem and only getting through once they arrived at cyclic sort; another said the team moved quickly from coding into LRU Cache and then straight into system design. That combination tells us Spinny values people who can solve under pressure and still explain why a solution is the right one, not merely one that passes.
A second theme is how much weight they place on low-level design and implementation detail. Multiple candidates mentioned being pressed hard on LLD-style questions like Twitter, hotel booking APIs, and log/graph problems, with little room for vague answers. We also saw a separate thread where web fundamentals came up aggressively — HTML, CSS, JavaScript, React, and even adaptive versus responsive design — which suggests they expect practical product engineering fluency, not just DSA strength. The candidates who struggled most were the ones who could outline an idea but couldn’t carry it through to a robust structure or code path quickly enough.
What stands out overall is that Spinny seems to reward breadth with depth: strong algorithms, but also the ability to reason about real systems and front-end basics when needed. Our candidates’ experiences suggest that the bar rises when the interviewer senses hesitation, especially on follow-up questions. In other words, the difference-maker here is often whether you can defend your design choices and implementation details while the clock is still running.
Synthesized from 2 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 Spinny process.
The hardest part for me was how quickly they moved from coding into design. I first had an online assessment with two medium-hard LeetCode-style questions, which felt pretty standard on paper but still required solid speed. After that, I went into two to three technical interviews. The first interview was actually handled by a third-party interview organization, and the rest were with Spinny employees. In the technical rounds, I was asked to implement an LRU Cache and then move into system design for a Hotel booking API, so it wasn’t just about getting a working solution — they wanted to see how I thought through tradeoffs and structure under pressure.
What stood out most was how deep they went on low-level design. In my case, they asked a Twitter LLD question and pushed very hard on it, and there was also a hard LeetCode question with very little time to solve it. I was able to get through more than half of the code, but without hints I couldn’t finish it. Overall, the process felt demanding and fairly technical, especially if you’re not comfortable with both coding under time pressure and detailed design discussions. I didn’t get an offer from the technical loop I went through, so I’d recommend practicing hard LeetCode problems, LRU Cache, and being ready to explain a full LLD clearly and in depth.
Prep tip from this candidate
Be ready for a very deep low-level design discussion like Twitter-style LLD, and practice implementing LRU Cache and other medium-hard LeetCode problems under tight time limits. If you get the assignment route, expect the follow-up to focus on your project history and the choices you made while building the website.
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 Spinny
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Find the Missing Number | |
| LRU Cache 1 | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N | |
| Random SQL Sample | |
| Top 3 Users | |
| Upsell Transactions | |
| Comments Histogram | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Hurdles In Data Projects | |
| Find the First Non-Repeating Character in a String | |
| Delivery Estimate Model | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| P-value to a Layman | |
| Recurring Character | |
| Rectangle Overlap | |
| Google Maps Improvement | |
| Address Schema | |
| Download Facts |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with a phone screen focused on your background, previous interview experience, tech stack, and overall fit for the Software Engineer role. In some cases, this is also where the recruiter discusses your resume, prior internships, and project experience.
Candidates complete an online coding test with two algorithmic problems. Reported questions included medium-hard LeetCode-style problems, dynamic programming questions, and other classic DSA patterns such as pick/not-pick, Rat in a Maze variations, and array problems. The first technical round is often coding-heavy and may be run by a third-party interviewer organization before moving to Spinny employees. Expect implementation questions such as LRU Cache, hard DSA problems, and follow-up discussion on approach, complexity, and correctness.
Subsequent technical rounds go deeper into algorithms and problem solving under time pressure. Candidates reported questions on cyclic sort, missing positive number, largest plus sign, and other variations where the interviewers expected an optimal solution rather than a brute-force approach.
Spinny appears to move quickly from coding into design, with strong emphasis on low-level design and system design tradeoffs. Reported prompts included designing a Hotel booking API and a Twitter-style LLD question, with interviewers pushing for clear structure, edge cases, and design decisions.
Some candidates faced a rapid-fire round on web development fundamentals, including HTML, CSS, JavaScript, React, adaptive vs. responsive design, and discussion of Spinny’s own website. This round appears to test breadth and practical understanding rather than just coding.
In an alternate path, candidates may be given a website-building assignment based on a description and then follow up with a manager interview. The manager discussion focuses on projects, previous work, and skills, and this route was described as moving quickly, with a decision sometimes coming within 24 hours. The process can end with an HR round covering resume details, previous internship experience, and general background discussion. This appears to be the final step before the offer or rejection decision.