Recruitment & Applicant Management Systems for South African Businesses

Manage vacancies, applications, candidate records, documents, screening stages, interviews, follow-ups and hiring or placement outcomes through one structured recruitment process.

An applicant tracking system should do more than store CVs. It should show which vacancy each person applied for, where that application currently sits, what still needs to happen, who is responsible for the next action and what decision history exists afterwards.

Repautomate can design custom recruitment and applicant management systems for internal hiring teams and recruitment businesses where spreadsheets, inboxes, shared folders and disconnected tools no longer support the workflow adequately.

Where an established applicant tracking or recruitment platform already fits the process, configuring or integrating that software may be more sensible than rebuilding it.

Explore Recruitment System Features Discuss Your Recruitment Process

A system may manage:

  • Vacancies and requisitions
  • Candidate records
  • Job applications
  • CVs and documents
  • Screening stages
  • Interview workflows
  • Recruiter and manager notes
  • Candidate communication
  • Client submissions
  • Offers, placements and handovers

What is a recruitment and applicant management system?

A recruitment and applicant management system is software used to organise the records and workflow from an open vacancy through candidate applications, screening, interviews and the eventual hiring or placement outcome.

It can provide recruiters and hiring managers with a structured view of vacancies, candidates, applications, interactions, documents, decisions and outstanding actions.

For internal HR teams, the final successful application may hand approved information into employee onboarding.

For recruitment agencies, the workflow may continue through candidate submissions to clients, client feedback and placement records.

The system should reflect which recruitment model the organisation actually uses rather than assuming internal recruitment and agency recruitment are identical.

A useful recruitment record helps answer:

  • Which vacancy is being filled?
  • Who has applied?
  • Which applications still need review?
  • What stage is each candidate in?
  • Who needs to take the next action?
  • Which interviews are scheduled?
  • What feedback has been recorded?
  • Which candidates were submitted to a client?
  • Who withdrew or was not progressed?
  • Who was hired or placed?

A candidate and a job application are not the same record

This distinction becomes important as soon as the same person applies for more than one vacancy.

The candidate profile can represent the person. Each application can represent that person’s participation in a specific recruitment process.

That keeps the history of one vacancy from overwriting what happened on another.

Example data structure

Candidate
Contact information, CV, approved profile information and appropriate communication history.

Application 1
Sales Administrator vacancy, screening status, interview history and final outcome.

Application 2
Account Coordinator vacancy, its own screening process, notes and decision.

One candidate can therefore have a history across several appropriate applications without becoming several duplicate people in the database.

When recruitment is spread across inboxes, spreadsheets and folders

A vacancy can attract dozens or hundreds of separate pieces of information.

Applications arrive through email or forms. CVs are downloaded into folders. A recruiter maintains a spreadsheet of candidate stages. Hiring managers send feedback by message. Interviews sit in separate calendars. A successful candidate is eventually handed to HR through another email.

The recruitment activity is happening, but the working record is fragmented.

A structured system connects the application to the actions and decisions that follow.

Applications are difficult to reconcile

Recruiters manually compare inboxes, CV folders and spreadsheets to confirm who applied and whether anybody was missed.

Candidate status becomes outdated

The recruitment spreadsheet says interview while the candidate has already completed the interview or withdrawn.

Hiring-manager feedback is scattered

Interview comments and progression decisions sit in messages instead of the application record.

Candidates need repeated follow-up

Recruiters manually remind people about documents, interviews and outstanding responses.

Agency submissions are difficult to track

The recruiter knows candidates were sent to a client but cannot quickly see which submission is awaiting feedback.

Reporting requires another spreadsheet

Vacancies, applications, interviews and placements have to be counted manually because the workflow record is incomplete.

How an application can move through the recruitment system

The actual stages should reflect the employer or agency, but a general recruitment workflow may look like this:

Vacancy created → vacancy approved where required → applications received → initial review → screening → shortlist → interview → feedback and decision → offer or client progression → accepted, placed, not progressed or withdrawn → appropriate hiring or placement handover

Not every recruitment process needs every stage.

A high-volume operational role may use a structured preliminary screening process. A specialist senior position may involve several interviews, technical evaluation and management approval. An agency may have client-submission stages that an internal HR team does not need.

The system should allow these processes to differ without losing a consistent application history.

The vacancy should define what candidates are being considered for

