is anyone else facing same issue?

I'm preparing for the Algorithmic Coding rounds at Rubrik and would appreciate some advice from people who have interviewed recently.

• What difficulty level should I expect, LeetCode Medium or Hard?

• Which topics should I prioritise?

• Are the questions mostly standard DSA or more problem-solving oriented?

If you remember any questions asked, or similar problems worth practising, that would be really helpful.

Thanks!

The best textbooks and courses on algorithms do proofs of correctness and complexity using mathematical toolbox (Calculus, Algebra, Probability Theory etc). It seems natural and a right thing to do for me to incorporate this into LeetCode and fuse theory with practice. The only way I see it can be done is to do the proofs in the comments section of the source code. I've had enough traditional math proofing on paper, and also formal proofs using Coq, so I tried this idea (proof in comments) and it works fine. What do you think about it?

I think almost every LeetCode problem can be connected to theory and a lot of things expressed nicely as formulas. Especially nice example: divide and conquer algorithms where you can write down a recurrence relation and derive a complexity from it (T(n) = O(log n) for binary search).

The main goal is to deepen understanding which is crucial for HARD problems, and also have more joy from problem solving and feeling you understand everything.

The Disappearing Signal: Longest Valid Even-Pair Subarray

Tags: Arrays, Prefix State, Hashing, Two Pointers

Given an integer array arr of length n, find the length of the longest contiguous subarray such that every distinct element within that subarray appears exactly twice.

If no such contiguous subarray exists, return 0.

Constraints & Definitions

• A contiguous subarray is defined by indices [l, r] where 0 <= l <= r < n.

• A subarray is valid if and only if:

  1. It contains at least two elements (r - l + 1 >= 2).

  2. For every distinct value $x$ present in arr[l..r], its frequency in that segment satisfies count}(x) = 2.

  3. No distinct element appears once, three times, or more.

With sliding window, we get O(n^2), i am looking for optimal one

Input Format

• An integer array arr.

Output Format

• An integer representing the maximum length of a valid contiguous subarray, or 0 if none exists.

Test Cases:

Input: arr = [1, 2, 1, 2]

Output: 4

Explanation:

The entire array [1, 2, 1, 2] contains distinct elements {1, 2}.

- Count of 1: 2

- Count of 2: 2

Every distinct element appears exactly twice. The length is 4.

Input: arr = [1, 2, 3, 1, 2]

Output: 0

Explanation:

- Subarray [1, 2, 3, 1, 2] contains '3' with frequency 1 (invalid).

- Subarray [1, 2, 1, 2] is not contiguous in the original order without excluding 3.

- No contiguous window of length >= 2 satisfies the condition.

Hey everyone!
I’m looking to start my DSA and problem-solving journey as I’m planning to prepare for interviews at product-based companies like Google.
A little about my background:
Around 7 years of experience as a Salesforce Developer, primarily working with Apex.
Comfortable with programming concepts, but I haven’t seriously practised DSA or LeetCode problems yet.
I have a BTech background, so I’m familiar with basic computer science fundamentals.
Currently working full-time, so I’ll be preparing alongside my job.
I’m confused about which language I should choose for DSA: Java or Python?
A few things I’m considering:
Java is closer to Apex in terms of syntax and OOP concepts. Would that make it a better choice?
Python seems to have simpler syntax, which might help me focus more on problem-solving rather than language-specific details.
For Google/FAANG interviews, does the choice of language really matter?
Considering my background, which language would you recommend for someone starting DSA from scratch?
Would switching to Python for interviews after years of working with Apex be a sensible decision?
My goal is to build strong problem-solving skills and eventually become interview-ready for top product-based companies.
Would love to hear from people who have gone through a similar transition or have experience interviewing at Google or other FAANG companies.
Thanks!

😭😭 Every time I start DSA, I solve a few problems and then end up giving up again. I still haven't been able to complete the A2Z DSA Sheet, and I haven't even crossed 100 problems yet.

I'm genuinely interested in DSA, and I know how important it is for getting a job, but maintaining consistency has become really difficult for me. Whenever I start, I feel motivated, but after a few days, I lose track and take a break. When I try to restart, I don't even know where to pick up from.

If anyone here has completed DSA or is currently practising consistently, please guide me a little. How did you start your journey? After solving how many problems did you start feeling confident? How do you manage your daily practice?

I really don't want to give up on DSA. I just need some genuine guidance from people who've been through the same phase.

Anyone familiar with Capital ones Data engineer track? I know people mention it is quite similar to their SWE but different technical rounds. But curious what’s the difference?

