Uurmi Systems Interview Experience | Set 1
Question Details
First RoundThe first round was a offline written test. It consisted of 22 questions . 12 objective and 10 subjective. Questions were from Networks, Operating Systems, Digi...
Full Details
First Round The first round was a offline written test. It consisted of 22 questions . 12 objective and 10 subjective. Questions were from Networks, Operating Systems, Digital Logic, C & C++. Only 5 students were shortlisted after the first round. Second Round This was a Face to Face technical Interview. Questions asked were from networking, operating Systems and Data Structures : 1) What is Paging? 2) What is MAC? 3) Schedulers and Page replacement Algorithms. 4) Quick Sort and Merge Sort ( With code ) 5) Given a pointer to a random node in linked list delete that node .(With Code) 6) Recursively reverse Linked List .(With Code) 7) Oral Explanation of Binary Search Trees , Stacks and Queues. Lot of other questions from networking which I wasn't able to answer. More Focus was on Linked Lists. Third Round Third round was the final round and was the HR round. Regular Questions like: Tell me about yourself? How were you able to recover after 4 year gap in education? What lessons did you learn from your problems? 1 Week later results were announced and I was selected.
About This Question
This is a reported interview question from a uurmi interview for a swe role during the recruiter round reported in 2025.
It covers the following topics: Linked List, Trees, Sorting, Binary Search, Os .
Topics
About Uurmi Interview Reports
This question was reported by a candidate who interviewed at Uurmi. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Uurmi are the higher-signal extractions to take from this report.
For broader preparation context, the Uurmi interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Uurmi reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Uurmi Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Uurmi reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.