I Didn’t Memorize Problems, I Learned the Patterns with Sheets

Hi everyone, I'm Avinash Gottapu, currently placed at Microsoft and also a B.Tech student at NIT Rourkela, with a strong interest in software engineering, backend development, and competitive programming.

I enjoy solving DSA problems, participating in coding contests, and building backend applications using technologies like Node.js, PostgreSQL, Redis, Docker, and WebSockets.

Finding the Right DSA Roadmap

I started my DSA preparation by completing the takeUforward A2Z DSA Sheet during my 2nd and 3rd semesters. It gave me a structured path to follow and helped me build strong fundamentals without getting lost in random questions.

Before interviews, I revised using the TUF SDE Sheet, which helped me refresh important patterns and build confidence with interview level problems.

Preparing Beyond DSA

Along with DSA, I focused on OS, DBMS, CN, and OOP and worked on backend projects to gain practical experience.

I also regularly practised coding problems and participated in contests to improve my problem solving speed and pattern recognition. Before interviews, I made sure I could not only solve problems but also clearly explain my approach.

When the Patterns Started Making Sense

My Microsoft placement journey started with an online test, where I was able to solve both coding problems comfortably.

In the first DSA round, I got two problems, one based on making pairs of strings anagrams with minimum character changes, and another based on sliding window. Although the exact questions weren't in the A2Z Sheet, the patterns were familiar because of the problems I had already practised.

The final round focused largely on my backend projects, followed by a DFS based coding problem and a few HR questions.

What Made the Difference

Looking back, I'd say around 80% of my Microsoft interview success came from the DSA foundation I built through the Striver A2Z Sheet, while the remaining 20% came from my core CS knowledge and project experience.

The biggest advantage wasn't memorising questions, it was being able to recognise patterns and apply what I had learnt to new problems.

My Advice to Juniors

Stay consistent instead of studying in bursts.

Follow the A2Z DSA Sheet, solve problems yourself instead of only watching solutions, study your core CS subjects, and build projects you can confidently explain.

Participate in contests, revise regularly, and practise communicating your approach during interviews.

You don't need to prepare everything overnight. Consistent effort over several months will always beat last minute preparation.

Recommended Reads

Post

Okta Is Hiring | Senior Software Engineer

Okta is looking for a Senior Full Stack Engineer to join its ISV Ecosystem team. The team is building developer-focused products that help B2B SaaS applications

Post

HPE Is Hiring | Systems/Software Engineer I

Location: Bengaluru, India Work Mode: Onsite Hewlett Packard Enterprise (HPE) is looking for a Systems/Software Engineer I to work in its lab engineering team.

Post

Why Should We Hire You Without a CS Degree?

Coming from a non-CS background and preparing for software engineering interviews can feel challenging. Whether you studied Mechanical, Electrical, Civil, Chemi

Post

Working 9-5 but Still Dreaming of a Better Job? How to Prepare Without Burning Out!

Working a 9-5 while trying to prep for a job switch is honestly exhausting. After spending 8-9 hours dealing with work deadlines, meetings, and daily responsibi

Post

Before You Give Up After Multiple Rejections, Read This

Getting rejected once is disappointing. Getting rejected multiple times, especially after putting in weeks or months of preparation , can make you question your

Comments0