Post Award Administrator
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
The posting includes:
- Overview (first paragraph about Yale, then "Overview The Portfolio & Grant Analyst is responsible...") So we can have an Overview section.
- Responsibilities: There's a "Principal Responsibilities" list with numbered items (1-6). Also earlier "Under general direction, this role manages post-award financial operations..." etc. So we can combine responsibilities.
- Required Skills And Abilities: list.
- Preferred Skills And Abilities: list.
- Required Education and Experience: includes Bachelor's degree required, two years of related financial experience required, etc.
- Compensation: Salary Range $55,000.00 - $85,000.00. Also Compensation Grade Administration & Operations Compensation Grade Profile Supervisor; Senior Associate (P4). So we have Pay info. Should we include a Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range, so we can include a Pay section.
- Schedule: Time Type Full time, Duration Type Staff, Work Model Remote. So we have schedule info (full-time, remote). So we can include a Schedule section.
- Benefits: Not explicitly mentioned. There's no benefits listed. So we should not create a Benefits section.
- Qualifications: Could be covered by Required Education and Experience and Required Skills. But we can have a Qualifications section maybe combining education/experience and skills? However the rule says prefer a few substantive sections over many thin ones. We could have sections: Overview, Responsibilities, Required Skills, Preferred Skills, Education & Experience, Pay, Schedule. That's many sections but each substantive. Could we combine Required Skills and Preferred Skills into a Skills section? Possibly but they are distinct. The rule says use headings like Skills, Benefits, Pay, Schedule. So we could have a Skills section that includes both required and preferred? But then we lose distinction. However we could still include both under Skills with subheadings? Not allowed because only
for section headings. Could we have two Skills sections? That would be repetitive. Better to have Required Skills and Preferred Skills as separate sections? The allowed headings list includes Skills (generic). It didn't forbid using Required Skills and Preferred Skills as headings? The examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule." It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So those are examples, not an exhaustive list, but we should likely stick to those generic headings. However we could also use "Required Skills" and "Preferred Skills" as headings if they are more specific; but the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings, but not that we cannot use others. However to be safe, we could map content to those headings: Overview, Responsibilities, Requirements (maybe combine required skills and education), Qualifications (maybe preferred skills?), Skills, Pay, Schedule. But we need to preserve all substantive information; we cannot lose distinction between required and preferred. We could embed both under Skills with separate
or
labeling. Eg: Skills
Required: ...
Preferred: ...
. That would preserve info.
Similarly, we could have Overview, Responsibilities, Requirements (education/experience), Skills, Pay, Schedule.
Let's see if we need a Requirements section: Could include education and experience. The posting has "Required Education and Experience". So we can put that under Requirements.
Qualifications: Could be used for preferred skills? But we already have Skills covering both required and preferred. Maybe we can have Qualifications for preferred skills and experience? But we risk duplication.
Better to have: Overview, Responsibilities, Requirements (education/experience), Skills (required & preferred), Pay, Schedule.
Check if any other substantive content: There's also "Job Posting Date", "Job Category", "Bargaining Unit", "Compensation Grade", etc. Those are minor metadata; we can fold into a short or drop. The instruction says: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a brief paragraph at top or bottom with metadata like posting date, job category, etc. But we should not create a heading for them. Could just include a
with that info.
We must remove boilerplate: EEO, background check, health requirements, posting disclaimer, note about tobacco-free campus, etc. Those are legal/EEO boilerplate; remove.
Also remove duplicated lines.
Now craft HTML.
Structure:
Overview
Working at Yale means contributing to a better tomorrow. Whether you are a current resident of our New Haven-based community, eligible for opportunities through the New Haven Hiring Initiative, or a newcomer, interested in exploring all that Yale has to offer, your talents and contributions are welcome. Discover your opportunities at Yale! The Portfolio & Grant Analyst is responsible for the financial management, proposal development, and stewardship of a portfolio of grants and contracts for sponsored research. Under general direction, this role manages post-award financial operations, including financial reporting, budgeting, forecasting, and compliance with university and sponsor policies. The Analyst collaborates with Principal Investigators (PIs) and other stakeholders to ensure accurate financial information, resolve budgetary issues, prepare financial statements, and provide long-term planning for research funding. This role includes involvement in managing budgets, preparing expenditure projections, overseeing grant renewals and closeouts, and maintaining up-to-date knowledge of policies and procedures.
Responsibilities
- Financial Analysis and Reporting: Present financial information and recommendations through data analysis and reporting in the development and maintenance of budgets; identify funding issues and develop appropriate solutions; review and approve reports for administrative actions including pre-award costs and no-cost extensions; analyze data and develop complex analytical reports for principal investigators including trend analysis, forecast future financial scenarios, develop long range projections, and variance analyses.
- Proposal Development: Develop proposals and budgets for grant and contract submissions; coordinate with partnering institutions; ensure compliance with sponsor regulations and University policies and procedures; advise principal investigators of new funding opportunities and requirements.
- Portfolio Management: Plan, organize and prioritize actions across multiple awards and investigators' portfolios; ensure appropriate charging of expenses and integration of data; advise and counsel principal investigators on financial issues and recommend alternative spending strategies; manage renewals, extensions and closeouts of grants, including final financial reporting to the sponsor; analyze and negotiate budgets, contracts, and terms and conditions of research proposals.
- Compliance and Risk Management: Provide appropriate guidance on compliance matters during management of portfolio and collaborate with account holders to maintain such compliance; review, interpret and effectively apply sponsor policies on a variety of topics including cost allowability, budget management and other award management activities to ensure compliance with sponsoring agency requirements and University policies and procedures.
- Collaborative Finance Partner & Lead: Provide a high-level of service that maintains strong working relationships by interacting with faculty and internal and external contacts, such as the School of Medicine, Office of Research Administration and granting agencies by managing the internal pre award proposal process and the management of sponsored funding.
- May perform other duties as assigned.
Requirements
Bachelor's degree required. Two years of related financial experience required. Demonstrated application of financial, accounting and economic concepts.
Skills
Required Skills and Abilities:
- Strong financial and analytical skills with demonstrated application of financial and accounting concepts.
- Proficiency in Microsoft Excel and other office software, with the ability to manage multiple data sources effectively.
- Excellent written and verbal communication skills, with the ability to present financial information clearly and accurately.
- Strong organizational skills with high attention to detail and the ability to prioritize tasks and meet deadlines.
- Ability to work both independently and collaboratively, demonstrating a positive attitude and strong customer service skills.
Preferred Skills and Abilities:
- Prior experience with grants and contract administration, including pre-award to post-award processes.
- Knowledge of university policies and procedures, particularly within an academic or medical research setting.
- Proficiency in using financial systems such as Workday and Yale Budget Tool (YBT) for financial management and reporting.
- Experience in managing international sponsored awards, including familiarity with relevant regulations and compliance requirements.
- Bachelor's degree in accounting, business management, or a related field, with several years of relevant financial experience.
Pay
Salary Range: $55,000.00 - $85,000.00
Schedule
Time Type: Full time; Duration Type: Staff; Work Model: Remote.
We might also include a brief metadata paragraph after Overview maybe: Job Posting Date: 09/17/2026; Job Category: Professional; Bargaining Unit: NON; Compensation Grade: Administration & Operations; Supervisor; Senior Associate (P4).
But we need to avoid creating a heading for it. Could place after Overview as a . However the instruction says "fold minor metadata into a short
or drop it." So we can include a short p after Overview.
Let's add after Overview:
Job Posting Date: 09/17/2026; Job Category: Professional; Bargaining Unit: NON; Compensation Grade: Administration & Operations; Supervisor; Senior Associate (P4).
Make sure not to duplicate info already in Pay section (we have salary range there). That's fine.
Now check for any leftover boilerplate: We removed background check, health requirements, posting disclaimer, EEO, note about tobacco-free campus, etc.
Check for duplicated lines: We have not repeated.
Check that we didn't invent or summarize away detail: We preserved all substantive info: overview, responsibilities (six items), requirements (education/experience), required skills, preferred skills, pay, schedule. Also we included metadata.
Check that we didn't create sections with filler: All sections have real content.
Check that we didn't include Benefits section (none).
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. The posting includes: - Overview (first paragraph about Yale, then "Overview The Portfolio & Grant Analyst is responsible...") So we can have an Overview section. - Responsibilities: There's a "Principal Responsibilities" list with numbered items (1-6). Also earlier "Under general direction, this role manages post-award financial operations..." etc. So we can combine responsibilities. - Required Skills And Abilities: list. - Preferred Skills And Abilities: list. - Required Education and Experience: includes Bachelor's degree required, two years of related financial experience required, etc. - Compensation: Salary Range $55,000.00 - $85,000.00. Also Compensation Grade Administration & Operations Compensation Grade Profile Supervisor; Senior Associate (P4). So we have Pay info. Should we include a Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range, so we can include a Pay section. - Schedule: Time Type Full time, Duration Type Staff, Work Model Remote. So we have schedule info (full-time, remote). So we can include a Schedule section. - Benefits: Not explicitly mentioned. There's no benefits listed. So we should not create a Benefits section. - Qualifications: Could be covered by Required Education and Experience and Required Skills. But we can have a Qualifications section maybe combining education/experience and skills? However the rule says prefer a few substantive sections over many thin ones. We could have sections: Overview, Responsibilities, Required Skills, Preferred Skills, Education & Experience, Pay, Schedule. That's many sections but each substantive. Could we combine Required Skills and Preferred Skills into a Skills section? Possibly but they are distinct. The rule says use headings like Skills, Benefits, Pay, Schedule. So we could have a Skills section that includes both required and preferred? But then we lose distinction. However we could still include both under Skills with subheadings? Not allowed because only
for section headings. Could we have two Skills sections? That would be repetitive. Better to have Required Skills and Preferred Skills as separate sections? The allowed headings list includes Skills (generic). It didn't forbid using Required Skills and Preferred Skills as headings? The examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule." It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So those are examples, not an exhaustive list, but we should likely stick to those generic headings. However we could also use "Required Skills" and "Preferred Skills" as headings if they are more specific; but the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings, but not that we cannot use others. However to be safe, we could map content to those headings: Overview, Responsibilities, Requirements (maybe combine required skills and education), Qualifications (maybe preferred skills?), Skills, Pay, Schedule. But we need to preserve all substantive information; we cannot lose distinction between required and preferred. We could embed both under Skills with separate
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings, but not that we cannot use others. However to be safe, we could map content to those headings: Overview, Responsibilities, Requirements (maybe combine required skills and education), Qualifications (maybe preferred skills?), Skills, Pay, Schedule. But we need to preserve all substantive information; we cannot lose distinction between required and preferred. We could embed both under Skills with separate
or
- labeling. Eg:
- Financial Analysis and Reporting: Present financial information and recommendations through data analysis and reporting in the development and maintenance of budgets; identify funding issues and develop appropriate solutions; review and approve reports for administrative actions including pre-award costs and no-cost extensions; analyze data and develop complex analytical reports for principal investigators including trend analysis, forecast future financial scenarios, develop long range projections, and variance analyses.
- Proposal Development: Develop proposals and budgets for grant and contract submissions; coordinate with partnering institutions; ensure compliance with sponsor regulations and University policies and procedures; advise principal investigators of new funding opportunities and requirements.
- Portfolio Management: Plan, organize and prioritize actions across multiple awards and investigators' portfolios; ensure appropriate charging of expenses and integration of data; advise and counsel principal investigators on financial issues and recommend alternative spending strategies; manage renewals, extensions and closeouts of grants, including final financial reporting to the sponsor; analyze and negotiate budgets, contracts, and terms and conditions of research proposals.
- Compliance and Risk Management: Provide appropriate guidance on compliance matters during management of portfolio and collaborate with account holders to maintain such compliance; review, interpret and effectively apply sponsor policies on a variety of topics including cost allowability, budget management and other award management activities to ensure compliance with sponsoring agency requirements and University policies and procedures.
- Collaborative Finance Partner & Lead: Provide a high-level of service that maintains strong working relationships by interacting with faculty and internal and external contacts, such as the School of Medicine, Office of Research Administration and granting agencies by managing the internal pre award proposal process and the management of sponsored funding.
- May perform other duties as assigned.
- Strong financial and analytical skills with demonstrated application of financial and accounting concepts.
- Proficiency in Microsoft Excel and other office software, with the ability to manage multiple data sources effectively.
- Excellent written and verbal communication skills, with the ability to present financial information clearly and accurately.
- Strong organizational skills with high attention to detail and the ability to prioritize tasks and meet deadlines.
- Ability to work both independently and collaboratively, demonstrating a positive attitude and strong customer service skills.
- Prior experience with grants and contract administration, including pre-award to post-award processes.
- Knowledge of university policies and procedures, particularly within an academic or medical research setting.
- Proficiency in using financial systems such as Workday and Yale Budget Tool (YBT) for financial management and reporting.
- Experience in managing international sponsored awards, including familiarity with relevant regulations and compliance requirements.
- Bachelor's degree in accounting, business management, or a related field, with several years of relevant financial experience.
Skills
Required: ...
Preferred: ...
. That would preserve info. Similarly, we could have Overview, Responsibilities, Requirements (education/experience), Skills, Pay, Schedule. Let's see if we need a Requirements section: Could include education and experience. The posting has "Required Education and Experience". So we can put that under Requirements. Qualifications: Could be used for preferred skills? But we already have Skills covering both required and preferred. Maybe we can have Qualifications for preferred skills and experience? But we risk duplication. Better to have: Overview, Responsibilities, Requirements (education/experience), Skills (required & preferred), Pay, Schedule. Check if any other substantive content: There's also "Job Posting Date", "Job Category", "Bargaining Unit", "Compensation Grade", etc. Those are minor metadata; we can fold into a shortor drop. The instruction says: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a brief paragraph at top or bottom with metadata like posting date, job category, etc. But we should not create a heading for them. Could just include a
with that info. We must remove boilerplate: EEO, background check, health requirements, posting disclaimer, note about tobacco-free campus, etc. Those are legal/EEO boilerplate; remove. Also remove duplicated lines. Now craft HTML. Structure:
Overview
Working at Yale means contributing to a better tomorrow. Whether you are a current resident of our New Haven-based community, eligible for opportunities through the New Haven Hiring Initiative, or a newcomer, interested in exploring all that Yale has to offer, your talents and contributions are welcome. Discover your opportunities at Yale! The Portfolio & Grant Analyst is responsible for the financial management, proposal development, and stewardship of a portfolio of grants and contracts for sponsored research. Under general direction, this role manages post-award financial operations, including financial reporting, budgeting, forecasting, and compliance with university and sponsor policies. The Analyst collaborates with Principal Investigators (PIs) and other stakeholders to ensure accurate financial information, resolve budgetary issues, prepare financial statements, and provide long-term planning for research funding. This role includes involvement in managing budgets, preparing expenditure projections, overseeing grant renewals and closeouts, and maintaining up-to-date knowledge of policies and procedures.
Responsibilities
Requirements
Bachelor's degree required. Two years of related financial experience required. Demonstrated application of financial, accounting and economic concepts.
Skills
Required Skills and Abilities:
Preferred Skills and Abilities:
Pay
Salary Range: $55,000.00 - $85,000.00
Schedule
Time Type: Full time; Duration Type: Staff; Work Model: Remote.
We might also include a brief metadata paragraph after Overview maybe:Job Posting Date: 09/17/2026; Job Category: Professional; Bargaining Unit: NON; Compensation Grade: Administration & Operations; Supervisor; Senior Associate (P4).
But we need to avoid creating a heading for it. Could place after Overview as a. However the instruction says "fold minor metadata into a short
or drop it." So we can include a short p after Overview. Let's add after Overview:
Job Posting Date: 09/17/2026; Job Category: Professional; Bargaining Unit: NON; Compensation Grade: Administration & Operations; Supervisor; Senior Associate (P4).
Make sure not to duplicate info already in Pay section (we have salary range there). That's fine. Now check for any leftover boilerplate: We removed background check, health requirements, posting disclaimer, EEO, note about tobacco-free campus, etc. Check for duplicated lines: We have not repeated. Check that we didn't invent or summarize away detail: We preserved all substantive info: overview, responsibilities (six items), requirements (education/experience), required skills, preferred skills, pay, schedule. Also we included metadata. Check that we didn't create sections with filler: All sections have real content. Check that we didn't include Benefits section (none).