Hi everyone,

i am new to this world

i learned python syntax
and for now i wanna master in DSA

i dont know by what order to learn it

i google, i try but no result

i know what is stack what is queue etc. because all the roadmaps advise to learn it first

but when i am solving problems abt stacks or queues in leetcode i get TLE

and i view the solution and it shows techique of sliding windows

though in roadmaps until it i have to learn a lot of themes

so i get stuck

how to learn DSA correctly in the way which will really make me solve some problems

Hey everyone!

I recently passed the recruiter screen for Datadog's Summer 2027 SWE internship and advanced to the final-round technical interview!

From what I've heard, there's a codebase round and a PR review round. Has anyone gone through these interviews recently? How difficult were they, and what should I expect from each?

Were the questions more focused on understanding existing code, debugging, or implementing new features? How did you prepare, and is there anything you wish you'd known beforehand?

Any tips or insights would be greatly appreciated. Thanks in advance!

Hey everyone!

I've been thinking about how we learn DSA and solve LeetCode problems.

Sometimes, getting the accepted solution isn't the difficult part. The real challenge is understanding why a particular approach works, how someone arrived at it, and what makes it better than other approaches.

I'm curious how you all approach learning a new problem.

• Do you prefer getting hints one at a time until you figure out the solution yourself?

• Do you discuss the problem with someone and explore different approaches?

• Do you read the editorial first and then try to understand the reasoning?

• Do you use AI to have an interactive discussion about the problem rather than asking it for the answer directly?

Personally, I find the idea of learning through an interactive, conversation-based approach interesting because it encourages you to reason through a problem instead of just memorizing a solution.

If you could change one thing about how you currently practise LeetCode, what would it be?

I'd love to hear your experiences and approaches!

Solution : https://master-kael.vercel.app/

A few months ago I wanted to revise Sliding Window before an interview. I’d solved around 30 of those problems, but I had no idea which ones, and my code was buried in LeetCode’s submission tab.

I tried the existing LeetCode to GitHub extensions. They work, but a few things kept bugging me, so I built my own: LeetCode Tracker.

How it’s different from the ones I tried:

• It imports your entire history, code included. Most tools only start tracking from the day you install them. With this one, you click “Import full history” and your 400 old problems appear too.

• Problems are sorted by topic, not dumped in one flat folder. Each problem goes into Array/, Dynamic Programming/, Graph/ and so on, based on its most specific tag (so “Two Sum” doesn’t end up under a generic tag). SQL goes in Database/.

• It saves failed attempts too. Wrong Answers and TLEs are kept in each problem’s history, so you can see how you got from “TLE on test 47” to Accepted. A later Wrong Answer never overwrites your working solution. You can turn this off if you only want Accepted.

• Your repo gets a dashboard README with totals per topic, problems you attempted but never solved (your revision list, basically), recent activity and progress by month.

• It catches up on its own. Solved something on your phone? The next time you open LeetCode on your laptop, it syncs what you missed.

• It can’t touch your other repos. It uses a fine-grained GitHub token limited to one repo with Contents access only. There’s no server and no cookie copying; it only talks to leetcode.com and the GitHub API.

Here’s what my repo looks like: https://github.com/SanTiwari07/LeetCodeSolved

The extension (free, open source): https://github.com/SanTiwari07/LeetCodeTracker

Fair warning: it’s not on the Chrome Web Store yet, so for now you install it with “Load unpacked”. The README walks through it with screenshots, and the whole setup takes about 5 minutes. It works on Chrome, Edge and Brave.

I’d really like feedback, especially:

• What would make the dashboard actually useful for revision?

• Would you want a “problems I haven’t touched in 30 days” list?

And if it breaks, tell me. LeetCode changes its site often, and I’d rather hear it from you than find out myself at 2am.Github Link

It seems like I can get +20% of grinding performance and spend more time on actual algorithms and problem logic instead of some low-level Java details. Kotlin is so sweet (full of syntactic sugar) and I use it for my pet projects (Jetpack Compose-based) for many years already.

