People & HR

How to run an interview loop as Foundation and Nonprofit Ops Teams

People & HRFor Foundation and Nonprofit Ops Teams4 apps11 steps~22 min to set up

Your foundation's interview loop for program officers, grants managers, or operations hires runs across at least four systems nobody synchronized. Scheduling candidates means a chain of emails to find a panel slot when three staff members' Google Calendars are all different levels of accurate. Interview notes live in a mix of someone's personal Google Doc, a sticky note, and half a Slack thread. Scoring rubrics are a PDF someone attached to an email in 2023. By the time the panel debrief happens, half the interviewers can't remember which candidate said what. For a 4-person ops team hiring once or twice a year, this is painful enough that you delay starting searches because the logistics feel like a project in themselves.

Build this on Starch → See the apps used

People & HRFor Foundation and Nonprofit Ops Teams4 apps11 steps~22 min to set up

Outcome

What you'll set up

A scheduling system that gives candidates a public booking link synced to your panel's real availability — no more 'does Thursday at 2 work for everyone?' email chains

A structured interview notes archive where every panel member's observations land in one searchable place, with action items and decisions extracted automatically after each call

A lightweight task tracker that keeps the hiring process moving — who still needs to submit feedback, which candidate is waiting on a follow-up email, what's the offer deadline

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 Email Agent

Data sources & config

Starch connects directly to Google Calendar via scheduled sync to power panel availability and booking. Calendly is also available as a scheduled-sync provider if your foundation already uses it for external bookings. Gmail is connected via scheduled sync so the Email Agent can read candidate threads and draft follow-ups without you switching tabs. Task Manager and Meeting Notes run on top of these connections — no additional data wiring required to start.

Prompts to copy

Build me a scheduling setup for a 3-round interview process: a 30-minute intro call with our HR lead, a 60-minute panel interview with 2 program staff, and a 30-minute final conversation with our Executive Director. Add 15-minute buffers between meetings and block off Fridays.

