Oxigen Wallet Interview Experience | Set 3 (On- Campus)
Question Details
First Round:Online coding test on Cocubes.comQ1. Given two integers m and n write the function to compute the number of bit changes required to convert one to another Exam...
Full Details
First Round: Online coding test on Cocubes.com Q1. Given two integers m and n write the function to compute the number of bit changes required to convert one to another Example: m=14 n=15 answer : 1 Explanation : 24 : 11000 15: 01111 Q2.linked list multiplication: Given two linked list that represents polynomial return a pointer to linked list which is multiplication of the two. struct node { int coeff; int exp; struct node*next; };
example: 4x(2)-2x+1 x-1 answer : 4x(3)-6x(2)+3x-1 Second Round:(F2F interview) Project related questions oops concepts in detail. Linked list what are its advantages. and some basic general questions on data structures. Third Round:(With the CTO) He asked oops concepts output related questions on virtual functions what are virtual constructors what are B trees can you code for that what are avl trees?why they are used? He said he will ask me to write code for avl tree later but at the end he forgot :p what are design patterns? what are singleton classes? is there any keyword to define a singleton class in c
Topics
More from Oxigen Wallet
About Oxigen Wallet Interview Reports
This question was reported by a candidate who interviewed at Oxigen Wallet. 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 Oxigen Wallet are the higher-signal extractions to take from this report.
For broader preparation context, the Oxigen Wallet 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 Oxigen Wallet reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Oxigen Wallet 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 Oxigen Wallet 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.