A bad interview usually fails before the first question ends because the answers stay vague, the examples are thin, and the room is full of guessing.
The fix is not to memorise polished lines. It is to walk in with proof. If you can show what the role asks for, where you have done the work before, and what changed because of your decisions, you stop sounding rehearsed and start sounding useful.
1. Read the job ad like a checklist
Start with the job description and strip it down to priorities. Look for repeated words, required skills, and anything marked as essential. If an operations role keeps mentioning process control, cost reduction, stock accuracy, or team coordination, those are the areas the interviewer is most likely to test.
Write the top five requirements on one page. Next to each one, add one example from your own history. If the ad says the job needs someone who can improve workflows, do not arrive with a vague story about being “hardworking”. Bring a case where you changed a process, fixed a bottleneck, or reduced errors.
2. Research the employer properly
The company website is the starting point, not the finish line. Read the news section, scan recent LinkedIn posts, and look for JSE announcements or integrated reports if the employer is listed. If you can find interviews, product launches, restructuring news, or expansion plans, use that to shape your answers.
A candidate who knows the business sounds less like a stranger and more like someone already thinking about the job. If the firm is under pressure on logistics, costs, or customer turnaround times, your examples should speak directly to those problems.
3. Prepare three work examples
Do not try to cover your whole career. Prepare three strong examples that each prove a different strength. One can show problem-solving, one can show leadership, and one can show technical or process skill.
Use a simple structure: situation, task, action, result. Keep the story tight enough to say in about two minutes. For an operations role, a weak line like “I improved efficiency” needs more meat. Try this instead: “Our dispatch process was causing late deliveries because orders were being checked manually twice. I mapped the handoff points, removed one duplicate approval step, and introduced a daily tracking sheet. Within six weeks, dispatch times fell from 48 hours to 24 hours, and the team handled 50% more orders without adding staff.”
That is the kind of answer an interviewer can work with.
4. Put numbers on your results
Numbers cut through vague claims. Use percentages, rand values, headcounts, time saved, or before-and-after comparisons. If you saved stock losses, say how much. If you shortened a process, state the old and new time. If you led a team, say how many people were involved.
For example, “reduced supplier delays” is soft. “Raised on-time supplier delivery to 95% and cut production downtime by 12% in one quarter” tells the story clearly. If you do not know the exact figure, use a careful estimate and be ready to explain how you arrived at it.
5. Practise the short version
Good answers are not long answers. Prepare bullet points for common questions like “Tell me about yourself”, “Why this role?”, and “Why should we hire you?” Aim for three to five points, not a script.
The point is to sound natural under pressure. If you know your main message, you can answer without rambling. Leave room for the interviewer to pull on a thread. That sounds more real than reciting a polished monologue.
6. Plan the salary discussion
Salary questions make people tighten up, then they either undersell themselves or talk themselves out of the job. Prepare for the conversation before it starts. Decide what range makes sense based on the role, your experience, and the market.
Do not force yourself into one fixed answer. You can say you are open to discussing a package that reflects the responsibilities, the total benefits, and the growth path. If they ask for a figure early, answer with a range and a reason. Keep it calm, direct, and tied to the work.
7. Ask questions that show you have read the room
Do not waste your turn asking what the company does. Ask about the first 90 days, the biggest challenge in the team, or how success is measured in the role. If the interview is for an operations post, ask what would most improve the current process flow or where delays usually start.
A good question does two things. It shows that you are thinking beyond the vacancy, and it gives you information you can use if the offer arrives.
8. Remove the avoidable stress
The night before, run a 30-minute checklist. Lay out your clothes if the role needs it, print your CV, pack certificates and references, charge your phone, check the route, and confirm parking or transport. For a virtual interview, test the camera, microphone, login details, and internet connection, then clear a quiet space.
Use the last five minutes before the interview for a fast review. Read your three examples, your salary range, your questions, and the job description. Then stop preparing. Walk in with notes, not panic.
A clean interview is usually built the night before. The candidate who arrives with real examples, clear numbers, and a calm plan sounds prepared because they are.
