Capstone: Mock Loop

You don't find out whether your scheduling holds up by reading about buffers and time zones. You find out by starting a 10-minute timer, opening a blank calendar and building a clean loop while narrating every choice. This section is that drill, built on the exact shape Cursor's practical round would hand you: a panel, a candidate flying in and constraints that don't quite fit.

Set the timer before you read the constraints. The clock is part of the test. The practical exercise is checking whether you can hold five moving pieces in your head and still produce something a candidate could follow without a single follow-up question.

Build the loop - 10-minute clocknarrate as you place each block

1. 1Convert to one zone first. Pin everything to ET, the office zone and translate the PT interviewer's 12:30 ET floor (9:30 their time) so you never quote a wrong number. Write the candidate's home zone next to her name so the invite shows both.
2. 2Place the hard constraints before the easy ones. The PT interviewer can only land in the afternoon and the HM is blocked 13:00–14:00 - solve those two against each other first, then fill recruiter and lunch around the gaps.
3. 3Add buffers, don't pack to the minute. Leave 10–15 minutes between interviews for the candidate to breathe and for a slow interviewer to wrap; bake a real lunch in, not a working one she eats alone.
4. 4Assign rooms and Zoom explicitly. In-person slots get a room name; the PT interviewer's slot gets a Zoom link in the invite and on the itinerary so nobody hunts for it at 14:00.
5. 5Write the candidate itinerary last. One clean schedule in her home zone and ET both, with names, roles, format (in-person vs Zoom) and where to physically be.

Self-check before you call it done

• Every time is stated in both zones and you triple-checked the PT translation.
• Buffers exist between every interview and lunch is a real break.
• Every interviewer has complete context: candidate name, role, resume, interview kit, what to assess.
• The candidate has one unambiguous itinerary: where to be, who she's meeting, in-person vs Zoom and your phone number for day-of.

Coordination is mostly writing. The candidate who flew across the country judges Cursor partly by your emails, so the comms test grades whether your words are warm, exact and impossible to misread. Draft all four core messages, then grade them against the rubric below.

The four messages every loop needs: an interview invite, a prep note, a status update and a rejection. Write each one, then go back and cut anything that reads like template boilerplate. Cursor wants comms that feel written by a person, not pasted from a system.

1. Interview invite - timezone-explicit

Subject: Your Cursor onsite - Thursday 6/19, Soho NYC

Hi Priya,

We'd love to host you at our Soho office this Thursday, June 19. Your
loop runs 10:00 AM–3:00 PM ET (7:00 AM–12:00 PM PT) - I'll send a
full itinerary with names and rooms once we lock it.

Address: [office], buzz suite 4. Ask for me at the desk and I'll come
down to meet you. Lunch is on us between sessions.

Could you confirm this works by EOD tomorrow? If anything about travel
or timing is tricky, reply here and we'll flex around you.

Looking forward to meeting you,
[Name] · [phone]

2. Prep note - set them up to win

Subject: Prep for Thursday - what to expect

Hi Priya,

A few notes so Thursday feels easy:

- You'll meet four people: [HM] (hiring manager), [recruiter] and two
  team members - one in person, one over Zoom (link in your invite).
- One session is a practical coordination scenario; it's conversational,
  not a quiz. Think out loud and you'll be in great shape.
- Dress is casual. Bring whatever helps you - notes are fine.
- My cell is below for anything day-of, including running late.

You've got this. See you Thursday,
[Name] · [phone]

3. Status update - short, honest, no dead air

Subject: Quick update on next steps

Hi Priya,

Wanted to keep you in the loop: the team is wrapping up debriefs and I
expect to have clear next steps for you by Tuesday. Nothing for you to
do right now - I just didn't want you sitting in silence.

Thanks for your patience and reach out anytime,
[Name]

4. Rejection - warm, human, leaves the door open

Subject: An update on your Cursor application

Hi Priya,

Thank you for the time you gave us - flying in and meeting the team is
no small thing and we genuinely enjoyed having you in the office. After
the debrief, we've decided not to move forward for this role.

This was a close, considered decision. If you're open to it, I'd love to
stay in touch as the team grows. Wishing you the best and thank you
again,
[Name]

