People & HR

How to run an interview loop as Restaurant and Hospitality Founders

People & HRFor Restaurant and Hospitality Founders5 apps10 steps~20 min to set up

You need to hire a line cook, a weekend bartender, or a front desk agent — fast. Your process is a mess of Indeed applications in your Gmail, a few DMs on 7shifts, and a Google Doc with interview questions you wrote two years ago. You schedule candidates by texting back and forth, forget who you talked to last Tuesday, and lose track of whether you sent the offer to the right person. There's no system. You're interviewing between lunch and dinner service, and half the time you're asking the same questions you already asked because you can't find your notes from the first call.

Build this on Starch → See the apps used

People & HRFor Restaurant and Hospitality Founders5 apps10 steps~20 min to set up

Outcome

What you'll set up

A structured interview pipeline that pulls candidate emails from Gmail, schedules interviews through a booking link synced to your real calendar, and keeps every conversation and decision in one place

Automatic meeting notes for every interview so you have a written record of what the candidate said — searchable after the fact, not stuck in your memory

A task list tied to each open role so follow-ups, reference checks, and offer letters don't slip through the cracks during a busy service week

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

Email Agent Scheduling Meeting Notes Task Manager Knowledge Management

Data sources & config

Starch syncs your Gmail data on a schedule so the Email Agent sees incoming applications as they arrive and can draft replies without you touching your inbox. The Scheduling app connects directly to Google Calendar — also a scheduled-sync provider — so your booking page always reflects your actual availability, not a static template. Meeting Notes works from the call transcript itself (no additional integration needed). Task Manager and Knowledge Management run standalone — no external connection required for core use.

Prompts to copy

Monitor my Gmail for job applications to the line cook and weekend bartender roles. Triage them by how complete their application is — do they mention restaurant experience, availability, and a phone number? Draft a reply to qualified candidates with my scheduling link and a short note about what the shift looks like.

Create a 30-minute 'Candidate Interview' meeting type on my booking page. Block out Tuesday and Thursday afternoons from 2:30–5pm. Add 15-minute buffers so I'm not running from the floor straight into a call. Send candidates this link in my reply.

After each interview call ends, summarize the key things the candidate said about their experience, their availability, and any red flags. Pull out one action item for me — like 'call their reference at their last restaurant job' — and add it to my task list.

Build me a wiki page for our line cook interview process: the questions we always ask, what a passing answer looks like, and what we're actually evaluating for (speed, mise en place habits, attitude under pressure). I want new managers to be able to run interviews without asking me every time.

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

Walkthrough

Step-by-step

1 Connect Gmail to Starch (scheduled-sync provider). Starch starts pulling your inbox on a schedule — the Email Agent can now see incoming applications from Indeed, direct email, or referrals.

2 Tell the Email Agent: 'Watch for emails about job applications for line cook and bartender roles. Flag ones where the candidate mentions relevant experience and has a phone number or availability. Draft a reply to those with my scheduling link.' Starch builds the triage rule and the reply template.

3 Set up the Scheduling app. Tell Starch: 'Create a 30-minute candidate interview slot. My availability is Tuesday and Thursday, 2:30–4:30pm. Add a 15-minute buffer after each meeting.' Starch generates your public booking page synced to Google Calendar.

4 Paste your booking link into the Email Agent's reply draft. From now on, qualified candidates get a real link to book time — no more text threads about 'does Tuesday at 3 work?'

5 Before your first interview week, open Knowledge Management and tell Starch: 'Build a wiki page for our hourly staff interview process. Include the five questions we ask every candidate, what we're looking for in their answers, and the deal-breakers.' Fill in your actual questions — Starch organizes and stores them so any manager can run the interview.

6 Run interviews. Meeting Notes transcribes each call (or in-person conversation if you record it) in real time and generates a summary — what the candidate said about their experience, their stated availability, and any hesitations you flagged.

7 After each interview, tell Starch: 'Add a task: call the reference for [candidate name] by Friday. Priority P2.' Task Manager logs it with a due date and will alert you if it goes overdue.

8 At the end of the week, tell the Email Agent: 'Draft a hold email to the two candidates I haven't decided on yet and a rejection to the one who couldn't work weekends.' Starch drafts all three — you review and send.