After each candidate interview, transcribe the call, summarize key moments, and extract action items — flag any commitments the interviewer made to the candidate (like 'we'll follow up by Friday').

Create a task list for our program officer search: track feedback deadlines for each interviewer, follow-up emails owed to candidates, and offer letter signature status. Alert me when anything is overdue by more than 24 hours.

Draft a follow-up email to a candidate we met with yesterday. Tone should match a foundation — warm but professional, not startup-y. Pull in the next steps we discussed from the meeting notes.

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

Walkthrough

Step-by-step

1 Connect your Google Calendar (and the calendars of any panel members) via Starch's scheduled sync. This lets Starch see real availability across your team without anyone manually maintaining a shared calendar.

2 Use the Scheduling starter app to build booking pages for each interview round — 30-min intro, 60-min panel, 30-min final. Set buffer rules and define which staff member hosts each round.

3 Share the Stage 1 booking link with candidates directly from your applicant tracking system or by email. Candidates self-schedule; Starch creates the calendar event for everyone automatically.

4 Before each panel interview, have Starch pull the candidate's prior round notes and draft a one-paragraph briefing for the interviewers — so no one shows up cold.

5 During or immediately after each interview, Meeting Notes transcribes the call and produces a structured summary: what the candidate said about their grants management experience, any red flags raised, and what you promised them as next steps.

6 After each round, route the summary into a shared interview log. Describe it to Starch: 'Build me a candidate tracker that shows each applicant's name, which rounds are complete, a one-line summary from each interview, and the interviewer's recommendation score.'

7 Use Task Manager to assign post-interview actions — 'Sarah needs to submit panel feedback by EOD Wednesday,' 'Send rejection email to Candidate B by Friday.' Capture these from chat: 'remind me to send the offer letter to Candidate A by next Tuesday.'

8 When it's time to draft candidate communications, pull the relevant meeting notes and tell the Email Agent: 'Draft a thank-you and next-steps email to the candidate we interviewed this morning. Use the notes from that call. Foundation tone — not corporate, not casual.' Review and send in one click.

9 Before the final debrief, ask Starch to produce a comparison view: 'Summarize the three finalists side by side — their backgrounds, what each interviewer said, and any open questions.' This replaces the 'does anyone remember what Candidate 2 said about program evaluation?' moment.

10 After the hire decision, archive the full interview record — transcripts, scores, emails — in Meeting Notes' searchable history. When you're hiring again in 18 months and want to remember what questions worked, it's all there.

11 If your foundation uses DocuSign for offer letters, Starch can automate checking signature status through your browser — no DocuSign API setup needed — and surface the status in your task list.

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

Program Officer Search — March 2026

Sample numbers from a real run

Stage 1 intro calls scheduled (8 candidates)	8
Panel interviews completed (3 candidates)	3
Interviewer feedback tasks auto-tracked	9
Candidate follow-up emails drafted by Email Agent	14
Hours of coordinator time estimated saved vs. prior search	11

In your last program officer search, scheduling alone took two weeks of back-and-forth because your Executive Director, two program staff, and the HR consultant all had different availability and none of it was visible in one place. This time, you built three booking pages in Starch — 30-min intro with the HR lead, 60-min panel with two program staff, 30-min final with the ED — each pulling live from their Google Calendars. You sent the Stage 1 link to 8 candidates on a Monday; all 8 had scheduled themselves by Wednesday with no emails exchanged. After each panel, Meeting Notes pulled the transcript and flagged that one interviewer had promised Candidate 2 a decision by March 21 — a commitment that would have been lost in a personal notes doc. The task list reminded that interviewer to submit her scorecard 36 hours before the debrief. Going into the final panel discussion, you had a Starch-generated side-by-side of the three finalists — summarizing each person's grants management background, the panel's open questions, and salary expectations. The offer letter went to the selected candidate on March 19. The full interview record — every transcript, every score, every email draft — is archived and searchable for the next time you hire.

Measurement

How you'll know it's working

Time-to-schedule per candidate (days from outreach to confirmed interview slot)

Interviewer feedback completion rate before debrief (% of scorecards submitted on time)

Candidate communication SLA (% of follow-ups sent within promised window)

Interview archive completeness (% of calls with transcript + summary on file)

Days from final interview to offer letter sent

Comparison

What this replaces

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

Calendly (standalone) + Google Docs for notes

Calendly handles scheduling well but doesn't connect to your interview notes, task tracking, or email drafting — you're still manually stitching four tools together after the meeting is booked.

Greenhouse or Lever (ATS)

Full-featured ATS with structured interview workflows, but requires a dedicated implementation, costs scale with headcount, and assumes a recruiting function that a 4-person foundation ops team doesn't have — Starch connects to Greenhouse or Lever from its integration catalog if you already use one, but doesn't require it.

Notion + Notion AI

Flexible for building a candidate tracker and notes archive, but doesn't automate scheduling, draft emails from live calendar data, or extract action items from call transcripts without significant manual setup — Starch connects to Notion via scheduled sync if you want to push structured interview data there.

Workable or BambooHR hiring module

Purpose-built for hiring workflows but adds another system to manage; BambooHR is reachable from Starch's integration catalog if you already use it for HR records, so you don't have to choose between the two.

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

Our foundation only hires 1-2 people a year. Is this worth setting up?

The scheduling and meeting notes pieces take under an hour to configure and pay back immediately — even for a single search with 8 first-round candidates, you're looking at 2-3 weeks of email back-and-forth eliminated. The task tracker and email drafting are things your team likely needs year-round anyway, not just during a search.

We use Outlook, not Gmail. Does this work?

Yes. Starch connects directly to Outlook via scheduled sync — messages, calendar events, and contacts. The Email Agent and scheduling flows work the same way for Outlook users as for Gmail users.

Can Starch integrate with the ATS we already use (Greenhouse, Lever, Workday)?

Greenhouse, Lever, and Workday are all reachable from Starch's integration catalog of 3,000+ apps — the agent queries them live when your app needs the data. You won't get a deep scheduled sync the way you do with QuickBooks or Stripe, but you can pull candidate lists, pipeline stages, and job details into a Starch surface.

Will Starch store our candidates' personal data?

Starch stores data that comes through scheduled-sync providers (like your Google Calendar availability) in its database. Interview transcript content captured by Meeting Notes and email content processed by the Email Agent passes through the platform. Starch is not SOC 2 Type II certified today — that's an honest limit worth knowing if your foundation has a data governance policy that requires it.

What if an interviewer doesn't want to use a new tool for their notes?

They don't have to. Meeting Notes captures the transcript from the call itself — the interviewer just has to be on a recorded video call. You can also tell Starch: 'Build me a simple form where panel members can paste their notes after each interview and I'll see all three responses side by side before the debrief.' Describe it, Starch builds it.

Can Starch help with the offer letter and DocuSign signature tracking?

Starch can automate checking DocuSign status through your browser — no API connection needed — and surface the signature status in your task list. The Customer Support Agent app that would handle more complex document workflows is coming soon, but the browser automation approach works for checking status today.