A recruitment system becomes easier to manage when applications are connected to a clear vacancy or requisition record.

That record can contain the position, department or client, responsible recruiter, hiring manager, location, recruitment status, number of openings and other approved information required to manage the process.

Internal businesses may also need a vacancy approval process before recruitment begins.

Recruitment agencies may need the vacancy connected to the relevant client and contact instead.

A vacancy record may include:

  • Role or vacancy title
  • Department or client
  • Hiring manager or client contact
  • Responsible recruiter
  • Location
  • Number of openings
  • Approved requirements
  • Vacancy status
  • Opening and closing information
  • Recruitment workflow or stage model

What a recruitment and applicant management system can include

The system should contain the recruitment records and controls the organisation genuinely needs rather than trying to recreate every feature of a large enterprise ATS.

Vacancy records

Manage open positions, responsible recruiters, hiring managers or clients and the recruitment status around each vacancy.

Candidate profiles

Maintain appropriate candidate information and history without unnecessarily creating a duplicate profile for every application.

Applications

Connect each candidate to the specific vacancy and preserve the status and history of that application.

CV and document collection

Keep CVs and appropriate supporting documents connected to the candidate or application with controlled access.

Screening stages

Move applications through defined review stages while showing what has been completed and what requires attention next.

Interview workflow

Coordinate interview requirements, scheduling information, responsible interviewers and appropriate feedback records.

Recruiter and manager notes

Keep appropriate recruitment notes within the controlled application record rather than scattered across private inboxes and messages.

Candidate communication

Record or trigger appropriate acknowledgements, interview reminders and other recruitment communication where the workflow requires it.

Client submissions

For recruitment agencies, track which candidates were submitted to which client vacancy and the status of client feedback.

Offer workflow

Manage approved offer preparation, review and candidate response where the recruitment process includes this stage.

Hiring and placement records

Record the successful outcome and hand approved information into onboarding, placement administration or another downstream process.

Dashboards and reporting

Provide current vacancy and application visibility using information already captured through the recruitment workflow.

Application forms can collect the structured information recruiters actually need

A CV is useful, but it may not contain every piece of information required for the recruitment process.

Digital Data Capture can provide structured application forms with required fields, conditional questions and document uploads where appropriate.

The application can then enter the correct vacancy workflow without an administrator manually copying information from an email.

The form should collect only information that has a legitimate purpose in the recruitment process. More data is not automatically better recruitment data.

An application may capture:

  • Contact information
  • Relevant work information
  • Vacancy-specific questions
  • Availability where relevant
  • CV
  • Appropriate supporting documents
  • Declarations required by the process

The exact fields should be justified by the vacancy and the organisation’s lawful recruitment process.

Screening stages should organise decisions, not hide how decisions were made

A recruitment workflow can structure preliminary review, screening, shortlisting and interview stages.

Defined questions and clear stage requirements can help recruiters apply the process consistently.

The system should still preserve appropriate human judgement where candidate suitability depends on context, experience and information that cannot be reduced safely to a simple rule.

Example candidate progression

Application received → initial review → screening → shortlisted → interview required → interview complete → feedback reviewed → progressed to offer or client stage, not progressed or withdrawn

Different vacancy types can use different stage models while maintaining a clear history of how each application moved.

Interview coordination should remain connected to the application

Interview scheduling often creates another trail of emails and calendar messages outside the applicant record.

A recruitment system can keep the interview stage, candidate, vacancy, interviewer, scheduled date and relevant feedback connected.

Depending on the workflow, candidates may be sent interview details or offered suitable scheduling options.

Interviewers can then record approved feedback in the application rather than sending separate notes to the recruiter.

Example interview workflow

Candidate selected for interview → interview required → date or available slot agreed → candidate and interviewers notified → interview completed → feedback requested → feedback recorded → recruiter or hiring manager reviews next step

The system can coordinate the administration without making the interview decision itself.

Recruiter notes and interview feedback need appropriate access controls

Candidate records can contain information that should not be visible to every user participating in recruitment.

A hiring manager may need application and interview information for their vacancies. A recruiter may need broader candidate and workflow access. An interviewer may only need access to the candidate information required for a particular interview.

Internal notes should therefore be treated as controlled recruitment records rather than informal comments available to every user.

