Why do you want to work here?

Answer

Use a concise present-past-future structure: state what you do now, select only relevant experience, and connect it to the role. Be specific without reciting the entire resume.

For Why do you want to work here?, start with the rule or behaviour, then anchor it in a small realistic example. Distinguish the default approach from the exceptions and name the observable outcome: correctness, maintainability, accessibility, performance, or security.

Example

Present: I lead frontend delivery for checkout.
Past: I improved conversion by simplifying a slow payment flow.
Future: This role lets me apply that product and performance experience at larger scale.

Keep the answer to roughly one or two minutes and adapt the final sentence to the role.

How to structure your answer

1. Define the concept in one or two sentences.
2. Explain when you would use it and when you would choose an alternative.
3. Walk through a small example, including an edge case.
4. Close with how you would test or measure the result.

Common mistakes

• Repeating a definition without connecting it to real code.
• Treating an optimization or abstraction as a default rather than a trade-off.
• Omitting lifecycle, error, cleanup, accessibility, or testing considerations when they apply.

Follow-up prompts

• What failure mode would you expect if this were implemented incorrectly?
• How would you test this behaviour?
• What changes when the feature must scale to a larger application or team?

Interview tip

For this easy-level question, narrate your assumptions before coding. Interviewers can assess reasoning from a clear, bounded example much better than from a list of APIs.