What is the Awaited utility type? | Interview Question

Q: What is the Awaited utility type?

**Target Audience:** Developers comfortable with `async`/`await` who want to describe "the value inside the promise" as a type. **Difficulty:** Medium **TypeScript version:** Every type claim below was checked by TypeScript 5.4.5 with `--strict`; that `Awaited` arrived in TypeScript 4.5 is cited, not run. > **How to read this doc:** Every idea is explained in plain language first, then tagged with `📌 Interview term:` so you also learn the exact words an interviewer expects. Type claims are checked by `tsc` (an `Equal ` line or a `// @ts-expect-error` line), and the **Verified** section quotes the real output in full. ## 1. Why This Even Matters — A Story First You order a gift online. It arrives in a shipping box. Inside the shipping box is a gift box. Inside the gift box is the watch. When you "open the present", you do not stop at the first box — you keep opening until you reach the watch. And if someone hands you the watch directly, there is nothing to open: you just have th

The problem

Question presented to candidate: "What is the Awaited utility type? Why did TypeScript add it when T extends Promise<infer U> ? U : T already existed, and where do you use it?"

What a strong answer should cover:

Awaited<T> is the type you get from await on a T: it unwraps promises recursively, unwraps any thenable (an object with a callable then), and leaves non-promise types unchanged
It distributes over unions: Awaited<boolean | Promise<number>> is boolean | number
Common use: Awaited<ReturnType<typeof fn>> for the resolved value of an async function; library typings such as Promise.all use it so tuples keep each slot type
It was added in TypeScript 4.5; a one-level infer version leaves Promise<string> behind for nested promises
Generic code: await on a T gives Awaited<T>, and an inferred generic async return type can be wrong, so annotate Promise<Awaited<T>>

Code / implementation expected: Optional — Awaited<ReturnType<...>>, or a hand-written recursive version.

awaited

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Developers comfortable with async/await who want to describe "the value inside the promise" as a type. Difficulty: Medium TypeScript version: Every type claim below was checked by TypeScript 5.4.5 with --strict; that Awaited arrived in TypeScript 4.5 is cited, not run.

How to read this doc: Every idea is explained in plain language first, then tagged with 📌 Interview term: so you also learn the exact words an interviewer expects. Type claims are checked by tsc (an Equal line or a // @ts-expect-error line), and the Verified section quotes the real output in full.

1. Why This Even Matters — A Story First

You order a gift online. It arrives in a shipping box. Inside the shipping box is a gift box. Inside the gift box is the watch. When you "open the present", you do not stop at the first box — you keep opening until you reach the

The solution is hidden so you can try first

8 min read · 11 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

TypeScriptWhat Awaited unwraps, at compile time and at run time

Practice

TypeScriptA hand-written Awaited, edge cases and Awaited in generic code

Practice

Discussion

Other approaches, follow-ups and how it went in real interviews.

Sign in to join the discussion.

No comments yet. Share how you would answer it.

The solution is hidden so you can try first

Keep your momentum going.