Tip 1 (DSA): Stick to a fixed set of patterns and solve problems regularly; even 3–4 quality problems a day build solid intuition.
Tip 2 (System Design): Try to understand how real systems work and why certain choices are made, instead of just memorising designs.
Tip 3: Keep your own notes or a GitHub repository — it makes revising much easier and keeps you on track.
Tip 1: Keep your resume clean and focused on what genuinely represents you.
Tip 2: Highlight the results of your work rather than just listing your responsibilities.
The DSA round was around 3 PM, and I was a bit nervous at first because the interviewer seemed very experienced. The environment was calm, though, and once we got into the problem, I settled in. The interviewer was patient and gave me space to think. Overall, it was a straightforward round, aside from the usual interview nerves.



Step 1: I started with the brute-force approach just to frame the problem, knowing it wouldn’t scale.
Step 2: The interviewer gave a small hint to think in terms of a “window,” which guided me toward the sliding window approach.
Step 3: Since this was a fairly standard question, I quickly moved to the optimal sliding window + HashMap solution. I explained how shifting the start pointer based on last-seen characters reduces the complexity to O(n).
We walked through one example, and the interviewer was satisfied.
'U' (Up): The robot's y-coordinate increases by 1.
'D' (Down): The robot's y-coordinate decreases by 1.
'R' (Right): The robot's x-coordinate increases by 1.
'L' (Left): The robot's x-coordinate decreases by 1.
Step 1: I kept two counters for horizontal and vertical movements.
Step 2: For each move, I updated the counters accordingly.
Step 3: At the end, I checked if both counters were zero.
If they were, the robot had returned to the origin.
The System Design round was in the afternoon, and I was a bit nervous since it was my first proper one. They started with a few basic questions and then moved into an ATM-style LLD problem, which helped me settle in. The interviewer was friendly and provided small hints whenever I slowed down. After the design part, the discussion shifted to core Java concepts — topics like the Collections framework internals, how the JVM handles memory, a few Spring Boot annotations, and some basics of Spring caching. It felt like a mix of design and core engineering fundamentals, but overall, the round was manageable.
I was asked to design a basic ATM system (LLD style). The interviewer wanted me to define the main entities, describe how they relate to each other, and outline a few basic REST APIs to support core functionalities such as card validation, balance checks, and cash withdrawals.
Tip 1: Start by identifying the key entities: ATM, Card, Account, User, Transaction, and BankServer, and show how they are connected.
Tip 2: Walk through the main flow step by step so the interviewer can follow your thought process.
Tip 3: Study RDBMS thoroughly; knowing how to structure tables and define relationships helps a lot in LLD discussions.
I was asked a simple SQL question about fetching the second-highest salary from an employee table.
The interviewer also asked how I would handle duplicates, how ORDER BY works internally, and the difference between using LIMIT and a subquery.
Tip 1: Know multiple ways to solve the same SQL question (subquery, LIMIT, ROW_NUMBER()). Interviewers often ask for alternatives.
Tip 2: Understand how sorting and indexing affect performance.
Tip 3: Be comfortable with basic RDBMS concepts such as primary keys, unique constraints, and how duplicates are handled.
I was asked a bunch of short, direct questions from core Java and Spring Boot, such as:
They also touched on the basics of Spring Caching and how the framework manages bean creation.
Tip 1: Have a solid grasp of Java fundamentals, collections internals, the memory model, and common OOP principles.
Tip 2: Know the purpose of key Spring annotations (@Component, @Service, @Repository, @Autowired, @RestController) and how Spring manages beans.
Tip 3: Brush up on how Spring Boot auto-configuration works and the basics of Spring Caching.
The HR round was in the afternoon and felt straightforward. They asked about my background, why I’m looking for a change, and a few questions about how I work in a team. Toward the end, we discussed compensation expectations and timelines. The HR was friendly and approachable, making the whole conversation feel natural and stress-free.

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
What is recursion?