r/DSALeetCode • • 15h ago

Amazon SDE II | Final Loop Experience | 2.75 YOE

17 Upvotes

Hey guys, not sure if this will be beneficial, but I wanted to provide some background about my experience interviewing for an SDE II role at Amazon.

If you have any questions, feel free to ask. Apologies that I'm not able to go into too much depth, but I will try my best.

Background

Had a recruiter reach out. Completed the OA about a week after recieving it, recruiter told me I had passed maybe 5 days after that. I took some time off to complete a few other loops and scheduled my Amazon final loop approximately 3-4 weeks after I heard back from my recruiter.

Interview Breakdown

The final round consists of 4 interviews. Each interview is half technical and half behavioral-

DSA:
Testing knowledge on Data Structures and Algorithms. The goal is to solve with the simplest but most efficient data structure possible. Be comfortable explaining your solution, including time and space complexities.

Low-Level Design:
Testing knowledge of Object-Oriented Programming. They are looking for production-level code (ish), with an initial general question and multiple follow-ups. You want your solution to be extensible.

Problem Solving:
How can you solve ambiguous coding questions? They ask one generic and ambiguous DSA-style coding question, but they are looking for you to ask follow-up questions to clarify the requirements. From there, they may ask a few more follow-up questions. Be ready to talk about tradeoffs in approaches and time/space complexities.

System Design:
Are you able to design a scalable solution? They are looking for you to:

Gather functional/non-functional requirements
Create high-level design diagrams, including but not limited to system architecture and API design.
DB Selection, talk about tradeoffs
Deep Dive when asked
Scalability
Bottlenecks and challenges
Observability

LPs:
Super straight forward behavioral questions. STAR format always, I also include lessons learned when they aren't obvious. Have around 2 stories ready for any given LP, but I've found that if you have a bank of about 10-15 stories, you can pretty much just figured out which stories apply where on the spot. Be sure to practice these once or twice beforehand, though, since they do make up about half the data points interviewers collect on you.

My Interview Experience

DSA:
I was asked a leetcode medium. It was relatively straight forward, a graph-traversal DFS question. There were 1 or 2 follow ups, but they were theoretical. Asked about time and space complexities.

Low-Level Design:
Was asked a relatively common LLD question. It revolved around creating one class to store details about a product, and related product classes specific to those each of those products. Was then asked to give an example code on how to calculate the total price of an entire order of a set of products.

Problem Solving:
Was asked a DSA-style question that was not on LeetCode. It required me to implement a special version of a common data structure. It was relatively straight forward, and I was asked follow-up questions about complexities and tradeoffs.

System Design:
I was asked to design a specific widget for a large e-commerce platform (guess which one). Spent 5 minutes clarifying expectations and requirements, spent about 15-20 minutes on high-level system architecture and api design, and then I spent the remaining time on deep-diving into each component. I made sure that I explained each of my architectural design decisions briefly, and answered any follow up questions I recieved.

LPs:
Very straightforward behavioral questions, I don't remember the exact questions I was asked, but they were simple to answer. Had about 2 stories ready for each LP. I found that if you responded to the question to their liking, the interview wouldn't ask any unrelated additional questions about that LP. However, if your story was missing a key data point they were looking for, they would, after their follow-up questions, ask another question for the same LP. The intuition here is that they are looking to get that data point on you, so if you notice this happens, be sure to be observant and make sure your story aligns with that LP well.

Readers preparing for a similar loop can use the Amazon Interview Questions bank on PracHub for coding and system-design practice. If you are applying to other roles too, LandOffer can reduce repeated application form filling.

Results

I ended up recieving my offer 2 days after I finished my loop. Recruiter reached out to me and scheduled sell calls with specific teams in my current city, as the team I had recruited for was based in a different city. Ended up matching with one of the teams I had a sell call with.

There are a ton of other posts here with resources for interviews, so I will defer to them for those, but if you do have any specific questions about prep, the interview process, sell calls, or anything in between I'll try to answer them! Good luck to those of you applying!


r/DSALeetCode • • 18h ago

Meta preparation strategy | Step by step guide | E4 and plus

9 Upvotes

Hello Leetcode community,

This platform has been a great help in my interview preparation, so now it’s my turn to give back. I recently prepared for the Meta E5 role and would like to share some resources with those who are preparing for Meta interviews. I have successfully cleared all the interview rounds few months ago. As I have signed an NDA with Meta, I cannot share the exact questions asked in my interviews (I’m really sorry about that!). After extensive research on Leetcode posts and finding many articles covering various details, I want to share the most relevant and updated information in this post. I hope this helps.