Access questions worth defining

  • Who may see the full CV?
  • Who may see screening notes?
  • Which interviewers may access the application?
  • Who may record a progression decision?
  • Who may view proposed offer information?
  • Which agency users may access client information?
  • What remains restricted after the vacancy closes?

Recruitment agencies need a candidate-to-client workflow as well

An internal employer usually progresses applicants toward its own employment process.

A recruitment agency also has to manage the relationship between the vacancy, candidate and client.

The system can therefore keep candidate progression separate from the act of submitting that candidate to a client.

Example agency workflow

Client vacancy received → candidate identified or applies → recruiter screens → candidate approved for submission → appropriate candidate information sent to client → client feedback recorded → interview arranged → outcome recorded → placement or further recruitment activity

Explore Automation & Business Systems for Recruitment Agencies for the wider agency operating environment.

Client submissions need controlled candidate information

A recruitment agency may need to share candidate information with a client as part of a defined recruitment service.

The system can track which candidate was submitted, to which vacancy, when the submission happened and what feedback followed.

It should not automatically expose the agency’s complete candidate database to a client.

The organisation should define what information is appropriate to share, the purpose and lawful basis for processing it, and which internal or client users may access it.

A client-submission record may include:

  • Candidate
  • Client vacancy
  • Date submitted
  • Responsible recruiter
  • Approved candidate documents
  • Submission status
  • Client feedback
  • Interview requirement
  • Final outcome

CRM and applicant management solve different relationship problems

Recruitment agencies often manage two connected relationships: candidates and clients.

The Recruitment & Applicant Management System can focus on vacancies, applications, candidate progression and placements.

A Custom CRM System can manage the broader client relationship, including contacts, opportunities, sales activity and follow-up.

The two can share appropriate organisation and vacancy context without forcing client sales activity into the candidate pipeline.

Useful separation

Recruitment system
Vacancies, candidates, applications, interviews, submissions and placements.

CRM
Client organisations, contacts, opportunities, sales follow-up and commercial relationship history.

This is particularly useful where recruiters and business-development teams participate in different parts of the agency workflow.

Successful recruitment should hand off into onboarding without turning the applicant record into the employee record

Once a candidate is hired, the recruitment process has largely completed its purpose.

Approved information can move into the employee onboarding process without requiring HR to capture everything again.

The employee system can then become responsible for employment records and ongoing HR administration.

Example hiring handover

Candidate selected → offer prepared and approved → candidate accepts → recruitment outcome recorded → approved information handed to HR → employee record created → onboarding begins

Explore Employee Management Systems for the post-hire workflow.

Candidate documents need more than a recruitment folder

CVs, application forms and other appropriate supporting documents should remain connected to the candidate and relevant recruitment process.

Users should be able to identify what the document is, which candidate it belongs to and who is authorised to access it.

If document management extends well beyond recruitment, a dedicated Document & Records Management System may be more appropriate for the wider organisation.

The recruitment system can reference the required documents without becoming the master repository for every HR and corporate record.

Candidate document context may include:

  • Candidate
  • Application
  • Document type
  • Date received
  • Status where review is required
  • Relevant vacancy
  • Access permissions
  • Replacement or updated record where appropriate

Candidate communication can be automated around clear workflow events

Recruitment contains predictable administrative communication that does not always require somebody to write a new email manually.

Workflow Automation can trigger appropriate acknowledgements, reminders and internal notifications when a defined event occurs.

More sensitive communication, including feedback around complex hiring decisions, may still need a recruiter or hiring manager to handle it directly.

The objective is not to remove people from candidate communication. It is to reduce avoidable administrative gaps around it.

Workflow communication may include:

  • Application acknowledgement
  • Missing-information request
  • Interview invitation
  • Interview reminder
  • Internal feedback reminder
  • Recruiter follow-up task
  • Offer-related notification
  • Approved status communication

AI is not required to build a useful applicant tracking system

Most recruitment administration is structured workflow.

Vacancy records, applications, stage changes, interview scheduling, reminders and dashboards can be managed with ordinary software and automation.

AI may be worth examining for specific tasks involving unstructured information, but it should not be added simply because the system contains CVs.

Human oversight matters in candidate decisions

Automated tools should not casually become the sole decision-maker for material candidate outcomes.

South Africa’s POPIA contains specific provisions concerning certain decisions based solely on automated processing of personal information.

