Software Engineering Daily · Hands-On Engineering Podcasts · November 2026
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.
…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.
…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?
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…
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.…
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…
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…