Prepare interview kits
Interviewers get the CV summary, questions and scorecard before the interview.
People and HR · When something happens · Updated
Works with
- Slack
- Google Calendar
- Microsoft 365
- Cal.com
- Calendly
Slack
Google Calendar
Microsoft 365
Cal.com
CalendlyHow do you prepare an interview kit?
To prepare an interview kit, connect your calendar and applicant tracker. Before each interview Maito reads the CV and role, sees which topic the interviewer covers, and sends a candidate summary, tailored questions and a scorecard in Slack. The interviewer can ask it to swap or change a question.
How it's done today
Interviewers read the CV in the elevator.
What Maito does
- Read the CV and the role
- Pick questions for this interviewer's focus
- Send the kit before the interview
Example
Loop run: Interview at 2:00 PM · Senior Backend Engineer
Alex, your kit for 2:00 PM with Hana, Senior Backend Engineer. You have system design. About Hana: 7 years in backend, last 3 on a payments ledger at a fintech. Strong on Postgres. CV shows no on-call experience. Questions: • Design a ledger that never loses a transaction. Where can it fail? • How do you make a payment webhook safe to retry? • Tell me about a migration you ran on a live table. • How do you decide when to split a service? • What would you check first in a slow checkout? Catch: Hana applied in 2025 and stopped at the final round. The old notes asked for more on distributed systems depth, so question 4 is a good one to push on. Scorecard attached: backend-scorecard.pdf. Please fill it in by 4:00 PM.
@Maito Swap question 5 for something about on-call.
Swapped. New question 5: "Walk me through the last incident you were paged for. What did you change afterwards?"
Maito (1:00 PM):
Alex, your kit for 2:00 PM with Hana, Senior Backend Engineer. You have system design.
About Hana: 7 years in backend, last 3 on a payments ledger at a fintech. Strong on Postgres. CV shows no on-call experience.
Questions:
• Design a ledger that never loses a transaction. Where can it fail?
• How do you make a payment webhook safe to retry?
• Tell me about a migration you ran on a live table.
• How do you decide when to split a service?
• What would you check first in a slow checkout?
Catch: Hana applied in 2025 and stopped at the final round. The old notes asked for more on distributed systems depth, so question 4 is a good one to push on.
Scorecard attached: backend-scorecard.pdf. Please fill it in by 4:00 PM.
Alex (1:06 PM):
Swap question 5 for something about on-call.
Maito (1:07 PM):
Swapped. New question 5: "Walk me through the last incident you were paged for. What did you change afterwards?"
How to set it up
- Ask your agent
“One hour before each interview on the hiring calendar, send the interviewer a kit: CV summary from Greenhouse, 5 questions for their focus area and the scorecard.”
- Connect calendar
- Google Calendar
- Microsoft 365
- Cal.com
- Calendly
- Use applicant tracker
- Greenhouse
- Ashby
- Workable
No MCP server needed. Ask your agent to save a skill with the steps, then add the login or API key in Settings → Vault.
Not connected yet? Your agent sends you a link to sign in.
What it won't do
Maito prepares from the CV and the role. It does not sit in the interview, and it cannot see what the candidate says on the day.
Questions
It reads your calendar through Google Calendar, Microsoft 365, Cal.com or Calendly and sends each kit ahead of time.
Yes, through a skill with a login or API key in the Vault. Greenhouse, Ashby and Workable are examples.
Yes. Ask in the same thread, for example for a question about on-call, and Maito updates the kit.
