Interview Scheduling — Case Study · Vamshi Prakash Kondapalli

01 — The Problem

Two scheduling problems making placements fall apart

Across both Oorwin and Workllama, I kept seeing the same two failure modes in recruiter workflows. Both stemmed from the same root: scheduling was entirely manual, with no platform intelligence behind it.

Problem 1 — Back-and-forth overload: Recruiters were coordinating interviews over email and WhatsApp, manually checking availability with hiring managers and candidates across separate threads. A single interview slot took 4–8 messages to confirm. Multiply that across 20+ open roles and the overhead was immense.

Problem 2 — Availability blindness: There was no real-time visibility into interviewer calendars inside the platform. Recruiters were booking slots based on guesswork or phone calls, leading to last-minute conflicts, reschedules, and cancellations — each one damaging candidate experience and recruiter credibility.

4–8

Messages to confirm a single interview slot

0%

Real-time calendar visibility inside either platform

~2 hrs

Weekly scheduling overhead per recruiter

The compounding effect was significant: reschedules eroded candidate trust, no-shows wasted interviewer time, and late cancellations were causing some strong candidates to drop out of processes entirely before an offer could be made.

02 — Discovery

Understanding where the friction really lived

Before designing anything, I spent two weeks in discovery across both platforms — shadowing recruiters, interviewing hiring managers, and auditing scheduling failure data from customer support tickets.

1

Recruiter shadowing — live scheduling sessions

10 recruiters across Oorwin and Workllama customer accounts

Watched recruiters schedule interviews in real time. The pattern was consistent: open email, open WhatsApp, open LinkedIn, open calendar, open the ATS — five contexts to schedule one interview. Time-on-task for a single confirmed slot: 22 minutes on average.

2

Support ticket analysis

90-day lookback across both platforms

Scheduling-related issues — double bookings, no availability visibility, no reminder failures — appeared in 34% of all support tickets. It was the single most common source of recruiter frustration. More tellingly: 6 churned enterprise accounts had cited "scheduling chaos" in exit surveys.

3

Hiring manager interviews

Understanding the other side of the scheduling equation

Hiring managers were equally frustrated — receiving calendar invites for slots they hadn't confirmed, getting interview requests with no context about the candidate, and being asked to reschedule via email chains rather than a self-serve tool. They wanted control, not coordination overhead.

4

Competitive analysis

Greenhouse, Lever, GoodTime, Calendly for recruiting

Purpose-built scheduling tools like GoodTime and Calendly solved parts of the problem well. The key gap: none of them were native to the ATS, so candidate context was always missing at the point of scheduling. Our opportunity was an integrated solution where scheduling intelligence sat on top of the full candidate record.

"I spend more time finding a slot than I do preparing for the actual interview. That's backwards."

— Senior recruiter, Oorwin customer account

03 — Before & After

What changed for recruiters and candidates

The redesign touched every step of the scheduling flow — from how availability was surfaced to how reminders were delivered and how rescheduling requests were handled.

Before — the old flow

Recruiter emails or messages hiring manager to check availability

Waits for reply — often 24–48 hours

Proposes 2–3 slots to candidate via separate message

Candidate replies with preference — more back-and-forth

Recruiter manually creates calendar invite

No automated reminders — recruiter sends manual follow-ups

Reschedule = restart the entire chain

After — redesigned flow

Recruiter opens availability panel — live calendar slots visible

Selects 3 slots from interviewer's available times

Candidate receives self-schedule link — picks their slot

Calendar invite auto-created and sent to all parties

Automated reminders sent 24hrs and 1hr before interview

Reschedule — candidate clicks link, picks new slot, done

Full history logged on candidate record in ATS

04 — Solution

Native scheduling intelligence built into the recruiting workflow

The redesigned Interview Scheduling module was built directly into both platforms' candidate workflow — not as a standalone tool, but as a native layer with full access to candidate context, job data, and interviewer calendars.

📅

Real-time availability panel

Live calendar integration showing interviewer availability without leaving the ATS. Recruiters could see open slots, conflicts, and preferred hours in a single view per candidate.

🔗

Candidate self-scheduling

Branded self-schedule links sent to candidates showing pre-approved time slots. Candidate picks, confirms, and the invite is created automatically — zero recruiter involvement after sending.

