Sponsored Research Administrator

We need to output HTML fragment with sections: About the role? Actually the posting includes "About the Department" and "Wolfpack Perks and Benefits", "Essential Job Duties", "Qualifications". Also "Pay" is given: Anticipated Hiring Range $65,000 - $73,525 (Commensurate with education and experience). The instruction: 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. Pay is stated: Anticipated Hiring Range $65,000 - $73,525 (Commensurate with education and experience). The phrase "Commensurate with education and experience" is filler? It's part of the range description. The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience". That refers to a heading with placeholder text. But we can still have Pay section with the range; the phrase "Comm..." is part of the content, not a heading. So we can include Pay section. Schedule: Work Schedule Monday through Friday, 8:00 am to 5:00 pm; position may be eligible for a flexible work schedule. Adjustments to the schedule are occasionally required to accommodate rigid sponsor proposal deadlines. So we have schedule info, we can include Schedule section. Benefits: Wolfpack Perks and Benefits section lists many benefits. So we can include Benefits section. We must not repeat job title as heading. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have: - About the Department (could map to About the role? Actually "About the Department" is about the department, not role. But we can use "About the role" heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. We have "About the Department" content; we could rename to About the role? But we must preserve ALL substantive information; we cannot change meaning. However we can keep heading as "About the Department" but the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to use "About the Department" as heading? Might be okay. But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those exact headings when applicable. For "About the Department", we could use "About the role" but that would misrepresent. However the content is about the department, not the role. Could we treat it as "About the role"? Might be okay but risk losing nuance. Better to keep heading as "About the Department". The instruction didn't forbid other headings; it just gave examples. So we can use

About the Department

. Similarly, we have "Wolfpack Perks and Benefits" -> Benefits section. We have "Essential Job Duties" -> Responsibilities. We have "Qualifications" -> Qualifications. We have Pay and Schedule. We might also include Skills? Not explicitly separate; qualifications include skills. Could omit Skills. We must not include empty sections. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove EEO paragraph, disclaimer about perks eligibility? That's part of benefits but maybe keep? The disclaimer: "Disclaimer: Perks and Benefit eligibility is based on Part-Time or Full-Time Employment status. Eligibility and Employer Sponsored Plans can be found within each of the links offered." That's still substantive? It's about eligibility; could keep but it's not boilerplate? It's a disclaimer; maybe considered legal. Might be safe to remove? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This disclaimer is legal; better to remove. Also remove "Other Responsibilities Other duties as assigned." That's generic; maybe keep? It's not substantive detail; could be considered boilerplate. Might drop. Also remove "Required License(s) or Certification(s) N/A" etc. That's filler; drop. Remove "Recruitment Dates and Special Instructions" etc. Remove "Position Details" etc. Remove "Supplemental Questions" etc. Remove "Application Materials Required" etc. We need to preserve all substantive information: about department, perks/benefits, essential job duties, qualifications, pay, schedule. Now craft HTML. Structure:

About the Department

... (the paragraph about COE ORA)

Benefits

