Practise the standard verbs for negotiating an API contract across teams.
0 / 5 completed
1 / 5
Fill in: 'We ___ the interface shape with the consuming team before writing a single line of implementation, so nobody builds against a contract that's still actually up for debate.'
We 'negotiate an interface' — the standard, simple collocation for agreeing an API's shape between two teams before building it. The other options are less idiomatic here.
2 / 5
Fill in: 'Designing an interface in isolation and only sharing it once it's finished can ___ the consuming team requesting changes that force a costly rework on both sides.'
We say a one-sided design will 'leave' both teams facing rework later — the standard, natural collocation for the resulting cost. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a draft schema early and share it for comment, rather than presenting a fully finished contract as if it were already beyond discussion.'
We 'propose a schema' — the standard, simple collocation for suggesting a draft interface for feedback. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ on field names and types explicitly in writing, since an assumption one team makes silently is rarely the same assumption the other team happens to make.'
We 'align on a detail' — the standard, simple collocation for reaching explicit shared agreement between teams. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the final contract with both teams before either side starts building against it, so a later disagreement is a documented change, not a surprise.'
We 'sign off on a contract' — the standard, simple collocation for formally confirming agreement on shared terms. The other options aren't idiomatic here.