Strengths & Flaws

Most candidates answer with willingness rather than method, so give the method. Three elements: timing, specificity and volume. Ask soon after a discrete piece of work rather than at a review, ask about one thing rather than in general, and do not ask constantly. A usable script is: is there anything you would want done differently on the next one of these. Say that you write it down and refer back.

A concrete question you actually use, because open requests for feedback usually get nothing back. Mentioning that you ask about the next piece of work rather than about yourself is the move that gets senior people to answer honestly.

• Stating openness to feedback with no method at all
• Only ever asking in formal reviews
• Asking so often it becomes a demand on senior time
• Asking how am I doing, which reliably produces nothing useful
• No mention of doing anything with what you receive

Narrower than the standard strengths question because it forces a comparison, so pick one thing and defend the comparison. Structure: the claim, why the comparison is fair, one piece of evidence, and where it is useful here. Thirty to forty seconds. Choose something a first year analyst is actually measured on, such as producing clean work under time pressure or asking the right question early.

One strength rather than three, with evidence that involves someone else noticing, since self-assessment alone is weak evidence. The most persuasive answers pick a modest, checkable strength over an impressive, unverifiable one.

• Listing three or four strengths so none of them registers
• A strength with no evidence beyond the assertion
• Choosing something irrelevant to analyst work
• Overclaiming, such as being better than anyone you have met
• Hedging so heavily that no comparison is actually made

The failure mode here is guessing, and the answer must rule it out. Give a sequence: try to resolve it yourself briefly by looking at a prior version of the same deliverable, then ask one specific question rather than saying you are lost, and where possible ask it as a confirmation of your best interpretation. Say you would ask before starting rather than after two hours of work.

Asking a closed question that contains your proposed answer, such as confirming which comparison set to use, because that costs the senior person seconds rather than minutes. Naming a time limit on trying to work it out alone is the detail that shows judgment rather than either helplessness or stubbornness.

• Guessing and hoping to correct it later
• Asking immediately without attempting to work it out
• Spending hours stuck rather than asking
• Asking an open question that offloads the thinking upwards
• Asking a peer who is equally unsure instead of the requester

Do not claim to enjoy it. Give two things instead: a standard you hold regardless of whether the task is interesting, and a method for keeping accuracy up when attention drops, such as batching similar work, checking in passes rather than continuously, or building the repetitive thing once properly. Then one example of tedious work you did well. Thirty to forty seconds.

Recognizing that boredom is an accuracy risk rather than a morale problem, which is the professional framing. A concrete technique for the moment your attention slips is worth more than any statement of attitude.

• Claiming you find everything interesting
• Treating it purely as an attitude question with no technique
• Implying you would look for ways to avoid or delegate such work
• No acknowledgment that accuracy falls when attention does
• An example where the tedious work was brief or low stakes

Give a rule, not a temperament. The usable one has three tests applied in order: what is externally committed, meaning a client or a market deadline, beats what is internal; what unblocks someone else beats what only you are waiting on; and what is irreversible beats what can be redone. Then say the second half out loud: you tell the people whose work you are deprioritizing, because a silent decision is not prioritization.

A stated ordering rule plus the communication step. Most candidates give the rule and stop, but the reason prioritization goes wrong in practice is that nobody is told, and saying so shows you have thought about it beyond the abstraction.

• Answering with effort, such as staying late to do it all
• Ordering purely by whoever asked most recently or most loudly
• A rule with no communication back to the people affected
• Ranking only by seniority of the requester
• No distinction between a real deadline and a soft one

Do not claim you love them. Give evidence you have sustained demanding periods before, describe the specific mechanisms you use to stay effective, and be realistic that it is hard. The interviewer is checking whether you know what you are signing up for, and an answer that sounds naive about the job is worse than one that admits the difficulty.

A real prior period of sustained intensity, with concrete coping mechanisms rather than adjectives. Acknowledging the cost while still committing reads as informed rather than deterred.

• Claiming to thrive on no sleep
• No evidence of ever having sustained real pressure
• Sounding naive about what the hours actually are
• Complaining, or signaling reluctance
• Generic claims about being resilient

Pick a real failure with a real consequence, ideally one where you were responsible. Set the situation up in two sentences. Say what you did and why it did not work. State plainly what went wrong and own your part without deflecting. Then spend most of the answer on what you changed afterward and evidence that the change held.

The story should cost you something to tell. A genuine failure with a concrete lesson and evidence you applied it. The recovery is where most of your time should go, not the setup.

• A disguised humblebrag, like working too hard
• Blaming teammates or circumstances
• A failure with no real consequence
• No evidence the lesson actually changed later behavior
• Choosing something so severe it raises new doubts