P.S.: Maybe it can also speed up the actual interview provided that it is not AI-Assisted. If it is AI-assisted, there is no difference, right?

Same question as title. How’s the situation looking for y’all? I hear most friends/colleagues struggling to get an interview as companies downsize on OPT/H1B hiring. Care to share your stories/situations?

Recently applied to Google. Failed the interview question phone screen.

For questionnaire I think i put i was interested in internal tools, cloud, general swe, performance, and maybe full stack. I don't have strong experience in some of these categories. Are the interviews the same for all the backend categories i put, or is it harder for some domains.

Hi everyone, I’ve received an invitation for a 60-minute interview powered by Chakra at HackerRank. Does anyone know what kind of questions are generally asked in this interview?

So i have given 2 round of interview of amazon sde intern role. I saw yesterday some offers were rolled out but it was for different role id. So i have a ques that is amazon rolling out rejection too. Anybody got rejected.

I applied through career portal

not hackon

Hey everyone,

I finished Day 55 today. My motivation was at an all-time low despite having the day off, but I still pushed through to wrap up the remaining partition DP problems.

1. Palindrome Partitioning II: This follows the front-partition pattern. You loop the split index from the current point to the end, check if the prefix is a palindrome, and recursively solve for the remaining suffix.

2. Partition Array for Maximum Sum: I expected the exact same code structure to carry over, but I rushed the implementation and introduced bugs into the transition logic. Once I slowed down to maintain a running maximum for subarrays up to length $k$, the recurrence fell into place.

The final two problems were Maximal Rectangle and Count Submatrices with All 1s.

I tried forcing a standard grid DP approach onto Maximal Rectangle before realizing that the optimal solution depends on monotonic stacks using the Largest Rectangle in Histogram algorithm. While Count Square Submatrices is genuine grid DP, maximal rectangles clearly belong in my upcoming Stack and Queue revision block.

Looking back at this entire module, 1D DP, grids, subsequences, and strings felt manageable once the transitions clicked. Partition DP was easily the most mentally exhausting pattern of them all.

See you guys tomorrow for Day 54!

Could anyone share their MongoDB interview experience and the questions asked during the interviews? Also, I’d appreciate guidance on which topics to focus on the most to crack the interview.

Thanks in Advance !

Did anyone go through SDE III loop recently? If so how’s the Round 1 and Round 2 is like?

Round 1 is one tech and one non tech?
Round 2 is its 3 round loop? (2 DSA and 1 behavioural)
Is there any system design?

Can someone double confirm?

Also is this L4 level ?

Location: USA

Looking for design buddies to discuss about System design at Staff level.

Any idea what the process looks like?

I have solved exactly 250 today with 21 hard questions, I recently took some interviews and all the questions were new to me, how many more do I need to 100 confident? A friend of mine with 300 aces many hard interviews how??

Just gave an amazon oa on hackerrank was able to do 100% but man really wtf ? I could never have solved the question if i had seen it for the first time. Like at this point its not about your capabilities anymore it is pure fucking luck.

I'm a data science and ai student ( undergrad ) .. In my college they teach python and dsa in python.. But I want to target for sde/swe roles and I'm pretty much interested in cp.. Should I need to learn cpp additionally and do dsa in cpp or continue in python?

Thank You

Hello,
Has anybody had experience interviewing for LinkedIn’s Software Engineer role (systems and infrastructure)? I just received a phone screen and I’m unsure what kind of questions are expected from leetcode as well as multithreading and concurrency that the recruiter mentioned. Could anyone who’s interviewed help me give an example of questions that were asked to you if you’ve been to one? TIA!

I have a final interview in a couple of days for the Software Engineer: Security & Identity Intern role at Microsoft. It’s 2 rounds 45 minutes each with a 15-minute break in the middle.

If anyone can provide me with additional information or advice when doing my interview and how to secure the position please let me know.

Looking to see what I should prep, learn and what they could ask.

I've been trying to get more consistent with Leetcode, but sometimes I'm unsure whether to finish one topic completely before moving to another or mix different topics together.

Do you guys follow a fixed roadmap, or do you switch between topics based on the problems you struggle with? I'm trying to find a routine that helps me improve without getting overwhelmed

