1 min lesson
Resilient SCM integrations
Talk through the example in "Resilient SCM integrations", then name the result it is meant to produce.
Step 1 of 3
The job description names it directly: build resilient abstractions over source-control providers. The skill being tested is whether you can hide GitHub's, GitLab's and Bitbucket's quirks behind one interface the rest of Cursor can trust.
Product surfaces should ask for "the diff for this PR" or "open a pull request," not learn that GitHub paginates with a Link header while GitLab uses X-Next-Page or that one returns 403 for rate limits and the other 429. The abstraction is where that knowledge lives and dies.