How to answer job application questions well

Application forms are full of open questions that are easy to answer badly: “Why do you want to work here?”, “Tell us about yourself”, “What is your greatest strength?”. The generic version of each answer is instantly forgettable. The fix is the same every time: work out what the question is really asking, then prove it with one real example.

Work out what kind of question it actually is

Most application questions fall into three types, and each wants a different shape. A “describe a time” question wants one specific story. A “why this company” question wants a real connection between what you have done and what the role needs. A “strengths” or “tell us about yourself” question wants a trait, proved.

“Describe a time…”: use a light Situation, Task, Action, Result shape, told as a flowing story rather than four labelled headings.
“Why this company” or “why this role”: name something real about the employer and tie it to your own experience, not general enthusiasm.
Strengths, weaknesses, or “tell us about yourself”: state the trait plainly, then prove it with one example.

Prove it with one example, not three adjectives

“I am a hardworking, dedicated team player” tells the reader nothing; anyone could write it, and most people do. One specific example, with a real detail or outcome, does the proving for you. Pick your strongest example and give it the space, rather than spreading three thin ones across the same answer.

Make it about this employer, and this length

A generic answer that could go to any company reads as one in thirty, because it is one of thirty. Pull one real detail from the job ad or the company itself and connect it to your own experience. If the form gives a word or character limit, treat it as a real constraint: write to fit it rather than writing long and hoping it gets read anyway.

Example

Question: "Why do you want to work here?" Answer: "I have used [Company]'s app for two years as a freelancer, and what stood out was how fast a support ticket got answered, usually inside an hour, by someone who clearly used the product themselves. I want to work somewhere that treats support as a product problem, not a cost centre, and bring my three years running a two-person support inbox down to a four-hour average reply time. I read the engineering blog post on your new ticket routing system, and would like to help build the next version of it."

Common mistakes

Answering the question you wish they had asked, not the one they actually asked.
Piling up adjectives instead of one proven example: “hardworking, dedicated, team player” tells them nothing.
Writing an answer generic enough to send to any employer. A recruiter can tell within a sentence.
Ignoring the word or character limit, then getting cut off or overflowing the form field.

For the “tell me about a time…” questions specifically, whether written or spoken, use the STAR method to keep the answer concrete and land an actual result.