1Mg Interview Questions (May 2026)
1 questions · 2 experiences · GeeksforGeeks (3)
Top topics
3 entries
Tata 1MG Interview Experience for SDE-1 (On-Campus)
1mg Interview Experience for SDE FTE | 1.3 Years Experienced
1mg Interview Experience | Set 1 (Off Campus)
Tata 1MG Interview Experience for SDE-1 (On-Campus)
Question Details
This is an On-campus offer. Eligibility Criteria was a minimum of 7 pointer. There were a total of 4 rounds (1 Coding Test+2 Technical Interviews+ 1 Managerial) Round 1 (Coding Assessment): It has 3 Coding Question of medium-hard level and time limit was 1 hour only. I don’t exactly remember the questions but I was able to do only two of them completely. Only 14 students were shortlisted for
next round. Suggestion: I would suggest doing coding practice from sites like GeeksforGeeks, Leetcode etc as it will give the confidence to solve problems. Tips: Don’t spend too much time on the first question you pick, if you are not able to do the first one try doing the second. Read the instructions very carefully Focus on the test input, then handle edge cases Then 3 rounds of Interviews was scheduled one day . Round 2(Technical Interview 80 min): First, the interviewer introduced himself and then asked to introduce myself. Then he asked about the projects I did. After an introductory discussion on projects, he gave me 3 coding questions on their personal live code environment. He asked me to explain the approach first and then code it down. I had to explain the time complexity of each solution and optimal code if possible with lesser time complexity. First question was based on cache memory, he has given me a function with arguments and i have to just write it's definition. After 5-10 minutes of discussion I was able to solve the problem and code it down. The approach uses concept of hashing. I would rate it as a easy problem. The second problem was Print all possible words from phone digits , I have already done this question before and I explained him the logic of my approach and he seems satisfied with it. It was sort of medium-level difficulty. Question: https://www.geeksforgeeks.org/dsa/find-possible-words-phone-digits/ Last question was slight variation of Count the number of words with given prefix using Trie. Instead of returning count i just need to print all the words. I gave him a brute force approach with which he was not satisfied. Then he gave me time to think and asked for more optimized approach. Then after 5 min i gave him this Trie solution and then i explained him the structure of trie along with the code Question: https://www.geeksforgeeks.org/dsa/count-the-number-of-words-with-given-prefix-using-trie/ Round 3(Technical Interview 80 min): In this round interviewer gave me 2 coding questions and asked me to code on any editor of my choice. I opened VS code to code those problems. The first question was Largest Sum Contiguous Subarray. I explained him my approach (Kadane's algorithm) and he seems satisfied with it and asked to code it down. Question: https://www.geeksforgeeks.org/dsa/largest-sum-contiguous-subarray/ The second question was LRU cache problem. I gave him brute force solution but interviewer was not satisfied. I was stuck for some time, then he helped me with data structure (doubly linked list). After 15-20 min of discussion I was able to do that question and code it down. Question: https://www.geeksforgeeks.org/system-design/lru-cache-implementation/ Suggestion: Even if have done coding question previously it's completely your responsibility to start the solution from basic idea and further you can proceed with optimization. Do not directly jump on the most optimized solution. And if you are feeling any difficulty, you can discuss it with interviewer. Round 3(Managerial 40 min): The interviewer was very friendly. He asked me about myself and previous interviews. Then he jumped on my projects. I explained him and answered all the follow up questions After share link to 1MG website and asked me design DB for it. He gave me 5-10 min to think and design DB. Finally in the end, he asked me standard HR type question like where do you see yourself in 2 years, startup with 2X salary or stable company with X salary, why you want to join us etc. Finally, after 2 hours results came and 4 students were selected. Luckily, I was one of them. Tips for interviews: Listen to the question carefully and clear all your doubts at the same time before proceeding to solution Even If you are stuck, discuss your thinking process with the interviewer. They can help you with some hints. Prepare HR question before coming to interviews. Stay calm, confident and be in sync with interviewer all the time
Topics
More from 1Mg
1Mg Interview Process Overview
The 1Mg interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show 1Mg runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: 1Mg coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use 1Mg Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. 1Mg updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in 1Mg reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of 1Mg's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common 1Mg Interview Mistakes
Reports tagged "no hire" at 1Mg consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.