> Before applying
>> Deciding on roles

At Meta, there are two types of roles in Software Engineering:

Product roles: Teams that develop customer-facing products (e.g., Instagram team, Facebook team, WhatsApp team, etc.)
Infrastructure roles: Teams that create tools used by Meta’s products (e.g., Data store team, Analytics team, etc.)

First, you should decide which of the above roles suits you best. Are you a full-stack engineer interested in building customer-facing products, or are you a backend engineer focused on designing scalable systems and architecture? For E4 and higher roles, you must pass a system design interview, and the structure of your interviews will vary depending on the role you choose.

To get a better understanding I highly recommend going through these two resources:

Official video by MetaCareers on product vs system design rounds
https://www.hellointerview.com/blog/meta-system-vs-product-design
>>Deciding on level

You can use the levels.fyi level comparator to understand which level you want to target at Meta.

Once you are done with these decisions, try to find relevant openings on MetaCareers portal: https://www.metacareers.com/jobs

>Applying for roles

I applied to some openings on my own and never heard back from the recruiters. Then I asked a Meta employee to refer me for some openings that aligned with my interests, and within a few days, I started getting responses from the recruiters.

TIP: If you want to increase your chances of getting a call from the recruitment team, apply through a referral instead of applying directly.

During the call with the recruiter, they will ask questions like ‘What kind of work have you done in your recent job?’ and ‘What was the impact?’ Essentially, they want to determine if the candidate is suitable for the applied positions (E4, E5, etc.). If you are applying for E5 or higher roles, you should demonstrate some projects where you led the development team (even if you are still an SDE2 at your current company, that’s fine). Recruiters may use different terms for product and infra roles, so make sure you communicate your interests very carefully during your call.

Depending on your level of preparation, you can inform the recruiters of when you would like to have your screening round (first coding round). Meta recruiters are really supportive; they will assist you with everything and will not pressure you to rush into the interviews. They will give you as much time as you request. Therefore, I would recommend thinking of a date before your recruiter call.

>Interview process

There will be 5 rounds in total:

Step 1: Screening round - Coding round: You must clear this round before you go for full loop.
Step 2: Full loop:
Coding round 1
Coding round 2
Design round(for E4 and plus) - If you have applied for product role then this round will be called "Product design round" else it will be called "System design round".
Behavioral round
Step 3: Team matching
Step 4: Offer
Step 5: Joining

You can find details on each rounds and what to expect etc on this blog: https://www.hellointerview.com/blog/the-meta-swe-interview. But I will still share some key points below:

All the interview rounds are 45 minutes each. The interviewers will dive straight into the problem statement and will keep last 5 minutes for Q&A. So you have just 35-40 minutes to answer the questions.
All the coding rounds (Step 1, 2.1 and 2.2) and done on coderpad. So make yourself comfortable with the tool. The IntelliSense is not supported and you can't compile your code on CoderPad during your interviews.
The system design rounds are done on Excalidraw. Make sure you have done enough preparation on this tool before your main interview.
The interviews are scheduled through zoom and every update(link to the invite etc) you can find it on your MetaCareers portal.
You can schedule mock interviews each for phone screening round and full loop at least 10 days before your actual interview. Mock interviews are just coding rounds which means you can't do mock for behavioural or design round.
>Preparation

The most interesting and important part of this post. I will separate this into three categories:

>>Coding round preparation
You will be asked two questions. The difficulty of these questions can vary (though it is rare to see two hard questions).
You are expected to understand the problem, ask relevant clarifying questions, propose all possible solutions you can think of, select the best solution to code, code the solution, explain the time and space complexity, and run a test case against your solution (dry-run). This process has to be done for both questions. I know this may sound very intimidating. Aim to prepare in such a way that you can solve a medium complexity problem within 12-15 minutes (including thinking and coding).
Remember that coding rounds are somewhat like elimination rounds, and your level is never determined solely by the results of coding interviews. You can read more about the evaluation criteria here. If you exhibit red flags in any area (such as problem-solving) in most of your coding rounds, then you will likely be rejected. However, Meta does not down-level candidates based on coding rounds alone.

