Jobs · Marketing · New York

Managing Video Editor (Video Podcast & Documentaries)

Mentor A Promise · New York, NY · 1 mo ago
MarketingVolunteer
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Mentor A Promise", "Position Overview", "Key Responsibilities", "Required Qualifications & Skills", "Preferred (Nice-to-Have) Qualifications", "What You'll Gain". Also maybe "How To Apply" but we must remove application instructions. So we exclude How To Apply. Also remove boilerplate about volunteering location constraints etc. Also remove EEO etc. Not present. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should map headings to these generic names? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those exact headings when appropriate. However we have specific sections like About Mentor A Promise, Position Overview, Key Responsibilities, Required Qualifications & Skills, Preferred Qualifications, What You'll Gain. We need to map them to the allowed headings? Probably we should use those headings as they appear, but the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It might be that we should use those headings as categories, but we can also use other headings if they match content? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not an exhaustive list. Likely we should use those exact headings when we have content for them. But we have content like "About Mentor A Promise" which is about the organization, not the role. Could map to "About the role"? Might be okay. However "About the role" is more about the position. We have "Position Overview". Could use "About the role". Similarly responsibilities -> "Responsibilities". Qualifications & Skills -> maybe combine into "Qualifications" and "Skills"? But we have both required and preferred. Could put under "Qualifications". Skills maybe separate? But we can combine. We must not repeat the job title as a heading. Also not put Job ID. We must preserve all substantive information. So we need to include all details from the posting except boilerplate. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Managing Video Editor (Video Podcast & Documentaries) ...

But we need to include description of Mentor A Promise? That's about organization. Could be under "About the role" or maybe a separate "About Mentor A Promise". But instruction says use those example headings; but we can also add other headings if needed? Safer to stick to those headings. However we risk losing some nuance if we map incorrectly. But we can include the content under appropriate headings. Let's map: - About Mentor A Promise (organization description) could go under "About the role"? Actually "About the role" is about the position, not org. But we could still include org description there as part of role context. Might be okay. - Position Overview: could be part of About the role as well. - Key Responsibilities: under

Responsibilities