Any use of automated ranking, profiling or rejection logic that may materially affect candidates should therefore receive careful privacy, legal, fairness and governance review before deployment.

How Repautomate’s service capabilities can fit inside the system

Digital Data Capture

Digital Data Capture can support vacancy requests, application forms, structured screening questions, interview forms and supporting-document collection.

Workflow Automation

Workflow Automation can create tasks, request feedback, issue reminders, route approvals and manage defined stage actions.

Live Dashboards

Live Dashboards can show authorised users open vacancies, applications by stage, interviews, outstanding actions and other relevant recruitment information.

Automated Reporting

Automated Reporting can create recurring internal, management or client reports from suitable recruitment records.

Dashboards should show where recruitment is waiting

The most useful recruitment dashboard is often the one that makes stalled work visible.

A recruiter may need applications awaiting review and interviews requiring follow-up. A hiring manager may need candidates awaiting feedback. An agency manager may need vacancies with no recent candidate activity or client submissions awaiting responses.

Different roles can use different views of the same recruitment records.

The purpose is to support the workflow, not to reduce hiring quality to a collection of activity counts.

Useful views may include:

  • Open vacancies
  • New applications awaiting review
  • Applications by stage
  • Interviews to schedule
  • Interviews awaiting feedback
  • Candidates awaiting follow-up
  • Offers in progress
  • Agency submissions awaiting client feedback
  • Placements or hires by period
  • Withdrawn or closed applications

Recruitment reporting should use the application history

If vacancy stages, application dates, interviews and outcomes already exist as structured records, they can support recurring reporting without maintaining another recruitment spreadsheet.

Reports can be designed around questions the organisation genuinely needs to answer.

For an internal HR team, that may be current vacancies and recruitment progress. For an agency, it may include client vacancies, candidate submissions, interviews and placement activity.

Reporting should be interpreted carefully. Recruitment quality cannot be determined from one speed or volume metric alone.

Reports may include:

  • Open and closed vacancies
  • Applications by vacancy
  • Applications by stage
  • Interview activity
  • Outstanding recruiter actions
  • Candidate outcomes
  • Client submissions
  • Placement or hiring records
  • Recruitment activity over time

Applicant information should not be kept forever just because storage is available

Recruitment systems contain personal information that was collected for a particular purpose.

South Africa’s POPIA includes requirements around purpose, retention and the eventual deletion, destruction or de-identification of personal information when the responsible party is no longer authorised to retain it.

The organisation should therefore define candidate-retention rules based on its lawful purposes, applicable obligations and recruitment model rather than applying an arbitrary retention period to every candidate record.

Retention design may need to answer:

  • Why is the candidate record being retained?
  • Is the application still active?
  • Does another lawful retention reason apply?
  • Is the person being considered for future vacancies?
  • How is that future purpose communicated and governed?
  • When should the record be deleted or de-identified?
  • What must remain for legitimate proof or legal purposes?

A custom system can support the retention workflow. It should not invent the organisation’s legal retention policy.

Applicant privacy needs deliberate system design

Applications may contain names, contact information, employment history, identification information and other personal records.

Some recruitment processes may also involve categories of information that receive additional protection under POPIA, such as certain health, biometric, criminal-behaviour or other special personal information.

That information should not be collected merely because a recruitment form makes it technically possible.

The system can support role-based permissions, controlled document access and appropriate security safeguards, while the organisation remains responsible for the lawful purpose and handling of the information.

System design may need to consider:

  • Candidate privacy notices
  • Purpose-specific data collection
  • Role-based access
  • Restricted interview notes
  • Document permissions
  • Special personal information where applicable
  • Retention and deletion workflows
  • Appropriate information-security safeguards
  • Controlled client access for agencies

Roles and permissions should follow the recruitment responsibility

A mature recruitment workflow usually involves several different roles.

Recruiters may manage the full candidate pipeline. Hiring managers may only need vacancies and candidates relevant to their team. Interviewers may need tightly scoped access to selected candidate information. HR may need the successful-candidate handover.

Recruitment agencies may additionally need account managers or client-facing recruiters with access to appropriate vacancy and submission information.

Possible roles

Recruiter
Manage assigned vacancies, applications, candidate progression and communication.

Hiring manager
Review relevant vacancies and candidates and record authorised hiring decisions.