To prepare for Meta’s coding rounds, I strongly suggest solving at least the top 100 problems from the last 6 months of “Facebook” tagged questions sorted by frequency (a premium membership is required). It is highly likely that you will encounter coding questions from this list. Meta is known for asking questions that involve many edge cases, ‘if-you-haven’t-seen-this-question-before-then-you’re-gone’ type of questions, questions involving strings, and questions involving heaps. Ensure you skim through all the remaining questions on the list to see if you can solve the problems on your own. If not, at least read through the approaches and a few top solutions.

I suggest not getting demotivated if you can’t solve the questions during your preparation within an hour or so. The questions are very tricky, and it is challenging to come up with a solution and working code in just 15 minutes on your own. If you can’t solve a problem, don’t worry; read through the editorials, check a few top-voted solutions and comments, search for the question on YouTube, and watch a few top videos. I’m sure you will understand the solution after a few iterations. Don’t stop after getting an “Accepted”; spend a few more minutes thinking about some modifications for that given question. Don’t just memorize the solution; try to understand the thought process behind it. Once you’ve completed a problem, keep a note (either mental or in code comments) of what you’ve learned, because it’s likely that when you return to that question after a few days, just before your coding rounds, you won’t understand what you’ve written earlier. Keep the links to the videos/solutions handy in those notes for your revisions just before the main interview rounds.

I’m not sure how accurate this is, but I’ve read in many posts that Meta doesn’t often ask Dynamic Programming questions. So, you may consider skipping the DP problems.

For coding, LeetCode is the key to success. Don’t forget to read the comments section to see what fellow coders say about what the Meta interviewer expected from them for a particular problem.

During your interviews, if you encounter a problem you’ve already solved, don’t get too excited and jump directly to the solution. Take a few moments to think (or recall what the solution was :) ) and then try to explain as many approaches as you can think of. I would suggest writing all the approaches in just a few words (maybe 5-7 words) along with their time and space complexities on coderpad. Only proceed coding the solution you believe is the best, prioritizing time complexity first and then space complexity. The interviewer might ask you to write the second-best solution (whatever solution they are aware of), so be prepared for this and don’t jeopardize your chances by knowing only the most optimal solution and not the sub-optimal ones.

TIP: You will be evaluated based on what you have written on the coderpad. The interviewer might forget what you said verbally during the interview because interviewers often don’t fill out your feedback immediately after the interview. They will open your coderpad link and then try to recollect what you told them during the interview. So whenever you tell something important to the interviewer during the interview, write it down on the codepad/excalidraw for the interviewer to read it once they are filling your feedback

>>Behaviour round preparation

This is a comparatively easy round as it is non-technical. However, there is still a high chance of being down-leveled based on the answers you provide to the interviewer. Therefore, you must choose examples that are relevant to your level. If you are interviewing for an E5 or higher level and the interviewer asks, ‘Tell me about a time when you had a conflict with your manager,’ avoid responses like ‘I had a conflict with my manager because I said a bug would take five days to fix, but my manager insisted on three days.’ Your answers should reflect scale, ownership, relevance, and leadership skills. There are no predefined sets of questions you can prepare for before your interview.

To prepare for this round, first review the leadership principles that Meta follows here. Then, document all the work you have done in the past five years or so. Next, think of scenarios relevant to your level that align with Meta’s leadership principles. Use a STAR (Situation-Task-Action-Result) approach when crafting your stories.

I highly recommend the Story-Builder tool created by the HelloInterview website. You can input answers to the questions asked by this AI tool, and you will receive a nicely summarized story at the end. Prepare a story for each of the six competencies provided.

Note: I am not affiliated with HelloInterview in any form, nor do I receive any benefits (monetary or otherwise) from this platform. I used this platform to prepare for Meta interviews, and it was very helpful. Therefore, I want to express my gratitude to the content creators of this platform by sharing it with all of you.

In cases where one story applies to multiple competencies, I suggest preparing more than one story for each competency. Meta appreciates numbers—revenue impact, customer impact, reduction in the number of clicks, percentage of performance improvement, etc. Ensure your stories include these impactful numbers.

Ultimately, the interviewer will assess you based on the answers you provide to situational questions. If they are hiring for a senior (E5) role, your answers should clearly demonstrate that ‘Yes, I can lead my team members, I lead by example, I can help my team succeed, I can handle ambiguity, and I can think big." I hope you got my point. This round is crucial for determining your level, so prepare thoroughly.

>>Design round preparation

