Interview Experience at Optimus Information Inc.
Interview Experience
The company conducted an off-campus drive.
Round 1 Written Test.Well, it was quite easy. Total number of questions - 35.Aptitude - 33.Operating System - 1.C - 1.Aptitude ...
Full Details
The company conducted an off-campus drive.
Round 1 Written Test. Well, it was quite easy. Total number of questions - 35. Aptitude - 33. Operating System - 1. C - 1. Aptitude questions were mainly related to amount of work done, colored cube questions and so on.
Round 2 HR interview. It was just a lookup to see if the candidate isn't dumb. After this, candidates who cleared the two stages were called in the office. Rounds at Optimus -
Round 1 Surprisingly, another written test followed but the pattern was exactly the same. Difficulty level was also similar.
Round 2 Small Technical Interview By small I mean, it wasn't much extensive. It was just to see if you are a candidate capable enough to go for a higher level Technical interview. Basic DBMS questions (Normalization), SQL queries were actually difficult (nested), virtual function question in C++, method over-loading in Java and same stuff. Important thing is projects. They can make you write the code for your project.
Round 3 Machine Round. In this, a basic question is given and you have to implement it programmatically. String and arrays are important topics for questions.
Round 4 Technical round with Team Leader. This is really tricky round. Learn your project's code by heart and I mean this. You must be ready to even write the whole project's code, literally. Be ready to defend your design pattern and SQL table structure (if any) in your project. Projects are a key for this round.
Round 5 Technical round with the Co-founder This is basically the same. Projects are the key. Be ready to tell what projects you are going to make after 6 months and what design pattern you have thought to implement. Also, you must prepare for a future project in terms of programming. This will make him happy. though, you must literally be prepared of the design pattern.
Topics
About Optimus Information Interview Reports
This question was reported by a candidate who interviewed at Optimus Information. 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 Optimus Information are the higher-signal extractions to take from this report.
For broader preparation context, the Optimus Information 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 Optimus Information reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Optimus Information 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 Optimus Information 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.