Manager, Production Technology

We need to output only HTML fragment with sections: About the role? Actually the posting includes sections: ABOUT VAYNERX, ABOUT VAYNERMEDIA, Who we are, Who you are, Role Summary, Experience & Qualifications, then hybrid note, then benefits and base salary. We must use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings appropriately. The instruction: "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. We need to include sections only when posting has real, specific content. So we need to decide which sections apply. We have content about the role: description of responsibilities etc. Could map to "About the role" (maybe a summary), "Responsibilities", "Requirements"/"Qualifications", "Skills", "Benefits", "Pay". Also "Schedule" maybe not present (hybrid note). The posting mentions hybrid and workplace attendance requirements, but not schedule specifics. Should we include Schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state hybrid work arrangement, but not schedule specifics like hours. Might be considered schedule? Probably not; better to omit Schedule if not explicit. We have Pay: Base Salary $90,000—$110,000 USD. So we can include Pay section. Benefits: list of benefits: Employer-sponsored 401k with match, Medical, Dental, and vision coverage, Unlimited PTO, Caregiver (Parental) Leave, Health and Wellness benefits. So Benefits section. Qualifications: Experience & Qualifications section includes experience, qualifications. Could map to Qualifications. Skills: maybe we can include Skills from the list: proficiency in software, troubleshooting, communication, etc. Could be separate Skills section. Responsibilities: Role Summary includes many responsibilities. Could map to Responsibilities. About the role: maybe a brief overview from Who you are and Role Summary? Could combine. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, legal, etc. Also remove navigation/cookie etc. Not present. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... summary ...

Responsibilities

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

Base Salary $90,000—$110,000 USD