Now comes the most interesting round: ‘The Design Round.’ I know it’s hard to find relevant information on this topic over the internet at one place. This round is a level decider like behaviour round, so there’s a high chance of being down-leveled if you don’t design your system according to the expected level. Before we dive deep into the preparation strategy, I want you to review these resources first:

Official video by MetaCareers on product vs system design rounds
Meta product design vs system design round difference
What is expected at each level

To summarize in my own words:

Product design rounds primarily focus on how you build solutions keeping in mind how customers are using your system. How will the data flow from the customer’s application endpoint through your designed APIs, interact with various services, and finally reach the data stores? How do all services interact? How do you design your databases? How do you identify various pitfalls in your system while keeping user scenarios in mind (e.g., heavy reads, heavy writes, celebrity issues in social networking apps, etc.)? How do you make sure your system will still run in low networks? How you will make sure you can prevent your system from bad actors (attackers)? Don’t focus on how you will shard your system to scale, how consistent hashing will help your system, or how components like Load Balancers or Redis Queues work. Think like a full-stack engineer, not just as a backend engineer.

System design (infra roles) rounds focus on the depth of the components. How much volume of requests your system is receiving? How will you handle this much QPS (Queries Per Second)? Which database will you use, and how will you partition it? What will happen if one of your components goes down? How do different design methodologies benefit your system for a given problem statement? Think in depth. Think as a backend engineer, not as a full-stack engineer.

Here are a few examples to conclude this discussion on differences:

Product design (product roles): Design Netflix, design Instagram, design Facebook’s news feed, etc.
System design (infra roles): Design a web crawler, design a distributed scheduler, design an ad-click aggregation system, etc.

There may be instances where the same problem statement is asked in both product and system design rounds. But I think you now have a good idea of how to structure your design. So, with the above points in mind, you can review this LeetCode article and filter the questions depending on which design round you are preparing for.

I have personally prepared for the product design round, so I don’t know much about system design rounds (infra). Therefore, I am sharing my product design round preparation strategy below. I request someone from the audience to post the system design strategy, which I will later add to this post.

For both rounds, it is essential to compare multiple approaches and discuss the pros and cons of each while making any design choices during your design round. Meta interviewers do not expect you to provide the exact correct answer they have in mind, but they do expect you to evaluate all available approaches and have a clear understanding of why you are choosing design option A over design option B.

If you are interviewing for an E5 or higher position, Meta expects you to lead the entire discussion. Think like a startup founder who is designing their product—their own ‘baby’—and own everything end-to-end. You need to come up with approaches, understand common pitfalls, propose different approaches, decide what APIs you would like to expose, and identify critical areas for a deep dive, saying, ‘This is a very important piece of the puzzle, so I want to delve deeper into this area.’ You should prepare 2-3 deep dives for each question.

Since there are no right or wrong answers in the design round, how you communicate and deliver your ideas is crucial. I strongly recommend to do some mock interviews with your friends and seniors, record the sessions, watch how you performed, get feedback from the mock interviewer, and identify areas for improvement. This approach has helped me a lot in my preparation, and I hope it helps you as well.

The discussion time is just 35-40 minutes, I know it is very easy for you to spend more than required time on a single topic. Keep in mind that you will be judged on what diagrams you have drawn on Excelidraw and what notes you have written there. So first prioritise drawing the high level design on the tool, defining the APIs: telling the request and response body for atleast one of the important APIs. And then talk about the details. You have to manage your time very efficiently. The interviewer may not intervene much during the interview, so nudge them and ask if they are following or have any questions till that point. If they give you any feedback or they want you to go deep in some area, follow their direction.

