Well, this looks like fun! Here's an altered version of your database.
I suggest adding dedicated JobRequirement and Projects_People (aka Candidates) tables, which gives you more flexibility (e.g. summing up all scores of a candidate for a job). Take the ProjectID_fk out of persons. What if a person applies for several jobs?
Assign/remove People and JobReqs to/from Projects, while making sure that each Project_People combination has CandidateScore records corresponding to the JobReqs you have set up for the project. (Check my script for comments on that). This is a script-intensive method, because you need to do a lot of housecleaning when adding/removing JobReqs and Candidates, but allows for very clean and nice interfaces
You can apply this generic method of display/selection/filter, as (partially) shown on the Projects layout, to all entities - Projects, JobReqs and People.
Job Candidates_eos.fmp12.zip 77.9 K
Wow. Thanks. It's going to take me a bit to digest it!
Back to you as soon as I do.