Add Gender, Date of Birth, and Customizable Display Settings

[ntuan2502]

Problem statement

As a recruiter, I struggle with managing candidates for roles that have specific demographic requirements. Currently, the system lacks fields for Gender and Date of Birth (DOB), which are essential for jobs that have legal age limits or specific gender requirements.

Furthermore, the current fixed format for names (First Name + Last Name) and dates (MM/DD/YYYY) is inflexible for international teams. In many regions (such as Vietnam or East Asian countries), the naming convention is Last Name + First Name. The fixed date format also leads to confusion and potential data entry errors depending on the user's locale.

Proposed solution

I propose adding the following fields and settings to Reqcore:

1. New Candidate Fields:

   • Gender: A dropdown or selection field (Male, Female, Other/Prefer not to say).
   • Date of Birth (DOB): A date picker field.
   • Display Name (Optional): A text field allowing recruiters to set a specific name format for the candidate, overriding the default concatenation.

2. Global/Workspace Settings for Localization:

   • Name Display Format: An option in settings to toggle between First Name + Last Name and Last Name + First Name.
   • Date Format Configuration: A dropdown in settings to choose the preferred date display format (e.g., DD/MM/YYYY, MM/DD/YYYY, or YYYY-MM-DD).

Alternatives considered

• Manual Notes: Currently, we have to type gender and age into the "Notes" or "Description" section, but this makes it impossible to filter or sort candidates based on these criteria.
• External Spreadsheets: Maintaining a separate sheet to track local naming conventions and age requirements, which defeats the purpose of using an integrated ATS like Reqcore.

Scope and impact

• Who benefits: Hiring teams operating in diverse geographical locations and recruiters handling roles with specific age/gender eligibility criteria.
• Success measures:
  • Recruiters can filter candidates by age range or gender.
  • Users can view candidate names and dates in a format that aligns with their local standards, reducing cognitive load and errors.
  • Reduction in manual workarounds for tracking demographic data.

Checklist

• I searched existing issues and did not find a duplicate.
• This request aligns with Reqcore's ownership/transparency/privacy direction.

[ntuan2502]

Following up on the fields mentioned above, I believe we should also implement filters for Gender and Date of Birth to allow recruiters to sort and screen candidates more efficiently.

Furthermore, there should be a dedicated Notes section within the candidate's detailed profile for internal remarks. On the main candidate list/table view, it would be highly beneficial to have a "quick view" for these notes—either by displaying them directly as a column in the table or by showing a preview when hovering over a candidate’s record. This would save time and provide immediate context during the initial screening process.

[JoachimLK]

Thank you for this incredibly well-articulated feature request. the practical examples and regional context made it very easy to understand the real-world impact

The following has been implemented in PR #157:

Gender field: Added as a dropdown (Male, Female, Non-binary, Prefer not to say) to both the candidate creation flow and the candidate detail page.

Date of Birth field: Added as a date picker to candidate creation and the detail page. Age is derived from DOB for display purposes.

Quick Notes: A dedicated quick notes field has been added to the candidate detail sidebar, supporting the internal remark workflow described in the follow-up comment. Notes are also surfaced as a column option in the candidates list.

Localization Settings: A new /dashboard/settings/localization page has been added with:

Name display format toggle: First + Last vs Last + First
Date format selector: DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD
These settings are stored at the organization level and applied consistently across the app.
Candidate filtering by gender and DOB/age range is on the roadmap as a follow-up.

Thank you again :)