AI is changing what it means to be a developer. It is no longer just about writing code, but knowing how to work with agents.
That is what HackerRank Orchestrate is built to test.
Meet Saai Syvendra, the winner of the May edition, and hear what it takes to stand out in an agentic hackathon.
Ready to test your own AI-building skills? HackerRank Orchestrate returns on June 19.
Register now: https://t.co/cNSOEUq7Ov
Nvidia is one of the most valuable companies on earth.
But it still does not manufacture its own chips.
Its future depends on a company in Taiwan that makes the chips, and a company in Veldhoven that makes the machines needed to make them.
This is the hidden supply chain behind AI.
0:00 - The Nvidia Contradiction
0:35 - Chapter 1: The Design
1:42 - Chapter 2: The Manufacturing
2:59 - Chapter 3: The Machine
3:58 - Chapter 4: The Data Center
5:02 - Chapter 5: What This Means for the Future of AI
In the agentic era, hiring has to test how candidates can actually build with AI.
At Zeta, AI is already part of how teams think, build, and solve hard problems in banking technology.
So their hiring process has to reflect that reality.
The next generation of builders need strong fundamentals, AI fluency, judgment, and business sense.
Watch Mithun from Zeta talk about how they are hiring for exactly that in the agentic era.
500+ talent and engineering leaders in one room, making sense of what hiring for the agentic era really looks like.
Thank you to all our customers for showing up, and how. Nights like this only happen because of this community.
Special thanks to our speakers: Juan Herrera, our President and CRO, @_gurubhat_ from Google, Harpreet Kaur from Adobe, and Atul Sahgal from Cognizant.
This was the room where great work finally got its moment. 🏆
Last month thousands of developers from different countries showed up to build AI agents.
Now we're back.
HackerRank Orchestrate June edition is here to challenge the next generation of AI-native builders.
June 19 - 20 | Registrations close 18th June, 7:30 AM PT
Register now: https://t.co/cNSOEUq7Ov
For the fifth time, we're rolling out the red carpet!
HackerRank Innovator Awards 2026 is back!!!
A night to celebrate the teams, leaders, and builders shaping the future of tech hiring.
#InnovatorAwards026
From building agents online to being celebrated on the Innovator Awards stage.
At HackerRank Innovator Awards 2026, we’re proud to felicitate the winner of HackerRank Orchestrate, our agentic hackathon, who joins us all the way from Sri Lanka.
Orchestrate was built to spotlight the next generation of AI-native builders. This moment is exactly why.
#InnovatorAwards2026 #HackerRankOrchestrate
Developers aren't just writing code anymore. They're orchestrating AI agents, reviewing AI-generated work, and deciding what's safe to ship.
The job has changed. The interview process has to keep up.
That's what our CEO @rvivek is talking about at @FD1conference, Manhattan on June 16.
How leading companies are rethinking technical hiring for the agentic era, and what it actually takes to make the shift.
Join us at Columbia's Lerner Hall: https://t.co/vKZNdTuDj4
Agents are getting better at doing the work. They’re still bad at knowing whether the work is done.
That’s one of the hardest problems in long-running agents. They can confidently stop after building half a feature.
The fix isn’t just "give it more context."
Two patterns matter more, and most teams skip them:
1. Don’t let the builder agent grade its own homework.
Use a separate evaluator agent to check the output against clear acceptance criteria.
2. Make failure predictable.
Break work into bounded loops with four constraints:
Fresh context for each loop, max iterations, stop conditions, and a clear exit criteria.
Trustworthy agents need a verifier and a clock. Most teams ship with neither.
Anyone can prompt. Few can build systems that actually deliver.
HackerRank Orchestrate is where developers prove they can do the second one.
24 hours. Real-world problem. Ship an AI agent that works.
June 19 - 20 | Virtual | Registrations close June 18, 8 PM IST
Register now: https://t.co/cNSOEUq7Ov
More MCP tools will just make your agent worse.
When your MCP has hundreds of tools to choose from it becomes a liability.
The model has to read every tool definition. Choose the right one, pass the right inputs, and not blow up the context window before the work even starts.
The better pattern isn't giving the agent more choices. It's giving it a cleaner way to find the right one.
Instead of giving the agent hundreds of preloaded tools, give it a smaller interface: search what exists, write the code, then execute the right call.