VR

Vivek Ravisankar

Things Vivek Says on Podcasts

Where to Find Them

Vivek Ravisankar has been a guest on Indie Hackers Podcast , Software Engineering Daily , Y Combinator Startup Podcast and Software Engineering Radio - the podcast for professional software developers .

Recently: “The Technical Interview Is Broken” on Software Engineering Daily (November 2026); “SE-Radio Episode 350: Vivek Ravisankar on HackerRank” on Software Engineering Radio - the podcast for professional software developers (December 2018); “#66 - Breaking Down HackerRank's Survey of 40,000 Developers with Vivek Ravisankar” on Y Combinator Startup Podcast (March 2018); “#030 – Pivoting Your Way to Three Million Users with Vivek Ravisankar” on Indie Hackers Podcast (September 2017).

What They Said

“I think we've changed the way that we build software, but I don't think we've changed the way that we review software. … You're still reviewing PRs. You're still reviewing code, but you've completely changed the way that you build software. … Maybe you should review the interaction with AI. What did the person actually talk to the AI? What do they actually say?” — Vivek Ravisankar, Software Engineering Daily

Asked whether HackerRank could move into code review, Ravisankar says review tools still look at the pull request even though AI has changed how code gets written, and suggests reviewing the conversation with the agent instead.

Software Engineering Daily · 2026-11-17 Permalink → Listen →
Software Engineering Daily Around 44:02 into the episode
Vivek Ravisankar

…of this can expand beyond just like hiring and beyond just Frontier Lab because you can transpose the same infrastructure to a larger business in the AI era. And that's something that we're building from ground up. It's not yet launched, but will launch pretty soon. We'll see how that goes.

Josh Goldberg

Good luck. I wonder if you could move or pivot or expand into other areas of developer life. Like, could you do code reviews or open source contribution validation just as a service based on the similar models or evals criteria?

Vivek Ravisankar

…I think, we've changed the way that we build software, but I don't think we've changed the way that we review software. I mean, yes, there is Greptile and Code Rabbit and things in those science that you can actually do auto reviews, but you're still reviewing PRs. You're still reviewing code, but you've completely changed the way that you build software. Like, I have some ideas on it, which is maybe you should review the interaction with AI. What did the person actually talk to the AI? What do they actually say? That's probably, I wouldn't say better, but that's an important signal in conjunction with your PR that you need to think about. So if I have to extrapolate, I think the shape of code review in itself will change quite a bit. We'll need to see how it changes, and then we'll obviously immediately adapt in the way that we think about hiring.

Josh Goldberg

That's so interesting. And now that you said it, it's such a hacker-ranked Vivek Ravisankar that you're evaluating not just the output, let's say, of an interview answer or the author of the pull request's actual pull request, but you're also evaluating the thing that went into that, how they…

Vivek Ravisankar

Yeah, yeah, agree. Because by the way, people do this all the time. I'm sure you have observed this, which is if you're going to give me a PR slop of, okay, there's like, you know, 50 files changed for a minor fix. Like, firstly, I'm going to probably reject that. And second, if at all I want to…

Josh Goldberg

Well, I look forward to interviewing you again in two years once it's all been figured out.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“I think the difference between any AI product that is a slop and a magical experience is in the quality of your evals. That's what it comes down to.” — Vivek Ravisankar, Software Engineering Daily

Asked how HackerRank keeps its AI interviewer from being biased or running on rote paths, Ravisankar explains why his team built an applied research group focused on evaluation.

Software Engineering Daily · 2026-11-17 Permalink → Listen →
Software Engineering Daily Around 29:37 into the episode
Vivek Ravisankar

…That's what we have actually built in a collaborative environment for both of them to get a sense of what it is like to work together with the person as well as on a real-world task. So, we call it the AI-led screen and the human-led interview. So, that is the combination for the next-gen process.

Josh Goldberg