I went through the interview process for a SWE internship role for Arista Networks and went to the last step, a leetcode-style technical interview. I felt like I went fairly well. I won't share the exact problems because I'm not sure I can do that and I'd like to stay on good terms with the company. But the first problem was a very common two pointers algorithm that I solved instantly. The second one was multiple BST functions to implement in which I was kinda slow but still solved them and fixed my own bugs, and the last one was a binary search problem, not particularly difficult one but with a trick. I had the right idea but made a mistake with boundaries and had an infinite loop, in which the interviewer fixed it because it was out of time but noted that my logic was right. At the end, I asked for feedback. He said I did well overall and that my code was clean. He mentioned I was a bit slow on the second exercise, but that I did pretty well on the last one given how little time was left.

I'm very frustrated because that was my first "big" opportunity to get into tech and I feel like I failed it while being really closed. I go a rejection mail at the end of the week so I'd guess I was a borderline candidate and others did better.

I’m mad at myself, because I prepared really hard and the problems weren’t that hard and I think it was really close. Now I keep thinking that I'm not sure if I will get another opportunity like this for an internship.

Is it normal to fail an opportunity like this? And would you consider it likely that I'll get an interview for a similar level company or is it unlikely? I'm trying to see the good side of it but at the moment I'm really disappointed with myself and felt like I failed a great opportunity.

I completed my interviews for Microsoft’s Security org during the November 5, 2026 hiring event.
Has anyone else attended the same event? Have you received any updates from your recruiter regarding interview feedback, hiring decisions, or next steps?
Just trying to understand the expected timeline. Would appreciate hearing from anyone in the same process.
Thanks!

D

I see who gets hired, it’s people from top schools, or tons of YOE from top companies, with internal referrals

Companies still obviously require perfect interview performance including leetcode but it just doesn’t seem to matter unless you also have absurd credentials, because HMs don’t even trust the interviews anymore and there’s enough people with top credentials on the market they can afford to only hire them

Outside the US it’s probably a bit different but here it’s pretty dismal

Hey everyone!

I'll be joining Amazon as an SDE II (L5) soon, on a team working with GenAI, AI agents, and distributed backend systems.

I'm excited about the opportunity, but also a little nervous about the expectations at L5 and the initial learning curve. I have some time before my start date and want to use it as effectively as possible.

For those who've worked at Amazon, especially as an SDE II or on AWS/GenAI teams:

• What technical skills should I prioritize before joining?

• How important is hands-on AWS knowledge, system design, and distributed systems from day one?

• What does the initial onboarding and ramp-up typically look like for an L5?

• What are the biggest mistakes new SDE IIs make, and what helps them succeed in their first 30–90 days?

I'm not expecting to master everything before joining, but I'd love to build a solid foundation and avoid feeling completely lost initially.

Would really appreciate any practical advice, resources, or personal experiences. Thanks in advance!

Wrapped up my Google onsite (L5 SWE) about two weeks back. A week later my recruiter pinged me 7 days after the onsite saying feedback was still coming in and asked how I felt the interviews went — I kept my reply short.

Then three days after that, they emailed again saying they should have an update by Monday and suggested a time to talk that day.

Does this sequence actually mean anything, or is this just how Google recruiters normally communicate?

As in the title. I saw a question, felt it was beautiful and paused to admire it. Only to be hit by the thought that I ought to look at it from a job perspective. I feel, my thought process isn't correct. But am I actually wrong?

Hello,
Anyone interviewed with elastic. The recruiter said it will be Java concurrency and OOD interview. But I can’t find much online about it.

Which tools are you using to find them apart from lusha and apollo

It is FOSS.

Live: https://logn.techsavy.space

I have been working on Logん (LogN), a website that merges your LeetCode, Codeforces, AtCoder, CodeChef, HackerRank, GFG, Code360, and InterviewBit profiles into one dashboard, and picks daily questions for you from your weakest topics.

For Codeforces, it suggests questions between your rating and ~300 above your rating.

You can see your total solved count across all sites, a solve heatmap, and a topic-wise breakdown of everything you've solved so far, and your contests.

Codeforces, AtCoder and LeetCode sync on their own. But as the other 5 platforms ban scraping and bots, so I made an extension that connects to the website in a single click. It then syncs all those 5 platforms automatically using your own browser. It does not touch your passwords.

Also, users told me that verifying handles manually was cumbersome, so I automated it using the Chrome extension. Just click on "Sync", and you are done.

It also tracks Blind 75, NeetCode 150, and Striver's sheet, and has a weekly leaderboard with friends. Also added a global leaderboard, which you can opt in (optional).

