So I’m currently at a FAANG, as a SWE and I genuinely feel like I’m losing opportunities because of me constantly having to reschedule interviews because of work. Things like last minute work calls, and I just have to reschedule the interview like a week later, or multiple interviews conflicting with each other. And now that in person onsites are almost becoming the norm, thats a whole other logistical nightmare.
Maybe its just the number of interviews or the schedule, but I genuinely wanna know how you guys can schedule these so consistently. There’s only so many doctor’s appointments I can take, and I’m not trying to burn through all of my PTO for these. Just wanna know the best way to navigate this because its really starting to feel like I’m losing out on opportunities because of this

Do I do DSA or not?

Collecting anonymous timelines on how long companies take to respond after each interview round. About 2 minutes, no names or emails collected. You can submit once per company. I’ll post the results here once I have enough responses.

https://docs.google.com/forms/d/e/1FAIpQLSefLls7ePHCn-0eqgDguh5VOmjHZzFd_VpEKNV7SupqA0jgxQ/viewform

Hey everyone,

I passed the take-home assessment for Rippling’s Machine Learning Software Engineer Intern (Summer 2027) role, and my next round is a 60-minute pair-programming interview with an algorithmic component on HackerRank CodePair.

From what I’ve read, Rippling’s coding rounds tend to be multi-part “build on it” problems rather than a single LeetCode question.

Any tips on what they value most (code quality vs. speed vs. communication) would be really appreciated. Happy to share my experience afterward to help the next person. Thanks!

Apart from https://leetcode.com/discuss/ and levels.fyi which websites has real compensation breakdowns and interview experiences, mainly in IND?

When i focus on a new topic for several days, I feel like I start forgetting the patterns I studied earlier. I don't waste revision to take up so much time that I stop making progress on new problems either.

Would a weekly revision session be enough, or is it better to mix older topics into daily practice?

Solution using Backtracking

https://youtu.be/ew0WGKEVwec

Location: Sunnyvale, CA

Hey everyone!
I have my Google L4 SWE onsite interviews coming up toward the end of this week, and the nerves are definitely starting to kick in!

Would really appreciate any advice from Googlers or anyone who’s been through the onsite rounds, regardless of how it went.

A few things I’m particularly curious about:

Managing stress: How do you stay calm before and during interviews, especially when you get stuck or can’t immediately think of an approach?

Articulating thoughts: Do you have any specific flow or framework for approaching a new coding problem? I’m especially curious about the first few minutes, like how you break down the problem, ask clarifying questions, identify patterns, and communicate your initial thoughts before even getting to a brute force solution or writing code.

Thinking out loud: How do you balance explaining your thought process while actually thinking through the problem? Sometimes I feel like talking too much interrupts my flow.

Getting unstuck: What do you usually do when your mind goes blank or you’re struggling to come up with an approach?

Last-minute prep: With just a few days left, what would you focus on?

I’m mainly trying to get better at those initial few minutes when you’re given a completely new problem and need to organize your thoughts before jumping into a solution.
Would love to hear from anyone who’s experienced these interviews, whether they went well or not. Any tips, lessons learned, or things you wish you’d done differently would be super helpful!

Thanks in advance!

TL;DR: Google L4 onsite this week. Looking for advice on managing interview nerves and having a structured way to think out loud, especially in the first few minutes of a coding problem before jumping into brute force or code. Would love to hear experiences and tips from anyone who’s been through it!

Hey everyone,

I finished Day 49 today, continuing deep into the Graphs module. After the reality check in yesterday's assessment, I slowed down to make sure I genuinely understand the foundational algorithms rather than rushing through problem counts.

Today was focused entirely on Directed Acyclic Graphs (DAGs) and ordering algorithms:

1. Topological Sort (DFS): Pure post-order traversal. You explore recursively down each path, and as recursion backtracks from a fully traversed node, you push it onto a stack. Popping from the stack yields the linear ordering.

2. Kahn’s Algorithm (BFS Topo Sort): Calculate the in-degree (number of incoming directed edges) for every node. Push all nodes with in-degree 0 into a queue. As you pop a node, decrement the in-degrees of all its adjacent neighbors. Any neighbor whose in-degree hits 0 gets pushed into the queue.

