People & HR

How to run an interview loop as Educators, Coaches, and Course Creators

People & HRFor Educators, Coaches, and Course Creators4 apps11 steps~22 min to set up

You're hiring a teaching assistant, a guest expert, or your first ops hire, and your interview process is held together with a shared Google Sheet, a Calendly link, and a mental checklist you re-create every time. Candidates book a slot, then you forget to send them the prep doc. You take notes in a separate doc that you never find again. You make a hire decision in your head but never write it down. Six weeks later someone asks why you hired that person and you genuinely can't remember your reasoning. You're not running a broken hiring process — you have no hiring process at all.

Build this on Starch → See the apps used

People & HRFor Educators, Coaches, and Course Creators4 apps11 steps~22 min to set up

Outcome

What you'll set up

A self-contained interview loop where candidates book their own slots, you walk in with structured questions ready, and every conversation is transcribed and summarized automatically

A searchable archive of every interview — notes, decisions, action items — so you can compare candidates without holding it all in your head

A simple task queue that tracks every post-interview follow-up (send rejection, check references, make offer) with due dates and alerts so nothing gets ghosted

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Scheduling Meeting Notes Task Manager Knowledge Management

Data sources & config

Starch connects directly to Google Calendar (scheduled sync) so the Scheduling app reads your real availability and blocks time without double-booking. Calendly is connected from Starch's integration catalog; the agent queries it live to pull existing booking rules you want to mirror. Notion is connected from Starch's integration catalog so your prep docs and hiring wiki pages sync into Knowledge Management. Zoom is connected from Starch's integration catalog so Meeting Notes can pull the call recording for transcription.

Prompts to copy

Create a 45-minute interview meeting type called 'Curriculum TA Interview' with 15 minutes of buffer after each slot. Block Thursdays and Fridays only. Add an automatic confirmation email that includes a link to our prep doc in Notion.

After each interview call ends, generate a summary with: candidate name, the role they're applying for, three strengths I mentioned, one concern, and my preliminary hire/no-hire lean. Extract any action items (e.g., 'check their portfolio link', 'ask for a sample lesson plan').

Build me a hiring tracker wiki page that logs each candidate: name, interview date, role, my summary notes, and final decision. Make it searchable so I can compare candidates side by side.

Add a task: send follow-up email to candidate within 48 hours of interview. P1 priority. Due two days after the interview date.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Google Calendar via Starch's scheduled sync and set up your Scheduling app with a dedicated 'Interview' meeting type — 45 minutes, buffer time, availability limited to two days per week so your teaching schedule isn't disrupted.

2 Drop your Calendly booking link in your outbound candidate emails; Starch mirrors your Google Calendar availability so there's no double-booking between your existing Calendly and the new scheduling layer.

3 Wire Notion into Starch's integration catalog connection so your existing prep doc (the one with your question bank and role criteria) is accessible inside Starch — candidates can be sent the link automatically at booking confirmation.

4 For each scheduled interview, Starch creates a Meeting Notes session. When the Zoom call starts, it transcribes in real time so you can stay in the conversation instead of typing.

5 When the call ends, tell Starch: 'Summarize this interview. Pull out my hire/no-hire lean, the top two things that impressed me, and any open questions I need to follow up on.' It generates a structured summary in under a minute.

6 Starch logs the summary into a candidate page inside your Knowledge Management wiki — one row per candidate, searchable, with interview date, role, and decision field.

7 Meeting Notes extracts action items automatically — things like 'review their sample lesson plan' or 'email references by Friday' — and sends them to your Task Manager with a due date and P1/P2 priority.

8 At the end of a hiring round (say, four candidates for one TA role), open your Knowledge Management wiki and search across all four candidate pages. You can compare notes without relying on memory or digging through separate docs.

9 Task Manager surfaces the follow-up queue: rejection emails to send, reference checks to complete, offer to draft. Each task has a due date; overdue alerts fire if you let something sit.

10 After you make a hire, log the final decision and reasoning in the candidate's wiki page. Three months later when someone asks why you hired that person, the answer is findable in thirty seconds.

11 At the end of each hiring cycle, tell Starch: 'Summarize this round — how many candidates interviewed, what the timeline was, and what I'd do differently next time.' Save that as a hiring retro page in your wiki so the next cohort launch is faster.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 Cohort TA Hire — 5 candidates, 2 weeks

