Oxigen Wallet Recruitment Process
Interview Experience
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other as...
Full Details
This article will give you information about the company, its recruitment process,
sample questions that have been asked previously, lots of experiences shared by other aspirants, and the portal where you can apply. Table of Content About Company: Recruitment Process: Academic Criteria: Online Coding Round: Technical Rounds:
HR Round: About Company: Oxigen Wallet is India’s first non-banked mobile wallet, approved by RBI in 2013 for instant money transfers to any bank. Oxigen Services India Pvt. Ltd., an ISO 9001:2008 certified FinTech company, is one of the major payment solutions providers in India. It is involved in the micropayment of services and remittances in real time. It was started in 2004 by, an alumnus of IIT Roorkee and a listed company on the South African Stock Exchange, Blue Label Telecom. The payment solutions provider allows customers to make mobile/DTH recharges, money transfers through the bank and Oxigen Wallet, utility bill payments, etc. In 2015, Oxigen Wallet was awarded by Money Transfer Programme Award 2015 by the Internet and Mobile Association of India. In 2014, the company was recognized as the Best Prepaid Payment Instrument for 2014 by the National Payments Corporation of India Excellence Award. Recruitment Process: Oxigen Wallet conducts 3-4 rounds to select freshers as Software Engineers in their organization. Online Coding Round Technical Round 1 Technical Round 2 HR Round Academic Criteria: 70 percent or above in B.Tech, Class X and XII. No backlogs at the time of the interview Online Coding Round: The online coding round consists of two 2 problems. To clear this round you should be strong in Data structures and algorithms. Technical Rounds: The students who clear the written round are called for a Technical Interview. To clear this round you should be clear with your basics. You should be prepared with Data structures and Algorithms, DBMS, OOP concepts, and a programming language of your choice. Students from branches other than CS should prepare for the other two subjects related to their branch. CS students will be expected to write codes in the interview. They should also expect questions from your resume or your previous experience. You may be asked puzzles in this round.
HR Round: General HR questions like : Tell me about Yourself Salary Expectations? How do you see yourself after five years from now? What are your strengths and weaknesses? Interview Experiences: It is always beneficial if you know what it is to be there at that moment. So, to give you an advantage, we provide you with the Interview Experiences of candidates who have been in your situation earlier. Make the most of it. Oxigen Wallet Interview Experiences Questions Asked in Oxigen Wallet: AVL Tree Insertion (Function Problem) What is a virtual function in C++? Difference b/w get and post? Difference b/w http and https? Where to Apply? Oxigen Wallet careers Oxigen Wallet Official Website
About This Question
This is a candidate experience report from a oxigen wallet interview for a swe role during the recruiter round reported in 2025.
It covers the following topics: Sql, Oop, Trees, Networking .
Topics
More Oxigen Wallet Interview Questions
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.