Best Practices
Talent Acquisition

Diary of a High Volume Recruiter Series: Ronnie Bratcher [Live from RecFest]

Chandal Nolasco da Silva
Chandal Nolasco da Silva
November 17, 2026
In This Article
Chandal Nolasco da Silva
Chandal Nolasco da Silva
November 17, 2026
summary

We're excited to bring you another special edition of this series, featuring sourcing veteran Ronnie Bratcher, Talent Sourcing Specialist at Black & Veatch. We sat down with Ronnie on the floor at RecFest USA in Nashville alongside our friends at WRKdefined. The one and only William Tincup hosted the session.

Subscribe to our Newsletter

Like what you're reading? Leave us your email, and we'll deliver to your inbox on the last Thursday of the month.

This series is dedicated to sharing the wisdom of high-volume recruiters. These are the hardest-working people in the industry. So we're asking how they get hiring right at scale. Recorded live, here is a special instalment of our high-volume recruiter series.

Meet Ronnie Bratcher. Ronnie has spent 27 years in sourcing and recruiting working everywhere from Microsoft to Amazon. He has watched hiring technology arrive in waves, and each time the prediction was similar. The tools would replace the people. His view is more practical. Watch or read the discussion below to get Ronnie’s take on reading skills beyond the keywords, and on where AI does and doesn't belong in hiring.

Interview Transcript: Ronnie Bratcher × WRKdefined

[00:00] William: Ronnie is one of the foremost sourcers in the world, which I know you would never say about yourself. But I will say that about you, because I've known you long enough to say that about you.

How do you view skills? When you get a req, and you're trying to go out and find the needle in the haystack, or the purple squirrel in the purple forest, or whatever the reference is, how do you look at skills?

[00:23] Ronnie: Yeah. So skills can be… it could be a hard stop, because on the req you read it as…

[00:31] William: Right.

[00:33] Ronnie: Let me give you an example from the engineering world. Art. But that can also mean other things. So what happens with sourcers and recruiters in our industry is that they don't go beyond the means of assessing that word that can mean other things that might not be written in their profile. So, from the old-school way, you would use the web to find synonyms. I can’t say that word very well by the way (laughs).

[01:02] William: Right. I say cinnamon.

[01:04] Ronnie: Yeah, cinnamons. But to find alternative meanings of that word that could be the same thing. So…

[01:10] William: And this is tangential skills. If they know Ajax, then you probably know … ok got it.

[01:15] Ronnie: Something yeah. That's one thing that I do now. And there are tools out there doing that kind of work for us, and we also have AI as well, of course. But I don't think our general population really sees it that way. They always think: this is the job, this is the role, those are the words. They don't think about how you can go beyond that. So that's the way I view skills.

[01:41] William: Well, in most development languages on the tech side, C and C++ are kind of the foundational stuff. If they know C and C++, they can pretty much learn anything else.

[01:50] Ronnie: If they want to learn.

[01:51] William: If they want to. They can read a Nutshell book over a weekend, and yeah they've got it. In fact, that happened to me when I had a web development agency. We had a project that was done in Perl, which…that takes you back.

[02:07] Ronnie: Yep. 

[02:08] William: But the developer didn't know it. He was an SMU in computer science graduate. He went home over a weekend, read a nutshell book, and then I get it, I can develop a site.

[02:15] Ronnie: Yeah, so that's kind of how I use skills assessment. Going beyond the keyword mumbo jumbo, being more intelligent, using all the tools that are available to you.

[02:25] William: How do you think about dimensionality? The difficulty I used to have in hiring for developers was that somebody would put HTML, which shows how long ago this was. Or, say, a Java developer: you have nine years of Java development experience? That's fantastic. Was that 20 different projects where you went this deep, or one project that went this deep? What's the dimensionality of that Java development skill? When you're working with candidates and trying to find those folks, how do you figure that stuff out?

[03:09] Ronnie: That's usually just the question. You can assess that from the profile, where you're like, "I don't really see where they're using this. It looks like they just did it at this particular organization." So, going from a sourcer to the recruiting mentality: why not just reach out to them? Let's just get into the conversation. They can say no. They can say, "Oh, I only did this at this organization for three months." And you're like, okay, well, we're looking for more.

[03:35] William: There's a depth thing here.

[03:36] Ronnie: Yeah. So you know Glen Cathy. I just wanted to drop a name today… just talked today about how not everything's going to be there.

[03:46] William: Right! 

