Say each answer aloud and swap the example for something you did. For questions that show up in every process, use the HR interview questions for freshers guide.
Contents
Technical/role knowledge
1. What is a useful difference between a lead, a prospect and a customer?
Say that teams define the words differently, then give a working version you can adjust. A lead might have a need and is not yet qualified, a prospect is a lead you have reason to pursue, and a customer has bought. Offer to learn the team’s own definitions in the first week rather than insisting on yours.
I treat a name on a list as a lead until I know there is a real problem and a person who can decide. After that I call them a prospect. A customer is someone who has already bought.
2. What should a discovery conversation find out?
Look for the problem, what they do today, who decides, the timing, and what a good result looks like. It is not a tour of features. Mention the offering only after you know which part of it matches the problem they described.
I would ask what is awkward about the current way they hire or train, who else has to agree, and when they need a change. I would not open with a list of modules.
3. What has to be true of every open item in a simple pipeline?
Each item needs a stage both people would define the same way, a next step, and a date for that step. Stages such as contacted, meeting set, or waiting on a decision only help when the meaning is shared. An item with no next step is a note, not a live opportunity.
If I spoke to someone and the next step is a call on Thursday, that item stays open. If I do not know what happens next, I either set a step or take it off the active list.
4. How is a business development role different from sending a lot of messages?
Messages are one tactic. The role is to find relevant conversations, understand the other person’s situation, and leave every live one with a next step. A high number of messages with no next step is activity, and I would not describe it as a pipeline.
I would rather have ten conversations with a written next step than a hundred notes that all say I am just checking in. The job is the next step, not the send count.
5. What makes a follow-up useful?
It refers to the last conversation, adds something that helps them decide, and asks for one specific next step. A message that only says you are checking in does none of those. Agree with yourself when you will stop if they do not reply.
I would mention the timing they gave me and ask for a 15-minute call on one of two days. If there is no reply after a few notes that each add something, I would close the loop politely.
Problem solving and scenario
6. Someone says to send a brochure and then goes quiet. What do you do?
Send what you promised, and add one question the brochure cannot answer. Propose a short time to talk, then stop after a few attempts that each add a new point. Do not resend the same line on a schedule and call it persistence.
I would send the brochure and ask which of two problems is closer to their year. I would offer Tuesday or Thursday for a short call. I would not write just checking in three times.
7. You must make a first call about a product you learned yesterday. How do you prepare?
Learn who it is for, the problem it addresses, and two questions you can ask. Write down what you will not claim, including any price or result you have not been given. Open by checking whether the problem is real for them, not by reading a paragraph.
I would learn the problem and two questions, and I would leave price to the person who owns it. I would start with their current process and only then connect a part of the product.
8. A prospect says it is too expensive. How do you respond without inventing a discount?
Ask what they are comparing it with, and restate the outcome they said they wanted. Do not offer a discount you cannot approve, and do not invent a saving or a return. Offer to bring in the person who can discuss commercial terms, or to narrow the scope if that is a real option.
I would ask whether they are comparing it with another tool or with doing the work by hand. I would not name a cheaper price. I would offer a call with the person who can talk about terms.
9. You have thirty leads and one afternoon. How do you choose?
Sort by a stated problem and a possible next step, not by who is easiest to message. Spend the time on conversations that could move, and write a next step or a reason to pause for each person you touch. Leave the rest with a time you will return, rather than a half-written note to all thirty.
I would call the people who already described a problem and a date. For the others I would schedule a later pass instead of sending one vague message to the whole list.
10. You promised a callback and missed it. What do you do?
Apologise in one sentence, without a long excuse. Offer two specific times and keep the one they pick. The repair is the call you then make, not the wording of the apology.
I would say I missed the time and offer today at four or tomorrow at eleven. I would not explain my whole day. I would make the call at the time they choose.
HR and behavioural
11. Tell me about a time you persuaded someone.
Use a real ask: a sponsor for a college event, a teammate, or a family business. Cover who they were, the objection, what you changed after you listened, and what they agreed. Do not invent a revenue figure or a conversion rate.
I asked a local shop to sponsor our fest stall. They said they had been promised footfall before and saw little. I offered a smaller package with a named slot and a photo they could use, and they took that rather than the large one.
12. Describe a rejection and what you changed afterwards.
State the no, what you think caused it, and the specific change in your next attempt. Keep the lesson behavioural, such as asking one more question before you pitch. Do not claim the next attempt always succeeds.
A club refused a collaboration because my first message was all about our needs. I rewrote the next request to start with their calendar and one ask. They still might have said no, but the second conversation lasted long enough to be useful.
13. How would you talk about a target you might miss?
Say it early, with the gap, the cause you can actually see, and the next action. Separate a thin pipeline from a late-stage stall, because the response is different. Do not wait for the final day and do not hide the number.
I would tell my manager the count I am short, which conversations are stuck, and what I will do this week. If the stuck ones are waiting on another team, I would say that rather than promise I can close them alone.
14. Why sales or business development?
Point at a conversation where questions changed the outcome, not at a liking for talking. Say you are comfortable with a no if you handled the conversation cleanly. Add what you want to learn, such as how a team qualifies a lead.
I like the part where a question changes what I offer. In college that was sponsorship, and the useful skill was hearing the objection before I answered it. I want a first role where that is the work, with someone reviewing my notes.
15. Tell me about a time you changed what you said because you listened.
Quote the assumption you walked in with and the fact that replaced it. Show the new sentence you used. End with the next step, even if the answer was not a yes.
I assumed a junior college wanted a long workshop. They said their constraint was one free period. I cut the offer to a single session with a leave-behind, and we booked that instead of the series.