A building products sales interview comes down to four things in different wordings: what your job actually involves week to week, who you have access to and how you built those relationships, whether your numbers are real, and what you do when you hit a technical question you cannot answer.
Those are the four things a hiring manager has to establish before they can make a decision, so the wording changes and the ground does not. Below is what each question is really asking and what a strong answer contains.
If you want the preparation routine rather than the answers, that is a separate guide and it is worth reading first.
What are they really asking?
Four things sit underneath the wording.
What does your job actually involve? Asked as some version of "talk me through your average week". They are checking whether the title matches the work. A strong answer names activities with rough proportions and is specific to this industry. A weak one could describe a sales job in any sector.
Who do you have access to? Asked as some version of "who do you sell to" or "who makes the decision". They want to know whether the relationships are yours or the company's, and how you built them. Talk about types of decision-maker, how the relationship started, and how long it took. The method is the part that carries into a new company.
Are your numbers real? Covered in its own section below.
What do you do when you do not know? Say that you will check, name who you would ask internally, and come back with the answer.
How should you talk about your numbers?
Talk about projects, clients and where you sit against the rest of the team.
Give the shape of the thing. Work in ranges and relative context, and only with what you are actually permitted to disclose.
Check that before you sit down. Your contract, and in some cases a project's own confidentiality terms, decide what you can say. Project values, annual volume and internal ranking can all be commercially sensitive, so treat none of them as automatically safe.
- Projects. A typical project value as a range, and roughly how many you run in a year.
- Clients. The kinds of accounts you hold, the ones you opened yourself, the ones you have held longest.
- Where you sit. Performance against the rest of the team, if you are free to say it. Top of the team, top three, best year on record for the area. Any award or internal recognition belongs here too.
That last one carries a lot. A hiring manager hearing "I was the top performer in a team of nine for two years running" has something to measure you by without an absolute revenue figure attached to it.
If you are estimating, say so and use an honest range.
How do you answer the experience question?
With evidence that you have moved into something new before and come good, and with the parts of your current work that genuinely carry across.
"Tell me about your experience in building products" is the question to prepare for when your product background is not an exact match. Two things answer it.
Show you have done this before. If you have moved product or sector previously and come good, that is the evidence. What you had to learn, how you learned it, how long before you were trusted in front of a customer without support. That is a track record with change in it.
Then name what carries across. The market sector, the project types, the customers, the stage of the process you sell at. If you have sold a different product into the same projects and the same people, say so plainly, because that is the part an employer would find hardest to replace. How employers actually weigh that is worth understanding before you walk in.
Name the gap yourself, then show the mechanism that closes it.
What should you avoid doing in the interview?
Two habits are worth avoiding: turning up without knowing what the company sells here, and running down where you have been.
Preparation. Know what the company sells in Australia, who it sells to and how the product reaches the market before you walk in.
Negativity about where you have been. Keep the reason for leaving short and factual.
"The structure changed and the role went in a direction I did not want" is enough. You do not owe anyone the full story at interview.
What should you ask them?
Ask about the things you need to know before accepting, and raise them early.
The questions worth asking are covered in two places rather than here. What separates a good role from a bad one has the verification framework, including what to ask about the area, the OTE and the person before you. The preparation guide has the shorter interview-stage list.
One thing worth saying regardless. Deal breakers are not rude questions. If you need something on money, travel or flexibility, raise it early and clearly. Name both sides' deal-breakers before the offer stage.