r/LeetcodeChallenge • • 17h ago

STREAKšŸ”„šŸ”„šŸ”„ Day 10 did the question forgot to post it

1 Upvotes

r/LeetcodeChallenge • • 12h ago

DISCUSS Advice!

2 Upvotes

i am stuck at this rating man idk why, please suggest me something..


r/LeetcodeChallenge • • 13h ago

PLACEMENTS What is the best way to start the dsa and how much dsa will be enough for placement purpose

2 Upvotes

I have only 3 months left before semester exams. So somebody who had an idea how I would complete dsa and mern( mern mai kr lunga sath mai kuki web development jaldi smjh skta hu mai) dsa ke liye proper khuch smjh nhi aa rha logic aa rhe h but striver se padha toh vo cpp se krata h and mai java se hu , jab raghav garg se padha toh question mujhe khud hi krne h isliye thoda idea dedo koi , abhi tak mai randomly leetcode attempt kr rha tha and yes mujhe smjh aaye bhi question and solve bhi kiye h ache se


r/LeetcodeChallenge • • 15h ago

DISCUSS Finally reached Guardian!!

Post image
76 Upvotes

Last week's contest ratings are now updated. I got to 2143, and am officially a Guardian now. It took me ~ 1 year of consistent practice and upsolving contest questions to reach this.


r/LeetcodeChallenge • • 18h ago

DISCUSS Roughly 320 solved problems, but I couldn’t reliably re-solve them cold. How do you measure readiness?

4 Upvotes

How many problems in a Solved list could you solve from a blank editor, with someone watching?

A candidate had solved roughly 320 LeetCode problems but still froze halfway through implementations. Even problems from a few weeks earlier could be hard to derive again. The green checkmarks were hiding gaps in recall and explanation.

The candidate started checking more after Accepted: identify the pattern without a hint, explain the approach before coding, justify time and space complexity, find edge cases, and dry-run the implementation. Doing that with a clock running exposes different gaps from solving alone.

Review also changed. Opening an old solution and recognizing ā€œtwo pointersā€ felt easy, but didn't show whether the reasoning could be reconstructed. Re-solving from a blank editor did. Harder problems came back sooner; easier ones could wait a few days, then a week or two, then about a month.

The spreadsheet, notes, and calendar reminders eventually became another chore. A lighter routine was easier to maintain: a minute or two of reflection, a short note on the mistake, and a manageable daily review load that left room for unfamiliar patterns.

Real technical interview questions can supply fresh prompts for checking whether a pattern transfers. If applications are competing with practice time, Agent autoapply and application autofill can reduce repeated application paperwork.

What tells you you're ready to interview? How do you distinguish knowing a pattern from recognizing a problem you've already seen?

Disclosure: I operate PracHub and LandOffer.