How would you explain what an API is to a business stakeholder with no technical background?

What the interviewer is looking for

• This question tests technical presentation. Explains complex ideas simply to mixed audiences, uses clear visuals and demos, and adapts to the room.
• Strong answers: A simple analogy, why it matters to the business such as partners or automation, and checking the listener understood.
• Likely follow-up: How would you change that explanation for their head of engineering?

Another way it may be asked: Your client's finance director asks what an API is and why they should pay for one. What do you say?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• Tell me about a technical demo or proposal that did not go well. What happened, and what did you change?
• A customer says they want to modernise their system. What questions would you ask before suggesting anything?
• What is the difference between a monolith and microservices, and when would you advise a client to stay with a monolith?
• A client needs their new online store to sync orders with an old inventory system that only exports nightly files. How would you design that?
• How do you bring security and compliance requirements, like data privacy rules, into a design from the start rather than at the end?

Browse all questions