1 min lesson
The six things you'll own
Connect "The job description lists six responsibilities" to the decision you would make.
Step 1 of 3
The job description lists six responsibilities. In the loop you'll be far more convincing if you can translate each one into something a Tuesday actually looks like, with the tools and the artifact named.
Read this section as the role contract. The diagram or table names the surface area, but the interview signal is whether you can turn it into a clear operating claim: what you own, what you do not own, what evidence proves the work is working and where judgment matters.
Learn more
Full explanation
The Six Duties, by How Hard the Loop Tests Them
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
The two engineering-flavored duties carry the highest bar - and are where most candidates are thin.
Learn more
Advanced table
Every JD bullet maps to a concrete activity and a tangible artifact
- Responsibility (JD)
- In-depth technical support over tickets and Slack
- What a real day looks like
- Pick up a ticket where Tab autocomplete stopped firing; ask for the exact OS, version and a screen recording; walk the user through it without condescension
- The artifact you leave behind
- A resolved ticket with a clear explanation the user can re-use next time
- Responsibility (JD)
- Debug, reproduce, troubleshoot bugs and usability problems
- What a real day looks like
- Reproduce an agent run that dropped context on a large repo, isolate it to one extension conflict, confirm root cause vs. symptom
- The artifact you leave behind
- A minimal reproduction across the relevant OS
- Responsibility (JD)
- Design and build internal tools and automations
- What a real day looks like
- Write a Python script that scrapes the Cursor diagnostics log and flags the three most common indexing errors automatically
- The artifact you leave behind
- A log parser or triage bot the whole team uses
- Responsibility (JD)
- Represent Anysphere in technical conversations with enterprise devs
- What a real day looks like
- Hop on a call with a customer's staff engineer about SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. behavior and hold the conversation as a peer
- The artifact you leave behind
- A trusted relationship and a precise answer, not hand-waving
- Responsibility (JD)
- Partner with Product and Engineering, feed the roadmap
- What a real day looks like
- Escalate a sev-1 with a clean repro; aggregate forty tickets into a single “privacy mode breaks X” signal for product
- The artifact you leave behind
- A crisp escalation and a roadmap input
- Responsibility (JD)
- Maintain customer-facing docs and internal KBs
- What a real day looks like
- Turn the fix you just shipped into a KB article so the next user self-serves
- The artifact you leave behind
- A doc that deflects the next twenty tickets honestly
| Responsibility (JD) | What a real day looks like | The artifact you leave behind |
|---|---|---|
| In-depth technical support over tickets and Slack | Pick up a ticket where Tab autocomplete stopped firing; ask for the exact OS, version and a screen recording; walk the user through it without condescension | A resolved ticket with a clear explanation the user can re-use next time |
| Debug, reproduce, troubleshoot bugs and usability problems | Reproduce an agent run that dropped context on a large repo, isolate it to one extension conflict, confirm root cause vs. symptom | A minimal reproduction across the relevant OS |
| Design and build internal tools and automations | Write a Python script that scrapes the Cursor diagnostics log and flags the three most common indexing errors automatically | A log parser or triage bot the whole team uses |
| Represent Anysphere in technical conversations with enterprise devs | Hop on a call with a customer's staff engineer about SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. behavior and hold the conversation as a peer | A trusted relationship and a precise answer, not hand-waving |
| Partner with Product and Engineering, feed the roadmap | Escalate a sev-1 with a clean repro; aggregate forty tickets into a single “privacy mode breaks X” signal for product | A crisp escalation and a roadmap input |
| Maintain customer-facing docs and internal KBs | Turn the fix you just shipped into a KB article so the next user self-serves | A doc that deflects the next twenty tickets honestly |
Every JD bullet maps to a concrete activity and a tangible artifact.
Two of these six are pure engineering work: building automations and writing reproductions. That weighting is deliberate. Interviewers want to know you'll reach for a script when you notice yourself doing the same triage by hand for the fifth time.
Tickets, Slack threads, live calls, reproductions, escalations.
This is where empathy and debugging speed show up.
Automations, parsers, macros, KB articles, roadmap signal.
This is where building and craft show up and where most candidates are thin.
If your stories are all reactive - “I closed a lot of tickets, customers loved me” - you'll read as a strong rep for a different company. Come with at least one proactive artifact you built: a script, a runbook, a macro, a dashboard. The proactive half is what makes this role engineering-flavored and it's where the bar is set.
Learn more
Optional practice