9 When you're ready to make an offer, tell the Email Agent: 'Draft an offer email to [candidate name] for the line cook role, Tuesday–Saturday, starting at $22/hour, start date two weeks from Monday.' Starch drafts it from your prior notes.

10 After the hire, tell Knowledge Management: 'Add a section to the line cook onboarding page: who interviewed [new hire], when they start, and which manager is responsible for their first week.' The record stays in your wiki — not in someone's head.

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 Line Cook Hire — Two-Week Sprint

Sample numbers from a real run

Applications received via Gmail (Indeed + direct)	14
Auto-triaged by Email Agent as qualified (experience + availability mentioned)	6
Interviews booked via scheduling link (no back-and-forth)	5
Interview summaries auto-generated by Meeting Notes	5
Reference check tasks created in Task Manager	3
Days from first application to signed offer	11

You posted a line cook role on a Tuesday. By Thursday morning, 14 applications had come in through Gmail. The Email Agent flagged 6 as qualified — they mentioned kitchen experience, weekend availability, and included a phone number. It drafted a reply to each with your booking link. Five booked slots for the following Tuesday and Thursday. You ran five 30-minute interviews without scheduling a single one manually. Meeting Notes gave you a one-paragraph summary after each call: what they said about their last kitchen, their speed on the line, whether they'd worked brunch. You added reference check tasks for the top three — all marked P2, due by Friday. One reference didn't call back; Task Manager flagged it overdue. You hired the candidate whose sous chef gave a four-minute enthusiastic reference. Total time from posting to offer: 11 days. You didn't lose a single application in your inbox.

Measurement

How you'll know it's working

Time-to-hire per role (days from job post to signed offer)

Interview-to-offer conversion rate (how many interviews before you find someone)

Application triage rate (what percentage of applicants are worth calling)

Candidate no-show rate on scheduled interview slots

First-90-day retention for hourly hires

Comparison

What this replaces

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

Indeed + Gmail + Google Calendar manually

Free and familiar, but you're manually triaging every application, scheduling by hand, and your interview notes live in a notebook you'll lose before the next hire.

Workable or Lever (ATS)

Purpose-built applicant tracking, but priced for companies hiring at volume — not cost-effective when you're filling one or two roles a quarter and need the tool to also handle your inbox and task list.

7shifts built-in hiring

Convenient if you're already on 7shifts for scheduling, but limited to applicant collection — no interview scheduling, no note capture, no task tracking after the candidate applies.

Calendly standalone

Handles the scheduling piece well, but it's a separate tool with no connection to your Gmail triage, your interview notes, or your follow-up tasks — you're still stitching everything together yourself.

On Starch RECOMMENDED

One platform — email agent, scheduling, meeting notes 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

Do I need a formal API connection to Indeed or my job boards?

No. Most candidate responses land in your Gmail inbox anyway. Starch syncs your Gmail on a schedule and the Email Agent reads applications from there. For job boards that don't email you directly, Starch can automate through your browser — no API needed.

What if I do interviews in person on the floor, not on a call?

You can record a short voice memo after the interview and feed the transcript to Meeting Notes manually, or just tell Starch the key points in plain text: 'Log my interview with [name] — she has 4 years line experience, available weekends, asked about benefits.' Starch saves it to your interview history in Knowledge Management.

Will my candidates see 'Starch' anywhere when they book an interview?

The scheduling link is yours — it's a public booking page that reflects your availability. The Gmail OAuth consent screen currently shows the underlying connector's name rather than yours; Starch-verified client branding is on the roadmap.

I hire seasonally — 6 people at once in the spring. Can this handle volume?

Yes. You can run the same Email Agent triage rule and scheduling setup across multiple open roles simultaneously. Tell Starch: 'I'm hiring for line cook, prep cook, and host — triage applications for all three and route each to the right interview type.' It handles the routing; you handle the calls.

What about storing candidate information — is there a privacy concern?

Starch is not SOC 2 Type II certified today. Candidate data pulled from Gmail lives in Starch's database. If you're in a jurisdiction with strict data handling requirements for job applicant information, factor that in. Starch is transparent about this limit rather than burying it.

I have a manager who runs hiring for the back of house. Can they use this too?

Yes. The Knowledge Management wiki with your interview process and questions is shareable with your team. You can set up the Scheduling app so your manager's availability is reflected, not just yours. Meeting Notes archives are searchable — your manager can pull up past candidates without asking you.