search

clyveycui / pe

0 stars 0 forks source link

Find by expected salary is not very useful #8

Open clyveycui opened 2 years ago

clyveycui commented 2 years ago

Ideally, it should allow the user to provide a custom range and return every salary in that range. This is more common I believe among recruiters, rather than the arbitrary range of +- 500

nus-pe-bot commented 2 years ago

Team's Response

This is a design consideration to keep the input simple for the user to type in.

You should still be able to find expected salaries within a reasonable range using the current find by expected salary feature.

Take note that this is expected salary and not the exact salary of the applicant, hence we believe that we can sacrifice specificity for convenience of use for the user.

Additionally, the severity of medium is too high even if this bug is accepted. The purpose of searching for +-500 is that we want for example 3450 to match even if the applicants search for 3500, since it is close and does not make sense for it not to be matched. Thus, for the purpose of applicant needing to find applicants close to expected salary of 3500, the user will almost never need to adjust the range. If the user does want to adjust the range, it would be for another purpose that is probably not intended, and thus is a rare scenario.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Hi, thanks for the explanation of the design. I understand that it is done this way to make it more convenient for the user. However, I think even if implemented, it won't create too much of a hassle for the user, as it is just typing in at most one more parameter (can be done either using LOW, HIGH or MEDIUM, +-RANGE).

The arbitrary choice of +-500 is also an issue. Why was that range chosen, as opposed to let's say +-1000? One could argue that 7000 is close enough to 8000, so those with expected salary of 7k should also show up for 8k.

The range feels rather forced and may cause even more of a hassle for the user. Consider a case where a recruiter is told that an acceptable range of salaries would be 7000-9000. With the current implementation, what recruiter will have to do is to perform two searches at 7500 and 8500. If let's say the LOW-HIGH implementation is used, the recruiter will only have to perform 1 search, on the range 7000 - 9000. As such, I feel that in many situations, the current implementation will be even less convenient for the user.

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

Reason for disagreement: Searching with a expected salary range should be a rather common operation, which many users would encounter.