Compensation Program Analyst, Physician and Faculty - Full Time

for section headings. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: current employees note, tip sheet, EEO, etc. Also remove duplicated lines. Let's extract substantive paragraphs: Intro paragraph: "The Physician & Faculty Compensation Program Analyst provides financial, technical and administrative support for physician, faculty and applicable advanced practice provider compensation programs. This role supports plan design, costing, implementation, incentive administration, productivity reconciliation, payment execution, program analysis and compensation-related system testing under the direction of the Director." Then list of duties (multiple sentences). We'll convert each sentence to

. List: - Calculates, validates, and reconciles incentive, productivity, and contractual payments across quarterly, annual, and scheduled compensation-payment cycles. - Applies approved targets, rates, thresholds, credits, caps, and calculation rules to ensure accurate payout execution. - Prepares and validates Workday EIB or comparable payment files while tracking payment calendars, approvals, exceptions, and submissions. - Translates approved plan concepts into calculation methodologies, administrative requirements, payout schedules, and operational formulas. - Documents assumptions, definitions, exclusions, calculation logic, and scenario models to support transparent plan administration. - Calculates and validates wRVU targets, clinical FTE levels, rates, credits, and ongoing productivity reconciliations. - Applies adjustments for leaves, productivity credits, FTE changes, start dates, and plan participation events to resolve calculation variances. - Develops financial cost projections and performs scenario, sensitivity, and year-over-year analyses under alternative performance assumptions. - Compares projected and actual financial results to identify material variances and prepare executive summaries for leadership review. - Analyzes incentive outcomes, payment patterns, productivity relationships, and cost drivers to uncover operational outliers and trends. - Supports post-payment and post-implementation program evaluations to recommend methodology refinements to senior directors. - Supports Workday system testing, calculation validation, and implementation activities for compensation modules. - Maintains program-specific models, calculation files, executive summaries, and committee reporting materials. - Executes ad hoc financial analyses, special projects, and process improvement initiatives to automate productivity calculations and program reporting. - Adheres to University and unit-level policies and procedures and safeguards University assets. - This list of duties and responsibilities is not intended to be all-inclusive and may be expanded to include other duties or responsibilities as necessary. Now Core Qualifications: Education: Bachelor’s degree in relevant field required Experience: Minimum 4 Years Of Relevant Experience Required Knowledge, Skills and Abilities: - Learning Agility: Ability to learn new procedures, technologies, and protocols, and adapt to changing priorities and work demands. - Teamwork: Ability to work collaboratively with others and contribute to a team environment. - Technical Proficiency: Skilled in using office software, technology, and relevant computer applications. - Communication: Strong and clear written and verbal communication skills for interacting with colleagues and stakeholders. Then there is a note: "This is a core job profile description and is not reflective of all duties that may be assigned to a specific position in each individual department. The above statements are intended to describe the general nature and primary responsibilities of this core job profile. Specific duties and tasks may vary based upon departmental needs. Other duties may be assigned to the above consistent with the knowledge, skills, and abilities required for the job." This is boilerplate; we should remove? It's generic but maybe considered boilerplate. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is generic description; might be considered boilerplate. I'd remove it. Then benefits paragraph: "The University of Miami offers competitive salaries and a comprehensive benefits package including medical, dental, tuition remission and more." Then description of UHealth etc: that's promotional; maybe not needed but it's substantive about employer. Could be considered boilerplate? It's about the organization; maybe keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those; it's about the employer. Might keep as part of About the role? But we already have About the role intro. Could add a paragraph about the organization under About the role or maybe a separate section? Not required. We could include it in About the role as additional prose. Then EEO statement: remove. Job Status: Full time Employee Type: Staff -> schedule. Now we need sections: - About the role: could combine intro paragraph and maybe the UHealth description? But we need to avoid filler. The UHealth description is substantive about employer; could be included. - Responsibilities: list of duties. - Requirements: maybe Education and Experience? Or we could have Qualifications for education/experience, Skills for KSA. The rules: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have content for: - About the role: intro + UHealth description. - Responsibilities: duty list. - Requirements: maybe Education and Experience? Could be under Requirements. - Qualifications: maybe same as Requirements? Might be redundant. Could treat Requirements as education/experience, Qualifications as knowledge/skills? But we also have Skills heading for KSA. Better: Use Requirements for education/experience, Qualifications for maybe "Core Qualifications" heading? But we already have "Core Qualifications" in text. Could map that to Qualifications section. Skills: Knowledge, Skills and Abilities list. Benefits: benefits paragraph. Pay: competitive salaries sentence. Schedule: Full time. We must not create sections with filler. All have content. Now we need to output HTML fragment only. Structure:

About the role

... intro ...

... UHealth description ...

Responsibilities

• ...
...

Requirements

Education: Bachelor’s degree in relevant field required

Experience: Minimum 4 Years Of Relevant Experience Required

Qualifications

This is a core job profile description... (maybe we removed). Actually we might not have Qualifications content besides the core job profile note which we considered boilerplate. Might be better to omit Qualifications section if no specific content. But we have "Core Qualifications" heading in original; but we already used that for education/experience? Actually original had "Core Qualifications Education: Bachelor’s degree ... Experience: Minimum 4 Years ... Knowledge, Skills and Abilities: ...". So we could treat that as Qualifications section containing education, experience, and KSA. But we also have Skills heading for KSA. To avoid duplication, we could put education/experience under Requirements, and KSA under Skills. Then Qualifications could be omitted or we could put something else? The instruction: Prefer a few substantive sections over many thin ones. So maybe combine education/experience and KSA under Qualifications, and not have separate Skills. But we have Skills heading defined; we could still use it for KSA. Let's follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus we need content for each. We have: - About the role: intro + UHealth description. - Responsibilities: duty list. - Requirements: maybe nothing specific besides generic? Could be "Minimum 4 Years Of Relevant Experience Required" and education. But those are qualifications. Hmm. We could treat Requirements as "Minimum 4 Years Of Relevant Experience Required" and education as part of Qualifications? But we need to decide. Let's map: Requirements: Education and Experience (the baseline). Qualifications: Knowledge, Skills and Abilities (the KSA). Skills: maybe we could leave empty? But we must not create heading with filler. So if we put KSA under Qualifications, we cannot also have Skills heading with nothing. So we could put KSA under Skills, and Qualifications could be something else like "Core Qualifications" maybe includes education/experience? But we already used education/experience for Requirements. Alternative: Use Requirements for education/experience, Qualifications for maybe "Core Qualifications" phrase (but that's just a heading). Not good. Better: Use Requirements for education/experience, Qualifications for the core job profile note (which we consider boilerplate). Might drop Qualifications. But we must follow instruction: include a section ONLY when the posting has real, specific content for it. So if we don't have specific content for Qualifications, we omit it. Similarly for Skills if we don't have specific content. We have specific content for KSA (Learning Agility, Teamwork, Technical Proficiency, Communication). That's under "Knowledge, Skills and Abilities". So we can put that under Skills heading. Thus: - Requirements: Education and Experience. - Skills: KSA list. - Qualifications: maybe we could put nothing; omit. - Benefits: benefits paragraph. - Pay: competitive salaries sentence. - Schedule: Full time. Now About the role: we have intro and UHealth description. Let's craft About the role paragraph(s): Intro: "The Physician & Faculty Compensation Program Analyst provides financial, technical and administrative support for physician, faculty and applicable advanced practice provider compensation programs. This role supports plan design, costing, implementation, incentive administration, productivity reconciliation, payment execution, program analysis and compensation-related system testing under the direction of the Director." UHealth description: "U