Interviewer
Access the information and feedback functions required for assigned interviews.

Recruitment manager
Monitor broader recruitment workflow and reporting.

HR user
Receive successful candidates into the post-hire process where appropriate.

Administrator
Manage approved system configuration and access.

When an established applicant tracking system is probably the better answer

Applicant tracking and recruitment software are mature product categories.

Established products can provide career sites, job posting, candidate pipelines, interview scheduling, offer management, recruitment marketing, agency functionality and integrations with large HR platforms.

If those standard capabilities fit the organisation, buying and configuring a mature ATS may be more appropriate than developing them again.

Existing software may make sense when:

  • The hiring process follows common ATS patterns
  • A public careers site is a major requirement
  • Job-board distribution is central to the process
  • High-volume candidate sourcing features are required
  • Standard HR-suite integrations already fit
  • Advanced enterprise recruiting functionality is important
  • The organisation can reasonably adapt its workflow

When a custom recruitment and applicant system becomes worth considering

Custom development becomes more relevant when the recruitment workflow is closely tied to business-specific records, client processes or handovers that standard applicant tracking systems cannot support cleanly.

A recruitment agency may need candidate submissions, client-specific workflows and CRM connections. An internal business may need a focused hiring process that connects directly with custom HR or operational systems.

In those cases, applicant management can form one module inside a wider Custom Business System.

Custom may deserve investigation when:

  • Candidate and vacancy information is fragmented across several tools
  • Agency client-submission workflows are unusually specific
  • Recruitment needs deep links to custom CRM or employee systems
  • Current ATS software requires persistent spreadsheet workarounds
  • Roles, documents or approval processes do not fit available products
  • The recruitment module forms part of a wider internal business platform
Use the Software Decision Calculator

Related systems that can work with recruitment and applicant management

The recruitment system can remain focused on candidates and vacancies while related systems manage client relationships, employee records, documents and external access.

Custom CRM Systems

Manage client organisations, contacts, opportunities and commercial relationships separately from the candidate-selection pipeline.

Employee Management Systems

Receive appropriate successful-candidate information and manage employee onboarding and ongoing HR records after recruitment ends.

Document & Records Management Systems

Provide broader document ownership, permissions, metadata, retrieval and review controls where recruitment documents form part of a wider records environment.

Customer Portals

For recruitment agencies, give approved clients controlled access to selected vacancies, candidate submissions, feedback requests or reports where that model is appropriate.

Explore the wider Custom Business Systems We Build library for other system types.

Recruitment systems connect HR and Sales in different ways

For an internal employer, HR Automation covers the wider employee lifecycle, with recruitment feeding successful candidates into onboarding.

For a recruitment agency, Sales Automation may also be relevant because client vacancies, account management and new-business opportunities sit alongside candidate delivery.

The recruitment system itself should remain focused on vacancies, applications, candidate progression and hiring or placement outcomes.

System versus department

Recruitment & Applicant Management System
Vacancies, applications, candidate stages, interviews, submissions and outcomes.

HR Automation
The wider workflow around hiring, onboarding and ongoing employee administration.

Sales Automation
The client acquisition and commercial workflow relevant to recruitment agencies and other service businesses.

Recruitment agencies have a different operating environment from an internal HR department

An agency may manage many clients, vacancies and candidate submissions at the same time. The same candidate may be relevant to several suitable client opportunities, while each submission needs its own history and client feedback.

That requires a different data model from an employer filling only its own positions.

The recruitment system should therefore be designed around the organisation using it rather than assuming one universal applicant-tracking process.

Explore the dedicated Recruitment Agencies Solutions page for candidate delivery, client relationships, vacancy workflows, placements and agency reporting in the wider recruitment-business context.

How we approach a recruitment and applicant management project

The recruitment stages, records and decision responsibilities should be understood before application screens and pipeline columns are designed.

1. Define how vacancies start

We identify who creates vacancies, whether approval is required and which information recruiters need before sourcing or receiving applications.

2. Define candidate and application records

We separate the reusable candidate profile from the vacancy-specific application history and determine which information genuinely needs to be collected.

3. Map screening and interview stages

We define how applications progress, who makes decisions, what feedback is required and which stages may differ by vacancy type.

4. Map communication and exceptions

We identify reminders, candidate communication, withdrawals, missing information and stalled applications that need a defined response.

