One Convergence Device Interview Experience | Set 1 (On-Campus)
Question Details
One Convergence Device (Hyderabad) came to our campus with a handy package on for Full time Software Engineer profile. MCA and Mtech were allowed. There was one written an...
Full Details
One Convergence Device (Hyderabad) came to our campus with a handy package on for Full time Software Engineer profile. MCA and Mtech were allowed. There was one written and two technical interviews round. Second technical interview also included HR interview. No separate HR round. Written round- There was only one written round after ppt presentation. It was pure technical based paper consisting of c, java, datastucture, network and operating system. There were around 60 questions to be done in one hour. All questions were easy but conceptual and little bit tricky. 1. In C. Most of the questions were based on bits manipulation and string and union. 2. In Data structure. Questions on tree , heap, red black tree and balanced tree and complexity. 3. In Operating System It was really conceptual. Most of the questions were on virtual memory concept and scheduling and semaphore. 4. Network Questions on layers and their protocols. Numerical that needed transmission ,propagation and bandwidth formula. Some general conceptual question including switch, hub and gateway. I attempted every section since sectional cutoff was there. I didn’t attempt any question that I was not sure for, since there was negative marking. I also didn’t attempt any numerical. So, attempt each section such that you can clear cut off. No need to attempt all questions of each section. First round- After written test , only 4 from Mca and 4 from Mtech were selected for
next round. It was also pure technical round. Interview started just after result was declared. Since there was only two panels, It was taking time. Questions. 1. Tell me about yourself in brief. 2. Write program to reverse string. 3. Write program to reverse bits of number. 4. Write program to check common sequence in two string. 5. Write program to the bits which is set. 6. Describe switch in n/w and how will you implement its s/w. 7. What is NAT and its functions ? 8. What is VLAN ? 9. How client and server establish their communication. How to create socket , explain step by step? 10. What is socket buffer? 11. What is function of bridge? 12. What is IPC(inter process communication) and ITC(inter thread communication) and how it happens and how to implement it. Second round- 1. Tell me about yourself and your achievement briefly and your family background. 2. What is linking? Explain in detail. 3. What is little endian ,big endian. How to implement it’s code? 4. What are different types of memory segment and tell about different parts of program and where they are stored? 5. Explain zombie, daemon and orphan processes and how they are different? 6. How to create parent and child process and different threads? 7. What are common segment used by parent and child processes? 8. What are common segment used by threads? 9. What is symbol table and what is it used for? 10. How to use gcc to compile program and what are different options available? Ex: -g etc..
About This Question
This is a reported interview question from a one convergence device interview for a swe role during the recruiter round reported in 2014.
It covers the following topics: Strings, Trees, Heap, Os, Bit Manipulation .
Difficulty rating: Easy
Topics
About One Convergence Device Interview Reports
This question was reported by a candidate who interviewed at One Convergence Device. 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 One Convergence Device are the higher-signal extractions to take from this report.
For broader preparation context, the One Convergence Device 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 One Convergence Device reports consistently are the ones worth investing in; one-off niche problems are not.
During Your One Convergence Device 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 One Convergence Device 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.