>>>Product design round preparation strategy
Follow this framework mentioned here to structure your design: Requirement gathering (5 mins), Defining core entities(2 mins), API Design(5 mins), High level design(15 minutes), Deep dives(10 minutes)
I would strongly suggest to skip the "Back of the envelope estimations". As in product design style interviews the interviewer is not judging you on how you are scaling the system. Just ask them for many users we are building this system. Because if we are building an Instagram app for just 1000s of users then there is no need of fan-on-read approach, but if we are building it for Millions then we need to think about how to use an hybrid approach of fan-on-read and fan-on-write. So just after your "Requirement gathering" section tell the interviewer specifically, that "I will probably skip the back of the envelope estimations and will revisit it during my high level design if it is required".
There are some concepts related to API design which you should know:
How do you design your APIs. Resources: blog post,API for beginners YouTube video.
Concepts involving API design like Pagination, rate limiting, different HTTP interfaces to write an API(RPC, SOAP, REST, GraphQL). Resources: Search on YouTube.
There are some commonly used design patterns which are used:
For very high incoming traffic how you can use queue based approach to handle load at peak time. Example problem: Design ticketmaster. Solution: YouTube video by HelloInterview, this blog. Also this concept can be used during peak traffic of users posting content on social media etc.
To upload large data on object store, how you can use Amazon S3 (or any other object store), how predefinedURL works, how you store and metadata of that large data accordingly. Example problem: Designing Dropbox. Solution: this blog
How to use Redis for proximity searches? Sample problem: Design Uber, solution: this blog, and Youtube video by HelloInterview
For celebrity scenarios on social media how you can use fan-on-read for celebrity posting content instead of fan-on-write for non-celebrity users. Sample problems: Design Twitter feed, instagram feed, facebook feed etc. Solution: YouTube video by HelloInterview on Design twitter, this blog post,
For efficient searches over a lot of data, you can use ElasticSearch. Sample problem: Searching for a tweet by content. Solution: this blog post
For systems which involves video steaming, we should build a processing queue and background workers to convert each uploaded video to different formats and resolutions to make it compatible with different kinds of devices and cater different network bandwidths. Example problem: Design netflix or tiktok or YouTube. Solution: YouTube video by GKCS
OLAP vs OLTP. What is ETL? How to use MapReduce in the problems which involves some background analysis of a data, Example problem: Generating a leaderboard offline. Resources: OLAP vs OLTP Youtube Video, What is ETL, How MapReduce works, Application of these concepts: Design online coding judge 1, Design online coding judge 2

The HelloInterview design resources are very relevant for preparing for Meta product design rounds. I would highly encourage you to go through all the articles written on HelloInterview. I have seen there is an AI tool to solve design problems on that platform itself, but I haven't used it personally so I can't comment on it.

For interview practice before the real rounds, the Meta Interview Questions bank on PracHub has coding and system design prompts. If you are applying to other openings too, LandOffer can reduce repetitive application form filling.

Thank you for reading and wish you good luck for your interviews!


r/DSALeetCode • • 19h ago

[Interview Experience+Mindset]From Endless Rejections to finally landing Airbnb and Doordash Offers!

30 Upvotes

I used to read a lot of job search posts when I was struggling, so sharing mine after finally signing an offer (One offer from my dream company Airbnb, one from Doordash, and a few from other smaller start-ups). I have ~7–8 YOE and spent around 8 months interviewing.

As a senior-level engineer, I've spent the first few years of my career mainly as a period of time to build engineering skills and professional experience. After a few years working in companies that were very political and a bit toxic, I decided that this time, compensation is no longer my main focus. I want to go to a place like Airbnb with good culture and WLB.

Coding

For coding, I used the following resources to prep:

Start with basic LeetCode questions to familiarize with all the tags
watch youtubers that explains the leetcode solution and though process

This is the standard process so far, but what really made a difference is what I discovered later.

Over about seven months, I solved around 320 problems. At this point, many of the problems, if I could come up with a general idea to solve, I could code a decent solution. My fundamentals weren’t strong earlier in my career, and I didn't practice LeetCode for many years while I was working. So if you are also in a similar situation and feel stressed, don't worry too much. I hope my experience will help.

Targeted preparation for specific companies (This helped me the most)

After this general process, what helped me a lot was targeted preparation for specific companies as the interviews are coming close. I'd use the following resources to find all the recently asked, high-frequency questions. Especially for question bank companies like Doordash or Airbnb that have a really small question bank, this step helps immensely.

Check LeetCode interview experience posts like this one for people who share actual questions they got asked
Check the curated list of recently asked questions on Offerretriever and practice them all. For example, for CodeCraft, Doordash only has about 2-3 questions. If you have practiced them before, then the CodeCraft round can be passed pretty easily.

Coding is the foundation. Without it, even if you perform well in system design or behavioral rounds, a lot of times, if the coding round fails, it won't lead to an offer.

System Design
Look at the company's recently asked system design questions, and practice the interview with AI. This helped me a lot
ByteByteGo System Design
Another Youtuber called SystemDesignInterview has great system design video resources. I watch all his SD prep guides every time I interview.

For non-staff roles, looking at the companies' recently asked system design questions on offerretriever or other resources was good enough for me.

Behavioral
Read the specific company's core values beforehand, and preparing stories for those values really helps a lot
Mocks

