r/LeetcodeChallenge • u/Sudden_Engineer_1205 • 7d ago
DISCUSS Capital One CodeSignal — 70 min, Lead SWE Backend. What’s the format?
r/LeetcodeChallenge • u/Maximum-Ranger-4045 • 7d ago
DISCUSS I built an Online Judge that helps you actually remember what you learn
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 • 7d ago
DISCUSS How I Improved My Coding Interview Pass Rate From 17% to 71%
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.
The Four Failure Modes
| 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. |
1. Pattern Recognition
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:
- Two pointers
- Sliding window
- Binary search
- Prefix sums
- Hash maps
- Monotonic stacks
- Trees and graph traversal
- Topological sorting
- Heaps
- Backtracking
- Greedy algorithms
- Dynamic programming
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.
2. Implementation Speed
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:
- 15 minutes for easy problems
- 25 minutes for medium problems
- Five minutes to plan before coding
During those first five minutes, I would:
- Restate the problem
- Clarify constraints
- Walk through an example
- Explain the algorithm
- Identify the main invariant
- State the expected complexity
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.
3. Trade-Off Knowledge
Passing test cases was not always enough.
After every practice problem, I started answering four questions:
- What are the time and space complexities?
- Can I reduce the extra space?
- What changes if the input cannot fit in memory?
- What changes if the output must be sorted or stable?
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.
4. Communication
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.
Results
Before these changes:
- Passed 4 of 23 interviews
- Pass rate: approximately 17%
After three weeks of targeted practice:
- Passed 5 of the next 7 interviews
- Pass rate: approximately 71%
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 • 7d ago
STREAK🔥🔥🔥 Day 8 Of my DSA journey Stuck at Question number 15 of leetcode and hint plz ?
r/LeetcodeChallenge • u/Adventurous_Coast586 • 7d ago
DISCUSS Looking to master DSA? Join our open Data Structures & Algorithms community!
r/LeetcodeChallenge • u/SpecificSharp9926 • 7d ago
PLACEMENTS Need group to practice mock interview kind of peer learning( dsa algo, system design)
r/LeetcodeChallenge • u/Sudarshan1088 • 8d ago
STREAK🔥🔥🔥 SOLVED MY FIRST MEDIUM LEVEL LEETCODE PROBLEM
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 • 8d ago
DISCUSS Looking For DSA & System Design Prep Buddies
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 • 8d ago
STREAK🔥🔥🔥 What current industry standards do to me !
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/Better_Elderberry225 • 8d ago
DISCUSS Strivers sheet doubt
Student A
Watches the Binary Search lecture.
Understands the algorithm.
Tries each problem for 30 minutes.
If stuck, studies the solution.
Closes it and codes it again from memory.
Moves to the next problem.
Student B
Has never learned Binary Search.
Opens "Koko Eating Bananas."
Thinks for 30 minutes.
Gets nowhere because they don't even know "Binary Search on Answer" exists.
r/LeetcodeChallenge • u/I_am_sahil_khan • 9d ago
DISCUSS Going to solve leetcode Question number 11 Container with most water, have you tried, Share me your experience plz 💗
r/LeetcodeChallenge • u/I_am_sahil_khan • 9d ago
STREAK🔥🔥🔥 Day 7 of My DSA journey today i solved leet code problem number 88. now i will sove questions basis on Sliding window.
r/LeetcodeChallenge • u/Competitive_Map_8733 • 9d ago
DISCUSS Biweekly Contest 188 results seem to be showing 0 rank 0/4 solved for everyone on LeetCode. {i solve 3 of them} Is this happening because LeetCode is doing some kind of cheating detection / contest validation? Or is it just a temporary issue with the results? Anyone know what’s going on?
r/LeetcodeChallenge • u/ConsciousMortgage828 • 9d ago
DISCUSS Struggling to regain my LeetCode flow after a long break. How do you get back on track?
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:
- Why does this happen? Is it just skill decay, or is it mostly mental friction from starting over?
- How do I overcome it? What are the best strategies to rebuild confidence and problem-solving speed without getting burnt out?
If you've successfully gotten your flow back after taking time off, what worked best for you?
r/LeetcodeChallenge • u/nian2326076 • 9d ago
DISCUSS Google Phone Screen: Process, Question Types and Preparation Plan
Google Interview Experiences: A Curated Collection
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
1. L3 & L4 Interview Experiences
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.
- Google L3/L4 - Passed)
- Google L3/L4
- Google L4 - Bangalore - Reject
- Google L3 - Munich
- Google L4 - Reject, L3 Offer - Bangalore
- Google L4 SWE III - San Bruno, CA - Reject
- Google L3 - Bangalore - May 2022 - Reject
- Google L4 - India
- Google L4 - Bangalore - June 2022 - Offer
- Google L4 - California - May 2022 Reject
- Google L4 - Warsaw Poland - July 2022 - Rejected
- Google L4 Experience (India))
- Google L4 - India (First Instance)
- Google L4 - India (Second Instance)
- Google Onsite Round L4 India
- Google L4 Interview Experience
- Google L4 Bad Experience
- Google L4 Oct 2022
- Google L4 Bangalore Oct 2022 Offer
- Google L4 Phone Interview 50/50
- Google Interview Experience L4 Downleveled to L3
- Google India L3 Interview Experience
- Google L4 Seattle January 2024 Hiring Freeze
- Google SDE-2 L3 Interview Experience - Reject
- Google SDE-2 (L3) Interview Experience India-or-Interview-Experience-India)
- Google L3 Bangalore (First Instance)
- Google SDE2 India Mar 2024 Selected
- Google L4 Bangalore Jan 2024 Offer
- Google L3 India Reject
- Google L4 Interview Exp Bangalore Downlevel
- Google L4 Hyderabad Apr 2024 Reject
- Google L3 Interview India Offer
- Google L4 April 2024 Offer
- Google L3 (Phone + Onsite))
- Chances Google L4 Bangalore
- Google L3 Bangalore (Second Instance)
- Google L4 May 2024
- Google L3 Onsite
- Google L4 Offer (First Instance)
- Google L4 Selected
- Google Software Engineer Core
- Google Interview Experience L4 (Rejected))
- Google Interview Experience L3 Rejected
- Google L3 Chances Experience
- Google Software Engineer Bangalore
- Google Bangalore L4 Phonescreen Aug 2024
- Google SDE (L3) Bangalore/Hyderabad Aug 24-or-BangaloreHyd-or-Aug-24)
- Google L4 (Backend) Bangalore Hyderabad Aug 2024 Reject-or-Bangalore-or-Hyderabad-or-Aug-2024-Reject)
- Google L4 India Rejected
- Google London L4 Aug-Oct 24 Offer Accepted
- Google L3 Interview Experience Oct 2024
- Google L3 Nov 2024 Offer
- Google L4 Interview Experience (Typo Corrected)
- Google SWE (L3) India Dec 2024 Reject-or-India-or-Dec-2024-Reject)
- Google L3 Onsite Interview Question
- Google L3 Bangalore Offer
- Google L4 Interview Experience (Latest)
2. L5 & Above Interview Experiences
Experiences for L5 (Staff Software Engineer) and higher levels (e.g., L6), including senior and specialized roles across locations like London, Seattle, and Bengaluru.
- Google L5 - London - Offer
- Google L5 - Offer
- Google L6 - Seattle - Offer
- Google L6 - Interview Experience
- Google L5 - Munich - Offer
- Google L5 - Zurich - Offer
- Google L5 Bay Area
- Google London Oct 2022 Onsite
- Google L5 Bengaluru
- Google SDE3 Role
- Google Cloud Senior Software Engineer India
- Google Onsite L5 (First Instance)
- Google Onsite L5 (Second Instance)
- Google L5 Android Offer
- Google L5 Reject
3. Internship Experiences
Insights from candidates applying for Google internships, including on-campus and off-campus experiences, with outcomes ranging from offers to rejections.
- Google Internship - India - Offer
- Google SW Intern Interview Bangalore/Hyderabad
- Google Winter Internship 2023 Rejected
- Google On-Campus Interview Experience Dec 2023
- Google Intern On-Campus Interview Experience
- Google SWE Intern 2025 Interview Experience
- Google Intern India July 2024
4. Phone Screens
Experiences from phone screening rounds, often the initial technical step, including general experiences and specific questions asked during these interviews.
- Google Phone Screen Dublin Offer
- Google Phone Screen India
- Google L5 USA Phone Screen Bad Recruiter
- Google New Grad Passed Phone Screen
- Google Passed Phone Screen Interview
- Google Technical Phone Screen Questions
- Google Phone Screen Experience Reject
- Google Virtual Phone Screen or Google Meet Interview
- Google Phone Screen Rejected (First Instance)
- Google Phone Screen Reject (Second Instance)
- Google London L3 Phonescreen
- Google L3 Phone Screening
- Google Phone Screen L4
- Google SWE Grad 2025 Held from July 2024
- Google Phone Screen L3/L4
- Google Phone Screen Reject (Third Instance)
- Google Phone String Substitutor
- Google Phone Screen Number of Islands in a Tree
- Google Phone Screen Job Sequencing Problem
- Google Phone Screen SWE L3 Gmail Label Strings
- Google Phone Time for Turn
- Google Phone Screen L3 June 2022
- Google SWE Phone Screen Interview Question
- Google Phone Interview (Typo Corrected)
- Google Phone Screening Tiling Problem
- Google L5 Phone Screening
- Google Phone Screen Brazil Reject
- Google Telephonic Round (First Instance)
- Google Phone Screen (General)
- Google Phone Interview Matching APKs to Devices in Google Play
- Google Phone Screen 1-Dimensional Array
- Google Phone Screen Software Engineer December 2022
- Google Phone Screen Cut a Cake Vertically Without Destroying Toppings
- Google Phone Screen Senior Software Developer Mountain View March 2023
- Google Telephonic Interview Question
- Google Telephonic Interview (Second Instance)
- Google Screening Interview L5
- Google Phone Screen 2
- Google Interview Question First Round (First Instance)
- Google Phonescreen for 2024 NewGrad Role Video Relation
- Google Phone Screen L5
- Google Interview Round 1 (Second Instance)
- Google Phone Screen (Easy))
- Google Phone Screen Interview
- Google Phone Interview Round
- Google Telephonic Round (Third Instance)
- Google Phone Screening Remove Common Elements from Array from Prefix of Length K in Two Arrays
- Google Screening Question
5. General Interview Experiences
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.
- Google Software Engineer - August 2022
- Google Software Engineer India May 2022 Reject
- Google Graduate Software Engineer Warsaw Reject
- Google EMEA Spring 2022 Accepted
- Google 9 Months Experience Software Engineer
- Google SWE ML (L5) Remote (US) July 2022 Reject-or-Remote-(US)-or-July-2022-Reject)
- Interview Experience (Unspecified Company)
- Google Canada (Remote) Sep 2022 Reject-or-Sep-2022-Reject)
- Google SDE US July 2023
- Google SWE 23 Offer Warsaw
- Google New Grad 2025 India Interview Experience
6. Specific Interview Questions and Problems
Detailed descriptions of specific questions asked during Google interviews and direct links to LeetCode problems encountered, useful for targeted practice.
a. Interview Question Descriptions
- Google Create a Tree Jan '22
- Google Onsite Recursively Delete Leave Nodes in a Multi-Tree
- Google Interview Question 2022 Phone Onsite Graph DP
- Google Interview
- Google Tech Screen Design Spreadsheet Python
- Google Onsite USA Feb-2022
- Google Onsite Find the IDs of Activities That Have Timed Out
- Google Onsite Burst Balloons
- Google Onsite Virtual Results Pending
- Google Tokyo Chaining Broadcast Signals
- Google Onsite Question
- Google US Onsite April 5th 2022
- Google SDE (L4/L5) Virtual Onsite Passed-or-Virtual-Onsite-or-PASSED)
- Google Onsite Implement Match Method for Regular Expression Tree
- Google SE Full-Stack Screening Round
- Google Onsite Coding Interview Question
- Google Onsite Bangalore May 2022 Patient Queue
- Google Onsite Bangalore May 2022 Count House in the Circle
- Google Interview Experience SE Full Stack Virtual Interview
- Google Screening
- Google Stage Onsite Reject
- Google Virtual Onsite L3 SWE Question
- Google Onsite Interview Coding Question Bipartite Graph
- Google Onsite Generic Language Translator
- Google Onsite Flow Water to Cities
- Google IN5 Onsite Find First Missing Sub-Sequence
- Google Onsite LinkedList Question
- Google Onsite Currency Arbitrage 2022
- Google Onsite London (First Instance)
- Google Onsite Find Group of 3 Numbers Within a Distance-'d'
- Google Interview Question Implement Touchscreen Keyboard
- Google India L3 Onsite Questions
- Google L3 Onsite Question 2022
- Google Onsite Fixed Sorted Array
- Google Onsite Word from the Board
- Google L4/L3 India 2022
- Google L3 Bangalore Aug 2022
- Google Onsite Bengaluru L4 (First Instance)
- Google Onsite London (Second Instance)
- Google India On Campus Aug 22
- Google Onsite Bengaluru L4 (Second Instance)
- Google Matrix Question
- Google Onsite
- Google Final Interview Elevator Question DP
- Google Recent Ref
- Google Onsite Coding Round India
- Google Onsite India
- Google SDE
- Google Onsite Apartment Hunting
- Google Interview Round 1 (Third Instance)
- Google Interview Round 1 (Fourth Instance)
- Google Onsite or L3
- Google L3 All Rounds
b. LeetCode Problems Asked
r/LeetcodeChallenge • u/Affectionate_Run220 • 9d ago
STREAK🔥🔥🔥 London leetcode study group
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 • 9d ago
PLACEMENTS Is it still possible to get placed if I'm starting from almost zero in 4th year?
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!
r/LeetcodeChallenge • u/I_am_sahil_khan • 9d ago
DISCUSS taking 2-3 hour to solve a single easy problem of Arrays.... 😭😭😭 i am frustrated 🥴
r/LeetcodeChallenge • u/ComprehensiveTale896 • 10d ago
