Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

LeetCode is dead. Developers don't write code line-by-line anymore. They orchestrate AI agents working in parallel, review AI-generated code, and make architectural decisions. That's the job now. But most interview processes haven't caught up. They still test algorithm memorization instead of AI fluency, code review, and judgment. We're building...

344,947 Aufrufe • vor 6 Monaten •via X (Twitter)

41 Kommentare

Profilbild von Ripu
Ripuvor 6 Monaten

Killer lines of this ad-- If your interview process requires candidates to pretend that AI doesn't exist. Then you're testing for a job that no longer exist. 👏

Profilbild von HackerRank
HackerRankvor 6 Monaten

We whole heartedly believe in those words!

Profilbild von MaqboolSaiyed
MaqboolSaiyedvor 6 Monaten

Finally, someone in the market understood this, startup’s have already realised this, and now MNCs will too, it’s not about coding line by line of using leetcode, it’s AI, Agents, System Design, Problem solving with ai These are what is required to crack a job in this market. Thanks HackerRank for realising it and working to improve and improvise this.

Profilbild von HackerRank
HackerRankvor 6 Monaten

We hope so too, we really want to help make this change.

Profilbild von Kartik
Kartikvor 6 Monaten

okay 🧐

Profilbild von nicolasmelo
nicolasmelovor 6 Monaten

It's sad that you guys spent actual money to create a really well produced and directed ad that goes nowhere. You haven't even announced a competing product to leetcode. It's catchy, humor is on point, but I mean, we all know what you guys are saying, show something.

Profilbild von Gurbinder
Gurbindervor 6 Monaten

yea fk dsa

Profilbild von mars
marsvor 6 Monaten

really cool to see how agent orchestration might play into technical interviews!

Profilbild von gaurav
gauravvor 6 Monaten

Btw.

Profilbild von HackerRank
HackerRankvor 6 Monaten

Not quite. We're not saying LeetCode the company is dead. We're saying that testing algorithm memorization instead of the skills developers actually use today should cease to exist.

Profilbild von Constantine
Constantinevor 6 Monaten

@Itstheanurag its not just algorithm memorization, but they also know what optimizes a algorithm. its a way of thinking and a person who can do dsa can as well be the better agentic developer as the knowledge needed to fix this gap is very small and trivial for them

Profilbild von HackerRank
HackerRankvor 6 Monaten

@Itstheanurag And we agree, that is an important skill to have. But, is it the only skill that someone should be assessed on while being hired? Absolutely not.

Profilbild von 🦑 🌎🌱
🦑 🌎🌱vor 6 Monaten

The new interview

Profilbild von Tom Cox
Tom Coxvor 6 Monaten

Leetcode is still a measure of how well they (anyone) understands the basic theory underpinning the implementations. When I do a malloc in C I am not anytime planning to implement malloc myself.. But I understand the cost.. I understand where that pointer came from. I understand what it means to write or read beyond the end of the block of memory that I requested from malloc. It's so very cool we have tools to automate the creation of code for us now.. But these tools are not perfect.. Not always optimal. If you can't read what they are generating.. Well eh..

Profilbild von Aditya
Adityavor 6 Monaten

🙂 just when i thought I'd get serious about LeetCode

Profilbild von Indra
Indravor 6 Monaten

this is actually the right path forwRs

Profilbild von Shammy 🤖
Shammy 🤖vor 6 Monaten

Hit me up! I've been working on a platform for this for a bit. Fix evals and interviews may just feel like they surface more useful signal.

Profilbild von Anas Khan
Anas Khanvor 6 Monaten

I see @OjashKush 👀

Profilbild von Constantine
Constantinevor 6 Monaten

Leetcode is not dead by a long mile, a proficient leetcoder is most likely to be the better developer, the agentic prompting gap is tiny ,human thinking gap is huge when compared to another dev

Profilbild von raunit ⓧ
raunit ⓧvor 6 Monaten

An era has changed.

Profilbild von LeetLLM.com
LeetLLM.comvor 6 Monaten

it's crazy how many companies still test loop syntax when the actual day-to-day is babysitting agent dags. wrote a breakdown of what top teams actually interview for now:

Profilbild von Pankaj Padekar
Pankaj Padekarvor 6 Monaten

@drago999765 Get ride of DSA rounds 🙏

Profilbild von Arpan (Locked In ARC)
Arpan (Locked In ARC)vor 6 Monaten

Shift is coming 💪

Profilbild von HackerRank
HackerRankvor 6 Monaten

💪

Profilbild von Khakha
Khakhavor 6 Monaten

Even tho that ever they say is right, but this is not the right way of doing things while you are learning, as they said, whatever code is written, the next-gen engineers have to assess the code before they merge it. For that you need to know whether the code is right, wrong or needs some tweaking, which can only be done if they know how to code line by line and only if they know the fundamentals. So get your asses and learn to code.

Profilbild von Zapidroid
Zapidroidvor 6 Monaten

Huge props! This makes me extremely bullish on this company but also in the SWE space because you are totally correct. swe is not like it used to be and leet coders are pretty much obsolete. many companies these days are hiring people who memorized how ro invert a binary tree over people who can actually ship software that scales.

Profilbild von Abdullah T. Alzariqi
Abdullah T. Alzariqivor 6 Monaten

"review AI generated code" means they still need to know the basics

Profilbild von Vaulthalla
Vaulthallavor 6 Monaten

If the job becomes “monitoring agents”, we didn’t eliminate LeetCode; we just replaced it with a different kind of busywork. Building systems still requires understanding them.

