The part that trips people up is they want something real, not the 'I care too much' non-answer.
Choose a genuine, non-fatal weakness that is relevant to the role but not a core requirement, such as over-engineering or difficulty asking for help. Then, describe specific actions you've taken to mitigate it and quantify the progress you've made. This shows self-awareness, honesty, and a growth mindset.
Pro tip: Avoid clichés like 'I work too hard' or 'I'm a perfectionist'—interviewers see through them. Instead, pick a real weakness that you've actively worked on, and frame it as a learning opportunity that has made you a better engineer.
Choose a weakness that is real but not a core requirement for the role, such as a soft skill or a technical area you've improved. Avoid weaknesses that are essential to the job (e.g., coding ability for a software engineer).
Illustrate the weakness with a concrete situation where it had a negative impact, showing you understand its consequences. Be concise and focus on the impact, not the story.
Explain the steps you've taken to address the weakness, such as training, feedback, or process changes. Emphasize proactive and sustained effort.
Share measurable outcomes or positive feedback that demonstrate improvement. This shows you've made tangible progress and are committed to growth.
Relate your growth to the demands of the role and Optiver's culture, showing how you've turned the weakness into a strength that benefits the team.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.