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 makes a support reply useful?
A useful reply acknowledges the problem, says what you already checked, gives the next step or the answer, and states what happens next. Short sentences beat a long apology. Do not add a promise, such as a refund or a fix date, that you are not allowed to make.
I would say I am sorry the sign-in failed, that I checked the reset steps, and that the next step is a link that expires today. I would tell them I will confirm once they reply that it worked.
2. What is the difference between an issue, a cause and a workaround?
The issue is what the person sees. The cause is why it happens. A workaround gets them moving while the cause is fixed, and it should be labelled as temporary. Do not present a workaround as if the problem were solved.
The issue is that the upload fails. The cause might be a file type we do not accept. A workaround is to send a PDF for now, and I would say the failure itself is still open.
3. What do you confirm before you escalate?
Write what the person wanted, what you already tried, the exact message on the screen, and how urgent it is. Include only identifiers you are allowed to share. Tell the next person what decision you need from them, so the ticket does not start again from zero.
I would pass on the error text, the browser they used, the two steps I already tried, and that their exam is today. I would not include their password. I would ask the specialist whether to reset the attempt or wait.
4. How do you respond to someone who is angry and still needs an answer?
Acknowledge the impact, do not debate their tone, and do not answer with false cheer. Give the next step you can actually take, including a time. If they want compensation, say you will check with the person who can approve it rather than promising it yourself.
I would say the missed deadline is a real problem and that I am looking at the submission now. I would give them a time for the next update. I would not promise a waiver I cannot approve.
5. When should you refuse to invent a missing help-article step?
If the approved article does not contain the click, you do not guess one. Tell the person you need to confirm, check with a senior or the owner of the article, and only then send the step. Invented steps are how a small problem becomes a larger one.
If the article stops before the last screen, I would say I want to confirm that click rather than guess it. I would ask a senior and then write the step in the reply and, if I am allowed, in the article.
Problem solving and scenario
6. A student cannot sign in. How do you troubleshoot without blaming them?
Ask which address they opened and the exact message, and check for a simple mismatch such as the wrong portal. Offer a reset without ever asking them to read a password aloud. Ask whether other people see the same failure, so you know if this is one account or a wider break.
I would ask for the message and the page, not for the password. I would send a reset and ask them to try the link once. If several students report the same message, I would treat it as an outage and say so.
7. Two people write at once, and one has a deadline today. How do you choose?
Take a complete outage, or anyone blocked from something they must finish today, before a general question. Tell the person who is waiting that you have seen them and when you will return. Do not pretend you can finish both at the same moment.
I would help the student whose test closes today before the person asking for a brochure. I would reply to the second person that I have their note and will answer after the deadline case. I would not leave either in silence.
8. You do not know the answer. What do you say?
Say that you do not know, name what you will check, and give a time you will come back. Do not fill the gap with a guessed click-path or a policy you have not read. Write the answer down once you have it so the next person does not guess either.
I would say I do not know whether that batch can retake the test, and that I will ask the coordinator and reply by 4 pm. I would not invent a yes to be kind.
9. Someone asks you to bend a rule. What do you do?
Repeat the request so they feel heard, explain the limit, and offer the closest step the rule allows. Escalate only if an exception path exists, and do not create one yourself. Be specific about what you cannot do.
If they want a late file accepted after the portal closed, I would say I cannot reopen it. I would offer to pass their note to the person who owns exceptions, if that path exists. I would not mark the file as on time.
10. You gave the wrong step and the person is now more stuck. What do you do?
Correct it quickly, apologise in one sentence, and stay until the new step is clear. Tell the next teammate what you sent so they do not repeat it. Update the note or the article if you are allowed to, so the wrong step does not travel.
I would say the earlier click was wrong, send the correct one, and wait for them to confirm. I would mark the ticket so the next person sees the mistake. I would not hope they did not notice.
HR and behavioural
11. Tell me about a time you helped someone who was frustrated.
Set the scene in a line, then the words you used and the next step you took. A lab, a fest desk, a hostel complaint or a family shop is valid. Show that you did not match their volume and that you did something concrete.
At a fest desk a visitor had paid and still had no pass. I said I could see why they were upset, checked the payment list, and issued the pass while they waited. I did not argue about whose fault the list was.
12. Describe repetitive work and how you stayed accurate.
Explain the unit you checked, such as a page or a batch, and the total that had to agree. Say what you did when you were interrupted. Accuracy is a system here, not a personality claim.
I registered fest participants in batches of twenty and matched the count to the forms before the next batch. When a queue interrupted me, I finished the open batch first. That stopped a double entry I had made on day one.
13. How do you take feedback on your tone?
Ask for the sentence that landed badly, and try a shorter version rather than defending your intent. Intent is invisible to the reader. Show one rewrite you would actually send.
If a senior said my reply sounded abrupt, I would ask which line. I would add what I had checked and the next step, and I would read it aloud before sending. I would not answer that I had meant to be efficient.
14. Why customer support?
Talk about staying clear when someone is stuck, and use one example. Say you know the work includes repetition and unhappy people, so it does not sound like you have missed the job. Add what you want to learn, such as how a team writes its help articles.
I like the moment a stuck person knows the next step. The fest desk taught me that a calm sentence matters more than a speech. I want a role where that is daily work, including the repetitive tickets.
15. Tell me about a time you said no clearly and kindly.
State the request, the reason you could not meet it, and the alternative you offered. Kindness is the alternative and the tone, not a hidden yes. Keep the story small enough to be specific.
A classmate wanted me to add their name to a fest list after it had closed. I said I could not change the closed list. I offered to put them first on the waitlist and told them who would decide if a place opened.