Clinical Research Project Manager
University of Utah · Salt Lake City, UT · 4 wk ago
$47k–$63k/yrFull-time
We need to output HTML fragment with headings
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive information. Let's parse the posting. Job Summary: description of role. Department Summary: description of department. Benefits Summary: list of benefits. Employee Health Requirements: vaccination requirement. Responsibilities: long list. Then there is "The following job levels and associated pay rates will be considered..." includes pay ranges for levels I and II. Then Minimum Qualifications: equivalency statement and levels. Preferences: list of preferences. Special Instructions: includes Requisition Number (should be dropped), Full Time or Part Time? Full Time, Work Schedule Summary, Work Locations, Department, Location, Campus, Pay Rate Range, Close Date, Open Until Filled, application instructions (to apply...), copyright etc. We need to drop application instructions, copyright, etc. We need to include Pay and Schedule sections only if posting actually states them. Pay: we have expected pay ranges for levels and overall Pay Rate Range: $46,584 - $76,593. So we can include Pay section with that range. Schedule: Work Schedule Summary: Full time, 40 hours per week, Monday – Friday swing shift (3pm-11pm). Occasional weekends via shared on-call responsibilities. Opportunities for hybrid telework... So we can include Schedule section with that. Benefits: we have Benefits Summary list. Qualifications: we have Minimum Qualifications and Preferences. Could combine into Qualifications section? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. We have Responsibilities (clear). We have Requirements? The posting includes Minimum Qualifications (education/experience) and Preferences (preferred qualifications). Could treat Minimum Qualifications as Requirements, Preferences as Qualifications or Skills? But we have separate headings for Requirements, Qualifications, Skills. We need to map content appropriately. We could put: - About the role: Job Summary + Department Summary maybe. - Responsibilities: the long list. - Requirements: Minimum Qualifications (education/experience) maybe. - Qualifications: Preferences list. - Skills: maybe not explicitly listed; but we could extract skills from preferences: knowledge of GCP, FDA, HIPAA, IRB, experience with multi-site collaborations, understanding of research procedures, knowledge of emergency medicine, working knowledge of computers/research software/large database management, ability to communicate, ability to function independently. Could put those under Skills. - Benefits: Benefits Summary. - Pay: Pay Rate Range. - Schedule: Work Schedule Summary. We must not create sections with filler text. Ensure each section has substantive content. We must not include boilerplate like EEO, etc. We must not include application instructions, copyright, etc. We must not include Requisition Number. We must not include Close Date etc? Those are metadata; could be omitted as per instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we could drop Close Date, Open Until Filled, etc. Or we could include them in a short paragraph under About the role? Probably better to drop them as minor metadata. We need to preserve ALL substantive information; but we can drop minor metadata like requisition number, close date, etc. The instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can drop them. Thus we will produce HTML with sections:
About the role
Job Summary + Department Summary combined.
Responsibilities
- ... each responsibility as list items.