nus-se-script
commented
5 days ago Team's Response
Thank you for raising this issue.
Talentcy is designed as a general-purpose tool for managing job applicant contacts and tracking interview stages, regardless of the type of job. The lack of specificity in the introduction is intentional, allowing flexibility for HR teams across industries to adapt the app to their workflows. Adding specificity (e.g., limiting it to tech/IT job applicants) would unnecessarily restrict its perceived scope and applicability.
Also, in our planned enhancement, we aimed to allow the addition of additional tags, empowering users to tailor the app to their unique needs. For HR applicants who don’t undergo technical interviews, users can simply ignore or redefine these tags. The current design ensures inclusivity for a broader audience rather than confining the app to a specific niche.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
In the DG, it is stated that the target user profile is "employees of a company's talent recruitment departments who need to manage contacts of job applicants". As such it does not specify which type of job applicants (i.e. tech job applicants, etc). Hence, having tags that indicate that a Technical Interview is in progress for example might to be relevant to a user who's only job is to manage HR job applicants for example since there is a very high likelihood that there is no technical interview for HR job applicants.
As such, changing the target user profile to "employees of a company's talent recruitment departments who need to manage contacts of tech/IT job applicants" might be a better suited.