…are a lot of common biases or repeat points that don't work well. So, given the very sensitive nature of an interview and the mixed non-deterministic results you get from AI, how do you make sure that this thing is actually interviewing properly and not just kind of going down rote original paths?

Vivek Ravisankar

…people speak to AI, it's usually in a voice form that people are used to. You've spoken to Alexa, you've spoken to Siri, spoken to ChatGPT voice. It doesn't have a video of TAR. So people are comfortable talking to AI and voice. So don't put a video on that. So the second one is like the form factor of how it actually appears. The third one, and by the way, this is all in no particular order. I think the difference between any AI product that is a slop and a magical experience is in the quality of your evals. That's what it comes down to. So we have a real applied AI research team that actually works on evals where we run chakra across many different scenarios, how much it can probe, how much it can pull back, how much it's able to ask follow-up questions so that it is Meaningful and it's really good. And we continuously make sure that we can improve our evals. And the fourth one is it needs to be like a combination of work and…

Josh Goldberg

Are you worried that if everyone uses something like Chakra, there won't be any strong differentiation between how different companies interview? Like, let's say that you build chakra and then Lee Code builds chakra. Like, how do you differentiate the hacker rank version of this versus your…

Vivek Ravisankar

A lot of it comes down, I think. Maybe I'll speak at the core aspect and then we can talk about like the specific features. I think there are two things that underpins success in this field: how strong is your evaluation and how strong is your integrity. So, you need to be able to make sure that…

Josh Goldberg

First of all, I'm excited to hear you. You seem genuinely excited about the product quality. But I do want to hone in on one little point you made there about bias because there's been a lot of research showing that traditional AI models are in fact biased against, let's say, folks who sound or…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“There was a lot of chatter on software engineering is dead. It still is there right now every time Anthropic or OpenAI launches a new model. But I think the narrative has shifted from software engineering is dead to software engineering is everywhere.” — Vivek Ravisankar, Software Engineering Daily

Asked where HackerRank's AI interviewer could go beyond technical roles, the CEO says customers now want to assess product managers, designers and support staff who build things with AI.

Software Engineering Daily · 2026-11-17 Permalink → Listen →
Software Engineering Daily Around 36:01 into the episode
Vivek Ravisankar

…grammatical correctness is a different one. We haven't actually seen that level of variation. But if you're going to use like Chakra for a general voice interview for 60 minutes, I can certainly see variance happening. And even that, we try our best to make sure that our evals work in that way.

Josh Goldberg

…question I'm sure a lot of your accompanying customers have is: well, what else can we use this thing for? Could you use it for culture screen or non-technical roles overall? Where do you see the end line or the final goal of it? Is there a line that you won't cross for a tool or system like this?

Vivek Ravisankar

Yeah, it's a really interesting question. It's one of those things I've thought about where we went from, I think, 2023, 2024, there was a lot of chatter on software engineering is dead. It still is there right now every time Anthropic or OpenAI launches a new model. But I think the narrative has shifted from software engineering is dead to software engineering is everywhere. Because what we see in our customers is: wow, this chakra really works well for software engineering job family. But my product managers are also building stuff. Maybe we should use chakra for product managers. Or my designers are also building stuff. Maybe we should use that. Well, my customer support person is no longer responding to tickets. They're building agents that can actually respond…

Josh Goldberg

It's funny you should mention that. My favorite story to tell about one of the recruiting situations I was in was there was a candidate who did very, very well technically, but failed the interview overall because he had found on LinkedIn one of the recruiters a woman had previously done modeling.…

Vivek Ravisankar

Yeah, I think we use in terms of like how the way Chakra evaluates is on three dimensions broadly. One is, were you able to do the work? The second is, how effectively did you use AI to do the work? And third is, do you understand what this is all about? So those are the three aspects. The first…

Josh Goldberg

I love that. There's a very common trope these days of software developers who just slop cannon something over their peers, meaning they throw something at the AI, it creates some output that vaguely looks good, and then they send it off for peer review. And then if they're lucky, a human will…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

Collections They Appear In