🔔

Automated reminder sequence

Smart reminders at 24hr and 1hr before the interview — sent to candidate, recruiter, and hiring manager. Configurable per customer. No-show rate dropped significantly post-launch.

🔄

One-click rescheduling

Candidates and recruiters could reschedule via a single link — no email chains. System automatically updated the calendar invite and notified all parties. Reschedule overhead cut from 22 minutes to under 2.

📋

Interview prep context

Hiring managers received interview invites with candidate CV, job spec, and interview stage context attached — eliminating the "who am I interviewing again?" problem before each session.

📊

Scheduling analytics

Recruiter-level dashboard showing time-to-schedule, reschedule rate, and no-show rate per role. Gave team leads visibility into scheduling efficiency for the first time.

05 — Execution

Shipping across two platforms without doubling the build

One of the key challenges was that this feature needed to ship on both Oorwin and Workllama — different codebases, different tech stacks, different customer bases. Rather than building twice, I worked with engineering leads on both teams to define a shared functional spec, with platform-specific UI adaptations on top of a common scheduling logic layer.

1

Shared functional spec

Same core logic, platform-specific UI skins

Defined the scheduling engine as a platform-agnostic service: availability fetching, slot selection, invite generation, reminder dispatch. Each platform then built its own UI layer on top. This halved the design rework and allowed both teams to ship within 2 weeks of each other.

2

Calendar integration decision

Google Calendar + Outlook — the two-provider problem

Enterprise customers were split between Google Workspace and Microsoft 365. I scoped both integrations for V1 rather than deferring one — because a scheduling tool that only works for half your customers isn't a scheduling tool. Used a unified OAuth flow that handled both providers from a single connection screen.

3

Beta with high-volume recruiters

3 accounts, 8 recruiters, 4-week beta

Selected beta partners with the highest scheduling volume — agencies placing 30+ candidates per month. Their feedback surfaced two critical fixes before GA: timezone handling for cross-country interviews, and a "propose new time" flow for candidates who had no availability in the offered slots.

06 — Results

Measurable improvements in scheduling efficiency and candidate experience

Six weeks post-GA, Interview Scheduling had become one of the most actively used daily features on both platforms — with strong adoption driven by the immediate, visible time savings recruiters experienced in the first session.

−30%

Reschedules and cancellations across both platforms

22→2

Minutes per confirmed interview slot

−40%

Scheduling-related support tickets post-launch

85%

Candidates used self-schedule link vs waiting for recruiter

2 wks

Between Oorwin GA and Workllama GA — shared spec worked

#1

Most cited improvement in post-launch customer NPS surveys

The feature was cited in Workllama's TIARA Award nomination and became a key demo moment in sales conversations — scheduling live during prospect demos to show the time savings in real time.

ⓘ

On measurement: The −30% reschedule figure was calculated by comparing scheduling event logs 90 days pre and post launch across both platforms, controlling for seasonal hiring volume variation. The 22→2 minute time-on-task reduction is based on direct observation during recruiter shadowing sessions — not system-logged data, so treat it as directional. The 85% self-scheduling adoption rate reflects candidates who used the self-schedule link rather than reverting to email coordination within the first 60 days post-GA.

07 — What I Learned

Lessons from redesigning a workflow people had given up on

The biggest UX wins come from eliminating steps, not beautifying them. Reducing interview scheduling from 7 manual steps to 2 automated ones created more value than any visual redesign could have. When the workflow itself is broken, polish is irrelevant.

Scope both integrations in V1 when they're both critical. The temptation was to defer Outlook support and ship Google Calendar first. But deferring it would have made the feature useless for half our enterprise customers and killed adoption. Doing both upfront was the right call.

Self-service flows outperform "smart suggestions" for scheduling. We debated AI-suggested optimal slots vs candidate self-scheduling. Self-scheduling won — candidates preferred control over intelligence. Autonomy beats optimisation when the decision is personal.

Support ticket analysis is underrated as a product research tool. The 34% figure I found in ticket analysis was more convincing to leadership than any user research quote. Quantifying pain in operational terms (tickets, churn signals) unlocks engineering resources faster than qualitative insights alone.

Interview Scheduling — eliminating the calendar chaos that kills placements