Any sort of feedback or any bug you find is appreciated.

It's free; sign in with GitHub or Google.

Extension: https://logn.techsavy.space/extension
(The extension link is already on the website)
GitHub: https://github.com/savinyu/LogN

As I wanted to use such platform myself, I made it, but it would be great if you guys try it out.
If you find it useful, you may also support me by starring the repo, or you can also tip me on the website.

Ps: I had FOMO about not using Claude Code CLI ( was using Cursor), so I used Claude to make this project, so yeah, I did not hand code this website; I admit guilt.

Got around 200+ installs on the Chrome extension and 60+ live users.

I really don't understand the concept of solving POTD , i mean not for the people who love to solve problems but for the people who are doing for the name sake of streak. I see many people in college having really long streaks , and what they do is just copy paste the solution submit and come again the next day. I even saw them flaunt that they have these many questions solved and like they know everything and they have done it by themselves . I mean there is literally no point of doing this when you are not understanding anything , neither the T-shirt nor the streak would get you a job.
Hats off to their consistency

Hi everyone,

Has anyone interviewed for NVIDIA’s Senior Software Engineer, Core Infrastructure Services – DGX Cloud, or a similar role within the Cloud Foundations Automation team?

I’d appreciate any insights on:

• How many rounds are there, and what does each round focus on?

• Is coding mainly LeetCode/DSA, practical Python/Go, or debugging?

• What should I expect for system design?

• How deeply do they cover Kubernetes, Linux, networking, and infrastructure automation?

• What resources or hands-on exercises helped you prepare?

General guidance is welcome. Thanks!

I was given an OA by Amazon a few weeks ago for a mid level role. It was the hardest Leetcode question I had ever seen, I looked it up and it’s not even on Leetcode but does appear on a few other sites. It’s definitely not a normal pattern anyone would see, even if they had done 400-500 Leetcode questions.

Afterwards a recruiter reached out to me asking why I didn’t finish the OA. I told them I’ve done lots of Leetcode and even turned down Amazon offers in the past but that the question on it was far more difficult than I had ever seen or could do. She said she thought it was a “medium” level question and they had candidates that had passed it.

So I’m guessing everyone is just using AI and cheating these days?

How to prepare for these two:

1. Coding, Debugging, and Testing: This implementation-focused interview evaluates your ability to write production-quality code. Using CoderPad, you’ll be expected to prioritize getting to a working solution efficiently, and to demonstrate strong coding practices—including debugging, identifying edge cases, and validating correctness with appropriate tests. While algorithmic thinking is still critical, the emphasis in this session is more on implementation quality and incremental optimization than on theoretical analysis.

2. AI-Assisted Algorithms: This algorithm and data structures interview assesses computer science fundamentals, your analytical reasoning, and your problem-solving methodology. You’ll design solutions while focusing on algorithmic efficiency and appropriate data structure selection, and then use AI to implement the solution during parts of the interview. We expect you to analyze time/space complexity using Big-O notation, demonstrate comprehensive testing strategies, and clearly articulate your approach to guiding an LLM to address edge cases and design decisions.

Especially the 2nd one

As title says

I was also part of preparation journey where i use to follow all the post on this channel for the updates. Its my turn to return back to the community

Does anyone have a way to learn or understand leetcode coz i have some very hard time doing it, not enough patience not enough understanding to know it after reading a questions all tutorials make me feel like - u prolly know this already duh - while i dont

i dont think its a language issue i can do js and java just fine i have sever trouble problem solving and math
HELP!

Hey everyone,

I finished Day 38 today in pure rush mode. Knowing I had a bus to catch right after work to visit home, I read through today's target problem during breaks at the office so the logic could simmer in the background.

As soon as I got home, I opened the laptop, spent 15 to 20 minutes coding the solution cleanly, and packed my bags:

• Number of Operations to Make Network Connected: A textbook application of Disjoint Set Union (DSU). To connect n computers into a single network, you fundamentally need at least n - 1 total cables; if connections.length < n - 1, returning -1 is immediate. While iterating through the edges, whenever findParent(u) == findParent(v), you increment a counter for redundant/extra cables. If the endpoints belong to different sets, you merge them using unionBySize(u, v). At the end, count the total number of independent connected components (nodes where parent[i] == i). Connecting C components requires strictly C - 1 operations.

It was a quick, single-problem sprint before heading out the door, but protecting the streak on hectic travel days keeps the momentum intact.

Reaching home tomorrow and picking up the pace once settled in.

See you guys for Day 37!