Influencer Marketing Coordinator
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we must not repeat job title as heading. We need to map sections to appropriate headings. The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. But we can also use other headings? It says use for section headings (e.g. ...). Likely they expect we use those headings for sections we have. We have content that maps to:
- About the role: maybe "About Slate" is company description, not role. Could be "About the role" corresponds to "WHO WE ARE LOOKING FOR"? Actually "About the role" is typical heading for role description. The posting includes "WHO WE ARE LOOKING FOR" which describes the role. So we could use About the role
and put that content.
- Responsibilities: "WHAT YOU GET TO DO" corresponds to responsibilities.
- Requirements/Qualifications/Skills: "WHAT YOU BRING TO THE TEAM" includes experience, skills, etc. Could split into Requirements and Skills. But we can combine into one section maybe "Requirements" or "Qualifications". The instruction: prefer a few substantive sections over many thin ones. So we could have "Requirements" covering experience, skills, etc.
- Benefits: "WHY JOIN TEAM SLATE?" includes culture values, not exactly benefits like health insurance. There's no explicit benefits like pay, schedule. So we should not create Benefits section unless posting actually states them. It does not state benefits like health, PTO, etc. So we should omit Benefits.
- Pay: not stated, omit.
- Schedule: not stated, omit.
- Work Authorization: could be included as a short paragraph maybe under Requirements or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. ...). Likely they expect we use those headings for sections we have. We have content that maps to:
- About the role: maybe "About Slate" is company description, not role. Could be "About the role" corresponds to "WHO WE ARE LOOKING FOR"? Actually "About the role" is typical heading for role description. The posting includes "WHO WE ARE LOOKING FOR" which describes the role. So we could use About the role
and put that content.
- Responsibilities: "WHAT YOU GET TO DO" corresponds to responsibilities.
- Requirements/Qualifications/Skills: "WHAT YOU BRING TO THE TEAM" includes experience, skills, etc. Could split into Requirements and Skills. But we can combine into one section maybe "Requirements" or "Qualifications". The instruction: prefer a few substantive sections over many thin ones. So we could have "Requirements" covering experience, skills, etc.
- Benefits: "WHY JOIN TEAM SLATE?" includes culture values, not exactly benefits like health insurance. There's no explicit benefits like pay, schedule. So we should not create Benefits section unless posting actually states them. It does not state benefits like health, PTO, etc. So we should omit Benefits.
- Pay: not stated, omit.
- Schedule: not stated, omit.
- Work Authorization: could be included as a short paragraph maybe under Requirements or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Work authorization is metadata; we could fold into a short
under Requirements or maybe a separate short paragraph without heading? Probably better to include as a short
after Requirements. - Also there is "WHY JOIN TEAM SLATE?" which includes values statements; could be considered "About the company" or "Culture". Not a standard heading but we could maybe put under "About the role"? But we already used About the role for role description. Could create a section "About Slate" but not in list of allowed headings. 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 stick to those headings. However we need to preserve all substantive information; we cannot drop the "WHY JOIN TEAM SLATE?" content. We could incorporate it into an existing section like "About the role" or "Requirements"? Might be odd but permissible. Perhaps we can add a section "About the company" but not in list; risk of being considered not following instruction. The instruction: "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, just gives examples. Probably okay to use other headings as long as they are . But to be safe, we could map "WHY JOIN TEAM SLATE?" to "About the role" as part of role description? Hmm.
Better: Use headings: About the role (contains WHO WE ARE LOOKING FOR), Responsibilities (WHAT YOU GET TO DO), Requirements (WHAT YOU BRING TO THE TEAM + WORK AUTHORIZATION REQUIREMENT), and maybe "Culture" or "Why Join Team Slate" as a separate section with heading "Why Join Team Slate". That is not in the examples but still a heading. The instruction didn't forbid; it just gave examples. I'd include it.
We must not include boilerplate like EEO etc. Remove that. Also remove "WORK AUTHORIZATION REQUIREMENT" maybe we incorporate into Requirements.
We must not repeat job title as heading (the page already shows it). No job title given in snippet, but we won't add.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The snippet includes EEO statement at end; we must remove that.
Also remove "WHY JOIN TEAM SLATE?" values statements? Those are not boilerplate; they are substantive about culture. Keep.
We must preserve ALL substantive information; do not invent or summarize away detail.
Thus we need to extract:
About Slate: "At Slate, we’re building safe, reliable vehicles that people can afford, personalize and love—and doing it here in the USA as part of our commitment to reindustrialization. The spirit of DIY and customization runs throughout every element of a Slate, because people should have control over how their trucks look, feel, and represent them."
WHO WE ARE LOOKING FOR: "We are looking for a highly organized, culturally curious Influencer Marketing Coordinator to support Slate’s growing creator and influencer programs. This role will help execute partnerships from initial research and outreach through content delivery, campaign tracking, and reporting. The ideal candidate understands creator culture, has strong instincts for identifying talent across a wide range of communities, and is excited to build relationships with creators who can bring Slate’s story to life. They are detail-oriented, proactive, and comfortable managing multiple campaigns, timelines, and stakeholders in a fast-paced startup environment."
WHAT YOU GET TO DO: list of responsibilities (multiple sentences). We need to put each as
. But to be safe, we could map "WHY JOIN TEAM SLATE?" to "About the role" as part of role description? Hmm. Better: Use headings: About the role (contains WHO WE ARE LOOKING FOR), Responsibilities (WHAT YOU GET TO DO), Requirements (WHAT YOU BRING TO THE TEAM + WORK AUTHORIZATION REQUIREMENT), and maybe "Culture" or "Why Join Team Slate" as a separate section with heading "Why Join Team Slate". That is not in the examples but still a heading. The instruction didn't forbid; it just gave examples. I'd include it. We must not include boilerplate like EEO etc. Remove that. Also remove "WORK AUTHORIZATION REQUIREMENT" maybe we incorporate into Requirements. We must not repeat job title as heading (the page already shows it). No job title given in snippet, but we won't add. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The snippet includes EEO statement at end; we must remove that. Also remove "WHY JOIN TEAM SLATE?" values statements? Those are not boilerplate; they are substantive about culture. Keep. We must preserve ALL substantive information; do not invent or summarize away detail. Thus we need to extract: About Slate: "At Slate, we’re building safe, reliable vehicles that people can afford, personalize and love—and doing it here in the USA as part of our commitment to reindustrialization. The spirit of DIY and customization runs throughout every element of a Slate, because people should have control over how their trucks look, feel, and represent them." WHO WE ARE LOOKING FOR: "We are looking for a highly organized, culturally curious Influencer Marketing Coordinator to support Slate’s growing creator and influencer programs. This role will help execute partnerships from initial research and outreach through content delivery, campaign tracking, and reporting. The ideal candidate understands creator culture, has strong instincts for identifying talent across a wide range of communities, and is excited to build relationships with creators who can bring Slate’s story to life. They are detail-oriented, proactive, and comfortable managing multiple campaigns, timelines, and stakeholders in a fast-paced startup environment." WHAT YOU GET TO DO: list of responsibilities (multiple sentences). We need to put each as
- . The responsibilities are separated by periods; we can split into items.
Let's list them:
- Support the day-to-day execution of influencer campaigns, creator partnerships, events, vehicle experiences, and always-on programs.
- Research, identify, and vet creators across automotive, lifestyle, DIY, design, technology, entertainment, small business, and other culturally relevant communities.
- Manage creator outreach, communications, follow-ups, scheduling, and relationship details throughout the partnership lifecycle.
- Coordinate campaign logistics, including creator travel, event attendance, product or material shipments, content capture, and on-site support.
- Support the development of creator briefs, campaign materials, shot lists, and production schedules.
- Review creator concepts and content submissions for alignment with campaign objectives, brand guidelines, platform requirements, and agreed-upon deliverables.
- Monitor creator posts to ensure content is published accurately, on time, and with the correct tags, links, disclosures, and calls to action.
- Collect campaign results and work closely with analytics partners to support reporting, identify key learnings, and inform future creator selections.
- Monitor social platforms, emerging creators, internet culture, and content trends to identify timely opportunities for Slate.
WHAT YOU BRING TO THE TEAM: list of items (some are sentences). We'll split into bullet points.
- 1–3 years of experience in influencer marketing, social media, public relations, talent relations, experiential marketing, or a related field.
- Experience supporting influencer campaigns or creator partnerships from outreach through execution and reporting.
- Strong knowledge of Instagram, TikTok, YouTube, and emerging social platforms, including an understanding of how creator content and communities differ across each.
- Excellent written and verbal communication skills, with the ability to represent Slate professionally in creator and partner interactions.
- Strong organizational and project management skills, with exceptional attention to detail and follow-through.
- Proficiency in Excel, Google Sheets, PowerPoint, Google Slides, and project management tools.
- Familiarity with influencer marketing and social analytics platforms such as CreatorIQ, Sprout Social, or similar tools is a plus.
- Comfort working in a fast-paced startup environment where priorities can evolve quickly.
- Passion for creators, social media, internet culture, and the communities shaping culture both online and offline.
WORK AUTHORIZATION REQUIREMENT: "Applicants must be authorized to work in the United States on a permanent basis. We are unable to offer visa sponsorship at this time."
WHY JOIN TEAM SLATE? includes values statements: "At Slate, we’re fueled by grit, determination, and attention to detail. The start-up spirit of ingenuity and resourcefulness move our business forward. Team Slate fosters a culture of excellence, innovation, and mutual respect, and is motivated by shared principles. Safety First Delight Customers One Team Relentless Improvement Fast, Frugal, and Scrappy Respectful Collaboration Positive Legacy WE WANT TO WORK WITH PEOPLE THAT REFLECT THE COMMUNITIES IN WHICH WE OPERATE. Slate is proud to be an Equal Employment Opportunity and Affirmative Action employer. We do not discriminate based upon race, color, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, disability, age, veteran status, marital status, parental status, cultural background, organizational level, work styles, tenure and life experiences. Or for any other reason. Slate is committed to providing reasonable accommodation for qualified individuals with disabilities in our job application procedures. If you need assistance or an accommodation due to a disability, you may contact us at slate-talent_acquisition@slate.auto."
We need to remove EEO boilerplate etc. The values statements include EEO statement; we must remove that. Also remove the accommodation line? That's also EEO/accommodation boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should strip out the EEO statement and accommodation line. Keep the rest: "At Slate, we’re fueled by grit, determination, and attention to detail. The start-up spirit of ingenuity and resourcefulness move our business forward. Team Slate fosters a culture of excellence, innovation, and mutual respect, and is motivated by shared principles. Safety First Delight Customers One Team Relentless Improvement Fast, Frugal, and Scrappy Respectful Collaboration Positive Legacy WE WANT TO WORK WITH PEOPLE THAT REFLECT THE COMMUNITIES IN WHICH WE OPERATE."
We should keep that as a paragraph.
Now structure HTML:
- ... each
- ... each
About the role
WHO WE ARE LOOKING FOR content
Responsibilities
Requirements
Work authorization: Applicants must be authorized to work in the United States on a permanent basis. We are unable to offer visa sponsorship at this time.
Why Join Team Slate
Values statement (without EEO)
Optionally include About Slate? Could be part of About the role? But we have "About Slate" separate. Could add another section "About Slate" but not in examples. Might be okay. However we already used About the role for role description; we could add a separate