10Giving answers that sound good to you (but aren’t)
This chapter outlines the subtle ways interview answers can sound fine to you but miss the mark for employers. It encourages reviewing your responses from an outsider’s perspective and refining for clarity, relevance, and impact. The overarching goal is to prepare and practice answers that are concise yet complete, easy for a broad panel to follow, and directly tied to what the employer needs.
Common pitfalls include answers that are too long (rambling, excess context, filler words) or too short (glossing over complexity and obstacles); overusing acronyms or “tech/industry speak” that some interviewers won’t understand; and focusing on what you did while neglecting how you did it and why it mattered. Candidates often fail to relate stories to the target job, company, or industry; omit results; overuse “we” (or “I”) in ways that obscure their true contribution; and miscalibrate tone—coming off as arrogant or insecure. Additional missteps include volunteering negatives or asking about compensation/benefits too soon, mishandling “Why should we hire you?” by offering vague claims or personal desires, and giving generalities when the question asks for a specific past example.
The remedy is disciplined preparation: tailor stories to the role and industry, keep most answers under two minutes without rushing, explain your methods and collaborators, and always land on results (quantitative or qualitative). When selling fit, speak from the employer’s perspective, cite concrete skills and metrics, and summarize a unique mix of 3–5 strengths that align with their priorities. Avoid jargon unless explained, balance “I” and “we,” project confident humility, and save compensation topics for the appropriate stage. Close the loop by auditing your answers against these traps and adjusting them so they demonstrate relevance, clarity, and measurable impact.
Key takeaways
The key takeaways from this chapter are:
Applicants may think that they have great answers, but that might not be true.
The issue could be a simple thing that gets in the way, such as giving answers that are too short or too long, or it could be something more critical, like not including or clearly describing results.
It’s important to review the list of potential problems, compare your answers, and make adjustments if needed.
FAQ
How long should my interview answers be, and how do I avoid rambling?Aim for 60–120 seconds. Clarify the question before you start, lead with the result, then summarize key actions. Prioritize the essentials, trim background, and skip filler words. Don’t try to “fix” long answers by speaking faster—prepare and practice instead.What if my answers are too short?Short answers can make your work sound simple. Add brief context, the key decisions and obstacles you handled, and the outcome. A simple flow is: situation (1–2 lines), actions (2–3 lines), results (1–2 lines). Practice expanding with specifics without getting lost in details.Is it okay to use acronyms or industry jargon?Assume a mixed audience. Define acronyms on first use, prefer plain language, and translate technical terms into business impact. If you notice confusion, pause and rephrase so everyone can follow.How do I show not just what I did, but how I did it and why it mattered?Describe the “how”: who you collaborated with, tools used, approvals gained, obstacles overcome, and how you earned buy-in. Then explain “why it mattered” by stating the result and who benefited (customer, team, or business).How can I tailor my answers to this job, company, and industry?Map your stories to the job description and the employer’s goals. Choose examples from the same industry when possible; if not, use the closest analog and highlight transferable skills. Avoid “better” but unrelated stories that dilute fit.Do I need to include results even if I don’t have hard numbers?Yes. Share qualitative outcomes (e.g., improved customer satisfaction, faster decisions, fewer defects) when metrics aren’t available. When you do have numbers, include them and, if relevant, note payback or ROI to show impact.Should I use “I” or “we” when describing my work?Use both. Say “I” for your specific contributions and decisions; say “we” for joint work and shared outcomes. Avoid starting sentences with “You should…” which can sound like lecturing.How do I balance confidence with humility?Be evidence-driven and gracious. State achievements and results clearly, give credit where it’s due, and mention what you learned or improved. Avoid exaggeration on one end and self-effacement on the other.What topics should I avoid bringing up unprompted?Don’t volunteer negatives (gaps, limited experience, industry switch) unless asked. Also avoid asking about compensation, time off, or benefits early; focus on role, impact, and fit. Prepare concise, positive responses in case these topics come up.How should I answer “Why should we hire you?” and other behavioral questions?For “Why should we hire you?”, summarize 3–5 strengths mapped to the job, each backed by brief evidence, and conclude with the unique combination you offer. For behavioral questions (“Tell me about a time…”), give a specific past example using a clear structure (situation, actions, results) rather than generalities.
pro $24.99 per month
access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
Interview Speak ebook for free
