Lazy loading of elements for job applicants

[harshil15999]

1. We will be having a lot of job applications and job applicants. Loading all of them together will hinder performance.

Solution Approach :

1. Recruiter Side : We scroll down by 10 job listings the frontend makes a backend call to load the next 10 job ids.
2. Applicant Side : Similarly on the side of the recruiter they should see lazy loading of all the candidates

[devshahofficial]

This makes sense. @amandesai01 how do we prioritize this in v2?

[amandesai01]

We need a better spec for this. currently, applicants are not sent linearly. We have list of postings with applicant id, and then a map of applicant id to profile. This is to ensure that if applicant applies to multiple postings, the profile gets sent only once.

Also, the page works by allowing user to select mutiple postings from dropdown and see all the applicants at once. How do we paginate that? (product wise)? @devshahofficial please spec this (establish clear expectations)

[amandesai01]

But I agree with the issue and had this in mind, that at some point we need to do this.

[devshahofficial]

@harshil15999 I will create a detailed spec and link it to the project roadmap.

[amandesai01]

@devshahofficial let's post the spec here, and we can raise PR on this issue itself.

[harshil15999]

@harshil15999 I will create a detailed spec and link it to the project roadmap.

Lets do that on the weekend. @devshahofficial