Defining who the team is looking for

Recruiters needed more than a job description to compare candidates consistently. I structured vacancy setup around the attributes that mattered during evaluation: candidate requirements, relevant skills, and assessment tests.

These inputs were then used to create a consistent evaluation framework for every candidate applying to the role.

Instead of showing assessment results as isolated scores, I explored a visual comparison between the candidate profile and the requirements defined for the vacancy. This made strengths and gaps easier to review at a glance.

Soft-skill results followed the same principle: give recruiters a quick overview first, while keeping detailed assessment data available when needed.

Making the hiring pipeline easy to scan

Recruiters needed to understand the state of a vacancy without opening candidates one by one. I used a Kanban-style pipeline to make hiring stages visible at a glance and allow candidates to be moved through the process directly from the board.

I chose this pattern because the stage-based model matched the recruitment workflow and was already familiar to many users.

Bringing candidate context into one place

Candidate information was spread across different parts of the hiring process: profile data, assessment results, interview status, communication, and team notes.

I brought this context into a single candidate workspace so recruiters could review a person, make a decision, change their hiring status, and leave internal notes without constantly switching between screens.

Making interviews asynchronous

Scheduling live interviews created additional coordination between recruiters and candidates. For early evaluation stages, the product supported asynchronous video interviews instead.

Recruiters prepared questions in advance, while candidates could record their answers when convenient. The team could then review responses without finding a shared time slot.

Assessment results were added to the same candidate context instead of becoming another separate workflow. Recruiters could review test results and psychological assessment data alongside the rest of the candidate information before making a decision.

Giving the team a shared view of hiring performance

Recruitment decisions were not only about individual candidates. Teams also needed to understand how vacancies and hiring stages were performing overall.

I designed a dashboard around the main operational views — candidate funnels, open vacancies, and video interviews — so recruiters and other team members could work from the same information instead of relying on fragmented updates.

←→

Supporting recruitment away from the desk

The product also needed to support recruiters when they were away from a desktop. I adapted the core workflows for mobile rather than treating the app as a collection of scaled-down desktop screens.

The focus was on the actions that needed quick access: reviewing candidates, checking hiring stages, and accessing key candidate information.

←→

Building consistency as the product grew

As more screens and workflows were added, maintaining consistency manually became harder. I created the initial design system to standardize recurring components, states, typography, spacing, and interaction patterns across the product.

It gave design and development a shared foundation for extending and maintaining the platform.

Conclusion

CallPanda was my first experience designing a product of this scale from the ground up. It taught me to think beyond individual screens and work with connected workflows, reusable patterns, and implementation constraints across an entire product.

It also changed how I approach complex projects today: I define the system first, clarify priorities early, and use reusable patterns to keep the experience consistent as the product grows.