A useful strength answer names a capability relevant to the role, proves it with a short example, and explains how it would create value in the new context. Avoid listing several adjectives. One or two well-supported strengths are more credible than a long catalogue.
A weakness answer should be real but manageable for the role. Describe the specific limitation, its past impact, the actions you have taken, and current evidence of improvement. Motivation answers should connect what the work requires with what you have learned about the team, product, users, or growth opportunity.