Sr. Specialist, Sponsorships & Corporate Giving
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- Job Summary (maybe "About the role"): includes summary of role.
- Responsibilities: bullet list.
- Education/Experience: maybe "Qualifications" or "Education/Experience". Could be "Qualifications". We'll treat as Qualifications.
- Requirements: bullet list.
- Knowledge, Skills & Abilities: maybe "Skills". Could be "Skills".
- Pay Details: includes Pay range $0 - $0 (but that's placeholder? It says $0 - $0, which is not specific; it's basically not specified. The instruction says: 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. Here Pay Details says base compensation range $0 - $0. That's essentially not specified; it's placeholder zero. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but it's $0 - $0 which is effectively not specified. However it's still stated. The instruction says avoid filler/placeholder text like "not specified". $0 - $0 is arguably placeholder. I'd lean to omit Pay section because it's not meaningful. But we need to consider if we should include it anyway? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if we include Pay heading with content "$0 - $0", that is filler/placeholder. So we should not include Pay section.
- Benefits: There's a "Why Join Us" and "Employee Benefits" with details. That's substantive. So we should include Benefits section.
- Schedule: Not mentioned. So omit.
- About the role: We have Job Summary. That's substantive. So include About the role.
- Responsibilities: yes.
- Requirements: yes.
- Qualifications: Education/Experience.
- Skills: Knowledge, Skills & Abilities.
- Benefits: yes.
We must not include sections like Pay or Schedule.
We need to format lists with - . For prose, use
.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the "Acrisure is an Equal Opportunity Employer..." etc. Also "Final candidates will be required to complete post-offer verification processes..." etc. Also "California Residents: Learn more..." etc. Also "Recruitment Fraud: Please visit here..." etc. Also "Welcome, your new opportunity awaits you." etc.
Also need to remove duplicated lines (maybe none). Also remove the "Why Join Us:" paragraph that is more marketing but still substantive? It includes benefits description; we already have Benefits section. The "Why Join Us:" includes some impact statements; maybe we can incorporate into Benefits or keep as part of About the role? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that content somewhere. Could be part of Benefits or a separate section like "About the company". But we only have allowed headings list; we could put it under Benefits or maybe under About the role? The "Why Join Us:" is about company culture and impact; could be considered part of Benefits? Not exactly. But we could include it as part of Benefits section (since it's about why join). However the Benefits section already lists benefits; we could add a paragraph about impact before the list. That would preserve info.
We also have "Employee Benefits" list with subcategories. We'll need to output as a list.
We need to ensure we don't include the "Acrisure is an Equal Opportunity Employer..." etc.
Also need to remove the "Applicants may request reasonable accommodation..." etc.
Also remove "Final candidates will be required to complete post-offer verification processes..." etc.
Also remove "California Residents: Learn more..." etc.
Also remove "Recruitment Fraud: Please visit here..." etc.
Also remove "Welcome, your new opportunity awaits you."
Also remove the "Why Join Us:" heading? We can keep the paragraph but not as heading if we merge into Benefits.
Now let's extract substantive content:
About Acrisure: (company description) - maybe we can include as part of About the role? Actually About the role is about the job, not company. But we could include a short paragraph about company as part of About the role? 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? 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 not add a heading like "About Acrisure". Instead we could incorporate that description into About the role section (maybe as a brief intro). But About the role should focus on the role. However we can include company description as part of About the role? Might be okay.
Better: Use About the role heading to contain the Job Summary plus maybe a brief about Acrisure? The Job Summary already includes role description. The About Acrisure description is separate but could be considered part of "About the role" as context. I'd include it as a paragraph before the Job Summary.
Now Responsibilities: we have several bullet groups. We need to convert each bullet line into
- . The responsibilities are grouped under headings like "Ticketing Operations & Hospitality Administration", "Intake & Workflow Administration", etc. Those are subheadings within responsibilities. Should we keep them as headings? The instruction only mentions using
for section headings (like About the role, Responsibilities...). It doesn't forbid using other headings inside? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could treat those subheadings as plain text within
or maybe as . However we need to preserve all substantive information; we could keep them as Ticketing Operations & Hospitality Administration: then list.
But the instruction says use
- for any list of duties/requirements/benefits. So we need to output a list for responsibilities. The subheadings could be separate
before each group of
- . That seems fine.
Similarly for Requirements: there is a paragraph then bullet list.
Knowledge, Skills & Abilities: bullet list.
Education/Experience: paragraph.
Benefits: we have a paragraph "Why Join Us: ..." then "Employee Benefits We also offer our employees a comprehensive suite of benefits and perks, including:" then subcategories with colon and list.
We need to output Benefits section with maybe a paragraph about impact then a list.
We must not include filler like "This list is not exhaustive of all available benefits." That's substantive? It's a statement but not specific benefit. Could keep as a paragraph.
We must not include eligibility waiting periods etc? That's substantive but maybe we can keep as a short paragraph.
We need to remove duplicated lines.
Let's extract the exact text.
I'll copy the job description and manually extract.
Job Description:
About Acrisure: A global fintech leader, Acrisure empowers millions of ambitious businesses and individuals with the right solutions. Bringing cutting-edge technology and top-tier human support together, it connects clients with customized solutions across a range of insurance, reinsurance, payroll, benefits, cybersecurity, mortgage services and more. In the last eleven years, Acrisure has grown in revenue from $38 million to almost $5 billion and employs over 19,000 colleagues in 21 countries. Our culture is defined by our entrepreneurial spirit and all that comes with it: innovation, client centricity and an indomitable will to win.
Job Summary: The Sr. Specialist, Sponsorships & Corporate Giving reports to the Manager, Sponsorships & Corporate Giving and is responsible for supporting the day-to-day administration, coordination, systems management, and operational execution of Acrisure's sponsorship, hospitality, partnership, and corporate giving programs. This role serves as the operational backbone of the Sponsorships & Corporate Giving function, supporting ticketing operations, intake and approval workflows, data management, reporting, documentation, contract administration, and cross-functional coordination. The Sr. Specialist ensures processes are executed accurately, assets are tracked effectively, records are maintained, and stakeholders receive timely support.
Responsibilities Ticketing Operations & Hospitality Administration Administer TicketOS, including inventory management, ticket requests, allocations, fulfillment, and user support.Manage the sponsorship and hospitality ticketing inbox and respond to stakeholder requests.Maintain accurate records of ticket distributions, asset utilization, and hospitality allocations.Coordinate ticket delivery, event logistics, and hospitality-related communications.Support utilization tracking and reporting for hospitality and partner assets. Intake & Workflow Administration Administer sponsorship, partnership, charitable giving, and event-related intake processes through Cvent and other platforms.Route requests to appropriate stakeholders and maintain approval workflows.Track submissions, approvals, deadlines, and required documentation.Maintain records supporting governance and compliance requirements.Ensure requests progress through established processes in a timely and accurate manner. Data, Reporting & Tracking Support Maintain records supporting sponsorship, hospitality, charitable giving, and community investment activities.Track asset utilization, spend, approvals, and program participation.Compile data for reports, dashboards, executive updates, and performance summaries.Support budget tracking and spend visibility efforts.Assist with maintaining portfolio, partner, and giving program records. Systems & Documentation Management Maintain SharePoint sites, team resources, templates, trackers, and document libraries.Organize and manage contracts, agreements, invoices, approvals, and supporting documentation.Ensure records are complete, accurate, and readily accessible.Support system administration activities related to sponsorship and giving operations.Maintain process documentation, procedures, and resource materials. Administrative & Operational Support Coordinate invoices, purchase requisitions, vendor setup activities, and payment tracking.Schedule meetings, prepare materials, and coordinate logistics for internal and external stakeholders.Support partner communications and routine administrative activities.Assist with sponsorship activations, hospitality events, charitable giving initiatives, and program execution.Provide operational support to the Director and Manager, Sponsorships & Corporate Giving as needed.
Education/Experience: Bachelor's degree in Marketing, Communications, Business Administration, Event Management, Sports Management, Nonprofit Management, Public Relations, or a related field preferred.Equivalent combination of education and relevant work experience may be considered.
Requirements: 3-5 years of experience in sponsorship administration, event operations, hospitality management, project coordination, marketing operations, nonprofit administration, corporate giving, or a related field.Experience managing administrative processes, workflows, records, or operational support functions.Experience working with ticketing systems, CRM platforms, databases, or workflow management tools preferred.Experience supporting cross-functional teams and coordinating multiple projects simultaneously.Corporate, agency, sports, entertainment, nonprofit, or event management experience preferred.
Knowledge, Skills & Abilities Strong organizational and administrative skills with exceptional attention to detail.Ab
. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the "Acrisure is an Equal Opportunity Employer..." etc. Also "Final candidates will be required to complete post-offer verification processes..." etc. Also "California Residents: Learn more..." etc. Also "Recruitment Fraud: Please visit here..." etc. Also "Welcome, your new opportunity awaits you." etc. Also need to remove duplicated lines (maybe none). Also remove the "Why Join Us:" paragraph that is more marketing but still substantive? It includes benefits description; we already have Benefits section. The "Why Join Us:" includes some impact statements; maybe we can incorporate into Benefits or keep as part of About the role? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that content somewhere. Could be part of Benefits or a separate section like "About the company". But we only have allowed headings list; we could put it under Benefits or maybe under About the role? The "Why Join Us:" is about company culture and impact; could be considered part of Benefits? Not exactly. But we could include it as part of Benefits section (since it's about why join). However the Benefits section already lists benefits; we could add a paragraph about impact before the list. That would preserve info. We also have "Employee Benefits" list with subcategories. We'll need to output as a list. We need to ensure we don't include the "Acrisure is an Equal Opportunity Employer..." etc. Also need to remove the "Applicants may request reasonable accommodation..." etc. Also remove "Final candidates will be required to complete post-offer verification processes..." etc. Also remove "California Residents: Learn more..." etc. Also remove "Recruitment Fraud: Please visit here..." etc. Also remove "Welcome, your new opportunity awaits you." Also remove the "Why Join Us:" heading? We can keep the paragraph but not as heading if we merge into Benefits. Now let's extract substantive content: About Acrisure: (company description) - maybe we can include as part of About the role? Actually About the role is about the job, not company. But we could include a short paragraph about company as part of About the role? 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? 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 not add a heading like "About Acrisure". Instead we could incorporate that description into About the role section (maybe as a brief intro). But About the role should focus on the role. However we can include company description as part of About the role? Might be okay.
Better: Use About the role heading to contain the Job Summary plus maybe a brief about Acrisure? The Job Summary already includes role description. The About Acrisure description is separate but could be considered part of "About the role" as context. I'd include it as a paragraph before the Job Summary.
Now Responsibilities: we have several bullet groups. We need to convert each bullet line into
for section headings (like About the role, Responsibilities...). It doesn't forbid using other headings inside? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could treat those subheadings as plain text within
or maybe as . However we need to preserve all substantive information; we could keep them as Ticketing Operations & Hospitality Administration: then list.
But the instruction says use before each group of