Every building products sales interview covers roughly the same ground. Your day-to-day. Your sales process. Your relationships. Your numbers. How you work.
The questions aren't usually surprising. But the answers separate the candidates who get offers from the ones who don't.
This post covers the questions you'll almost certainly face, the ones that catch people out, and the questions you should be asking back that most candidates get wrong.
Not sure where to start? Take the 5-minute readiness check.
The questions you should expect
These come up in nearly every building products sales interview I'm involved in. If you're not ready for them, you haven't prepared.
"Walk me through your average day." They want to understand how you structure your time. How many calls. How many site visits. How much is proactive versus reactive. How you balance existing account management with new business development. Have a clear answer. Don't ramble.
"Talk me through your sales process." From identifying an opportunity to closing it. What steps do you follow? How do you qualify? How do you manage a pipeline? This tests whether you have a repeatable method or whether you're winging it.
"What tools and systems do you use?" CRM experience matters. If you use Salesforce, HubSpot, or even a well-maintained spreadsheet, say so. If you don't use a CRM, that's a conversation worth having honestly rather than pretending.
"How do you like to work? How much autonomy do you need?" They're assessing whether you'll fit their management style. Some companies are hands-off. Some want weekly pipeline reviews and daily check-ins. Be honest about what works for you. If you say you love autonomy and they micromanage, that mismatch will surface eventually.
"Tell me about your key relationships." This is a big one. Building products is a relationship-driven industry. They want to know who you know. Which architects, builders, developers, or specifiers you've built relationships with. Not just that you can build relationships in general, but specifically who you've worked with and how deep those connections are.
Be ready with names, companies, and context. "I've got strong relationships with three of the top-10 commercial architecture firms in Melbourne" is better than "I'm good at building relationships."
"What are your numbers?" Budget, revenue, growth. You need to know your own figures if you're in sales. This isn't optional. If you can't talk confidently about your targets, your actual performance, and how you got there, it raises questions.
You don't need to know every number to the dollar. But you should know your budget, what you delivered against it, and the trajectory. "My territory was $1.6M when I took it over. I grew it to $2.2M over two years" tells the hiring manager everything they need to know.
Ideally, you can show a track record of delivering growth. Nobody expects you to start with a multi-million dollar budget. But you need to demonstrate that you can build. In sales, you're often starting from scratch. Show that you've done it before.
The questions that catch people out
Technical questions you can't answer. If the role involves a product you're not familiar with and the hiring manager asks a technical question, don't try to bluff. You'll get found out. It's never a good look.
"I'm not across the specifics of that product, but I understand the application and here's how my experience with [similar product] would transfer." That's honest, confident, and far better than guessing.
Contradictions with your CV. Sometimes candidates accidentally mention a role or a period that isn't on their resume. Or they describe their responsibilities in a way that contradicts what's written down. Hiring managers notice this. Make sure what you say in the interview matches what's on paper.
The vague numbers answer. "I was doing well" or "My territory was growing" without any specifics. If you can't put a number on your performance, the hiring manager will assume there isn't one worth sharing. Even approximate figures are better than nothing.
The questions you should ask (and how to frame them)
This is where most candidates get it wrong. Not because they don't ask questions, but because they ask the wrong ones at the wrong time.
Questions that show genuine interest and long-term thinking:
- "Where could this role take me? What does career progression look like here?"
- "What would I need to achieve in the next two years for you to consider this hire a success?"
- "What does the team look like? How does the sales team work with technical and marketing?"
- "What are the biggest challenges in this territory right now?"
- "What happened with the person who was in this role previously?"
These questions make the hiring manager see that you're thinking beyond just getting the job. You're thinking about succeeding in it. You're thinking about the long term. You're thinking about how you can support them. That registers.
One question worth borrowing. I came across this from a Diary of a CEO episode with Chris Williamson. "What would have to happen by the end of this year for me to look back and consider it a success?" It's powerful because it shifts the conversation from generic ambition to genuine reflection. It forces both of you to think about what actually matters.
Questions to save for later (or address early in the process):
Specifics around salary, benefits, car allowance, work from home policy. These are legitimate and important. But if you lead with them before you've demonstrated your ability and interest in the role, they get interpreted the wrong way.
The hiring manager hears "what's in it for me?" before they've heard "here's what I can do for you." It doesn't come across as genuine interest. It comes across as purely self-interested.
I completely respect that everyone needs to make the best decision for themselves. It's just about how you frame it and when. If salary or work from home are genuine deal breakers, raise them in the phone screen before the interview. Get them out of the way early so neither side wastes time. But don't lead the interview itself with them.
The deal-breaker conversation
This connects directly toPart 1 of this series, but it's worth repeating because it costs candidates so many opportunities.
If you have non-negotiables, surface them in the phone screen. Before the interview. Before everyone invests hours in the process.
The two biggest deal breakers that come out too late:
- Salary expectations that don't match the budget.
- Work from home expectations that don't match the policy.
These are straightforward to resolve early. They become painful when they surface at the offer stage. I've seen entire processes collapse because a candidate waited until the final round to mention that they need two days from home and the company requires four in the office. That could have been a two-minute conversation in week one.
Be clear where your process is at. If you're waiting on other offers, tell the hiring manager or the recruiter so they can move at the right speed. If you need a week to think, say so. Transparency makes everything smoother.
The biggest red flag in how you answer
Saying yes to everything.
I see it regularly. A candidate says in our phone call that they don't want to be in the office five days a week. Then in the interview, when asked if they're happy to be in the office every day, they say yes.
I understand why it happens. You want the job. You want to please the interviewer. You think you'll sort it out later.
But hiring managers see through it. When someone agrees to everything without pushing back or asking questions, it doesn't build confidence. It raises doubt. Are they telling me what I want to hear? Will they actually be happy in this role? What else are they agreeing to that they don't really mean?
It's better to be honest. "I'm flexible on office days, but ideally I'd like one or two days from home each week. Is that something that works here?" That's a mature, confident answer. It shows self-awareness. And it gives the hiring manager real information to work with.
Check the culture before you start
Culture fit is hard to assess from an interview alone. You can ask about it, and you should, but the answers you get in an interview will always be the polished version.
Two better ways to find out what a company is actually like to work for.
Use your network. Ask around. See if anyone you know works there or has worked there before. In building products, the industry is small. Someone in your network will have an opinion. That firsthand perspective is worth more than anything a hiring manager will tell you in an interview.
Ask to meet the team. If you've been offered the role or you're in the final stages, ask to have a quick meet and greet with a couple of your future colleagues. Most reasonable companies will accommodate this. It gives you a feel for the team dynamics, the office environment, and whether you'd actually enjoy working there.
Culture is one of the hardest things to evaluate from the outside. But it's also one of the most common reasons people leave a role within the first year. Do your homework.
Quick checklist
- Know your numbers. Budget, revenue, growth, key wins. No vague answers.
- Be ready to talk about your relationships. Names, companies, depth.
- Don't bluff technical questions. Honesty beats a bad guess every time.
- Ask questions that show long-term thinking and genuine interest in the role.
- Save salary and benefits questions for the phone screen or the end of the process, not the start of the interview.
- Surface deal breakers early. Salary and work from home expectations should be clear before the interview.
- Don't say yes to everything. Honest answers build more trust than people-pleasing.
- Check the culture through your network and by meeting the team before you accept.