Tell me about a time you unblocked yourself by writing code in a repo your team didn't own.

We were trying to work out why people were dropping out of a multi-step onboarding form, and we couldn't see it. The shared form package that renders our fields emitted nothing when a field failed validation, so our instrumentation only ever knew about successful submits. There was an open issue about it in the public repo with a couple of upvotes and nobody assigned. I didn't want to monkey-patch it locally where it would quietly rot, so I commented on the issue with the exact event shape I wanted and asked whether they would take a pull request. A maintainer said yes, with one constraint: no new dependency, and the event had to be opt-in so nobody else's behaviour changed. That constraint made the change small — a shade under eighty lines, plus tests written in the style they already used and a changelog entry. It sat for nine days. I nudged once in their weekly triage thread rather than pinging anyone directly, and it merged. Once we picked up that release, we could finally see that a single postal-code field was throwing roughly two-thirds of our validation errors, and fixing that field is what moved our numbers. What I took from it: asking for the shape of the patch before writing it turned a maybe into a merge, and the whole cost of asking was one comment.

My team's checkout surface was blocked on server-side rendering support in the shared component package. Without it, first paint carried a visible layout shift on the highest-traffic route we owned, and the team maintaining that package had it slotted for the following half. Their maintainer was plainly underwater, so I offered labour rather than pressure. I asked their lead for a scoped agreement rather than a favour. We would implement the render path behind a flag inside their repo; we would take the pager for anything that broke in it for one release cycle; in exchange we wanted review turnaround inside three days and one of my engineers added as a reviewer on that directory. She agreed and wrote it into the repo's ownership file, which mattered more than the handshake did. It took two of my engineers about five weeks. The thing I insisted on internally was that we build it their way — we threw out a cleaner abstraction because it didn't match the pattern the rest of the package used, and that is why it was still theirs and still maintained long after we moved on. Layout shift on that route went from a quarter of a second of movement to effectively none. My engineer stayed on as a reviewer there, which turned out to be worth more than the patch.