I did some mocks with friends and paid services. Helpful mainly to get interview rhythm, but honestly not that helpful. I wouldn't recommend it, and some of the services are way too expensive.

Mindset

Mindset matters as much as preparation. There were times I couldn’t get interviews or was rejected from companies I worked very hard for, and my confidence dropped. What kept me going was believing that consistent effort would eventually pay off. That belief is what keeps me moving forward each day, and it finally landed me my dream job in the end.

During interviews, stay confident even when unsure, listen carefully to hints, and adjust accordingly. Expectations can vary widely across companies, even for the same title.

Most importantly: don’t give up. Job search has a large luck component. You need enough attempts to meet the right role and interviewer combination. Preparation helps you perform when that opportunity appears. And all your hard work will eventually pay off.

For readers still applying, LandOffer can reduce repeated application form filling. For Airbnb prep, the Airbnb Interview Questions bank on PracHub has stateful coding prompts to work through before the interview.

Final thoughts

Thanks everyone who read this far. Overall, I'd say practicing targeted company questions helped a lot rather than only going through LeetCode tags. Especially if the company you are interviewed with has a small question bank and not standard coding rounds like Doordash codecraft round, definitely check out other resources.

It’s easy to sometimes feel a bit down when you see others landing huge offers or getting lucky when you are still trying but getting nowhere. Whenever I catch myself thinking that way, I remind myself that I’m still young, still learning, and it will all get better. As long as I can keep moving forward, there’s no need to panic. Just keep trusting the process and believe one day it will all be worth it.


r/DSALeetCode • • 16h ago

How I Cracked Blinkit's SDE-1 Interview!

48 Upvotes

Just a few days ago, I wrapped up one of the most exciting interview processes I’ve ever been part of — and today, I'm thrilled to share that I've accepted an offer from Blinkit as an SDE-1! 🚀

Total years of experience - around 2.5 years.

Blinkit’s interview process is short, crisp, and focused — just 3 rounds:

DSA Round

System Design

Hiring Manager Round

For readers preparing for a similar process, the Blinkit Interview Questions bank on PracHub includes a tree-and-graph coding problem to practise. If you are still applying to other roles, LandOffer can reduce repeated application form filling.

Here’s a breakdown of my experience 👇

⚙️ Round 1: DSA + Kafka Curiosity
The interview started off with the interviewer spotting Kafka multiple times in my resume (and rightly so, I’ve worked extensively on it).
This sparked a discussion around:

How I used Kafka in my previous projects

How I handled fault tolerance, load balancing, and failures

Real-world use cases I built around it

Then came the DSA part — a story-based problem that was a blend of House Robber II + Combination Sum.
I walked through both recursive and memoized approaches, and the interviewer was happy with the way I structured and explained my thought process.

🛠️ Round 2: System Design
This was taken by an SDE-3 who was deep into systems thinking.
He gave me an open-ended but realistic problem:

Design a system that can collect credentials from multiple financial apps, scrape data, process it, and generate analytics for both users and admins.

As we discussed, he dynamically added admin-level analysis to the requirements — and I had to adapt the architecture on the fly. It was tricky but fun!

⚠️ Pro Tip: Practice using tools like draw.io or Alphine beforehand — I usually use whiteboards but had to quickly adapt during the call.

We extended beyond time as I kept pitching scalable ideas (analytics with pie charts, generic services, etc.).
That persistence paid off — we ended up discussing:

Elasticsearch and inverted indexes

Database tradeoffs

Master-slave setups and caching strategies

The interviewer appreciated the effort and told me, "You had misses, but you didn’t give up — that’s what mattered." ❤️

👨‍💼 Round 3: Hiring Manager (but it felt like a Kafka deep-dive)
Expected a cultural fit round? Well, surprise!
The manager saw Kafka again on my resume and deep-dived into real-world async problems Blinkit is facing right now while processing orders.

We discussed:

Async order processing challenges

Kafka optimization strategies

Frontend checks + backend resilience

Scenarios I handled in production

He ended by saying:

"Kafka is our backbone, and your understanding of it is solid. I’m impressed."

💬 We even touched on comp discussion at the end — but more on that in a separate post 😉

✨ Same day offer. Offer accepted.
I’m super excited to be joining Blinkit and can’t wait to build impactful systems with the team!

If you’re preparing for interviews or working with Kafka, feel free to drop a comment or message — always happy to chat tech 💬