• Medical, Dental, and Vision
• Flexible Spending Account
... etc. Need to list each benefit as separate
• . The benefits list: Medical, Dental, and Vision; Flexible Spending Account; Retirement Programs; Disability Plans; Life Insurance; Accident Plan; Paid Time Off and Other Leave Programs; 12 Holidays Each Year; Tuition and Academic Assistance; Childcare benefits; Wellness & Recreation Membership; Wellness Programs. Also "And so much more!" is vague; maybe drop as filler. We'll list the concrete ones. We need to preserve all substantive information; "And so much more!" is not substantive; could drop. Also "Attain Work-life balance with our Childcare benefits, Wellness & Recreation Membership, and Wellness Programs that aim to build a thriving wolfpack community." This is descriptive; we could incorporate into benefits as sentences? But we already have those items listed. Could add a

  describing work-life balance. But instruction: use

  for prose. So we could have a

  describing the work-life balance statement. Thus Benefits section:

  • Medical, Dental, and Vision
  • Flexible Spending Account
  • Retirement Programs
  • Disability Plans
  • Life Insurance
  • Accident Plan
  • Paid Time Off and Other Leave Programs
  • 12 Holidays Each Year
  • Tuition and Academic Assistance
  • Childcare benefits
  • Wellness & Recreation Membership
  • Wellness Programs

  Attain Work-life balance with our Childcare benefits, Wellness & Recreation Membership, and Wellness Programs that aim to build a thriving wolfpack community.

  Now Responsibilities: "Essential Job Duties" includes detailed description. We'll put heading

  Responsibilities

  then

  maybe a brief intro then

  for list of duties. The content includes paragraphs: "The College of Engineering is looking to hire multiple Sponsored Research Administrators (SRA) within the newly established college-managed operating model, responsible for orchestrating both pre-award and post-award lifecycles for an assigned departmental faculty portfolio." Then details about localized, etc. Then "Detailed Description Of Core Responsibilities" with subheadings Pre-Award Portfolio Management & Proposal Development, Post-Award Financial Management..., Model Alignment, Cross-Coverage & Leadership. We could break into
  items for each bullet. But we need to preserve all substantive information; we can convert paragraphs into

  and lists. Simplify: Provide a

  summarizing the role, then

  with each duty as
  • . Use the detailed bullet points. Let's extract duties: Pre-Award Portfolio Management & Proposal Development: - Localized Faculty Consultation: Partner directly with PIs in the embedded unit to develop accurate, compliant proposal budgets and detailed justifications from initial concept through final submission. - Standardized Regulatory Screening: Analyze complex agency Requests for Proposals (RFPs) and Funding Opportunity Announcements (FOAs) to ensure strict alignment with F&A rules, cost-sharing restrictions, budget caps, and direct cost allowability, reducing front-end submission errors. - Institutional System Management: Fully execute and route records within institutional software suites, including RED Proposal Development, ensuring data integrity is validated at the departmental level before final central routing. - Electronic Research Administration (eRA): Build, format, and package proposal submissions within varied sponsor portals (Research.gov, GRANTS.gov, eRA Commons, ASSIST), acting as the localized technical expert for the department’s faculty. Post-Award Financial Management, Forecasting & Closeout: - Award Onboarding & Budget Translation: Review select incoming award notices alongside the PI to establish accurate internal ledger setups, ensuring F&A is calculated correctly based on MTDC or TDC parameters. - Compliance Monitoring & Risk Mitigation: Perform continuous financial analysis of active grant ledgers. Monitor expenditures for accuracy, allowability, and strict compliance with Cost Accounting Standards (CAS), Uniform Guidance, state rules, and university policies. - Projections & Planning Models: Build multi-year spending projections and variance analysis models for faculty to optimize fund utilization, prevent over-expenditures, and manage labor distributions/personnel charges. - Reconciliations & Cost-Share Tracking: Audit human resource expenditures, travel vouchers, and procurement charges against grant terms. Track, document, and report mandatory or voluntary committed cost-sharing obligations. - Lifecycle Closeouts: Execute comprehensive closeouts for expiring grant segments. Prepare and process Project Modification Requests (PMRs) for budget modifications, no-cost extensions, or residual balance distributions, ensuring audit-ready documentation is permanently archived. Model Alignment, Cross-Coverage & Leadership: - Matrixed Team Collaboration: Actively participate in the broader College ORA network to ensure alignment with university-wide research administration standards. Navigate the dual priorities of central College compliance policy and local departmental workflow. - Cross-College Workload Balancing: Participate in the new model’s agile resource framework, willingly stepping in to provide temporary pre- or post-award coverage for other COE departments during peak submission cycles or staff absences to maintain college-wide continuity. - Faculty Onboarding & Training: Develop and deliver targeted resources, onboarding guides, or info-sessions for new faculty and departmental business officers regarding centralized ORA standard operating procedures and financial management tools. Also earlier sentence: "While the incumbent is physically co-located within a department to provide high-touch, localized customer service, the position is an integral part of the centralized College ORA team." Could be a

    . We'll include that as prose. Now Qualifications: heading

    Qualifications

    . Content: Minimum Education and Experience: Bachelor’s degree; or an equivalent combination of training and experience. All degrees must be received from appropriately accredited institutions. Other Required Qualifications: list bullet points. Preferred Qualifications: list bullet points. Required License(s) or Certification(s) N/A (drop). We'll keep Minimum Education and Experience as

    maybe. Then

    for Other Required Qualifications. Then maybe another
    for Preferred Qualifications with heading? Could just combine but better separate. We'll do:

    Minimum Education and Experience: Bachelor’s degree; or an equivalent combination of training and experience. All degrees must be received from appropriately accredited institutions.

    Other Required Qualifications

    but we only allowed

    for section headings. Could use

    for each subsection? Might be too many headings. But we can keep

    with bold. Or we can use

    directly after a

    intro. Simplify:

    Qualifications