Motion Design Lead

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description (About the role) - we can treat as About the role. Responsibilities: list of accountabilities. Requirements: listed. Qualifications: maybe overlapping with requirements; but we can treat Requirements as qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content. We have content: description (intro) -> About the role. Accountabilities list -> Responsibilities. Requirements list -> Requirements. Qualifications: maybe we can treat the education and experience as Qualifications, but we already have Requirements covering experience, portfolio, proficiency, etc. Could split: Requirements (experience, portfolio, proficiency) and Qualifications (education, plus plus). But we need to avoid thin sections. Could combine into Requirements and Qualifications both present. Skills: maybe list of specific software proficiencies etc. Could be part of Requirements. But we could create Skills section listing software: Cinema 4D, Redshift/Octane, After Effects, Figma, Unreal Engine 5/Unity, Lottie, Rive, Spline, Houdini/Maya, Premiere, Audition, DaVinci Resolve, AI platforms (NanoBanana, Midjourney, Topaz, Firefly). However that may be redundant. Benefits: present: Salary range, Remote position, Opportunity to work across..., Exposure to advanced AI..., Collaborative environment..., Opportunity to contribute..., Inclusive and supportive work environment... Pay: we have salary range; could be separate Pay section. But Benefits already includes salary range. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and remote work (schedule? remote). It does not explicitly state schedule (like full-time, hours). So we can include Pay section with salary range, and Benefits section with other benefits. Or we could combine Pay into Benefits. But we have both Pay and Benefits headings allowed; we need to include only if real specific content. Salary range is specific; we can put in Pay. Benefits: remote, opportunity, exposure, collaborative environment, inclusive environment. Those are benefits. Schedule: not mentioned (no mention of full-time/part-time/hours). So omit Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. We must preserve all substantive information. So we need to keep the description, responsibilities list, requirements list, qualifications (education/experience), skills (software list), benefits, pay. We need to format using

for headings,