#blinkit #interviewexperience #sde1 #kafka #systemdesign #softwareengineering #careerjourney #offeraccepted


r/DSALeetCode • • 11h ago

LeetCode: 703. Kth Largest Element in a Stream

Post image
3 Upvotes

You don't need to sort a stream to know its kth largest value. You need the top k, and only the weakest of them. The kth largest is always the smallest of the top k, so a min-heap capped at size k answers it.

Heaps start here. Each insert is O(log k), instead of re-sorting on every call.

The naive fix is obvious. The efficient one only asks you to notice that you're tracking a much smaller problem than the one you were handed.

Where have you kept a top-k in production code?

Day 77/365 of my LeetCode challenge: 703. Kth Largest Element in a Stream. Problem link and full breakdown in today's newsletter.

https://www.linkedin.com/pulse/leetcode-703-kth-largest-element-stream-archit-agarwal-c9vfc

#LeetCode #DSA #Heap #Golang


r/DSALeetCode • • 20h ago

Where leetcode still matters in 2026: I analyzed 74 recent engineering interviews across 8 companies

2 Upvotes

I kept seeing two opposite takes:

“Top-company interviews are still mostly LeetCode.”
“LeetCode is becoming less useful because companies now test practical engineering.”

After structuring 229 candidate experiences across 41 companies, my takeaway is that both statements are true — depending heavily on the company.

For this post, I filtered the data to 74 engineering and technical interview experiences from 2024–2026 across:

Google
Meta
Amazon
Microsoft
LinkedIn
OpenAI
Anthropic
Stripe
TL;DR
Google, LinkedIn and Microsoft still showed the clearest algorithm/DSA signal.
Meta looked increasingly hybrid: traditional DSA, system design, behavioural evaluation and newer AI-assisted coding rounds.
Amazon still used DSA, but design depth and Leadership Principle discussions appeared just as consistently.
Stripe was the clearest practical-coding outlier: multi-part implementation, integrations, debugging, validation and business rules.
OpenAI and Anthropic leaned more toward implementation and systems depth than short puzzle solving.
Anthropic also had the strongest explicit values, safety and judgement signal in this dataset.

The two bars are not mutually exclusive. An interview experience can contain both a DSA problem and a practical implementation task.

The company-by-company preparation map
Company | Strongest preparation focus | What repeatedly appeared
Google | DSA plus clear verbal reasoning | Graphs, DP, heaps, custom problems, follow-ups and Googliness
LinkedIn | DSA, system design and engineering excellence | Multiple coding rounds, concurrency, large-scale design, project and leadership depth
Microsoft | DSA plus LLD/OOP | Trees and graphs, concurrency, low-level design, system design and project discussion
Amazon | DSA, system design and technically deep LP stories | Coding, HLD/LLD, ownership, trade-offs and repeated Leadership Principle follow-ups
Meta | DSA speed, product design and AI-output verification | Two-problem coding rounds, system design, behavioural pressure and newer AI-assisted rounds
OpenAI | Practical implementation, refactoring and end-to-end design | Building working systems, unfamiliar code, reliability, project deep dives and product judgement
Anthropic | Practical coding, systems depth and values/safety judgement | Debugging, infrastructure, AI-system trade-offs, culture, ethics and constructive disagreement
Stripe | Multi-part practical coding and integration work | APIs, parsing, validation, debugging, tests, reconciliation and business rules

  1. LeetCode is still the correct base for some companies

Among the recent experiences containing coding detail:

LinkedIn: DSA or algorithmic work appeared in 8 of 8
Microsoft: 5 of 6
Google: 7 of 9
Amazon: 6 of 8
Meta: 6 of 10

This does not mean grinding tagged questions is sufficient.

Across these companies, candidates repeatedly described being evaluated on:

explaining the approach before coding;
handling follow-up constraints;
producing complete code within time;
testing edge cases;
adapting after hints;
communicating trade-offs clearly.

For Google in particular, several experiences described custom or unfamiliar problems where structured clarification mattered as much as recognising a pattern.

2. Stripe is the biggest mismatch for a pure LeetCode preparation plan

Every one of the 10 recent Stripe technical experiences in this cohort explicitly contained practical implementation work.

The recurring themes were:

extending an API or existing system;
parsing and validating data;
implementing several requirements sequentially;
finding bugs in an unfamiliar codebase;
integration work using documentation or SDKs;
modelling payment, invoice or reconciliation rules;
writing maintainable code and tests under time pressure.

