One of the easiest ways to make
interview scheduling harder than it needs to be is to treat every interview as the same meeting.
A screening call is not the same as a hiring manager interview. A hiring manager interview is not the same as a founder-led final interview. A panel interview is not the same as an ad hoc call where the founder suddenly needs legal, operations, or a specialist involved.
They may all end up as calendar events, but they do not need the same rules.
That is what this video is really about. I walk through the different event types in calendr.so using a recruiting workflow, because hiring is a good example of how scheduling starts simple and then becomes a coordination problem as soon as more people are involved.
Why event types matter in interview scheduling
Most basic booking tools are built around individual links. A recruiter has a link. A hiring manager has a link. A founder has a link. If someone else needs to attend, the meeting is usually fixed afterwards by forwarding the invite or manually adding colleagues.
That works until the hiring process has stages.
Once a candidate moves from screening to interview to final stage, each meeting has a different job. The host may change. The required attendees may change. The format may change. The candidate may need different information. The team may need different availability rules.
An event type lets you define the meeting properly before the candidate books it. Instead of sending a vague calendar link, you are sending the right booking page for the right stage of the hiring process.
Example: screening calls
In the video, the first stage is a screening call.
This is often the easiest meeting to distribute across a team. If several HR or talent people can run the same screening conversation, the candidate should not need to wait for one named person to be free.
With a
team event type, the screening call can belong to the HR team rather than being rebuilt separately by each individual. You can still share a named person's link when that makes sense, but the underlying meeting setup stays consistent: duration, description, location, form fields, availability rules, and fallback behaviour.
That matters because screening calls are usually high-volume. Small inconsistencies multiply quickly. One recruiter asks for the phone number, another does not. One link says 15 minutes, another says 30. One person leaves and their old link stays inside a candidate email template. The process looks organised from inside the applicant tracking system, but the booking layer is quietly messy.
Example: hiring manager interviews
The second stage in the video is an interview with the line manager or hiring manager.
This is where a generic team link is not enough. The candidate may need to meet the person they would actually work with. At the same time, the Head of People, recruiter, or another internal person may need to attend every version of that interview.
That is where
multi-host booking becomes useful. The booking page can be led by the hiring manager, while additional required hosts are included automatically. The candidate only sees times where the required people are available.
Without that, the process tends to get patched after the booking. The candidate picks a time with the manager. The recruiter forwards the invite to the Head of People. Someone is not available. The time gets moved. The candidate experiences the internal calendar problem even though none of it is their fault.
Good interview scheduling hides that complexity from the candidate.
Example: final interviews
Final interviews often need a different level of control.
Sometimes the founder or senior leader needs to attend. Sometimes the conversation is more sensitive. Sometimes the candidate has already invested a lot of time in the process, so the booking experience needs to feel sharp and intentional.
For this stage, the meeting type should usually be more specific. You may want fewer available windows, more notice before booking, a clearer description of what will be covered, and a booking page that goes to the right senior person rather than a general team pool.
The video shows how you can search for the relevant final interview event type and copy the right link, rather than digging through old messages or asking the founder to resend their availability.
Fallback options stop old links breaking the process
One of the more powerful parts of team event types is what happens when the team changes.
In real hiring teams, links end up everywhere. They sit inside email templates, job-stage automations, saved replies, internal notes, and old candidate messages. Then someone leaves, changes role, or stops handling a certain type of interview.
If the old link points only to that person, the candidate can hit a dead end.
With
fallback scheduling options, a team event type can offer an alternative route when the original colleague is no longer available. Depending on your settings, that might mean offering the candidate alternative hosts, routing to a team, using round robin, or sending them to a default person.
That is not just a convenience feature. It protects the hiring process from the normal mess of people moving around inside a company.
Round robin works when several people can run the same meeting
Some interview stages need one named person. Others do not.
If any trained HR team member can run the screening call,
round robin scheduling can help distribute those meetings across the eligible people. This can give candidates more available times and prevent one person from becoming the default owner of every first call.
The important rule is simple: use round robin only when the people in the pool can genuinely run the same meeting. Do not use it for a hiring manager interview where the candidate needs one specific person. Do not use it for a technical interview where only two people understand the role properly.
The event type should match the decision the hiring team has already made.
Ad hoc meetings need a fast path too
Not every meeting deserves a permanent workflow.
Sometimes something unusual comes up. The founder wants to speak to the candidate with the head of legal. The hiring manager wants a specialist to join a follow-up call. A senior person wants one extra conversation before making an offer.
You do not want to build a full repeatable event type every time something like that happens. You just need a booking page that checks the right calendars and gives the candidate times that work for the internal people involved.
The video shows how calendr.so can be used to create an ad hoc multi-person booking page quickly, then keep that event type available if it becomes useful again later. That is helpful because recruiting does not always follow the neat version of the process written in the handbook.
What a Head of People should take from the video
If you manage hiring or people operations, the main lesson is not "use more booking links". It is the opposite.
Use fewer vague links and more deliberate event types.
For each stage of the hiring process, decide:
- Who can host this meeting?
- Does the candidate need one named person or anyone from a trained group?
- Does the meeting need additional required hosts?
- Should the candidate be able to choose phone, video, or in-person options?
- What details should be collected before the meeting?
- How much notice and buffer time does the team need?
- What should happen if the original host is no longer available?
Those decisions are the real hiring workflow. The booking page is just where those decisions become usable for the candidate.
Why this is useful beyond HR
The video uses recruiting because the stages are easy to understand, but the same idea applies across client-facing teams.
A sales team has discovery calls, demos, technical reviews, and pricing calls. A customer success team has handoffs, onboarding, training, support reviews, and renewal conversations. A professional services firm has consultations, partner meetings, client reviews, signing appointments, and ad hoc specialist calls.
If those meetings are all handled through personal links, the team eventually starts working around the booking tool. If they are handled through proper event types, the scheduling setup starts to reflect the way the business actually works.
Watch the video if your team has outgrown personal booking links
This video is worth watching if your hiring process still depends on someone manually repairing calendar invites after the candidate has already booked.
It shows how event types, team event types, multi-host booking, fallback options, round robin, and ad hoc booking pages work together. More importantly, it shows why those features exist. They are not there to make the product look complicated. They are there because real teams need different types of meetings to behave differently.
The best scheduling setup is not the one with the most links. It is the one where the right meeting type carries the right rules, so the candidate can book without seeing the internal coordination work behind it.