• for lists,

  for prose. We must not include markdown code fences. Let's extract content. About the role: The initial paragraph(s) before "Accountabilities". Let's capture: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Motion Design Lead based in United States. This role leads motion design across digital, web, advertising, video, and emerging immersive experiences. You will bridge traditional 2D motion design with advanced 3D workflows and AI-powered creative technologies to create high-fidelity visual storytelling. The position combines creative direction, hands-on craft, technical innovation, and production excellence across a broad range of formats. You will partner closely with Creative Directors and multidisciplinary teams to transform concepts into compelling, polished visual experiences. The role offers significant scope to experiment with generative AI, real-time rendering, spatial computing, and evolving production techniques. You will help establish motion strategy and maintain a high standard of visual quality across animation and VFX pipelines. This is a remote U.S. opportunity for an experienced creative technologist who wants to push the boundaries of motion, 3D, and AI-assisted storytelling." We should remove the first sentence about partner company? It's part of description but maybe considered boilerplate? It's not navigation/legal/EEO. It's substantive about the role being via partner. Keep it. Responsibilities: list under "Accountabilities". Each bullet starts with a verb. We'll capture each. List: - Serve as a key creative collaborator across digital, web, advertising, and video assignments, aligning motion solutions with broader campaign and creative objectives. - Develop and execute high-end motion graphics, 3D assets, cinematic environments, and spatial experiences for broadcast, web, branded content, and emerging digital platforms. - Integrate generative AI, neural rendering, automated rotoscoping, and AI-assisted pre-visualization into creative and production workflows. - Create mood boards, style frames, storyboards, and visual concepts that explore depth, physics, spatial design, and multi-layered narratives. - Lead look development, lighting, texturing, modeling, and rendering to deliver premium and brand-consistent 3D work. - Partner with Creative Directors and multidisciplinary teams to develop visual stories from initial concepts through final production. - Maintain high standards of design excellence, visual craft, technical execution, and quality control across animation and VFX pipelines. - Present and communicate creative and technical concepts clearly to stakeholders, explaining the strategic rationale behind visual and production decisions. - Drive technical innovation by exploring emerging technologies such as real-time rendering, spatial computing, and AI-assisted creative workflows. - Help streamline production processes through new tools, technologies, and more efficient creative workflows. Requirements: list after "Requirements". Let's capture: - At least 6 years of motion design experience with a strong emphasis on advanced 3D workflows within integrated agencies or production environments. - A strong portfolio demonstrating original conceptual thinking, motion graphics, and high-fidelity 3D visual effects across advertising and digital campaigns. - Advanced proficiency in Cinema 4D with Redshift or Octane, After Effects, and Figma. - Strong 3D generalist capabilities across modeling, lighting, texturing, and rendering. - Demonstrated experience incorporating AI platforms such as NanoBanana, Midjourney, Topaz, and Firefly into production workflows for asset generation, texture enhancement, or upscaling. - Strong communication and collaboration skills, with experience partnering closely with Creative Directors and multidisciplinary teams. - Ability to translate conceptual ideas into polished visual narratives while balancing creative ambition with technical execution. - Bachelor’s degree in Graphic Design, Animation, Film, or a related field, or equivalent practical experience. - Experience with Unreal Engine 5 or Unity and interactive motion platforms such as Lottie, Rive, or Spline is a plus. - Advanced VFX experience with Houdini or Maya, AR/VR/XR spatial design experience, and proficiency with Premiere, Audition, or DaVinci Resolve are additional advantages. - Applicants must be authorized to work in the United States; this role is not available for hire or work in New Mexico or Hawaii. We might separate Qualifications: education and degree etc. But we can keep as Requirements. Skills: maybe list software proficiencies etc. Could extract from requirements: Cinema 4D, Redshift/Octane, After Effects, Figma, Unreal Engine 5/Unity, Lottie, Rive, Spline, Houdini/Maya, Premiere, Audition, DaVinci Resolve, AI platforms (NanoBanana, Midjourney, Topaz, Firefly). Also mention 3D generalist capabilities, motion design, etc. But we already have those in Requirements; making a separate Skills section may be thin. However we could create Skills section listing the specific tools and technologies. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Skills into Requirements and not create separate Skills. But we have to include sections only when posting has real specific content for it. If we don't have a distinct Skills section beyond what's in Requirements, we could omit Skills. Qualifications: we could treat education and degree as Qualifications separate from Requirements (experience). But we already have education in Requirements list. Could split: Requirements (experience, portfolio, proficiency) and Qualifications (education, plus plus). However that may create thin sections. But we have enough content for both: Requirements (experience, portfolio, proficiency, AI platforms, communication) and Qualifications (education, Unreal Engine/Unity, interactive platforms, VFX experience, AR/VR/XR, Premiere etc, work authorization). That seems substantive. Let's decide: - About the role (prose) - Responsibilities (list) - Requirements (list) focusing on experience, portfolio, core proficiencies, AI platforms, communication, ability to translate ideas. - Qualifications (list) focusing on education, Unreal Engine/Unity, interactive platforms, VFX experience, AR/VR/XR, Premiere/Audition/DaVinci, work authorization. - Skills (list) maybe focusing on specific software: Cinema 4D, Redshift/Octane, After Effects, Figma, Unreal Engine 5, Unity, Lottie, Rive, Spline, Houdini, Maya, Premiere, Audition, DaVinci Resolve, NanoBanana, Midjourney, Topaz, Firefly. Could be considered Skills. But we already have many of those in Requirements/Qualifications; might be redundant. However we could keep Skills as a concise list of tools. But the instruction: "Prefer a few substantive sections over many thin ones." Having Skills may be thin if it's just a list of tools already covered. Better to omit Skills and incorporate tools into Requirements/Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have content for Benefits and Pay. Benefits: list after "Benefits". Let's capture: - Salary range of $108,000–$142,000 USD. - Remote position within the United States, subject to the stated location restrictions. - Opportunity to work across digital, advertising, branded content, immersive experiences, and emerging creative technologies. - Exposure to advanced AI-assisted workflows, 3D production, real-time rendering, and spatial computing. - Collaborative environment with Creative Directors and multidisciplinary creative, design, and technology teams. - Opportunity to contribute to high-impact visual experiences while expanding creative and technical capabilities. - Inclusive and supportive work environment with reasonable accommodations available throughout the recruitment and employment process. Pay: we could separate salary range as Pay, and other items as Benefits. But the salary range is also in Benefits list. To avoid duplication, we could put salary range in Pay section, and other items in Benefits. Thus: Pay: Salary range of $108,000–$142,000 USD. Benefits: remote position, opportunity to work across..., exposure to..., collaborative environment..., opportunity to contribute..., inclusive and supportive work environment... Schedule: none. Now we need to ensure we don't include boilerplate like "This position is listed on behalf of a partner company..." maybe keep as it's substantive about partner. It's not navigation/legal. Keep. Now produce HTML. Structure:

  About the role

  ... paragraph(s) ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Pay

  Salary range of $108,000–$142,000 USD.

  Benefits

  • Remote position within the United States, subject to the stated location restrictions.
  • Opportunity to work across digital, advertising, branded content, immersive experiences, and emerging creative technologies.
  • Exposure to advanced AI-assisted workflows, 3D production, real-time rendering, and spatial computing.