This repository was archived by the owner on Mar 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
Top Skill Selection & Matching #400
Labels
Milestone
Comments
cagdas001
added a commit
to cagdas001/taas-app
that referenced
this issue
Jul 27, 2021
cagdas001
added a commit
to cagdas001/taas-app
that referenced
this issue
Jul 27, 2021
cagdas001
added a commit
to cagdas001/taas-apis
that referenced
this issue
Jul 27, 2021
* Accept `hoursPerWeek` for jobs, when creating a team. * Fix `getSkillIdsByNames` to return ids in the exact same order of names. * Include skill ids in `getSkillsByJobDescription` response Addresses topcoder-archive/topcoder-platform-taas-app#400, topcoder-archive/topcoder-platform-taas-app#407
Sorry I made a couple typos in the copy on the page. Need to update a title and remove the word "the" from both modals. Correct copy below "Input Job Description" flow labels: "Input Skills" flow labels: |
cagdas001
added a commit
to cagdas001/taas-app
that referenced
this issue
Aug 11, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to increase chances of getting viable matches, we need to make some changes on the "Skills Identified" screen that appears on the "Input Job Description" workflow.
This will also need to happen with minor label changes when the user clicks "Continue" on the "Input Skills" workflow.
This feature will require the user to select up to n skills as the most important skills:

n should be able to be defined at the app level. Start with n=3.
"Input Job Description" flow labels:
Title: "Identified Skills"
Subtitle: "Topcoder has identified the following skills referenced in your job description. Select your the n skills most important to be successful in the job. These skills will be weighted more heavily in matching."
"Input Skills" flow labels:
Title: "Identified Skills"
Subtitle: "You have chosen the following skills in your request. Please select your the n skills most important to be successful in the job. These skills will be weighted more heavily in matching."
On each request be sure to save which skills the user has marked as most important for future reporting and analysis.
When performing the role match, only match the marked skills against the role, skills not marked by the user should not be evaluated in the match.
The text was updated successfully, but these errors were encountered: