Tip 1: Build strong fundamentals in DSA, OOP, and DBMS instead of just memorizing concepts.
Tip 2: Work on real-world ML/DL projects and be ready to explain them in depth.
Tip 3: Practice clear communication and explain your thought process during interviews.
Tip 1: Include only those projects and skills that you can confidently explain in depth.
Tip 2: Tailor your resume according to the role (ML/Dev) and highlight relevant experience.
Tip 3: Keep your resume concise, well-structured, and impact-focused.



Step 1: I first understood the problem requirement clearly — to move all zeroes to the end while maintaining the order of non-zero elements.
Step 2: I initially thought of using an extra array to store non-zero elements and then appending zeroes at the end, but realized it uses extra space.
Step 3: Then I optimized it using a two-pointer approach, where one pointer tracks the position to place the next non-zero element.
Step 4: I iterated through the array, and whenever I found a non-zero element, I swapped it with the element at the pointer and incremented the pointer.
Step 5: This ensured all non-zero elements stayed in order and all zeroes were pushed to the end in-place, which satisfied the interviewer.
Step 1: I started by clearly explaining the core concepts like polymorphism and its types with simple examples.
Step 2: For questions like deep copy vs shallow copy, I first defined both and then explained the difference using practical scenarios.
Step 3: In topics like garbage collection in Python, I explained how memory management works along with reference counting.
Step 4: Whenever the interviewer asked follow-up questions, I focused on answering step-by-step instead of jumping directly to conclusions.
Step 5: I made sure to relate concepts with real-world examples, which helped in making my answers more clear and understandable.



1- In one successful operation, Ninja can remove two positive integers, ‘A’ and ‘B’, and insert their sum, i.e., ‘A’ + ‘B’ into the position of either ‘A’ or ‘B’.
2- To insert sum in the position of element ‘A’, the condition 2 * ’A’ >= ‘B’ should be satisfied. Similarly, to insert the sum in the position of element ‘B’, the condition 2 * ‘B’ >= A should be satisfied.
3- We will insert the sum at one position, and the value at the other position should be changed to -1.
4- The resultant array should contain only 1 positive element.
A combination is different if they lead to a different position of the element that remains positive at the end of all successful operations for that combination.
Let ‘ARR’ be: {2, 1}
Combination 1:
Pick 2 and 1 and insert their sum at the position of 2: [3, -1]
Combination 2:
Pick 2 and 1 and insert their sum at the position of 1: [-1, 3]
So total combinations are 2.
Step 1: I first understood the problem — to scale all values of the array into the range [0, 1] using Min–Max Normalization.
Step 2: I identified that I need to find the minimum and maximum values in the array.
Step 3: I traversed the array once to compute the min and max.
Step 4: Then, I applied the normalization formula to each element: (value - min) / (max - min).
Step 5: I created a new array with the normalized values and explained the edge case when all elements are equal.
Step 6: Finally, I discussed the time complexity as O(n), which satisfied the interviewer.
DBMS:
OOP:
Tip 1: For ACID properties, always explain each property with a simple real-world example (like banking transactions) to make your answer clear and practical.
Tip 2: In SQL queries, first think of the logic in plain English (grouping, counting, filtering) and then convert it step-by-step into a query using GROUP BY and HAVING.
Tip 3: For serializability, focus on understanding concepts visually — practice drawing precedence graphs and identifying conflicts, as it makes explanations much easier.
Tip 4: While explaining DBMS concepts, try to relate them to real-world systems like booking platforms to show practical understanding.
Tip 5: In OOPS follow-ups, stay calm and build answers step-by-step from basics instead of rushing, and use small code or real-life examples when needed.
Tip 1: Be ready to explain your project end-to-end — problem statement, dataset, preprocessing, model choice, and final results clearly.
Tip 2: Justify your design decisions (why this model, why this approach) and discuss trade-offs or alternatives to show deeper understanding.
Tip 3: Prepare for follow-up questions by understanding limitations, improvements, and how your project can be scaled to real-world scenarios.
No DSA questions were asked.
This round was heavily focused on real-life, case-based problem-solving.
The interviewer selected one of my time-series forecasting projects and framed multiple scenario-based questions aligned with Big Billion Days use cases.
Key Case-Based Questions:
At the end of the interview, I was asked about my aspirations and long-term goals in this domain.
Tip 1: Scenario-based ML problem-solving is heavily tested, especially when applying models to real business use cases.
Tip 2: Practice applying ML concepts to real-world business scenarios (like sales forecasting, recommendations, or sentiment analysis) instead of focusing only on theory.
Tip 3: Structure your answers clearly—define the problem, list key factors, propose an approach, and explain how you would evaluate the solution.

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
Which SQL keyword removes duplicate records from a result set?