We must ensure we don't create sections with filler. All sections have content. Now extract content. From posting: ABOUT VAYNERX and ABOUT VAYNERMEDIA: maybe not needed for role? Could be considered "About the role"? But they are company overview. Might be considered part of About the role? However instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could treat company overview as part of About the role? Might be okay. But we need to preserve all substantive information. So we need to include that info somewhere. Could put in About the role paragraph. Let's parse: ABOUT VAYNERX: description. ABOUT VAYNERMEDIA: description. Who we are: VaynerX Production Services is the centralized engine... Who you are: We're looking for a solutions-oriented Manager, Production Technology... Role Summary: bullet list of responsibilities. Experience & Qualifications: list. Hybrid note: "This position is currently designated as hybrid and is subject to the Company's workplace attendance and in-office work requirements, as in effect from time to time. The Company reserves the right to modify these requirements at any time." Then legal boilerplate (EEO etc) to remove. Then benefits list. Then Base Salary. We need to exclude EEO etc. Now craft sections. About the role: combine company overview and who you are? Could be two paragraphs. Responsibilities: from Role Summary bullet points. Qualifications: from Experience & Qualifications. Skills: maybe separate from Qualifications? Could merge but we need Skills section if we have distinct skill items. The Experience & Qualifications includes skills like proficiency in software, troubleshooting, communication, etc. Could treat as Skills. But we already have Qualifications; maybe we can treat Qualifications as experience and requirements, and Skills as technical skills. Let's extract: Experience & Qualifications bullet points: - 6-8+ years of experience in post-production technical roles, assistant editing, and editorial workflow management - Strong working knowledge of commercial editorial pipelines from ingest through final delivery, with experience supporting editorial teams in high-volume commercial or agency environments - Advanced proficiency in post-production software including Adobe Premiere Pro, DaVinci Resolve, Avid Media Composer, and After Effects - Strong understanding of media formats, codecs, color pipelines, and delivery specifications - Proven experience using Frame.io, including training teams and establishing workflows at scale - Experience with shared storage and cloud-based workflows (EditShare, LucidLink, etc.) - Exceptional troubleshooting and problem-solving skills within fast-paced production environments - Ability to translate technical workflows into clear, practical guidance for creative teams, with strong documentation and communication skills - Willingness to respond to production needs that may arise outside of standard working hours We could split: Qualifications: years of experience, knowledge of pipelines, experience using Frame.io, experience with shared storage, willingness to respond outside hours. Skills: proficiency in software, understanding of formats/codecs, troubleshooting, ability to translate workflows, documentation/communication. But it's okay to keep all under Qualifications and omit Skills if we think it's redundant. However instruction: prefer a few substantive sections over many thin ones. So maybe combine into Qualifications and Skills? But we need to follow headings list; we can include Skills if we have content. Let's decide: We'll have Qualifications (experience and knowledge) and Skills (technical proficiencies). That yields two sections. Responsibilities: from Role Summary bullet points. Let's extract Role Summary bullet points (they are sentences separated by line breaks): - Oversee the day-to-day operational health of editorial workflows across active productions, acting as lead assistant editor when projects require hands-on media ingest, prep, conform, and delivery - Ensure projects are set up correctly within internal systems, including folder structures, media organization, and workflow templates - Troubleshoot workflow issues during active productions to minimize downtime and maintain creative momentum - Leads naming archive and retention policy, storage capacity monitoring, proxy and offline/online workflows, and dailies handling. - Serve as the primary technical resource for editors, assistant editors, and production teams, providing guidance on media management, project organization, and editorial best practices - Partner with editorial teams to ensure projects are properly prepared for finishing, conform, color, sound, and delivery - Train and monitor editors, assistant editors, and production staff on internal post-production workflows and best practices, and help onboard new team members and freelancers - Maintain documentation for editorial pipelines, project setup standards, and media management procedures - Serve as the global lead for Frame.io implementation, training, and workflows across VaynerX, including account and project structure, permissions, integrations with editorial tools, documentation, and ongoing support for all entities and pods - Implement workflows and systems designed by the Director of Technology, and help test and deploy new tools, plug-ins, and workflow solutions that support scalable production pipelines - Ensure media is properly organized, backed up, and archived according to internal protocols, working alongside assistant editors to maintain project hygiene and consistent file organization - Work closely with Production, Editorial, and Post teams to ensure technical workflows align with production timelines - Liaise with internal IT and technical support teams when issues impact editorial productivity - Identify workflow inefficiencies and recurring technical challenges across productions, and partner with the Director of Technology to recommend solutions and refine post-production workflows as the department scales - Stay current on evolving editorial technologies and tools that could improve production efficiency Now Benefits list: - Employer-sponsored 401k with match - Medical, Dental, and vision coverage - Unlimited PTO - Caregiver (Parental) Leave - Health and Wellness benefits Now Pay: Base Salary $90,000—$110,000 USD Now About the role: combine company overview and who you are. Company overview: ABOUT VAYNERX: VaynerX is a family of companies building brands for the now. Founded by Chairman Gary Vaynerchuk in January 2017, the modern-day parent company is home to relevance-driving businesses including VaynerMedia, ChukMedia, Tamara Group, Gallery Media Group, Tingley Lane Trading, and VaynerSpeakers. ABOUT VAYNERMEDIA: VaynerMedia is a global integrated creative and media agency, built for today's consumers. As the Modern Agency of Record, it understands the nuances of today's attention landscape, empowering brands to win attention, drive relevance, and deliver business results. Founded in 2009, by Gary Vaynerchuk, the independently owned agency operates in 15 offices worldwide, including Amsterdam, Bangkok, Chicago, New Delhi, Kuala Lumpur, London, Los Angeles, Mexico City, Miami, New York, Tokyo, Toronto, Singapore, and Sydney. VaynerMedia is part of the VaynerX family of companies. Who we are: VaynerX Production Services is the centralized engine that powers production excellence across all VaynerX entities and pods. While each pod is empowered to execute production independently, Production Services ensures that the entire system runs cohesively: operationally, technically, financially, and strategically. This team is not embedded within pods; it operates horizontally across the organization to enable consistency, scalability, and best-in-class production practices across all disciplines and entities. Who you are: We're looking for a solutions-oriented Manager, Production Technology to support the day-to-day workflows that power editorial and post-production at VaynerX. This role sits at the intersection of creative production and technical execution, keeping projects moving smoothly through the editorial pipeline, giving teams the tools and support they need, and leading internal Frame.io and editorial processes across the company. This is a unique hybrid role, where your tasks will span hands on assistant editing to big picture policy scaling. Working closely with the Director of Technology, you'll support editors, assistant editors, and production teams by implementing best practices, troubleshooting workflow issues, and anticipating challenges before they become problems. The ideal candidate is deeply familiar with commercial editorial workflows and thrives in fast-moving environments where technical clarity directly impacts creative output. We can combine into a paragraph or two. Now we must not include boilerplate: EEO etc. Also remove the hybrid note? The hybrid note is substantive: "This position is currently designated as hybrid and is subject to the Company's workplace attendance and in-office work requirements, as in effect from time to time. The Company reserves the right to modify these requirements at any time." This could be placed under Schedule? But we decided not to create Schedule unless explicit schedule. However hybrid note is about work arrangement; maybe we could include it under About the role or Responsibilities? Could add a sentence in About the role about hybrid. But we have no Schedule section; we could incorporate hybrid note into About the role paragraph. But we must not invent sections. We can include