Stewardship Assistant

We need to output HTML fragment with sections: About the role? The posting includes "Job Summary" and description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. We must not repeat job title. We must not include Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro about Caltech: "Caltech is a world-renowned science and engineering institute..." This is about the organization; could be "About the role"? Actually "About the role" maybe includes job summary. We'll treat "Job Summary" as About the role. - Job Summary paragraph: "The purpose of Advancement and Alumni Relations (AAR) is to foster a thriving and engaged community of support for Caltech..." etc. - Reporting to the Director of Stewardship... description of two functions. - Essential Job Duties: list of duties (multiple sentences). We need to turn into

• items. - Basic Qualifications: list of qualifications. - Preferred Qualifications: list. - Required Documents: Resume, Cover Letter. This is not a standard heading; maybe we could put under Requirements? But we have sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Required Documents could be under Requirements? Or we could omit if not fitting. The instruction: include a section ONLY when posting has real, specific content for it. So we can include a section "Required Documents" only if we have a heading for it, but headings list is fixed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings. Required Documents could go under Requirements or Qualifications? Probably Requirements (like required documents). We'll put under Requirements. - Hiring Range: $30.75 - $48.75 per hour. That's Pay. - Benefits description: paragraph about benefits. - Schedule: not mentioned. So we should not include Schedule section. - Skills: maybe we can extract from qualifications: e.g., Strong Proficiency in Microsoft Office, etc. Could be Skills section. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate: EEO statement, disability accommodations, etc. Remove those. We must preserve all substantive info: So we need to keep the details about duties, qualifications, preferred qualifications, benefits, pay, etc. We must not invent or summarize away detail. So we need to keep each bullet as is, not combine. We need to output only HTML fragment, no /, no markdown. Let's structure:

  About the role

  Job Summary paragraph(s). Possibly also include the intro about Caltech? The intro about Caltech is generic; maybe we can include as part of About the role. But we need to preserve all substantive info; the intro about Caltech is substantive but not role-specific. However it's part of job posting. We'll include it in About the role. Thus About the role will contain two paragraphs: the Caltech intro and the Job Summary. Then

  Responsibilities

  with
  • each duty from Essential Job Duties. We need to split duties into separate items. The duties are a long paragraph with semicolons and periods. We'll break each sentence or clause into separate
  • . Must preserve all info; we can split at each sentence. Let's list duties from text: "Independently coordinate the daily processing of gift acknowledgment and related correspondence for Caltech leadership." "Track, prepare, and coordinate routing of correspondence for the Vice President of AAR’s and Provost’s signatures; track and support the preparation of correspondence for the President’s signature." "Develop and apply specialized knowledge and expertise to maintain and utilize confidential data in AAR’s Advance database." "Input and maintain designated data, and on a daily basis, run relevant gift reports and scan and upload correspondence and stewardship reports into the database, ensuring timeliness and accuracy of entries." "Research, compile, analyze, and present data needed for gift acknowledgment and donor reporting purposes." "Facilitate the production and mailing of materials, including gift correspondence, invitations, reports, donor gifts, and other items." "Track the Stewardship team’s operating budget, by reviewing and reconciling expenditures, as well as monitoring actual expenses against projections." "Assist with projecting cost estimates and schedules." "Oversee and administer purchasing activities for the team, including P-card reconciliation and travel arrangements for department team members." "Manage team meeting schedule and help team members with coordinating other meetings and events." "Provide administrative support at meetings as needed; track and follow-up with action items to ensure completion." "Assist with preparation and follow up for donor recognition events and donor gift mailings." "Develop and maintain professional relationships with counterparts across AAR." "Serve as content expert for the Stewardship team for the Advancement and Alumni Relations SharePoint site, maintaining team data and ensuring the work of the team is conveyed appropriately to team members." "Perform other duties and special projects as assigned." That seems comprehensive. Now

    Requirements

    maybe include Required Documents and Basic Qualifications? Actually Basic Qualifications is under Requirements? Usually Basic Qualifications are requirements. We'll put Basic Qualifications under Requirements as list. But we also have a separate Qualifications heading (maybe for Preferred Qualifications). The instruction list includes both Requirements and Qualifications. We can treat Requirements as Basic Qualifications (required) and Qualifications as Preferred Qualifications. Or we could swap. Let's decide: Requirements = Basic Qualifications (must have). Qualifications = Preferred Qualifications (nice to have). Skills could be derived from both but we can also put specific skills under Skills. But we have to avoid duplication. Let's map: - Requirements (h3) -> Basic Qualifications list. - Qualifications (h3) -> Preferred Qualifications list. - Skills (h3) -> maybe list of skills like Microsoft Office proficiency, communication skills, etc. However many of those are already in Basic Qualifications. To avoid duplication, we could still list them under Skills if they are distinct. But we must not invent or summarize away detail; we can still include them as they appear in Basic Qualifications. However if we put them under both Requirements and Skills, that duplicates content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could put the skill-specific items under Skills and keep Requirements focused on education/experience. Let's parse Basic Qualifications: "Bachelor’s degree or equivalent related work experience." "Three years or more of progressively responsible administrative and project coordination experience, two of which should be in a nonprofit or higher education setting." "Excellent organizational, project and time management skills; including ability to work independently and collaboratively, manage multiple projects at same time, prioritizing tasks and meeting deadlines with a fast-paced environment with multiple and competing demands." "Meticulous attention to detail and accuracy." "Excellent written communication skills, including strong editing, spelling, grammar and proofreading." "Excellent verbal communication skills, interpersonal skills, and the ability to communicate clearly and tactfully within Caltech and to external constituents." "Experience using business databases to maintain and extract data." "Demonstrate discretion and diplomacy; experience and judgment to deal appropriately with confidential information." "Strong customer service skills, demonstrating a professional and friendly demeanor, including the ability to anticipate and provide friendly and helpful service to internal and external partners." "Sensitivity to constituent relations and service." "Strong Proficiency in Microsoft Office (Word, Excel, PowerPoint, Outlook)." "Authentic curiosity about science and technology." "Demonstrate the ability to practice and adhere to AAR’s Guiding Principles." Thus many are skills. We could put education/experience under Requirements, and the rest under Skills. But the instruction says we have a Requirements heading; we can put education/experience there. Then Skills heading for the skill items. Qualifications heading for Preferred Qualifications. Let's do that. Thus:

    Requirements

    • Bachelor’s degree or equivalent related work experience.
    • Three years or more of progressively responsible administrative and project coordination experience, two of which should be in a nonprofit or higher education setting.

    Skills

    • Excellent organizational, project and time management skills; including ability to work independently and collaboratively, manage multiple projects at same time, prioritizing tasks and meeting deadlines with a fast-paced environment with multiple and competing demands.
    • Meticulous attention to detail and accuracy.
    • Excellent written communication skills, including strong editing, spelling, grammar and proofreading.
    • Excellent verbal communication skills, interpersonal skills, and the ability to communicate clearly and tactfully within Caltech and to external constituents.
    • Experience using business databases to maintain and extract data.
    • Demonstrate discretion and diplomacy; experience and judgment to deal appropriately with confidential information.
    • Strong customer service skills, demonstrating a professional and friendly demeanor, including the ability to anticipate and provide friendly and helpful service to internal and external partners.
    • Sensitivity to constituent relations and service.
    • Strong Proficiency in Microsoft Office (Word, Excel, PowerPoint, Outlook).
    • Authentic curiosity about science and technology.
    • Demonstrate the ability to practice and adhere to AAR’s Guiding Principles.

    Qualifications

    (Preferred)
    • Proficiency with Advance or other fundraising CRM database experience.
    • Expert-level proficiency with Microsoft Excel, and other programs that provide the ability to interpret, manage, and track large quantities of data.
    • Experience working in donor relations/engagement, stewardship, events, or development/fundraising environment.
    • Experience with additional applications such as event systems, project management software, Encompass, InDesign, or other graphic design programs.
    • Experience with SharePoint.

    Benefits

    As one of the largest employers in Pasadena, CA, Caltech is committed to providing comprehensive benefits to eligible employees and their eligible dependents. Our benefits package includes competitive compensation, health, dental, and vision insurance, retirement savings plans, generous paid time off (vacation, holidays, sick time, parental leave, bereavement, etc.), tuition reimbursement, and more. Non-benefit eligible employees will have access to some benefits such as onsite counseling and sick time.

    Pay

    Hiring Range $30.75 - $48.75 per hour. The salary of the finalist(s) selected for this role will be set based on a variety of factors, including but not limited to, internal equity, experience, education, specialty and training.

    We should not include Schedule section. Now About the role: we need to include Caltech intro and Job Summary. Let's craft:

    About the role

    Caltech is a world-renowned science and engineering institute that marshals some of the world's brightest minds and most innovative tools to address fundamental scientific questions. We thrive on finding and cultivating talented people who are passionate about what they do. Join us and be a part of the diverse Caltech community.

    The purpose of Advancement and Alumni Relations (AAR) is to foster a thriving and engaged community of support for Caltech. By strengthening and nurturing the community of people who share and support the Institute’s mission and values, we will ensure the Institute receives the necessary resources to achieve our aspirations and advocate for excellence in teaching, research, and scholarship in perpetuity. Reporting to the Director of Stewardship, the Stewardship Assistant performs two diverse functions in support of the Philanthropic Initiatives and Stewardship team. First, in collaboration with members of the Ste