GC Digital Talent is the new recruitment platform for digital and tech jobs in the Government of Canada. // Talents numériques du GC est la nouvelle plateforme de recrutement pour les emplois numériques et technologiques au gouvernement du Canada.
Recruitment team reporting that pools where they had processed absolutely everyone (as in, all applicants had been screened out, removed, or placed,_ somehow have new people marked as "screened in" a year later.
How might this have happened?
🕵️ Details
This has been reported by David and Sophie. Normally David reviews new applications to a pool (candidates with NEW APPLICATION status) and screens them in or out. Sophie then looks at the candidate table for a pool, filters by SCREENED_IN status, and continues with other assessments until all candidates are QUALIFIED or DISQUALIFIED.
We have as examples of the problem, three IT-ongoing pools from last year. You can find these pools by filtering by
IT-02/IT-03/IT-04
Project Portfolio Management stream
IT Jobs (ongoing) publishing group
D and S report that as of the end of last summer, there were no candidates in these pools who were still NEW APPLICATION status or SCREENED_IN status. Then at some point in Oct 2024, they looked at these pools and noticed there were some candidates with a SCREENED_IN status in these pools. Also, they don't remember screening-in these names at all.
📋 Steps to Reproduce
Filter pools in production by
IT-02/IT-03/IT-04
Project Portfolio Management stream
IT Jobs (ongoing) publishing group
Filter candidates by SCREENED_IN status
See that there are candidates left
📸 Screenshot
🙋♀️ Proposed Solution
We want to understand why these candidates are here. Did they gain the SCREENED_IN status in an unexpected way? Were they hidden from the table for some amount of time?
Some ideas:
check the database for submitted_at and updated_at timestamps. Were they last updated in an expected or unexpected time window?
Check the activity-log for these candidates. Does it show when they become screened in, or anything unexpected?
Is there anything in common between these candidates or their user profiles? Its possible there was a bug in the table at some point that caused them not to appear, or to be filtered out unintentially
Is it possible they had a REMOVED status at some point (candidates suspending themselves?) which was later reverted?
Question
Recruitment team reporting that pools where they had processed absolutely everyone (as in, all applicants had been screened out, removed, or placed,_ somehow have new people marked as "screened in" a year later.
How might this have happened?
🕵️ Details
This has been reported by David and Sophie. Normally David reviews new applications to a pool (candidates with NEW APPLICATION status) and screens them in or out. Sophie then looks at the candidate table for a pool, filters by SCREENED_IN status, and continues with other assessments until all candidates are QUALIFIED or DISQUALIFIED.
We have as examples of the problem, three IT-ongoing pools from last year. You can find these pools by filtering by
D and S report that as of the end of last summer, there were no candidates in these pools who were still NEW APPLICATION status or SCREENED_IN status. Then at some point in Oct 2024, they looked at these pools and noticed there were some candidates with a SCREENED_IN status in these pools. Also, they don't remember screening-in these names at all.
📋 Steps to Reproduce
📸 Screenshot
🙋♀️ Proposed Solution
We want to understand why these candidates are here. Did they gain the SCREENED_IN status in an unexpected way? Were they hidden from the table for some amount of time?
Some ideas: