Three candidates describe Intellian software interviews that begin with a HackerRank assessment. One front-end candidate also reports a live React debugging round and a Google Sheets-style system design round.
$130K
Avg. Base Comp
$150K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates who interviewed for software roles at Intellian Technologies describe a process that starts with a HackerRank online assessment. All three reports are from different roles (an SDE intern, a Front End Developer and an SDE II), so treat the details as role-dependent rather than a fixed pipeline.
The intern candidate reports a 90-minute assessment with one easy-to-medium string problem. It involved counting the steps needed to type a word on a keyboard layout, and a hash map solved it in under 50 minutes. The SDE II candidate reports a 90-minute, webcam-proctored assessment with JavaScript problem solving, multiple-choice React questions (including types of routers) and a React project question. The front-end candidate reports a 75-minute assessment with two algorithm problems: converting numbers to Roman numerals and finding maximum taxi earnings from pickup, drop and tip arrays.
Only the front-end candidate describes later rounds. They report a live session debugging a buggy e-commerce React app, followed by a system design round on a Google Sheets-like frontend covering cells, formulas, undo/redo and real-time collaboration. That candidate was rejected after the design round, and the other two also report no offer.
To prepare, practice clean array, string and hash map solutions under a timer, and review core React concepts such as routing and state management. If your role leans front end, rehearse debugging components out loud and sketching a large UI architecture. With only three reports, expect some variation.
Synthesized from 3 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 Intellian Technologies process.
I started with an online assessment on HackerRank that lasted 75 minutes and covered two data structures and algorithms problems. The first asked me to convert an array of numbers into their Roman numeral equivalents, which was straightforward string manipulation once I mapped out the conversion logic. The second was more involved—given arrays for taxi pickups, drops, and tips, I had to find the maximum earning. It required some careful iteration and tracking, but was doable within the time constraint.
After passing that, I moved into a live coding round that caught me off guard. Instead of a traditional algorithmic problem, I was given a React application with bugs embedded in it and asked to debug and fix them. This felt like a real-world task, which I appreciated, though it meant context-switching from pure DSA prep. The app was e-commerce focused, so I had to trace through component logic and state management issues rather than optimize a search algorithm.
Next came a system design round where I was asked to design a Google Sheets-like system from a frontend perspective. This was the toughest part of the process. I had to think through how to structure columns, cells, formulas, undo/redo, real-time collaboration—a lot of surface area to cover in a limited time. I don't think my design was as polished as they wanted, and I felt rushed trying to balance depth with breadth. The interviewers asked clarifying questions but seemed less engaged as I went deeper, which made me realize I'd probably missed some key architectural decisions early on.
I was rejected after the system design round. Looking back, the process mixed different skill areas—classic DSA, React debugging, and systems thinking—without clear signals about what mattered most for this particular role. The online assessment felt disconnected from the later rounds, and I wish I'd had more clarity on whether the role was backend-focused or frontend-focused before diving in.
Prep tip from this candidate
The system design round for a frontend-focused role centered on designing Google Sheets—prepare to handle large-scale UI architecture, not just backend systems. Also, brush up on debugging React apps under time pressure, as this was a live coding component that tested practical troubleshooting over algorithmic problem-solving.
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 Intellian Technologies
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Prime to N | |
| Get Top N Frequent Words | |
| Over-Budget Projects | |
| Size of Joins | |
| The Brackets Problem | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Cyclic Detection | |
| Justify a Neural Network | |
| Sort Strings | |
| Append Frequency | |
| Find Duplicate Numbers in a List | |
| Swapping Nodes | |
| Groups of Anagrams | |
| CNNs vs Intensity-Based Features | |
| Swap Variables | |
| Closed Accounts | |
| Longest Increasing Subsequence | |
| Skyscanner Partner ETL | |
| Relational Migration | |
| Precision and Recall | |
| Valid Anagram | |
| Success Measurement | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Portfolio Platform Architecture | |
| Word Frequency | |
| Check Matching Parentheses |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report receiving a HackerRank link shortly after applying. Reported formats vary by role: one easy-to-medium string problem, two algorithm problems, or a JavaScript and React assessment. Timing was 75 to 90 minutes, and one candidate said the session was webcam-proctored. Expect fundamentals such as hash maps and string or array traversal.
The SDE II candidate reports a multiple-choice React section, including a question on router types, and a React project question within the same assessment. The front-end candidate reports a separate live round fixing bugs in an e-commerce React app. This stage may apply mainly to front-end or web-leaning roles.
One candidate reports being asked to design a Google Sheets-like system from a frontend perspective, covering columns, cells, formulas, undo/redo and real-time collaboration. They felt rushed and were rejected afterward. Other candidates did not describe this round, so it may not apply to every software role.
All three candidates report no offer. One heard nothing after submitting the assessment, and another was rejected after the system design round. Candidates did not report an end-to-end timeline, so timing after the assessment is unclear.
