The 6 Golden Rules for Every Interview Answer
Before you prepare answers to specific questions, internalise these six golden rules — they apply to every answer you give in an HR or managerial round. Get these right and even an unrehearsed question lands well; ignore them and even a polished story falls flat. Think of them as the operating principles behind every good interview answer.
1. Use the STAR method
For any “tell me about a time…” question, structure your story as Situation → Task → Action → Result. It keeps you from rambling and guarantees you cover the part the interviewer actually cares about — your actions and the outcome. This rule has its own page: The STAR Method.
2. Be honest, but frame it positively
Lies get caught — usually by the second or third follow-up, when the details stop adding up. So tell the truth, but choose the positive frame of that truth. If you’re asked about a weakness or a failure, admit it plainly, then pivot to what you learned and what you changed.
Interviewer: “Tell me about a project that failed.”
You: “Early in my career I led a rewrite that we shipped three weeks late because I under-scoped the migration. It was a real miss. What I took from it: I now break large work into a thin vertical slice first and ship that, so estimates are grounded in reality instead of optimism. I haven’t blown a timeline like that since.”
3. Don’t blame
Never speak badly of a past manager, team, or company — even when it’s justified. The interviewer’s silent reaction is always the same: “They’ll talk about us the same way one day.” Describe the situation neutrally and focus on your response to it, not on who was at fault.
❌ “My manager was disorganised and never gave clear requirements.” ✅ “Requirements shifted often, so I started writing a short spec and confirming it before each sprint — that cut the back-and-forth a lot.”
4. “It depends” + reasoning
For scenario questions — “What would you do if…” — never fire off a one-line answer. Start with “it depends”, clarify the missing context, lay out the trade-off, then decide. This shows judgment instead of a reflex.
Manager: “Would you ever skip writing tests to hit a deadline?”
You: “It depends on the risk. For a throwaway internal script, maybe. For payment code, never — the cost of a bug there dwarfs the time saved. If a deadline is genuinely immovable, I’d cut scope rather than cut tests on critical paths, and I’d flag that trade-off explicitly to you.”
5. Be concrete
“I’m hardworking” is a claim anyone can make, so it’s worth nothing. Replace adjectives with evidence: a specific situation, what you did, and the measurable result. “Last sprint we had deadline X; I did Y; Z was the outcome” is far stronger than any list of traits. Concreteness is what makes the STAR method so effective.
6. Disagreement ≠ disrespect
You’re allowed to disagree with a manager — good engineers should. But do it respectfully and with data, and once the decision is final, commit to it fully. This is the “disagree and commit” principle: argue your case hard before the call, then back the decision wholeheartedly after it. Sulking or sabotaging after a decision is what loses trust, not the disagreement itself.
Tips & mistakes to avoid
- ✅ Run every answer through these six rules as a mental checklist.
- ✅ Pair honesty with a lesson learned — it turns a weakness into a strength.
- ✅ Show “disagree and commit” explicitly in conflict answers.
- ❌ Don’t blame previous employers, ever, even subtly.
- ❌ Don’t give one-line answers to “what would you do” questions.
- ❌ Don’t list abstract traits without a concrete example behind them.