Strengths and Weaknesses Interview Guide for Singapore Students

Strengths and Weaknesses Interview Guide for Singapore Students

"What are your greatest strengths?" and "What is your biggest weakness?" are among the most common and most poorly answered questions in Singapore internship interviews. Candidates either give generic strengths with no evidence, or offer fake weaknesses that no interviewer believes. This guide gives you honest, credible answers that work.

The Strengths Question

What interviewers are looking for: Evidence, not adjectives. "I am analytical" tells an interviewer nothing. "I built a financial model from scratch for NUS BIZkids competition and identified a valuation gap that our team's initial estimate missed by 40%" tells them something real.

The formula for a strong strengths answer:

1. Name the strength (one word or short phrase)
2. Give one specific example that demonstrates it
3. Connect it to the role you're applying for

Aim for 45–60 seconds per strength. Interviewers typically ask for two or three.

Top 5 Strengths with Example Frameworks:

1. Analytical thinking / Structured problem-solving Example anchor: A complex data analysis project, a case competition win, a research paper where you identified a non-obvious insight. "My strength is structured analytical thinking. During my NUS Business Analytics course, I worked on a dataset of 50,000 customer transactions for a local retail chain and identified a customer segment that was churning at 3x the average rate but had been missed in previous analyses. The insight led to a targeted retention campaign. I consistently approach problems by breaking them into components before generating solutions."

2. Communication and presentation Example anchor: A presentation that changed someone's mind, a complex idea you explained simply, a stakeholder update you managed under pressure. Particularly valued in consulting and client-facing banking roles.

3. Attention to detail / Rigour Example anchor: A modelling or research project where you caught an error that would have been costly. "In my internship at [company], I reviewed a competitor analysis deck and found an inconsistency in the revenue figures — the presenter had used two different fiscal year conventions without adjusting. That catch saved the team from presenting inaccurate data to the client."

4. Learning agility / Fast learner Example anchor: A skill you picked up quickly in a high-pressure context. Particularly valued at tech companies and startups where the learning curve is steep. "I started my previous internship knowing virtually nothing about cloud architecture. Within three weeks, I had deployed my first AWS Lambda function in production. I'm comfortable being the least knowledgeable person in the room at the start of a project — that's when I learn fastest."

5. Initiative and ownership Example anchor: A problem you identified and fixed without being asked. "During my polytechnic industrial attachment, I noticed the team was manually copying data between two systems every Friday — a two-hour process. I wrote a Python script in my own time that automated it. After testing it for three weeks, I suggested it to my supervisor and it's now used by the whole team."

The Weakness Question

The cardinal rule: Your weakness must be real. Interviewers have heard "I'm a perfectionist" ten thousand times and have stopped believing it. A credible weakness, framed with self-awareness and a genuine improvement, scores far higher than a manufactured one.

The formula for a strong weakness answer:

1. Name the weakness honestly
2. Give a brief, specific example (not catastrophic, but real)
3. Explain what you are doing to improve
4. Note any progress made

Aim for 60–75 seconds. Do not dwell.

Top 5 Weaknesses with Example Frameworks:

1. Public speaking / Presenting under pressure "Presenting to large groups — particularly when the audience includes people significantly senior to me — makes me visibly nervous. In my second year at NUS, I lost composure during a class presentation when a professor challenged my assumption mid-slide. Since then, I've deliberately put myself in discomfort: I joined Toastmasters at NUS for one semester, and I've volunteered to present first at every group project. I'm not fully comfortable yet, but I'm materially better than I was a year ago."

2. Over-preparation / Difficulty acting on incomplete information "I tend to want to analyse a problem thoroughly before I act, which can slow me down when speed is more important than completeness. I've become more aware of this and now explicitly set a 'decision point' for myself — a time at which I'll commit to an approach even without perfect information. This is an area I continue to work on."

3. Difficulty delegating "I struggle to let go of tasks I care about. I tend to take on more than my share in team projects because I worry that the output won't meet my standards if I hand it off. I'm improving this — in my last group project, I deliberately assigned a critical section to a teammate and resisted the urge to redo it. The quality was excellent and I learned I'd been underestimating my teammates' capability."

4. Speaking up in meetings with senior people "I hold back in meetings when I'm the most junior person in the room, even when I have a view worth sharing. This is something I'm actively working on — I've set a personal rule that I will contribute at least one substantive comment per meeting. It's uncomfortable but I'm getting better at it."

5. Written communication "I sometimes over-explain in writing — adding more context and caveats than the reader needs. I've started asking a peer to review any document longer than one page before I send it, with a specific brief to flag anything that could be shorter. The feedback has been useful."

What NOT to Say

• "I'm a perfectionist" (fake and overused)
• "I work too hard" (not a weakness)
• "I care too much about the people around me" (patronising)
• "I don't have any major weaknesses" (the worst possible answer)
• Any weakness that directly disqualifies you for the role: "I find financial modelling very challenging" in an IBD interview is not a good answer