5. Define the successful-outcome handover

We map employee onboarding for internal recruitment or client submission and placement records for agency recruitment.

6. Review privacy, integrations and reporting

We assess candidate-data handling, existing HR or CRM systems, user permissions and the operational reporting required from the recruitment history.

Has the recruitment spreadsheet become the applicant tracking system?

A spreadsheet can work well for a straightforward vacancy tracker.

It becomes harder to use as the working recruitment system when several people need candidate documents, application history, interviews, permissions, reminders, communication, client submissions and vacancy-specific reporting at the same time.

Explore the Automation Resource Hub for practical guidance on choosing the right level of software and automation.

Not sure whether to buy, integrate or build?

Compare established applicant tracking systems with custom development based on recruitment workflow, candidate volume, integrations, privacy, client requirements, ownership and maintenance.

Use the Software Decision Calculator

Recruitment & Applicant Management Systems FAQs

An applicant tracking system is software used to manage vacancies, candidates and job applications through a recruitment process. It can include application capture, screening stages, interviews, communication, offers, hiring outcomes and reporting.

The candidate record represents the person. An application represents that candidate’s participation in a specific vacancy. One candidate can therefore have several separate applications over time without requiring several duplicate candidate profiles.

Yes. Digital Data Capture can provide structured application forms and document uploads where appropriate. The exact candidate-facing experience depends on the recruitment process and project requirements.

Yes. Appropriate candidate documents can be connected to the candidate or specific application and protected by role-based access. The organisation should collect and retain only information justified by its lawful recruitment process.

Yes. A custom system can support different recruitment processes according to vacancy type where required. One vacancy may need a short review and interview process while another requires several screening, interview and approval stages.

Yes. The system can manage interview status, dates, interviewers, candidate communication and appropriate feedback records. Exact calendar or meeting-platform integrations depend on the systems and technical access involved.

Yes. Hiring managers or interviewers can be given appropriate access to submit structured feedback for candidates assigned to them. Permissions should limit access to the recruitment records they genuinely need.

Yes. A submission record can connect a candidate to a client vacancy, record when information was submitted, track client feedback and show whether the candidate progressed to interview or placement.

Potentially. Once a candidate accepts an offer and the recruitment process is complete, appropriate approved information can be handed into an Employee Management System so onboarding can begin without unnecessary recapture.

Yes. Application acknowledgements, interview reminders, internal feedback reminders and other predictable communication can potentially be automated around defined workflow events. Sensitive or complex candidate communication may still be better handled personally by a recruiter or manager.

Technically, automated candidate analysis is possible in some recruitment environments, but it should not be treated as the default solution. POPIA contains specific rules concerning certain decisions based solely on automated processing of personal information. Any automated ranking, profiling or rejection that could materially affect candidates requires careful legal, privacy, fairness and human-oversight review before implementation.

There is not one universal retention period that should be applied blindly to every recruitment record. POPIA requires personal information not to be retained longer than necessary for the purpose for which it was collected unless another lawful retention basis applies. The organisation should establish and implement an appropriate candidate-data retention policy.

No. The system can support purpose-specific data collection, role-based access, retention workflows and security safeguards, but POPIA compliance depends on the organisation’s complete processing activities, lawful purposes, notices, governance, retention and security measures.

Potentially. Recruitment information can be exchanged with CRM, HR or other systems where suitable technical access exists. Integration depends on APIs or other access methods, licensing, authentication, security requirements and the information that needs to move between platforms.

Not necessarily. Established applicant tracking and recruiting products are often the better choice for standard recruitment processes. Custom development becomes worth considering when candidate, client, vacancy or hiring workflows require deep business-specific connections that available products cannot support adequately.

Potentially, yes. The workflows are different and should be designed accordingly. Internal recruitment generally hands successful candidates into employee onboarding, while an agency may require client vacancies, candidate submissions, client feedback, placement records and CRM connections.

Show us how a candidate moves from application to a hiring or placement decision

You do not need to arrive with an applicant-tracking feature list.

Show us how vacancies are opened, where applications arrive, how screening happens, who schedules interviews, where feedback is recorded, what candidates are repeatedly chased for and what needs to happen after somebody is selected.

We can assess whether an established ATS, better data capture, workflow automation, integration or a custom recruitment and applicant management system is the more sensible approach.