Event Technology Coordinator
FIRST · New York, NY · 1 mo ago
HybridManagement$66k–$73k/yrVolunteer
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include only sections with real specific content. We need to parse the posting.
Let's extract content:
Company description: "Building a Brand starts with a Story FIRST is a leading global brand experience agency providing Content, Creative, Digital Technology, Management & Delivery, and Data & Insights services. For 30 years, we have utilized three flexible delivery models: Embedded teams, Corporate Campus operations, and a Full-Service Agency. Managing over 37,000 events & projects annually across 110 countries, FIRST serves 130+ brands, specializing in Fortune 500 companies within the Financial Services, Technology, Healthcare, Media, and Professional Services sectors. FIRST is part of the broader Encore family of companies. Encore is a global leader in event production and technology. Consistently recognized for excellence, recent honors include 2026 Chief Marketer Agency of the Year, the Ad Net Zero Award for sustainability, and more. Location: Hybrid 2 days in NYC office (subject to change at any time to 5 days.) Learn more at www.firstagency.com"
That's about the company; could be "About the role"? Actually "About the role" is typical heading for description of role. But we have description of company and location. Could treat as "About the role" or "About the company". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly.
We have "What You Would Get To Do" which is responsibilities. Then bullet list of contributions (list). Then "What We Are Looking For" includes requirements/qualifications/skills. Then benefits and pay.
We need to avoid boilerplate like EEO, accommodation repeated lines, application instructions, etc.
We must not include duplicated lines. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to preserve all substantive information.
Let's extract sections:
- About the role / About the company: Could combine company description and location. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include only sections with real specific content. We need to parse the posting.
Let's extract content:
Company description: "Building a Brand starts with a Story FIRST is a leading global brand experience agency providing Content, Creative, Digital Technology, Management & Delivery, and Data & Insights services. For 30 years, we have utilized three flexible delivery models: Embedded teams, Corporate Campus operations, and a Full-Service Agency. Managing over 37,000 events & projects annually across 110 countries, FIRST serves 130+ brands, specializing in Fortune 500 companies within the Financial Services, Technology, Healthcare, Media, and Professional Services sectors. FIRST is part of the broader Encore family of companies. Encore is a global leader in event production and technology. Consistently recognized for excellence, recent honors include 2026 Chief Marketer Agency of the Year, the Ad Net Zero Award for sustainability, and more. Location: Hybrid 2 days in NYC office (subject to change at any time to 5 days.) Learn more at www.firstagency.com"
That's about the company; could be "About the role"? Actually "About the role" is typical heading for description of role. But we have description of company and location. Could treat as "About the role" or "About the company". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly.
We have "What You Would Get To Do" which is responsibilities. Then bullet list of contributions (list). Then "What We Are Looking For" includes requirements/qualifications/skills. Then benefits and pay.
We need to avoid boilerplate like EEO, accommodation repeated lines, application instructions, etc.
We must not include duplicated lines. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to preserve all substantive information.
Let's extract sections:
- About the role / About the company: Could combine company description and location. Use About the role
maybe. Or "About the company". But instruction says use headings e.g. About the role, Responsibilities, etc. So we can use About the role for company overview and location.
- Responsibilities: from "What You Would Get To Do" and the bullet list after that (the contributions). Actually "What You Would Get To Do" is a heading; then bullet list of contributions. So responsibilities section includes that paragraph and list.
- Requirements / Qualifications / Skills: The "What We Are Looking For" includes a paragraph about experience not always looking like we describe it, accommodation lines (duplicate), interview process, etc. Then list of qualifications: 1+ years experience..., Bachelor's Degree preferred, Intermediate proficiency..., Experience with registration website platforms..., General knowledge of HTML..., Able to manage multiple projects..., Good written..., Motivated..., Flexible..., etc. Also note about travel 10-20% etc.
We need to separate maybe into Requirements (experience, education) and Skills (technical, soft). But we can combine into one section "Requirements" if content is substantive. However instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills if distinct.
But we have also "Benefits" section: list of benefits after "At FIRST, we believe that our success is driven..." includes medical, dental, vision, 401(k), etc. Also "Global Opportunities" etc. Also "United States Residents: The base pay for this position ranges from $66,300.00 - $72,785.00. This role is also eligible for an annual discretionary bonus." That's pay.
We also have schedule? Not mentioned besides hybrid location (2 days in NYC office). That's location not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting actually states them. It does not state schedule explicitly, so we omit Schedule.
We need to avoid duplication: accommodation lines appear twice; we should keep only one instance? The instruction: remove duplicated lines. So we should include accommodation request line only once.
Also remove application instructions: "Please be aware that we know experience does not always look like we describe it. If you believe you would be an excellent fit for this role, please apply - we would love to see how you could fit at FIRST." That's basically encouragement to apply; might be considered application instruction? It's not exactly instruction to apply but encourages applying. Might be considered boilerplate? The instruction says remove application instructions. This line is more of a encouragement; but could be considered part of "What We Are Looking For". Might keep as part of that section? It's not a requirement. Might be considered fluff. Safer to remove it as it's not substantive about role. Also the duplicate accommodation lines: we can keep one.
Also "As part of the interview process, you might be asked to complete a short written assessment to demonstrate your skill set." That's substantive about interview process; could be kept under Requirements or maybe separate? Could be part of Requirements (selection process). Keep.
Now we need to format lists with - . For responsibilities list, we have bullet points after "What You Would Get To Do". Let's capture them exactly:
- Support the team with event registration websites, app builds and all technological aspects of our events
- Database management to ensure consistency in information, accuracy of new and existing data, and list generation
- Effectively communicate with internal and external clients via available communication lines; responding to all client queries within the agreed service level agreements
- Assist in contacting clients for relevant information pertaining to the event
- Coordination of name badges, tent cards, place cards, departure notices, email confirmations, agenda, signage etc. where appropriate
- Lead onsite registration procedures, including training temp staff and monitoring attendee participation.
- Travel periodically to oversee attendee logistics and registration for offsite events.
- Create and distribute post event client surveys
- List manipulation to provide team members with relevant registration data, year on year statistics, and insight into varied elements and event analytics
- Track and maintain time spent to projects to accurately reflect the work being done
We need to preserve all substantive information; keep as is.
Now Requirements/Qualifications/Skills list:
From "What We Are Looking For" after the fluff:
- 1+ years of experience in Attendee Data Management and Event Technology, including entry level meeting planning and coordination with registration and event technology or relevant internship experience preferred
- Bachelor's Degree preferred
- Intermediate proficiency in Microsoft Office, with a focus on Excel
- Experience with registration website platforms such as Cvent, Splash, Certain, Aventri, Eventbrite other registration website platforms preferred, but not required
- General knowledge of HTML and CSS is a plus, but not required
- Able to manage multiple projects simultaneously
- Good written and oral communication skills at all levels
- Motivated, self-starter, ability to take direction and work independently; ability to think innovatively
- Flexible and willing to work outside of normal business hours (evenings, weekends) and travel (10-20%) when required to be on-site at events
Also we have the interview assessment line: "As part of the interview process, you might be asked to complete a short written assessment to demonstrate your skill set." Could be included as a note.
Also the accommodation line: "Please contact recruiting@firstagency.com if you need an accommodation at any stage of the recruitment process." (duplicate). We'll keep one.
Now Benefits list:
- Medical, Dental & Vision, which includes the option of a high deductible health plan (HDHP) with a health savings account (HSA)
- 401 (k)
- Five Flexible Spending Accounts Options
- Generous Paid Time Off Allowance
- Employee Assistance Program (EAP)
- Life, Disability & Pet Coverages
- Wellness Stipend
- Mobile Phone Allowance
- Complimentary access to Headspace, Teladoc, Maven, Rocket Lawyer, Mobilo & more
- Aura Identity Theft Protection
- Discretionary Bonus Structure
- Global Opportunities: With a presence in 7 countries worldwide, including headquarters in London, New York, and Singapore, you may have the opportunity to work on exciting projects across different locations.
Also maybe "United States Residents: The base pay for this position ranges from $66,300.00 - $72,785.00. This role is also eligible for an annual discretionary bonus." That's pay.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce:
About the role
... company description and location ...
Responsibilities
What You Would Get To Do
...
But maybe we shouldn't repeat the heading "What You Would Get To Do" as a paragraph; we could just have responsibilities section with intro paragraph then list. The instruction: Use for prose. So we can have a short prose sentence: "The Event Technology Coordinator is responsible for assisting the event technology team with registration websites and database management, ensuring consistency in information, accuracy of new and existing data, and list generation. This role may also need to provide support to the event delivery team needing assistance with event and meeting coordination. Limited domestic and/or international travel may be required with this role." That's from the earlier paragraph. Then the list.
Thus responsibilities section:
Responsibilities
... intro ...
...list...
Now Requirements section: Could be Requirements
... maybe a short intro about what we are looking for (the fluff about experience not always looking like we describe it, accommodation request, interview assessment). But we need to keep substantive info: we can include a paragraph: "Please be aware that we know experience does not always look like we describe it. If you believe you would be an excellent fit for this role, please apply - we would love to see how you could fit at FIRST. As part of the interview process, you might be asked to complete a short written assessment to demonstrate your skill set. Please contact recruiting@firstagency.com if you need an accommodation at any stage of the recruitment process." That's the combined fluff but we need to ensure not duplicate accommodation line. We'll include once.
Then
list of requirements/qualifications/skills.
Now Benefits: Benefits
...list...
Pay: Pay
United States Residents: The base pay for this position ranges from $66,300.00 - $72,785.00. This role is also eligible for an annual discretionary bonus.
We should not include Schedule.
Check for any duplicated content: we removed duplicate accommodation line.
Check for any boilerplate: EEO statements at end: we need to remove them. The posting ends with a long EEO statement. Must remove.
Also remove "enerbahçe"? Not relevant.
Now ensure we preserve all substantive information: Did we miss any? Let's review original text for any other substantive bits not captured.
Original text sections:
- Opening paragraph about FIRST (company description). We captured.
- "Location: Hybrid 2 days in NYC office (subject to change at any time to 5 days.) Learn more at www.firstagency.com" We included location in About the role paragraph.
- "What You Would Get To Do" paragraph: we used as intro to responsibilities.
- The bullet list of contributions: we captured.
- "What We Are Looking For" paragraph: we captured the fluff lines (experience
About the role
... company description and location ...
Responsibilities
What You Would Get To Do
- ...
for prose. So we can have a short prose sentence: "The Event Technology Coordinator is responsible for assisting the event technology team with registration websites and database management, ensuring consistency in information, accuracy of new and existing data, and list generation. This role may also need to provide support to the event delivery team needing assistance with event and meeting coordination. Limited domestic and/or international travel may be required with this role." That's from the earlier paragraph. Then the list. Thus responsibilities section:
Responsibilities
... intro ...
- ...list...
Requirements
... maybe a short intro about what we are looking for (the fluff about experience not always looking like we describe it, accommodation request, interview assessment). But we need to keep substantive info: we can include a paragraph: "Please be aware that we know experience does not always look like we describe it. If you believe you would be an excellent fit for this role, please apply - we would love to see how you could fit at FIRST. As part of the interview process, you might be asked to complete a short written assessment to demonstrate your skill set. Please contact recruiting@firstagency.com if you need an accommodation at any stage of the recruitment process." That's the combined fluff but we need to ensure not duplicate accommodation line. We'll include once. Then
- list of requirements/qualifications/skills.
Now Benefits:
Benefits
- ...list...
Pay
United States Residents: The base pay for this position ranges from $66,300.00 - $72,785.00. This role is also eligible for an annual discretionary bonus.
We should not include Schedule. Check for any duplicated content: we removed duplicate accommodation line. Check for any boilerplate: EEO statements at end: we need to remove them. The posting ends with a long EEO statement. Must remove. Also remove "enerbahçe"? Not relevant. Now ensure we preserve all substantive information: Did we miss any? Let's review original text for any other substantive bits not captured. Original text sections: - Opening paragraph about FIRST (company description). We captured. - "Location: Hybrid 2 days in NYC office (subject to change at any time to 5 days.) Learn more at www.firstagency.com" We included location in About the role paragraph. - "What You Would Get To Do" paragraph: we used as intro to responsibilities. - The bullet list of contributions: we captured. - "What We Are Looking For" paragraph: we captured the fluff lines (experience