[03:47] Ronnie: Why not reach out to them, it’s just a conversation? It's just another connection. If they don't want to connect, they're not going to connect. So you've got to have that conversation. You're going to learn more. I'm working on a role right now where, if you don't talk to these people, you're not going to know. It's all about product ownership, and they don't really talk about product ownership. So you've got to ask them those questions: What did you do with this product? Did you own it? Who were your stakeholders? Did you work with vendors? Did you work with developers? You have to. You just can't write them off.

[04:25] William: Right. Well, fraud has always been in staffing, recruiting, sourcing, et cetera. We've always dealt with fraud; that's not new. However, now, especially with ChatGPT and some of these other models, you can take a job description and then take your resume and say, "Make my resume look like this job description.” I need to know what you're doing with this particular skill, so I understand what we have here. And I think you're right. There's the human part of that which people have wanted to skip over for the last couple of years: "AI is going to replace…" It's like, okay, that's cute. Like "the internet is going to replace us…" all this other stuff.

[04:58] Ronnie: With the group I traveled up here with today, we had this conversation this morning. It wasn't specifically about the skills assessment piece, but just about how I think the main talk of this whole conference is that all these tools are doing this. I talked to two leaders I rode up with today and asked them that question: what are your thoughts on this? And basically the answer I got was: if you're doing general, high-volume roles, yes, you can use an AI tool to do the skills assessment. Can you lift 50 pounds? Can you show up to work every day? Can you deal with customers? But at the opposite, higher end, say I'm working on a ServiceNow role, which is more of a professional role, you cannot have an AI tool do that. It's going to take a human to connect and get all that data. It's archaeology, anthropology, pulling out all those things.

Going back to the question of AI taking away sourcing: it depends on the role. And in my personal opinion, with all these great tools… this isn't my first rodeo. I'm 27 years into my career. It seems like I've seen different cycles of…

[06:20] William:  A lot of waves.

[06:21] Ronnie: I worked before the internet. So basically, you've got to take what we have and adapt. And in my opinion, talking about what I know, which is sourcing: I'm going to take these tools and they're going to help me be faster, but I'm going to be the quality check. I do not want the tool to automatically send professional service. Right now people bypass a need before it gets to a person.

‍[06:53] William: When all that started with "AI is taking away sourcing. We're going to get rid of sourcing, blah blah blah." Actually, the first thought I had was that it pushes sourcers more toward sourcing operations, which is absolutely needed. Like recruiting operations, you need sourcing operations: someone to manage all the tools, look at things, watch what's working and what's not, what needs to be calibrated, this, that and the other. So I was actually excited. You don't have to be deep into whatever you’re doing; you can be managing some of that. But I think you're right about the line of demarcation. If you're hiring hourly, that's a different toolset and a different candidate set. If you're hiring professional, that's a different toolset and different candidates.

[07:38] Ronnie: And I think we do have to educate the executive branches of staffing right now, the VPs and the CEOs, who think these things are going to take away payroll. There's a lot of talk at this conference about decreasing payroll costs, which is fine. I get that; it's a business. But we need to educate them that these tools are going to better us. They will save some payroll, but we still have to have that quality check.

[08:08] William: Yeah. Well, what's not being factored in is the amount of cost being sunk into AI, and whether or not it's working. So yes, you have less headcount, but you're actually spending more in terms of headcount plus technology. It looks better on the balance sheet because there's less headcount. Revenue per employee looks better, and Wall Street and Silicon Valley love that number. But at the same time it’s like okay, how much money is going into AI? That number isn't as tracked.

[08:40] Ronnie: So that's kind of what I'm getting out of this conference, and that’s the conversations I'm having here with people here and just listening in and hearing the different views on what people are saying. But in my opinion, I don't think my job's going to go away.

[08:57] William: Exactly. Nor should it.

‍

HiringBranch would like to extend a sincere thank you to Ronnie Bratcher for participating in this special edition of our series, and to WRKdefined for making the conversation happen. For the previous interview in this series, click here, and stay tuned for the next installment coming next month.

Image Credits

Feature Image: Property of HiringBranch. Not to be reproduced or distributed without permission.

‍

Explore more blog posts

Cures for the Most Common Call Center Problems
Contact Center
Customer Service

Cures for the Most Common Call Center Problems

Interview with a Call Center Veteran: Better Quality Agents Starts at the “R” not the “T”
Contact Center
Customer Service
High-Volume Recruitment

Interview with a Call Center Veteran: Better Quality Agents Starts at the “R” not the “T”

45 Talent Acquisition Statistics to Guide Your Hiring Strategy
Talent Acquisition

45 Talent Acquisition Statistics to Guide Your Hiring Strategy