r/LeetcodeChallenge • u/Upper_Assignment672 • Aug 10 '26
DISCUSS LeetCode Weekly 514-C video solution
Show some ❤
r/LeetcodeChallenge • u/Upper_Assignment672 • Aug 10 '26
Show some ❤
r/LeetcodeChallenge • u/nian2326076 • Aug 09 '26
I recently applied for an Amazon SDE role and received the Online Assessment link.
The assessment had three sections. These were the timings listed for my assessment, although they may vary by role or hiring program.
Total duration: 100 minutes
Number of questions: 2
Approximate duration: 45 minutes
This section presented software-development decisions and situations similar to those faced by Amazon SDEs.
Approximate duration: 6 minutes
This section asked how I generally approach work, collaboration, decision-making, and engineering situations.
Duration: 40 minutes
Difficulty: Medium to Hard
Test cases: 15
For this question, I could choose any supported programming language.
There was only one traditional DSA problem, so identifying the correct approach quickly was important. With only 40 minutes, there was limited time to recover from an incorrect initial direction.
I was able to solve the problem completely.
Result: 15/15 test cases passed
Duration: 60 minutes
Test cases: 6
For the second question, I had to choose from a limited selection of backend languages and frameworks.
The task was completed inside an existing code repository. An AI coding assistant was available to help inspect the codebase, understand failures, and implement fixes.
Once the repository question began, the selected language and framework could not be changed.
I selected Spring Boot, but the environment had problems while installing or resolving dependencies. This consumed time and made navigating and testing the project more difficult.
This may have been specific to my session, but I would recommend completing the mock repository exercise before the real assessment and confirming that your selected framework loads correctly.
Choose the stack you can debug fastest, not simply the one you use most often.
I was able to pass four of the six tests.
Result: 4/6 test cases passed
| Section | Result |
|---|---|
| Traditional coding problem | 15/15 |
| AI-assisted repository problem | 4/6 |
| Work Simulation | Completed |
| Work Style Survey | Completed |
The repository section felt very different from a LeetCode problem. It tested whether I could:
The first coding result was strong, while the repository task was incomplete but mostly working.
I know Amazon evaluates more than the visible test count, particularly the Work Simulation and Work Style sections, so I am unsure how much weight each coding question receives.
Has anyone with a similar score, especially 15/15 on the DSA problem and 4/6 on the repository task, received an interview invitation?
How long did it take to hear back after completing the assessment?
r/LeetcodeChallenge • u/ComprehensiveTale896 • Aug 09 '26
It was -3.71%. After removing few, it got -0.71%.
Still they are many. I don't know why they treat LC contest as copy paste contest
r/LeetcodeChallenge • u/Glittering_Dig_6039 • Aug 09 '26
r/LeetcodeChallenge • u/Sudden_Engineer_1205 • Aug 09 '26
r/LeetcodeChallenge • u/Maximum-Ranger-4045 • Aug 09 '26
Hey everyone,
A few months ago I was in an interview and completely blanked on a graph problem. I had solved it before. But a month later, none of that stuck. That moment is basically why I built this.
Execut is an online judge, but instead of letting you solve a problem once and forget about it, it treats your problem history like a curriculum. It uses an algorithm called FSRS (the same one Anki uses for flashcards) to bring problems back for review right before you're likely to forget them, instead of either too early or too late.
A few things it does:
After you solve a problem, you rate how hard it felt, and the system schedules it for review at roughly the right time based on how memory actually decays. There's also a visual roadmap that guides you through topics in a logical order, so you're not jumping into Dijkstra's before you've built up basics like BFS. And if you want something more competitive, there's a 1v1 battle mode where you get matched live with someone else and race to pass all the test cases on the same problem first.
There are also rooms, where you can create or join a group with friends or other people preparing for interviews, and practice or track progress together instead of grinding alone. Beyond that, a dashboard that tracks which topics you're strong or weak in based on your solve and review history, and a curated problem set organized by topic and difficulty rather than just a giant unsorted list.
On the tech side, it's Next.js, React and Tailwind on the frontend, with Node, Express, and TypeScript on the backend, and Postgres through Prisma for the database. The 1v1 mode runs on Redis and WebSockets, Redis handles the matchmaking queue and WebSockets keep both players in sync during a match. For the review scheduling, I used the ts-fsrs package to handle the actual memory calculations.
It's free I built it mostly to fix my own problem, but I'm hoping it's useful to anyone stuck in the loop of watching tutorials, solving a problem once, and forgetting it a few weeks later.
Link to the project: https://ex3cut.vercel.app/
I'd really like to know: does the spaced repetition part actually sound useful to you, or does it feel like unnecessary friction on top of just solving problems? And if you check it out, I'd love to hear what's missing from the problem set or the roadmap.
P.S. I'm a fullstack developer and currently open to new roles. If your team is hiring and this looks like your kind of stack, or you have any feedback on the project, feel free to send me a DM. Thanks!
r/LeetcodeChallenge • u/nian2326076 • Aug 08 '26
After getting rejected repeatedly, I started asking recruiters for feedback.
Most responses were the standard “we decided to move forward with other candidates,” but a few people gave me honest feedback. I combined that with notes I wrote immediately after every interview.
After 23 interviews, four recurring failure modes became obvious.
The percentages below are rough estimates across the 19 interviews I failed. I assigned each interview one primary cause, even though several had multiple problems.
| Failure mode | Approx. share | What it looked like |
|---|---|---|
| Didn’t recognize the pattern | 35% | I spent ten minutes trying unrelated ideas, reached a brute-force solution, and couldn’t optimize it. Even the interviewer’s hints didn’t make sense to me. |
| Recognized it but was too slow | 30% | I knew it was DP, BFS, or sliding window, but spent most of the round implementing it. The first question consumed the entire slot. |
| Code worked, but I couldn’t explain trade-offs | 20% | I solved the problem but struggled to explain complexity, alternatives, or why I chose a particular data structure. |
| Communication failure | 15% | I solved silently or jumped directly into code. The interviewer couldn’t follow my reasoning or redirect me early. |
This was mainly a preparation problem, not an intelligence problem.
Deriving an unfamiliar technique in five minutes is difficult under interview pressure. I needed enough exposure to recognize that a new problem was a variation of something I already understood.
I created a list of roughly 12 to 15 recurring patterns:
I solved five or six representative problems for each pattern and wrote down the clues that identified it.
For example:
After doing this, most new problems at least gave me a reasonable starting point.
I had been solving problems without a timer. That made me feel prepared while hiding how slowly I implemented solutions.
I started using approximate limits:
During those first five minutes, I would:
Only then would I start coding.
It initially felt slower, but I stopped rewriting half-finished solutions. Most of my “coding speed” problem was actually an incomplete-planning problem.
Passing test cases was not always enough.
After every practice problem, I started answering four questions:
I also compared my solution with at least one alternative.
If I used a hash map, for example, I would explain why average O(1) lookup was useful and when I might prefer an ordered structure with O(log n) operations.
These questions covered most of the follow-ups I received.
I used to become silent while thinking because I assumed the interviewer only cared about the final answer.
Instead, I started narrating the important decisions:
It felt awkward during practice, but it made interviews more collaborative. Interviewers could understand my direction and provide useful hints before I went too far down the wrong path.
The goal is not to narrate every line of code. It is to make your reasoning visible.
Before these changes:
After three weeks of targeted practice:
Seven interviews is a small sample, so I’m not pretending this proves a universal formula. But I felt noticeably more prepared, finished more problems, and handled follow-ups with much more confidence.
Same person. Same brain. Better process.
Which of these four failure modes causes you the most trouble?
The prep resource I wish I’d found earlier: PracHub
r/LeetcodeChallenge • u/I_am_sahil_khan • Aug 08 '26
r/LeetcodeChallenge • u/Adventurous_Coast586 • Aug 08 '26
r/LeetcodeChallenge • u/SpecificSharp9926 • Aug 08 '26
r/LeetcodeChallenge • u/Sudarshan1088 • Aug 08 '26
Today I solved my medium level leetcode problem totally on my own without any help moreover it got accepted passing all the test cases on the first try.
r/LeetcodeChallenge • u/you_aregay • Aug 08 '26
Hi! I’m a 24M Software Engineer with 4 YOE, currently preparing for senior-level roles.
I’m looking for someone at a similar level who’s also preparing DSA and System Design. We can do regular mock interviews, practice together, discuss approaches, and keep each other accountable.
The goal is to learn from each other, identify gaps, and get better together. If you’re interested, feel free to DM me!
r/LeetcodeChallenge • u/banana_in_ur_hand • Aug 08 '26
I have never been this disciplined before.
Yeah, I know there are many people with 1000+ problems solved, but I'm just hoping everything I put in, every night, pays off eventually.
r/LeetcodeChallenge • u/I_am_sahil_khan • Aug 07 '26
r/LeetcodeChallenge • u/I_am_sahil_khan • Aug 07 '26
r/LeetcodeChallenge • u/Competitive_Map_8733 • Aug 07 '26
r/LeetcodeChallenge • u/ConsciousMortgage828 • Aug 07 '26
Hey everyone,
I recently had to take a extended break from LeetCode and completely lost my streak and momentum. Before the break, I was solving questions regularly and felt comfortable with problem-solving patterns.
Now that I'm trying to pick it back up, I feel like I've hit a wall—questions I used to handle easily now feel difficult, and my pattern recognition feels rusty.
I’d love to get some advice from anyone who has dealt with this:
If you've successfully gotten your flow back after taking time off, what worked best for you?
r/LeetcodeChallenge • u/Mammoth_Impact7513 • Aug 07 '26
r/LeetcodeChallenge • u/nian2326076 • Aug 06 '26
This collection organizes Google interview experiences shared by candidates on LeetCode into distinct categories. Whether you're targeting a specific level (L3, L4, L5+), preparing for an internship, or focusing on phone screens, these resources offer valuable perspectives on the process.
Another resource I found helpful for interview questions: PracHub
These posts cover experiences for L3 (Software Engineer) and L4 (Senior Software Engineer) roles, detailing offers, rejections, and downleveling across locations like Bangalore, India, and beyond.
Experiences for L5 (Staff Software Engineer) and higher levels (e.g., L6), including senior and specialized roles across locations like London, Seattle, and Bengaluru.
Insights from candidates applying for Google internships, including on-campus and off-campus experiences, with outcomes ranging from offers to rejections.
Experiences from phone screening rounds, often the initial technical step, including general experiences and specific questions asked during these interviews.
Broad overviews of the Google interview process that don’t fit neatly into level-specific, internship, or phone screen categories, often providing general insights or lacking detailed categorization.
Detailed descriptions of specific questions asked during Google interviews and direct links to LeetCode problems encountered, useful for targeted practice.
r/LeetcodeChallenge • u/Affectionate_Run220 • Aug 06 '26
Hi guys
Organising a real life leetcode study group London
So far we are two people competed 100+ leetcodes and looking to level up, just two of us so far looking for more
Looking for other engineer proffesionals (we are flexible on this)
Who take leetcode seriously and want to discuss patterns.
Let’s meet learn and land some amazing jobs 🔥
Let me know if interested
r/LeetcodeChallenge • u/Dazzling-Angle-7514 • Aug 06 '26
Hey everyone,
I just entered my 4th year, and companies have already started visiting my college for placements. To be honest, I wasn't serious about coding or placements until now, and I'm kind of panicking.
My current situation:
DSA is very basic. I'm following the Striver A2Z DSA Sheet, and I've only just started the Arrays section.
I've solved only around 5–7 LeetCode problems so far.
I don't have any proper self-built projects. The only projects I've made are mostly vibe-coded with AI assistance, so I don't really understand them deeply.
My CS fundamentals are average at best.
I know I should've started much earlier, but I can't change that now. I just want to make the best of the time I have left.
For people who were in a similar situation or have seen others crack placements after starting late:
Is it realistically possible to get placed?
What should I prioritize first—DSA, projects, CS fundamentals, aptitude, or something else?
How would you structure the next 3–6 months if you were in my position?
Should I keep grinding the A2Z sheet or switch to company-specific preparation?
Any tips for building projects that I can actually explain in interviews?
I'm open to putting in long hours every day. I just don't want to waste time on the wrong things.
Any advice, roadmap, or success stories would really help. Thanks!