Fresher sales executive rounds test whether you can talk to strangers, take rejection, learn a product fast and explain simple sales ideas in your own words. They rarely ask for numbers you have hit, because you have none yet. Expect short role-plays, a few basics like leads versus prospects, and questions about fests, part-time jobs, internships and group projects. It is written for final-year students, new graduates and anyone coming out of an internship who wants a first job in sales. Each question shows what the interviewer is checking, the shape of a good answer and a sample you can say out loud. Swap in your own stories before you practice.
Search all questions by round, difficulty and level, or save the ones you want to practice.
Pick one real example: a fest, a part-time job, a family shop, a club drive.
What you did: who you approached, what you said, what happened.
What it taught you: one lesson you will carry into this job.
“The closest thing I've done to sales was getting sponsors for our college cultural fest. I was on a team of four and we had to raise money from local shops and a few small companies. At first I just handed over a brochure and asked for support, and almost everyone said no. Then I started asking owners who their customers were, and pointed out that most of our visitors were students who lived nearby. That changed the conversation, because I was talking about their business, not our fest. I signed up six sponsors that season. It taught me that people say yes when you talk about what they get, and that's a big part of why I want to start my career in sales.”
Saying you have no experience of persuading anyone, or giving a story where someone else did all the talking.
The day: calls, visits or meetings, follow-ups, updating records, reporting.
Honest hard part: name one thing that will be tough for you.
Your plan: how you'll get better at it.
“From what I've read and from talking to a friend who sells for a distributor, I think the day starts with planning who to call or visit, then a long block of calls or field visits, then follow-ups, and updating the system with what happened before going home. There's probably a daily or weekly check-in with the manager on numbers too. The part I expect to find hardest is the volume of rejection early on, when I don't know the product well and people hang up quickly. My plan is to prepare a few strong opening lines, learn the most common questions customers ask in the first two weeks, and track my calls so I can see myself improving even before I start closing.”
Describing only meetings and closing deals, or saying nothing about the job will be hard.
A realistic goal: a strong individual performer, a bigger territory or key accounts.
Skills to build: product knowledge, prospecting, handling objections, planning.
How you'll learn: shadowing, feedback, practice.
“In two years I'd like to be someone my manager trusts with bigger or harder accounts, and ideally hitting my target most months without being chased. I'm not aiming to manage people that soon, because I think you need to be a strong seller first. To get there I'll need to know the product and the competition really well, get good at finding my own leads rather than waiting for them, and handle the common objections calmly. I'd also like to learn how to plan my pipeline so I'm not scrambling at month end. The way I plan to learn is by shadowing the best rep on the team in my first months, asking for feedback after calls, and reviewing my own numbers every week.”
Saying you want to be a manager in six months, or that sales is a stepping stone to something unrelated.
Context: the company, your role, how you met customers.
What you saw: a real moment when someone bought or didn't.
The lesson: what drives the decision, in your own words.
“I did a two-month marketing internship with a company that sells water purifiers. Most of my work was calling people who had filled in an enquiry form online, to book a home demo. What surprised me was that price almost never came up in the first call. People wanted to know if someone would come and service it, and how quickly. The ones who booked a demo were usually the ones where I could answer that clearly. When I didn't know the service details, they'd say they'd think about it. So I asked the service team for a simple sheet with timings and areas, and my booking rate went up noticeably in the last few weeks. What I learned is that people buy when they feel safe after the sale, not just when the product sounds good.”
Describing only office tasks with no customer contact, or having no lesson to share.
The disagreement: what the team wanted and what you proposed.
How you persuaded: listened first, used facts, gave them a way to say yes.
Result: what happened and what you learned.
“In a marketing project in my final year, we had to plan a launch for a new snack brand. Most of the group wanted to spend the whole imaginary budget on social media ads. I thought we should also do sampling near colleges, because the target buyers were students and they try food before they buy it. Instead of arguing in the meeting, I asked each person what worried them about my idea. The main worry was that it was hard to measure. So I suggested a small trial with a coupon code on every sample so we could count who came back. They agreed to split the plan. Our faculty liked that part most. I learned that people move when you deal with their worry, not when you repeat your point louder.”
A story where you won by being the loudest, or where the team simply gave in to you.
The deadline: what you had to learn and how little time you had.
Your method: sources, notes, practice out loud, asking experts.
How it went: result and what you'd reuse on a new product.
“In my second year I joined a business quiz team a week before the event because someone dropped out, and the theme was banking and payments, which I knew almost nothing about. I made a list of the twenty terms that kept coming up in old quiz questions and wrote one simple line for each in my own words. Every evening I explained five of them out loud to my roommate, because if I couldn't explain it simply I didn't really know it. I also asked a friend studying finance to quiz me on the hard ones. We came second in the college round. I'd use the same method for a new product: learn the words customers use, explain each one simply, and test myself on the hard questions before I face a real buyer.”
Saying you'd just read the brochure, or describing a last-minute cram with no method.
The situation: internship applications, sponsorship, a club drive, a survey.
How it felt and what you did: honest, then practical.
What you changed: a new approach and the result.
“In my third year I applied for summer internships and got about thirty rejections or no replies before anything came through. For the first few weeks I was sending the same CV and a generic message to everyone, and I started taking the silence personally. Then I sat down with a senior who'd got placed and she pointed out my messages didn't say why I wanted that company. So I changed my approach. I applied to fewer places, read about each one, and wrote two lines about what I could help them with. I also started messaging people who worked there, not just the careers email. Within three weeks I had two interviews and one offer. What kept me going was treating each no as information, not a verdict on me.”
Claiming rejection never bothers you, or giving a story where you gave up without changing anything.
The goal: clear and measurable.
Tracking: how often you checked and what you wrote down.
Adjusting: what you changed when you fell behind, and the result.
“Before my final year, I set myself a goal to run ten kilometres in under an hour, because I'd never run more than three. I made a simple sheet with three runs a week and wrote down distance and time after every run. Around week five I stopped improving and nearly gave up. Looking at the sheet, I could see I was running too fast at the start and dying at the end. So I slowed my first two kilometres and added one longer, slower run each week. I hit the target in about eleven weeks. I think that's close to how a sales target works. You break it into weekly actions, you check the numbers honestly, and when you stall you look for the one thing to fix instead of just trying harder.”
No real number, no tracking, or a goal that someone else set and chased for you.
Respect the time: say who you are and ask for a short slice of it.
One reason to care: a problem people like them usually have.
Small ask: a short visit or a better time, not a sale on the phone.
“Sorry to catch you at a busy time. I'm Riya from a company that supplies billing machines to shops in this area. I'll be very quick. A lot of shop owners tell us the rush hour queue is where they lose customers, because billing by hand is slow. We've helped a few shops near you speed that up. I don't want to explain it over the phone while you're serving people. Could I drop by for ten minutes on a quieter day to show you? Would tomorrow morning or Thursday afternoon suit you better? And if it's easier, I can call back after closing time today instead. Whatever works for you.”
Launching into a long pitch about the company or product before giving the owner a reason to listen.
Don't dismiss them: they can still open the door for you.
Ask how decisions are made: who else is involved, what they care about.
Next step together: ask them to help set up a meeting with the decision maker.
“I'd keep treating that person with respect, because they often know the problems best and they can help me get to the right person. I'd ask something simple like, 'When your company buys something like this, how does that usually work, and who else would want a say?' Then I'd find out what matters to each of those people, so I'm not guessing later. Before leaving I'd ask whether they'd be willing to set up a short meeting with the decision maker, and whether they'd like to join it. I'd also offer to send them a short summary they can forward. Next time, I'd ask about who decides when I book the meeting, not halfway through it.”
Losing interest in the person as soon as you learn they can't sign, or asking to go over their head.
Follow up with value: send something useful, not just 'any update?'
Vary and space it: different times and channels, a few days apart.
Close the loop politely: a final message that makes it easy to reply either way.
“First I'd remind myself that silence usually means they're busy or it's slipped down their list, not that they hate me. I'd send a short message with something useful, like the answer to a question they asked in the meeting, rather than just asking for an update. If there's no reply, I'd try a call a few days later at a different time of day. After three or four tries over a couple of weeks, I'd send a polite final note saying something like, 'I don't want to keep chasing you. If now isn't the right time, just let me know and I'll check back in a few months.' That often gets a reply. Either way, I'd note everything in the system and set a reminder to try again later.”
Calling every day until they answer, or giving up after one unanswered message.
Open questions: start with what, how, tell me, so the customer talks.
Three real examples: current way, what's not working, what a good result looks like.
Listen and dig: follow up on their answers before you pitch.
“I'd use open questions, the ones that can't be answered with yes or no, so the customer does most of the talking. My first would be, 'How do you handle this today?' That tells me what I'm replacing. The second would be, 'What's the most annoying part of doing it that way?' That's where the real need usually is. The third would be, 'If this worked perfectly six months from now, what would be different for you?' That gives me the words I should use when I do pitch. Then I'd follow whatever they say with 'Tell me more about that' before jumping in. The mistake I want to avoid is hearing one problem and starting my pitch straight away, when there's often a bigger reason underneath.”
Listing only yes-or-no questions, or saying you'd explain the product first and ask questions later.
Let them finish: no interrupting, pause before you reply.
Play it back: sum up what they said in their own words and check.
Use it: your pitch refers back to what they told you.
“For me it comes down to three things a customer can see. First, I let them finish, even when I think I know what they're going to say, and I take a moment before answering. Second, I sum up what I heard and check it. Something like, 'So the main issue is that orders get missed when your staff are busy, is that right?' If I've got it wrong, they correct me, which is useful. Third, I use their own words when I explain how we can help. If they said 'missed orders', I don't start talking about 'workflow efficiency'. I also take short notes, which shows I care about getting it right. The real test is whether my pitch sounds like it was made for them.”
Just saying 'I'm a very good listener' with no example of what you actually do.
Prepare: check what each customer bought, when, and any notes on why they left.
Open with a question: ask how things went and why they stopped, and listen.
Next step: fix what can be fixed, offer something relevant, record everything.
“I wouldn't start dialling straight away. First I'd look up what each customer used to buy, how often, and whether there are any notes or complaints in the system. I'd also ask my manager or a senior if they know why people on this list dropped off. Then I'd sort the list, starting with the ones who bought most. On the call I'd say I've just joined, I can see they used to buy from us, and I'd genuinely like to know why they stopped. Most people will tell you if you ask honestly. If it was a service problem, I'd check whether it's been fixed before promising anything. If they moved to a competitor, I'd ask what they like there. Then I'd note every answer, because even the no's tell my manager something useful.”
Treating the list as cold leads and pitching the same script to everyone without checking their history.
Learn the business: what they do, size, customers, recent news.
Learn the person: their role and what they probably care about.
Plan the meeting: a goal, a few questions, likely objections, the next step you want.
“I'd spend about an hour, not the whole night. First I'd look at their website and social pages to understand what they sell, who they sell to and roughly how big they are, and I'd check for any recent news, like a new branch. Then I'd look up the person I'm meeting, what their job is and what they'd likely be judged on. After that I'd check our own system to see if anyone from our company has spoken to them before. Then I'd write down one goal for the meeting, usually to understand their needs and agree a next step, plus four or five questions and the two objections I think they'll raise. Finally I'd check the route and plan to arrive ten minutes early.”
Saying you'd just turn up and see how it goes, or planning a long product presentation with no questions.
Stay calm and honest: you're new and want to check what was agreed.
Don't promise: no discount you aren't allowed to give.
Follow through: check with your manager and call back when you said you would.
“I'd say something like, 'Thanks for telling me. I'm new on your account and I want to make sure you get whatever was agreed with you. Let me check what arrangement you had and call you back by this evening.' I wouldn't say yes on the spot, because if I give a discount I'm not allowed to, I've set a price I can't take back and I've gone around my manager. I also wouldn't flatly say no, because they may be right. Then I'd check the account history and ask my manager straight away. If there was a standing discount, I honour it. If there wasn't, I'd ask my manager what I can offer instead, and call the customer back on time with a clear answer. Calling back when I said I would matters as much as the answer.”
Giving the discount to keep the customer happy, or refusing flatly without checking whether they're right.
Your line: you won't give a customer a date you know is false.
Still sell: be honest about the real time and give a reason to buy anyway.
Handle the colleague: stay polite; raise it with your manager if it keeps happening.
“I'd politely not do it. I'd tell the customer the honest time, maybe say it usually takes around ten days and that I'll message them as soon as it ships. Most people accept a longer wait if they know it upfront. What they don't forgive is being told three days and waiting ten, and then they don't buy again or they tell others. With my colleague, I wouldn't lecture them. I'd just say I'm not comfortable giving a date I can't stand behind, and that I'd rather lose a sale than lose the customer later. If I saw it happening a lot, I'd mention it to my manager as a customer problem, not a complaint about a person, and ask whether we can speed up delivery or explain it better.”
Going along with it because you're new, or turning it into a public fight with the colleague.
| Lead | someone who might be interested, not yet checked. |
|---|---|
| Prospect | a lead you've qualified: they have a need, can buy and could decide. |
| Customer | someone who has bought, and whom you want to keep. |
“A lead is just a name that might be interested, like someone who filled in a form on the website, visited our stall at an event, or a shop I spotted on my route. I don't know yet if they need what we sell. A prospect is a lead I've spoken to and checked. They have a real need, they can afford it, and I'm talking to someone who can decide or influence the decision. A customer is someone who has actually bought. The difference matters because my time is limited. If I treat every lead like a prospect, I'll spend hours on people who were never going to buy. And once someone becomes a customer, the job isn't over, because keeping them and getting repeat orders is usually easier than finding new ones.”
Using the three words as if they mean the same thing, or having no idea why the difference matters.
Business buyers: several people decide, longer cycle, logic and return matter, repeat orders.
Consumers: one person or a family, quicker, more emotion and trust.
Your fit: which suits you and why, linked to this role.
“When you sell to a business, there are usually several people involved, like the user, a manager and someone who approves the budget. It takes longer, they compare options carefully, and they care about whether it saves money or time. But once you win, they often reorder for years. Selling to consumers is usually faster. One person or a family decides, often in one or two conversations, and trust and feelings play a bigger part. I think business selling suits me better, and that's partly why I applied here. I like preparing, understanding how a customer's work runs and building a relationship over several visits. I'd still expect to learn a lot from the quick back-and-forth of consumer selling if I got the chance.”
Saying there's no real difference, or picking the type of selling this role doesn't involve without any reason.
Upsell: a better or bigger version of what they're buying.
Cross-sell: something related that goes with it.
When not to: it doesn't fit their need, their budget is stretched, or it would feel pushy.
“Upselling is offering a better or bigger version of what the customer is already buying. If someone buys a basic phone plan, suggesting the one with more data because they told me they stream a lot is an upsell. Cross-selling is offering something that goes with it, like a screen protector or a case with the phone. Both are fine when they genuinely solve something the customer mentioned. I wouldn't do it when it doesn't match what they told me, when they've already said the budget is tight, or when they're clearly in a hurry and it would feel like a trick. A customer who feels pushed into extras might buy once and never come back, which is worse than a smaller sale that brings repeat orders.”
Mixing up the two terms, or saying you'd always offer the most expensive option.
Who it's for: name the type of customer and their problem.
What it does for them: one or two outcomes, not a feature list.
Why us and a next step: one reason to trust you, then a small ask.
“Say the company sells cloud accounting software for small businesses. I'd go, 'You know how a lot of small business owners spend their Sunday evenings sorting bills and chasing payments? Our software lets you send invoices from your phone, reminds customers when they're late, and shows you in one screen who owes you what. Owners who use it tell us they get paid sooner and stop dreading month end. It takes about an hour to set up, and we help you do it. Could I show you how it would look with your own invoices? It takes fifteen minutes.' In the real interview I'd use what I actually learned from your site, and I'd be ready for you to tell me what I got wrong.”
Reading out a list of features, or admitting you didn't look at the company before the interview.
Honest feeling: a bit nervous, mostly motivated.
Why it suits you: effort shows up in results you can see.
Realism: you expect a learning curve and plan for it.
“Honestly, it makes me a little nervous, because I know my first few months won't be my best while I'm still learning the product. But mostly I like it. In college I always did better when I could see a direct link between effort and result, and commission is exactly that. It also means nobody has to push me, because I'll want to push myself. I'd rather be in a role where working smarter shows up in what I earn than one where it makes no difference. I'm planning my own spending around the fixed part of the pay for the first few months, so I can focus on learning properly instead of chasing quick sales that aren't right for the customer.”
Saying you'd prefer a fixed salary only, or that you'll do whatever it takes to earn commission.
Clear yes, with reasons: why the field suits you.
Proof: something you've done that needed stamina or travel.
Practical plan: how you'll manage energy, travel and any limits you have.
“I'm fine with it, and I'd rather know now than be surprised later. I don't want a desk job where I sit in one place all day. In college I volunteered for a survey project where we went door to door across several neighbourhoods for two weeks in summer, and I actually enjoyed meeting people even when it was tiring. I have my own scooter and a licence, and I know the city fairly well. For long days, I'd plan my route so I'm not criss-crossing, carry water, and keep my evenings light so I'm fresh the next morning. Saturdays are fine too. If there's ever a family commitment, I'd tell my manager well in advance rather than cancel on the day.”
Saying yes without any thought, then revealing you don't want to travel or work any weekends.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your live interview audio and screen are never stored. Your resume and notes are saved to your account so the app fills them in on any computer. It stays out of screen share on every plan, including Free; only you can see it.