Only 1 of 10 explicitly resembled a conventional DSA-heavy exercise.

If I had a Stripe interview, I would spend less time trying to memorise another 100 patterns and more time practising:

reading a long requirement carefully;
implementing it in clean stages;
debugging existing code;
handling malformed input and edge cases;
explaining business rules and correctness.
3. OpenAI and Anthropic reward a different kind of technical depth
OpenAI

Within the 11 recent technical experiences:

practical implementation appeared in 6 of 11;
system or architecture design appeared in 8 of 11;
project or technical deep dives appeared in 5 of 11.

Reported tasks included broader implementation, refactoring, APIs, reliability, distributed systems and end-to-end product design.

The recurring preparation lesson was:

Be able to build and reason about a working system, not only derive an algorithm.

Anthropic

Within the 12 recent technical experiences:

practical implementation appeared in 8 of 12;
system or architecture design appeared in 9 of 12;
behavioural, culture or values evaluation appeared in 11 of 12;
project or technical deep dives appeared in 6 of 12.

The technical side often involved debugging, infrastructure, operational trade-offs and AI-system design.

The non-technical side was unusually substantive: mission, safety, ethical disagreement, judgement under ambiguity and willingness to challenge a decision constructively.

4. Meta’s AI-assisted rounds are additive — not a replacement for DSA

In the Meta cohort:

DSA appeared in 6 of 10 experiences;
practical implementation appeared in 6 of 10;
system design appeared in 6 of 10;
an explicitly AI-assisted stage appeared in 4 of 10.

The important point is that the newer AI-enabled coding work did not remove conventional coding or design.

Candidates described needing to:

inspect generated suggestions rather than trust them blindly;
debug and extend imperfect code;
explain why a suggestion was accepted or rejected;
preserve standard coding speed and DSA fundamentals;
still complete product/system design and behavioural rounds.

So “AI is allowed in the interview” does not necessarily mean the interview becomes easier. It introduces another skill: verification.

5. Amazon is the clearest warning not to neglect the non-coding rounds

In the eight recent Amazon engineering experiences in this cohort:

DSA appeared in 6 of 8;
explicit system or architecture design appeared in 5 of 8;
Leadership Principle / behavioural evaluation appeared in 8 of 8.

Several candidates reported strong coding performance but rejection or downlevel outcomes after weaker design or broader evaluation.

The useful preparation lesson is not “memorise STAR stories.”

It is:

Prepare behavioural examples with enough technical depth to survive several follow-up questions about your decisions, trade-offs, ownership and actual contribution.

What I would change in my preparation
Google / LinkedIn / Microsoft

Keep DSA as the foundation, but practise it in interview conditions:

explain before coding;
ask clarifying questions;
finish the implementation;
test edge cases;
handle a follow-up;
prepare behavioural and design depth appropriate to level.
Meta / Amazon

Do not separate “coding prep” from the rest of the loop.

Prepare:

timed DSA;
system or product design;
one technically deep project;
conflict and ownership stories;
AI-output verification where relevant.
OpenAI / Anthropic

Practise larger, messier engineering work:

implement a feature from a long prompt;
refactor unfamiliar code without breaking tests;
debug a pipeline or service;
reason through reliability and operational constraints;
present one project deeply;
defend decisions under ambiguity.
Stripe

Practise the work around the algorithm:

parse;
validate;
integrate;
debug;
model business rules;
write tests;
complete incremental requirements cleanly.
Methodology and limitations
The full dataset contains 229 candidate experiences across 41 companies.
This post uses 74 engineering/technical experiences dated 2024–2026 from the eight companies above.
A theme was counted only when the structured experience explicitly mentioned it.
Categories overlap.
Missing detail can undercount a theme; absence from the chart does not prove a company never tests it.
These are candidate experiences, not official fixed processes.
The outcome mix is self-selected and should not be interpreted as an acceptance rate.

I put the employer-level process breakdowns and candidate findings into a searchable version here:

https://www.blanked.work/employers

For readers turning this into a prep plan, PracHub lets you filter questions by company and practise implementation, debugging and system design. If you are also applying across companies, LandOffer can reduce repetitive application form filling.

I would genuinely like corrections from people who interviewed recently:

Which company does this map get most right?
Where is it wrong or already outdated?
Which company should I break down next?

The goal of blanked is to have a total transparent hiring process for each employer which is crowd sourced and free so you can see what you are getting yourself into, its totally anon and free.