Sample numbers from a real run

Candidates interviewed	5
Interview slots scheduled (no back-and-forth emails)	5
Follow-up tasks auto-created in Task Manager	11
Days from first interview to offer letter	9
Candidate summaries searchable in wiki	5

You're filling one TA slot before your April cohort of 80 students launches. You create an 'Interview' meeting type in Scheduling, drop the link in five outbound emails on Monday. By Wednesday all five candidates have booked Thursday and Friday slots — no one emailed you asking 'when are you free?' During each Zoom call, Meeting Notes runs in the background. After candidate 3, you realize you've already forgotten what candidate 1 said about curriculum design — you open the Knowledge Management wiki, search 'pacing,' and find the exact quote from her transcript. After all five interviews, Task Manager shows 11 open items: 5 follow-up emails (P1, due in 48 hours), 3 reference checks (P2, due by end of week), 2 portfolio reviews, and 1 offer letter draft. You send the offer on day 9. Your hiring retro page notes that you should add a 'sample lesson plan' submission requirement before the interview next time — it's there for the next round without you having to remember it.

Measurement

How you'll know it's working

Days from first interview to offer letter (target: under 14 days so you're not scrambling before cohort launch)

Percentage of post-interview follow-ups completed within 48 hours (candidate experience depends on it)

Number of hiring rounds where you can cite specific reasoning for your final decision (without digging through email)

Time spent on scheduling back-and-forth per candidate (target: zero emails)

Repeat use of the interview question bank across rounds (are you actually reusing what you built, or rebuilding every time?)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Sheets + Calendly + a notes doc

Works for one hire, falls apart by the third candidate — notes live in three places and you lose the thread between the booking, the call, and the follow-up.

Notion hiring tracker (built from scratch)

Good for storing decisions but doesn't connect to your calendar, doesn't transcribe calls, and doesn't create follow-up tasks — you're still doing all the linking manually.

Greenhouse or Lever (full ATS)

Built for recruiters running 50+ roles, not a solo course creator hiring one TA every six months — the setup cost and monthly price are hard to justify at your volume.

Calendly + Otter.ai + Asana

Three separate tools that don't talk to each other; you're copying action items from Otter into Asana by hand and the candidate history is still scattered across apps.

On Starch RECOMMENDED

One platform — scheduling, meeting notes, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

I only hire two or three people a year. Is this overkill?

Probably not — the pain isn't volume, it's losing context between a booking, a call, and a follow-up email that needs to go out in 48 hours. Even for two hires a year, having a searchable record of why you made each decision is worth more than the setup time. The Scheduling and Meeting Notes apps are also useful for your day-to-day coaching calls, not just hiring.

Can Starch send automated emails to candidates — confirmations, rejections, offers?

Starch syncs your Gmail data on a schedule and can draft emails for you to review and send. It doesn't send emails fully autonomously without your approval by default, which is intentional — a misfired rejection email to the wrong candidate is a real risk you don't want automated away. You stay in the loop; Starch just prepares the drafts and flags when they're overdue.

My interviews are on Zoom. Does Starch actually capture the transcript, or does it just summarize from my notes?

Starch connects to Zoom from its integration catalog and Meeting Notes works from the recording or live session. It transcribes the actual conversation, not just your notes. That's the difference between 'I think she mentioned curriculum design' and finding the exact quote from minute 14.

I use Calendly already and candidates know the link. Do I have to replace it?

No. Starch connects to Calendly from its integration catalog; you can keep using your existing Calendly link and pull that booking data into Starch's workflow. You don't have to migrate candidates to a new booking page mid-search.

Is Starch SOC 2 certified? Candidate information is sensitive.

Starch is not SOC 2 Type II certified today — that's an honest limit worth naming. If your hiring process involves sensitive candidate data that your organization requires SOC 2 controls for, that's a real consideration. For most solo educators and small coaching businesses, the risk profile of storing interview notes in Starch is comparable to storing them in Notion or Google Drive — but you should make that call based on your own situation.

What if my interview structure changes between hiring rounds?

Tell Starch: 'Update my interview summary template — add a field for the candidate's teaching philosophy and remove the salary expectations field.' It rebuilds the template. Your old summaries aren't affected; new ones use the updated structure. You can also describe a completely different process from scratch for a different role type — Starch builds it from your description, not a fixed template.