Grade every draft against this rubric

Hiring managers make decisions off whatever the ATS shows them. If the pipeline is messy, they're deciding on bad data and the loop slows down while everyone reconciles. This exercise hands you a tangled Ashby pipeline and grades whether you can clean it and propose one improvement worth making.

The mess in front of you: candidates sitting in the wrong stage, completed interviews with no scorecard attached and an interview kit pointing the wrong panel at the wrong round. Fix it in order, then propose exactly one process change - scoped tight enough that you could ship it this week.

Triage the messy pipeline in order

• Mis-staged candidates first - anyone who's actually further along than their stage shows. A candidate parked in “Screen” who already did the onsite blocks the HM's view of the real shortlist; move them to true stage and note why.
• Missing scorecards next - find completed interviews with no submitted feedback and chase the interviewer, because a decision made without their input is the costliest gap.
• Broken interview kits last - confirm each stage routes the right panel, the right kit and the right scorecard template before the next candidate hits it.
• Then reconcile the record - names, stages and dates that disagree with the calendar or email thread get corrected to a single source of truth.

Propose one improvement - before / after

The values rounds at Cursor screen for warmth and ruthless reliability at the same time, plus genuine excitement about the mission. You can't fake either under pressure, so you rehearse: run the likely questions out loud, in STAR, each one mapped to a value the company actually holds.

Run these six prompts as a full mock. Answer each in STAR - situation, task, action, result - and quantify the result wherever you honestly can. Record yourself or grab a peer, then review the tape for the two signals these rounds chase: warmth and reliability.

1. 1The complex schedule. “Walk me through the hairiest loop you ever coordinated.” Map to detail obsession and calm under load. End on the outcome: candidate showed up on time across three zones, zero reschedules.
2. 2The experience save. “Tell me about a time you turned a rough candidate moment into a good one.” Map to hospitality and empathy. Quantify if you can - they accepted or referred someone later.
3. 3The conflict. “A busy interviewer keeps no-showing your invites.” Map to stakeholder management and reliability. Show how you set expectations without burning the relationship.
4. 4Discretion. “You saw comp data you shouldn't share. What did you do?” Map to discretion and trustworthiness. Keep it crisp and unembellished - over-explaining here reads as the opposite of discreet.
5. 5Initiative. “What did you change that nobody asked you to?” Map to ownership and initiative. Tie it to a before/after, like the scorecard reminder from the ops exercise.
6. 6Failure. “Tell me about a coordination mistake.” Map to truth-seeking. Own it plainly, say what you changed and don't hide behind a humblebrag.

The 90-second “why Cursor, why this role”

Time it. If it runs past 90 seconds you're rambling; if it's under 30 you're underselling. The structure that lands: mission, why this role specifically and one concrete thing about how you work that proves you mean it.

Closing questions and a confident close

• Ask something that shows you've thought about the actual job: “What's the part of the loop that breaks most often when you're hiring fast and how would you want me to own it?”
• Ask about the team, not just the perks: “How does the team make sure a fly-in candidate leaves feeling great even when it's a no?”
• Close with intent: thank them by name, say plainly you want the role and confirm next steps and timing before you leave the room.

The last mile isn't more cramming. It's an honest scan of where you're sharp and where you're soft, so the hours before the loop go to the reds, not to re-reading what you already own. Rate each area red, yellow or green - and be ruthless, because a generous self-grade is the most expensive shortcut here.

Treat the rubric as a gap finder, not a score to admire. Mark the weakest proof, turn it into one practice rep and keep the artifact you would show an interviewer.

Name Cursor's actual process - cold

Story bank coverage check

Walk your stories against the JD's pillars and Cursor's values. Every pillar should have at least one story; every value should have at least one. Gaps are where the interviewer will find air.

• Pillars: complex scheduling, candidate hosting, comms hub, stakeholder collaboration, ATS hygiene, process improvement, discretion.
• Values: truth-seeking, ownership, reliability, detail obsession, empathy, calm under load, discretion, hospitality.
• If a pillar or value has no story, build one before the loop - even a small, true one beats a confident blank.