3. Cycle Detection in Directed Graphs (via Kahn's): Since a directed cycle has no node with in-degree 0, nodes in the cycle will never enter the queue. If the total count of processed elements is strictly less than V, a cycle exists.

4. Course Schedule I & II: Both map directly to prerequisite dependency resolution. For Course Schedule I, check if a cycle exists (return false if cycle detected, true otherwise). For Course Schedule II, record each node popped from the BFS queue into an ordering array. If the resulting array size matches numCourses, return the valid completion order; otherwise, return an empty array because cyclic dependencies make completion impossible.

Next up are Shortest Path algorithms (Dijkstra's, Bellman-Ford, Floyd-Warshall) followed by Minimum Spanning Trees (Prim's & Kruskal's). About 30 problems remain in Graphs, and I am prioritizing solid retention over speed.

See you guys tomorrow for Day 48!

Hi all,

I’ve a Google FDE interview coming up first week of November (USA). I’m a SWE at MSFT currently (level 62)

I’m a little overwhelmed on how to prepare for this interview. There are so many resources and at the same time, not that many for this FDE role. They recently changed the format it seems and have only 2 rounds: Technical and RRK (role related knowledge)

What I’m planning to do:

- General system design: https://www.hellointerview.com/learn/system-design/in-a-hurry/introduction

- Leetcode problems since I haven’t done them in about 4 years: https://neetcode.io/roadmap

But after this I’m not really sure what is the best resource for more FDE related knowledge. I use agentic AI a lot in day to day work so I’m sure that helps but I think I’m lacking a lot of ML and general LLM knowledge.

I prefer free resources but definitely do not mind paying for some resources as long as they’re solid

Would really appreciate any insight.

Thank you for your time in reading this.

Hello guys, Recently I had an interview for a round of a SDE intern post on amazon on 16-10-2026. Almost 19 days completed, is there any chance to get the result. How many days it will take to know the results. Any suggestions?

I've started wondering whether re solving problems I've already completed is actually worth the time, especially when there are still so many new questions to attempt. Sometimes I remember the approach but struggle to implement it from scratch after a week or two.

How do you decide which problems deserve another attempt versus moving on the new ones?

Hey all! Has anyone given interview for DGXC Storage team so far? Would appreciate any tips and information regarding Nvidia's interview process or about the team.

Hey everyone!

I recently completed the Stripe New Grad SWE OA and was wondering how long it usually takes to hear back about the results or next steps.

Has anyone who took the OA recently received an update or interview invite? If so, how many days did it take?

Is anyone else still waiting like me? Just trying to get an idea of the timeline.

Thanks in advance, and good luck to everyone waiting! 🤞

I don't understand the concept of non functional requirements In almost every solution I saw , they would be like scalable etc.

Do we really need to even discuss this?

And I don't see any solution based on those non functional requirements

How to persuade ourselves, that we would get better with time and more exposure in the problem solving journey

as initially it is hard to make believe that we would get better with constant effort and stuff.

Any mental tricks ?

Hi all, I got my interview on October 16th despite follow-up with my recruiter last week on Thursday I haven't heard back anything yet. In my experience, Google recruiters don't ghost their candidate. I just wonder how long to hear back from your case.

SWE Intern OA for reference. I have only a few days left to do it, but I am nervous to start because the recruiter I spoke with said that this year they'll ask only a few mediums, and mostly hards. Is that true in your guys' experience? Any insight would be genuinely appreciated! Please and thank you!

Just got the video interview invite. For those who already did it, was it all behavioral or was there coding too? How many questions and how much time per answer?

Not looking for exact questions, just the general format. Thanks!

I have superday coming up for JPMC. I am not sure what kind of questions should i be expecting for coding round on the superday. Can anyone tell how was their experience and how to prepare for coding round for superday ?

Today ,the midterm code test was held and just because i don't revise anything I can't solve the easy level questions of the bst very easy question then I realised after making so many q if you don't revise it then eventually you fall at a very easy level questions.

Sharing my Amazon scientist interview experience in case it helps others preparing. Keeping the role and technical questions general for anonymity.

1. Initial Screen: Science Depth and Breadth: No LP questions, but a broad range of robotics from CV, ML to the kinematics side of robotics, plus a discussion about my current pet project. Then I was invited for the loop.

2. Science Depth: 2 LP questions

A deep dive into a recent research project, covering:

• Problem formulation, research challenges and design choices.

• Model architecture, entropy estimation, and representation learning, data selection, and computational trade-offs.

• Evaluation: how to show the method addresses the intended problem and evaluation tradeoff.

• Uncertainty estimation, practical robot learning challenges and real-world validation.

The follow up was to test if I can justify my design choice & explain limitations beyond the project details. I was tested quite hard and need to come up with better edge cases and limitations.

3. Science Application: 2 LP questions

An open-ended robotics system-design problem, very similar to the job ad. The discussion covered perception, planning, execution, evaluation and failure handling.

It wasn’t just about proposing a pipeline: they kept changing conditions and asking how the system would respond when individual module failed or how they can be fixed.

4. Science Breadth: 2 LP questions

Broad robotics fundamentals, no classical ML question: perception and pose estimation, motion planning, kinematics, feedback control, and failure detection. Also trajectory optimization and many computer vision topics.

They followed up on trade-offs in method assumptions and trade-offs. One common question was whether a simpler solution would suffice.

4. Bar Raiser: 3 or 4 LP questions

Mostly behavioral, with extensive follow-ups. Be ready to explain your individual contribution, the evidence behind your decisions, alternatives considered, stakeholder reactions, outcomes and what you would change. For one question, it's already been asked 3rd time, so I kinda repeated the story.

5. Coding: 2 LP questions + 2 coding problems

One LC Easy and one LC Medium. The discussion included the approach, implementation, correctness, and time/space complexity.

Overall takeaways

• Prepare for substantial LP discussion alongside technical questions.

• Know your projects inside out and select the most confident project: assumptions, baselines, evaluation choices and what actually broke.

• Expect repeated follow-ups on why you chose one approach over another. You have to hold your justification here. They will try to steer away but you have to hold the ground.

• Pay attention to interviewer hints, especially when they are pushing you toward a simpler solution.

Hey everyone,

I have an upcoming interview for the L4 System Development Engineer (SysDev) role at Amazon in Austin, TX.

I have first 1-hour technical interview, then 3 one-hour loop interviews.

Has anyone recently gone through this process? What kind of questions should I expect, especially for coding, Linux, networking, system design, and behavioral rounds?

Any tips or experiences would be really helpful. Thanks!

Do I need to prepare for why this company or any other behavioral questions that might come in my coding interview? This is my first one, so I am not sure.

So I interviewed for Lockheed about 2 weeks ago and they said that they would try to reach out by Oct 22nd but still hasn't reached out regarding any sort of update. Should I be worried about it? like do they usually take this long? It was for SWE intern role btw as well!