Profilbild von Sotiri Georgiou
Sotiri Georgiouvor 6 Monaten

@kostyafarber_ the hypocrisy 😂

Profilbild von Arjun Dubashi
Arjun Dubashivor 6 Monaten

"Leetcode is dead that's why all our assessments still involve leetcode style questions."

Profilbild von suki - ANTI-CLAUDE TASKFORCE
suki - ANTI-CLAUDE TASKFORCEvor 6 Monaten

thanks. its kinda strange to be tested with 5 rounds of LC hards just to supervise multiple agents. then change job only to get more LC hards, just to then supervise more agents LOL

Profilbild von oxcrow
oxcrowvor 6 Monaten

Shut the fuck up.

Profilbild von RG 🇦🇷
RG 🇦🇷vor 6 Monaten

recently took the hackerank ai based assessment it was one of the worst ai assessment test i ever took please avoid this shit company

Profilbild von Anant Shah
Anant Shahvor 6 Monaten

Finally someone saying it out loud. LeetCode-style interviews testing algo memorization while real jobs have shifted to orchestrating AI agents, reviewing code, and making smart architectural calls. HackerRank cooking with this one

Profilbild von Denis
Denisvor 6 Monaten

@grok can you summarize this video?

Profilbild von heizen_dev
heizen_devvor 6 Monaten

So how to prepare for interviews as a fresher!?

Profilbild von Kanishk
Kanishkvor 6 Monaten

@hackerrank do one thing if you really want to push this thinv remove the option fir leetcode types interviews entire in your software

Profilbild von Mikon
Mikonvor 6 Monaten

Dsa tests are effectively IQ measures. They measure critical thinking beyond an established problem space. They are condensed expressions of a full curriculum. What you're proposing doesn't challenge that, at all. Entirely different interview steps.

Profilbild von Esteban Porras
Esteban Porrasvor 6 Monaten

@Tak291 thoughts?

Profilbild von White
Whitevor 6 Monaten

Ik for a fact DSA is still being asked... dont tell me that yall are planning to start some system design subscription based thing... 101 sys design interview question pay ₹499 type shit

Profilbild von 𝗿𝗮𝗺𝗮𝗸𝗿𝘂𝘀𝗵𝗻𝗮— 𝗲/𝗮𝗰𝗰
𝗿𝗮𝗺𝗮𝗸𝗿𝘂𝘀𝗵𝗻𝗮— 𝗲/𝗮𝗰𝗰vor 6 Monaten

So DSA business is dead?

Ähnliche Videos

Marc Andreessen: AI coding doesn’t eliminate programmers — it redefines them. The job is no longer typing code line by line, it’s orchestrating 10 coding bots in parallel, arguing with them, debugging their output, changing the spec, and pushing them toward the right result. But here’s the catch: if you don’t understand how to write code yourself, you can’t evaluate what the AI gives you. The next layer of programming isn’t writing scripts — it’s supervising AI that writes them. Today’s best programmers spend their day jumping between terminals, managing multiple coding bots, fixing mistakes, and refining instructions. The irony? You still need deep fundamentals, because without them, you won’t know when the AI is wrong. The job of the programmer has changed. Now it’s about arguing with coding bots, debugging AI-generated code, and understanding why something doesn’t work or isn’t fast enough. AI abstracts the work — but only people who truly understand code can tell if the abstraction is doing the right thing. Programmers aren’t going away — they’re becoming 10x, 100x, even 1,000x more productive. Tasks are changing, the job is changing, but humans are still overseeing the process, evaluating results, fixing errors, and making judgment calls. AI changes how we code, not who is responsible. The future programmer isn’t replaced by AI — they’re upgraded by it. You still need to learn how to write and understand code, because when the AI gets it wrong, humans are the ones who have to know why. That up-leveling of capability is the real revolution.

Ian Miles Cheong

913,857 Aufrufe • vor 8 Monaten

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,073 Aufrufe • vor 5 Monaten

Marc Andreessen explains why AI coding won't replace programmers, but fundamentally change what they do. He argues that AI coding is just the latest abstraction layer, and the job of a programmer has always evolved with each one. Andreessen's key reframe of what's actually happening: "AI coding actually abstracts away the process of actually writing the scripting code... This is the next layer of the task redefinition under the job of programmer." He's clear that the best programmers aren't being replaced. They're already adapting, even if their day-to-day looks radically different now. Their job has shifted from writing code line by line to managing dozens of AI agents working in parallel. "The world's best programmers today will tell you, 'My job is I'm sitting there and I'm orchestrating 10 code bots running in parallel.' Their day job now is kind of arguing with the AI bots to try to get them to write the right code." But Marc Andreessen 🇺🇸 is adamant this doesn't make foundational knowledge obsolete — it makes it more important. "You need to still fully understand and learn how to write and understand code, because if it doesn't work or it's not doing what you expect, you need to be able to understand the results of what the AI is giving you." He draws a direct parallel: Just as someone writing scripting languages still needs to understand how a microprocessor works, someone orchestrating AI bots needs to understand the code those bots produce. "It's this upleveling of capability where you actually want the depth to go down and understand what the thing is actually doing, even if you're not spending your day doing that by hand." The result, in his view, is transformative: "Now programmers are going to be 10 times or 100 times or a thousand times more productive. And that is overwhelmingly a good thing." The pattern: New abstraction layer emerges → tasks change → the job gets redefined upward → productivity explodes It raises a question every programmer should be sitting with... Are you building the depth to evaluate what AI gives you, or just accepting the output?

Big Brain AI

45,371 Aufrufe • vor 8 Monaten