Automated Bulk-scheduling feature
Automated Bulk-scheduling feature
HR Staffing & Recruitment
HR Staffing & Recruitment
At a glance 👀
At a glance 👀
Connect is a recruitment platform used by staffing agencies and talent teams to manage high-volume hiring.
During discovery, one insight appeared in almost every conversation with recruiters: Recruiters were manually calling or texting every single candidate to schedule interviews.
For roles where 80–200 candidates need to be processed per week, this created massive inefficiencies.
Connect is a recruitment platform used by staffing agencies & talent teams to manage high-volume hiring.
During discovery, one insight appeared in almost every conversation with recruiters: Recruiters were manually calling or texting every single candidate to schedule interviews.
For roles where 80–200 candidates need to be processed per week, this created massive inefficiencies.
Problem Statement
Problem Statement
Manual, one-by-one interview scheduling was slowing down the hiring pipeline and increasing recruiter workload.
Manual, one-by-one interview scheduling was slowing down the hiring pipeline and increasing recruiter workload.
My Role
Talk to the users, collaborated with PMs, developers and Stakeholders
My Role
Talk to the users, collaborated with PMs, developers and Stakeholders
Platform
Website
Prototype
Prototype
This prototype showcases how recruiters can schedule interviews in bulk with minimal effort.
This prototype showcases how recruiters can schedule interviews in bulk with minimal effort.
Jobs section overview
Jobs section overview
It gives recruiters a clear overview of all applicants and their movement through the hiring pipeline.
It gives recruiters a clear overview of all applicants and their movement through the hiring pipeline.
Filter Section
Filter Section
Here, recruiters can refine their candidate list by applying score filters.
Here, recruiters can refine their candidate list by applying score filters.
Automated Bulk-scheduling feature - why?
Automated Bulk-scheduling feature - why?
Recruiters were handling 10+ candidates manually, making individual scheduling inefficient and error-prone.
Recruiters were handling 10+ candidates manually, making individual scheduling inefficient and error-prone.
Medium - through Email, SMS and Both
Medium - through Email, SMS and Both
Recruiters currently use multiple external platforms. Supporting multiple channels reduces dependency on external tools and improves reach.
Recruiters currently use multiple external platforms. Supporting multiple channels reduces dependency on external tools and improves reach.
Follow up - why?
Follow up - why?
Manual follow-ups were a major pain point; separating this view helps recruiters quickly identify and act on non-responsive candidates.
Manual follow-ups were a major pain point; separating this view helps recruiters quickly identify and act on non-responsive candidates.
Medium - through SMS
Medium - through SMS
Sending an interview link through SMS.
Sending an interview link through SMS.
Medium - Both (Email & SMS)
Medium - Both (Email & SMS)
Sending an interview link through both the medium.
Sending an interview link through both the medium.
My Process
My Process
Research Findings - user interviews & observations
Research Findings - user interviews & observations
Candidate communication happens outside the Connect platform using multiple tools
Sending interview links individually is time-consuming and repetitive
Manual follow-ups are difficult to track and often missed
Scheduling and coordination require high effort and time
Candidate communication happens outside the Connect platform using multiple tools
Sending interview links individually is time-consuming and repetitive
Manual follow-ups are difficult to track and often missed
Scheduling and coordination require high effort and time
Requirement Flow
Requirement Flow
Before jumping into design, I visualized the complete flow and walked stakeholders through it, allowing us to identify gaps and remove unnecessary complexity upfront
Before jumping into design, I visualized the complete flow and walked stakeholders through it, allowing us to identify gaps and remove unnecessary complexity upfront
Recruiter flow
Recruiter flow
Candidate Flow
Candidate Flow
Personas
User Persona
User Journey Map
User Journey Map
Conversation with the Director of Engineer
Conversation with the Director of Engineer
STAGES - work flow (understanding needs)
STAGES - work flow (understanding needs)
Design Decision - Initial Wireframe Idea
Design Decision - Initial Wireframe Idea
I start with wireframes to communicate the initial concept and validate my understanding with stakeholders before moving into high-fidelity design.
I start with wireframes to communicate the initial concept and validate my understanding with stakeholders before moving into high-fidelity design.
Initial Screen flow
Initial Screen flow
My core idea was to automate interview scheduling by introducing a smart action button where recruiters simply describe what they want to do, and the system handles the rest.
My core idea was to automate interview scheduling by introducing a smart action button where recruiters simply describe what they want to do, and the system handles the rest.
Iteration
Iteration
Simplified the bulk scheduling trigger from multiple CTAs to one primary action
Added Email / SMS / Both options after realizing recruiters use multiple channels
Introduced a follow-up screen to reduce missed candidate responses
Refined success states to clearly confirm actions
Reduced steps after validating the requirement flow with stakeholders
Simplified the bulk scheduling trigger from multiple CTAs to one primary action
Added Email / SMS / Both options after realizing recruiters use multiple channels
Introduced a follow-up screen to reduce missed candidate responses
Refined success states to clearly confirm actions
Reduced steps after validating the requirement flow with stakeholders
My Learning
My Learning
Working closely with engineering and stakeholders helped align technical feasibility with user needs early in the process.
Breaking the problem into smaller, validated steps made it possible to deliver quality outcomes within limited time.
Early alignment reduced cognitive load, clarified constraints, and removed blockers before they impacted the solution.
Repeated iterations and continuous validation helped refine the experience and ensured the solution addressed real user problems.
Working closely with engineering and stakeholders helped align technical feasibility with user needs early in the process.
Breaking the problem into smaller, validated steps made it possible to deliver quality outcomes within limited time.
Early alignment reduced cognitive load, clarified constraints, and removed blockers before they impacted the solution.
Repeated iterations and continuous validation helped refine the experience and ensured the solution addressed real user problems.