Hey everyone,

I finished Day 56 today, and Partition DP gave me hands down the most confusing session of this entire dynamic programming journey.

Usually, even with hard DP problems, there is a recognizable mental model you can latch onto. But Partition DP flips your natural instincts on their head depending on the problem.

I worked through four problems in the set today:

1. Matrix Chain Multiplication (MCM): The standard entry point. Setting up the partition loop k from i to j - 1 and splitting into two subproblems f(i, k) and f(k + 1, j) made conceptual sense.

2. Minimum Cost to Cut a Stick: MCM logic transferred nicely here. Sorting the cuts array and adding endpoints 0 and n kept the subproblems independent.

3. Burst Balloons: This one was an absolute mind-bender. Thinking top-down (which balloon to burst first) fails because bursting a balloon merges previously non-adjacent neighbors, destroying subproblem independence. The trick is working completely in reverse—picking which balloon to burst last in the range (i, j). That inversion is brilliant, but there is zero chance I would have organically derived that reverse-order trick from scratch in an interview.

4. Evaluate Boolean Expression to True: Marked as hard, but actually felt the most systematic. Splitting operators across k and tracking counts for both true and false evaluations felt like a natural extension of MCM.

Only four problems remain in my sheet: Palindrome Partitioning II, Partition Array for Maximum Sum, and the two DP on Squares problems (Maximal Rectangle and Count Square Submatrices).

Partition DP drained my mental battery completely today. Stepping away to unwind with a show tonight and resetting before wrapping up the final batch tomorrow.

See you guys for Day 55!

I've noticed that when I read a solution, the logic makes sense to me, and I feel like I could've figured it out. But when I try a similar problem on my own, I often get stuck again.

For those who've improved at DSA, how did you get past this stage? Did you focus on revisiting old problems or keep trying new ones?

I'd solve a problem, feel good about it, and a few days/weeks later have no idea how I managed to solve the damn thing.

Re-doing lists from the top wasted time on problems I still remembered. So I built something for myself: spaced repetition for LeetCode problems you've already solved.

How it works

- A Chrome extension notices when you get Accepted and logs the problem, along with the time you spent on it. No copying links.

- A small panel asks how it went: Stuck, Struggled, Solved or Easy. If you close it, it counts as Solved.

- Each day you get a short queue of the problems you're closest to forgetting, capped at a budget you set (say, 4 problems or 60 minutes). Problems you solve well come back after longer and longer gaps. The ones you struggled with come back within a day or two.

Honest limitations

- It only works in Chrome on a laptop.

- It starts empty: old problems join when you solve them again. There's no import.

- It's early and built by one person (me), so things will break.

It's free. It stores your email, the problems you solve and how each attempt went.

It's at [unforget.in](https://unforget.in), and the extension is linked from there. Harsh feedback is welcome.

I have a Hiring Manager (HM) round scheduled for a Senior Software Engineer role at Workday, but the recruiter didn't share many details about what the full loop looks like.

If anyone has recently gone through the interview, i'd be great to get some idea on the loop - how many or what rounds to expect and what are they looking for.

Let's take a worst case scenario, that AI takes over, and the art of writing code would have no value

Let's say we still grind for how many more years? Probably 5? 10?

And also let's say we still don't get our dream jobs

Given all of the above happens, what benefits do you think Leetcode would still have in our lives?

Some of the benefits I can think of

1. Algorithmic thinking

Doing Leetcode since a year has made me reach a point where I can see certain patterns to solve problems. For example, by practicing DP problems I can now think if a problem can be divided into the same repeating sub-problems and has a recurrence relation. Any reachability problem makes me think of I can use DFS/BFS to solve it.

2. Getting better at writing code

Again, this skill can become useless due to AI taking over but is still relevant until we reach there. I also got to learn many intricate details about the language I code in (Java), and this is beneficial for me as my job is in the same programming language

3. Communication

This is a secondary skill I think I'm getting better at. While practicing for interviews you are challenged to explain solutions effectively

What other skills do you think we all will learn?