Senior Grants Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes intro paragraphs about Rosendin, then "Your Next Opportunity" heading then description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have content for responsibilities (What You’ll Do), requirements/qualifications (What You’ll Need To Be Successful, What You Bring To Us), benefits (YOU Matter – Our Benefits). Also schedule/hybrid info (Working Conditions). Pay not mentioned. So we should not include Pay or Schedule unless present. There's no explicit pay. So omit Pay. Schedule? Not explicit schedule; we have hybrid work environment but not schedule like full-time/part-time. Could treat as Working Conditions but not a required heading; we can include maybe under "Schedule"? Not appropriate. Better to include a section for "Working Conditions" not in list; but instructions say use headings from list only. So we should not create a heading not in list. Could we embed working conditions in Responsibilities or Requirements? Probably better to include a "Benefits" section for benefits, and maybe a "Qualifications" for education/experience. Responsibilities for duties. Requirements maybe for skills? The list includes Requirements, Qualifications, Skills. We can combine. We need to decide. We have: - Responsibilities: "What You’ll Do" bullet list (actually paragraphs with many duties). We'll put in

• . - Requirements: "What You’ll Need To Be Successful" (skills, experience). Could be Requirements. - Qualifications: "What You Bring To Us" (education, experience). Could be Qualifications. - Benefits: "YOU Matter – Our Benefits" list. - Possibly "About the role": we have intro paragraphs about Rosendin and the role overview before "Your Next Opportunity". Could be About the role. We must not include headings with filler text. All sections have content. We must not include Job ID etc. No metadata. We must not include boilerplate like EEO etc. Remove that at end. We must preserve all substantive information. So we need to keep the descriptive paragraphs. We need to output only HTML fragment, no /. Use

  for each section heading. We need to wrap responsibilities in

  • . Each duty is a sentence; we can split by sentences or keep as paragraphs? The instruction: Use
    • for any list of duties/requirements/benefits. So we need to convert the duties into list items. Similarly for requirements/qualifications/benefits. We must preserve all substantive information; not invent or summarize away detail. So we need to keep the content but can break into list items. We need to be careful not to lose any detail. Let's extract sections. First, About the role: The introductory paragraphs before "Your Next Opportunity": "Whether you’re a recent grad or a seasoned professional, you can experience meaningful career growth at Rosendin. Enjoy a true sense of ownership as you work with a proven industry leader on some of the most exciting and high-profile projects in the nation. We offer a wide range of job opportunities, competitive compensation, full benefits, an Employee Stock Ownership Plan and more. Why Rosendin? Committed. Innovative. Engaged. If you’re looking to take your career to the next level and work with some of the best and brightest in the industry, we want to hear from you. Since our founding over 100+ years ago, Rosendin has been driven to positively impact the communities where we live and work. We are an organization built on integrity and we have a culture that empowers people, embraces diversity, and inspires everyone to do their best. As one of the largest EMPLOYEE-OWNED electrical contractors in the United States, you will have the unique benefit of being a shareholder at a company that is experiencing tremendous growth and success. When our people succeed and fuel our success, we reward them. We'd love to have you as a shareholder!" That's about the company; we can put as About the role. Then "Your Next Opportunity The Senior Grants Specialist plays a critical role..." That's role overview; could also be part of About the role. But we already have About the role; we could include that paragraph as part of About the role as well. Better to treat "Your Next Opportunity" as role summary; we can include in About the role. Then Responsibilities: "What You’ll Do" followed by many sentences each starting with a verb. We'll make each sentence a list item. Let's copy the responsibilities text: "Manage all aspects of The Rosendin Foundation’s grants management administration process throughout the full grant lifecycle. Review, process, and ensure internal/external compliance for all grant inquiries, applications, approvals, payments, reporting requirements, and grant closeout activities. Own and lead implementation of CRM Grant Making systems (ie: Blackbaud/Raiser’s Edge Grantmaker) as well as updates, management, administration, documentation, and communication. Manage and oversee grants management systems that include ensuring system functionality and compliance, accurate documentation, reporting, and data integrity. Serve as the Foundation’s internal first point of contact for interpreting, applying, and ensuring grant administration policies, procedures, and operational inquiries are internally/externally compliant as well as continually evolving and aligning with the Foundation’s mission and values. Ensure grantmaking activities comply with Foundation guidelines, corporate foundation regulations, governance requirements, and internal policies and recommend areas of improvement Develop, maintain, and recommend/implement operational process improvements in standardized grant tracking, reporting, and recordkeeping processes. Manage and track proactively grant deadlines, reporting requirements, and payment schedules to ensure timely completion of grant obligations. Manage and provide proactive direction to volunteer grant committee members throughout the grant review process to ensure both internal/external policies/procedures are followed, including application guidance, system navigation, and administrative support. Partner with finance teams to ensure accurate, timely, and consistent grant payment processing, reconciliation, budget tracking, and fiduciary oversight. Collaborate with communications and Foundation leadership to support grant announcements, impact reporting, and stakeholder engagement efforts. Generate and analyze data/information reports in order to synthesize/summarize information, identify trends/outliers, and recommend areas of opportunity/improvement that support leadership decision-making and ongoing program evaluation. Identify and recommend opportunities for process improvements, operational efficiencies, and technology enhancements related to grant administration. Partner and collaborate with IT to own and lead implementation and optimization of grants management technology platforms and related workflows. Maintain grant files and records in accordance with Foundation policies, audit requirements, and record retention standards. Prepare reports, dashboards, summaries, and presentations for the Executive Director, leadership teams, and volunteer committees. Provide administrative and operational support for Foundation initiatives, fundraising events, and special projects as needed. The duties and responsibilities are intended to describe the general nature and scope of work performed by this position. This is not all-encompassing, and other duties may be assigned based on the position role within the Foundation and company." We need to keep the last two sentences as part of responsibilities? They are more generic; we can include as list items or maybe as a note. We'll include as list items. Now Requirements: "What You’ll Need To Be Successful" list: "Demonstrated strong understanding of grants administration and foundation operations across the full grant lifecycle. Demonstrated experience managing grantmaking processes, systems, workflows, reporting, and compliance requirements. Demonstrated experience and strong knowledge of grants management databases and CRM platforms. Demonstrated strong experience with Blackbaud/Raiser’s Edge Grantmaker is required. Manage volunteer teams with professional tenacity. Exceptional attention to detail with strong organizational and project management skills. Strong data/information analysis experience that drives and supports informed decision-making, including synthesizing/summarizing information, identifying trends/outliers, and recommending areas of opportunity/improvement. Strong understanding and application of data integrity, reporting accuracy, and records management principles. Ability to prioritize multiple projects and adapt effectively and efficiently to changing business and operational needs. Strong written, verbal, and interpersonal communication skills. Demonstrated strong problem-solving skills and sound professional judgment. Demonstrated ability to collaborate and partner effectively with leadership, volunteers, community partners, and cross-functional teams. Service-oriented Foundation driven mindset with the ability to provide guidance and support to grant applicants and volunteer committee members. Proficiency in Microsoft Office applications including Outlook, Word, Excel, PowerPoint, and Teams. Commitment to continuous improvement, operational excellence, and mission-driven work." Now Qualifications: "What You Bring To Us": "Bachelor's degree in Nonprofit Management, Business Administration, Public Administration, Communications, Philanthropy, or a related field preferred. 5-7 years of experience in nonprofit grants management, corporate foundation administration, philanthropy operations, or related grantmaking functions. Demonstrated experience in leading successful implementation of at least 1-2 CRM Grant Making systems, especially Blackbaud/Raiser’s Edge Grantmaker Experience administering grants management systems and serving as a primary system user. Experience supporting nonprofit organizations, foundations, charitable giving programs, or community investment initiatives preferred. Demonstrated success working in collaborative, mission-driven, and high-accountability environments. Equivalent combinations of education, training, and relevant experience will be considered" Then Travel: "Limited travel may be required based on Foundation programs, volunteer events, fundraising activities, community engagement opportunities, and business needs. Occasional attendance at Foundation-sponsored events, committee meetings, and community partner functions may be required." We could include travel under Requirements or maybe a separate section? Not in headings list. Could incorporate into Responsibilities or Requirements. Probably better to include under Requirements as a bullet. Working Conditions: "Hybrid work environment based in South Tempe, Arizona. Primarily office-based work with periodic attendance at community events, fundraising activities, and Foundation programs. Frequent use of computers, telephones, and virtual collaboration tools. General work environment includes sitting for extended periods, standing, walking, typing, carrying, pushing, and bending. Work is conducted primarily indoors with varying environmental conditions such as fluorescent lighting and air conditioning. Noise levels are typically low to moderate. Occasional lifting of up to 20 lbs." We could include under a section maybe "Work Environment" but not in list. Could incorporate into Responsibilities? Not ideal. Perhaps we can create a section "Schedule"? Not accurate. The instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid creating a section not in the list? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those headings; but we could also use other headings? The examples are given but not exclusive? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should stick to those. Thus we need to map content to those headings. We have About the role, Responsibilities, Requirements, Qualifications, Benefits. Skills could be merged into Requirements or Qualifications. We'll not create Skills if not distinct. We have no Pay or Schedule specifics, so omit those. Now we need to ensure we include all substantive info. Travel and Working Conditions need to be placed somewhere. Could be included under Responsibilities (as part of duties) or Requirements (as part of qualifications). Travel could be under Requirements as a bullet. Working Conditions could be under Responsibilities? Not exactly duties. Could be under Requirements as well (like work environment). Might be okay. We'll add travel bullet under Requirements. Working conditions bullet under Requirements as well. Now Benefits: list from "YOU Matter – Our Benefits". We'll extract each benefit as list item. Benefits list: ESOP – Employee Stock Ownership 401 K Annual bonus program based upon performance, profitability, and achievement 17 PTO days per year plus