What are your strengths and weaknesses?
Reported in CrowdStrike USA engineering loops. Behavioral HR question assessing self-awareness and growth mindset.
Interview scenario
Often asked in CrowdStrike on-site or virtual loops at US offices (Bay Area, Seattle, NYC, Austin, and remote US). Prepare a clear spoken answer plus key trade-offs.
Model answer
Try answering aloud first
Cover trade-offs, structure, and a concrete example before revealing the baseline response.
How to frame this at CrowdStrike: Connect your answer to measurable impact, clarity of thought, and trade-offs the team cares about. Below is a strong baseline response you can adapt with your own project examples.
Pick one or two strengths backed by evidence, not adjectives. Instead of "hard worker," say: "I break ambiguous tickets into measurable milestones—in my last internship I delivered the auth module a week early by writing a design doc first."
For weakness, choose a real area you are actively improving—not a disguised strength ("I work too hard"). Good example: "I used to jump into code before aligning on requirements; now I start with a short RFC and stakeholder sign-off, which reduced rework on my team."
Show the improvement loop: what you noticed, what action you took, and measurable outcome. Avoid weaknesses core to the job (e.g., "I hate debugging" for an SDE role).
Delivery matters: be honest, concise, and forward-looking. Interviewers assess maturity, not perfection.
Discussion
Comments (0)
Share how this question came up in your loop, or add tips for others preparing.
Log in to comment on this question.