with
  • ... - Required Qualifications & Skills: under

    Qualifications

    maybe also Skills. Could split:

    Qualifications

    for required qualifications, and

    Skills

    for skills? But they are intertwined. Could combine. - Preferred (Nice-to-Have) Qualifications: could be under

    Qualifications

    as a sublist? Or separate

    Preferred Qualifications

    but not in examples. Might be okay to add but risk violating instruction. However 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 says use h3 for section headings (giving examples). Likely they expect us to use those headings where applicable. If we have content that matches "Preferred Qualifications", we could still use

    Preferred Qualifications

    as it's a section heading. The examples are not exhaustive. So we can use any appropriate heading, but must be h3. Thus we can keep original headings: About Mentor A Promise, Position Overview, Key Responsibilities, Required Qualifications & Skills, Preferred (Nice-to-Have) Qualifications, What You'll Gain. All as h3. We must not include How To Apply. We must remove boilerplate: the lines about volunteering location constraints etc. Also remove "Edit with purpose — help shape stories..." maybe that's motivational but not boilerplate? It's part of posting but maybe considered a tagline; could keep? It's not navigation/legal/EEO. It's substantive? It's a call to action but not application instruction. Might keep as part of "What You'll Gain"? Actually it's a separate line: "Edit with purpose — help shape stories that honor humanity, amplify voices, and reflect the care at the heart of Mentor A Promise." That's like a tagline. Could be kept under "What You'll Gain" or as a separate paragraph. I'd keep it as a p under "What You'll Gain" maybe. Also "Thank you for your interest in volunteering with our organization. At this time, our volunteer opportunities are limited to individuals who are based in the United States. This limitation is due to legal, safeguarding, data-privacy, and programmatic requirements associated with our work. We appreciate your interest in our mission and your understanding of these constraints." This is boilerplate about volunteer location constraints; we should remove. Thus final HTML:

    About Mentor A Promise

    Mentor A Promise is a New York City–based nonprofit serving children and youth (ages 5–18) experiencing housing instability, grounded in the belief that every child is a Promise—full of potential, dignity, and possibility. We deliver consistent, high-quality programming across mentorship, literacy, social-emotional learning, and creative expression in shelters, schools, and community spaces, creating structured environments where students can grow, be seen, and build lasting skills. Through signature experiences like The Imagination Studio, The Kitchen Table, The Sound Lab, and The Story Space, we nurture academic development, emotional well-being, and creative voice, all within a trauma-informed, culturally responsive, and accessibility-centered framework. Our work prioritizes dignity-protective storytelling, consent-driven engagement, and deep community partnership, ensuring that how we serve is as intentional as whom we serve. We are not only addressing immediate needs - we are building pathways to confidence, belonging, and long-term opportunity, so every child has the support and foundation to carry their promise forward.

    Position Overview

    The Managing Video Editor is the creative and operational backbone of MAP’s editing team. Combining hands-on video and audio editing with team leadership, this role guides a small team of editors, sets quality and workflow standards, and ensures every episode and short-form piece meets MAP’s bar for care, clarity, and respect. The Managing Video Editor works closely with producers to translate raw interviews, B-roll, archival footage, and images into finished, platform-ready storytelling, while also reviewing team members’ cuts, giving constructive feedback, and keeping projects organized and on schedule. This is not fast-turnaround content editing. It is ethical storytelling through visual craft—led with rigor, mentorship, and organization.

    Key Responsibilities

    • Team Leadership & Workflow Management: Lead, coach, and coordinate a small team of volunteer editors, assigning episodes and short-form deliverables based on skill and availability.
    • Establish and maintain a consistent editorial and technical review process, including notes, revision rounds, and final sign-off before delivery to producers.
    • Build and maintain organized project structures (bins, naming conventions, version control) so multiple editors can work efficiently across shared media.
    • Set and track deadlines across the editing pipeline, flagging bottlenecks early and reallocating work as needed to keep episodes on schedule.
    • Onboard new editors to MAP's brand, tone, and post-production standards, and serve as the go-to resource for technical or editorial questions.
    • Video Editing: Craft compelling video podcast episodes and short documentaries from interviews, B-roll, archival footage, images and graphics.
    • Identify the strongest moments in interviews and build narratives that resonate.
    • Use pacing, music, visuals, and transitions to keep viewers engaged.
    • Incorporate captions, titles, lower thirds, and motion graphics consistent with Mentor A Promise's brand.
    • Perform color correction and basic post-production finishes.
    • Create platform-specific versions for YouTube, Podcast Platforms Shorts, Instagram, TikTok, and LinkedIn.
    • Ability to research, source, and organize high-quality, royalty-free music, sound effects, and archival media.
    • Maintain meticulous tracking of usage rights, licensing terms, and attribution requirements across the team's projects.
    • Audio Editing (Podcasts & Sound Design): Edit full-length video podcast episodes for pacing, clarity, and engagement ensuring smooth transitions between segments, intros, outros, and sponsor reads.
    • Clean and enhance dialogue while maintaining a natural conversational flow.
    • Incorporate music, and transition and clean up audio to support the story.
    • Deliver polished, well balanced audio ready for publication.
    • Clean up raw podcast recordings by removing filler words, awkward pauses, and background noise while maintaining a natural conversational flow.
    • Source, license, and layer background music and sound effects to elevate the narrative tone and overall production value.
    • Balance audio levels and export final master files to industry-standard loudness levels (e.g., -16 LUFS for podcasts).

    Required Qualifications & Skills

    • Minimum 2-3 years of proven experience editing both narrative audio podcasts and documentary-style video content, including experience reviewing or mentoring other editors.
    • Demonstrated ability to lead a small team assigning work, giving clear and constructive feedback, and holding a consistent creative and technical bar across multiple editors' output.
    • Software Proficiency: Adobe Premiere Pro, DaVinci Resolve or equivalent professional video editing software.
    • A strong editorial ear and eye—knowing how to cut a scene or an interview to maximize emotional impact and keep the audience engaged.
    • Excellent organization skills for managing large media assets across multiple editors, syncing multi-cam footage, and organizing multi-track audio.
    • Ability to take direction from producer notes, incorporate feedback gracefully, translate that feedback into clear guidance for the team, and work efficiently under tight deadlines.

    Preferred (Nice-to-Have) Qualifications

    • Prior experience managing or leading a team of editors, in a volunteer or professional setting.
    • Familiarity with Riverside recordings.
    • Experience working with nonprofit, journalism, or documentary content.

    What You'll Gain

    • Leadership experience shaping both the creative output and the team behind a growing storytelling platform.
    • Meaningful storytelling experience with real community impact.
    • Portfolio-ready podcast and digital media work, including team-lead credit.
    • Collaboration with producers, hosts, and creative teams.
    • Professional references and letters of recommendation.

Similar jobs

Podcast Video Editor

Vox MediaNew York, NY· 1 mo ago
Marketing$76k–$80k/yrapply on app.greenhouse.io

Video Editors

HandshakeUnited States· 4 mo ago
RemoteWritingapply on app.joinhandshake.com