LEAD EDITOR

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About Harp & Sling (company description), About The Role (role description), Responsibilities (multiple subheadings), Required Skills And Experience (technical, editorial, collaboration), Who You Are (culture fit), Core Values, Schedule and Location (Full Time or Freelance, Hybrid, DFW or Remote), Compensation: "Competitive" (but not specific). Also "Compensation Competitive" is vague; we should not create Pay section unless posting actually states them. It says "Compensation Competitive" which is not a specific number or range; it's vague like "commensurate with experience". According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay section. Benefits: none specific. Schedule: we have "Schedule Full Time or Freelance Type Hybrid Location DFW or Remote". That's schedule and location info. We can create a Schedule section with that content. Also maybe a Location subsection? But we only have headings for Schedule. Could embed location in schedule section. Or we could create a separate section? Not in list. We'll put schedule info under

Schedule

with a

. We need to avoid repeating job title as heading. Also we should not include Job ID etc. We need to preserve all substantive information. So we need to include About Harp & Sling, About The Role, Responsibilities (with subpoints), Required Skills And Experience (maybe split into Skills? but we have a Skills heading allowed). The posting has "Required Skills And Experience" with subcategories Technical & Post-Production, Editorial & Story, Collaboration & Process. Also "Who You Are (and this matters)" and "Core Values". Those could go under Qualifications or Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: includes About Harp & Sling and About The Role? Actually "About the role" heading could contain the role description. The company description could be maybe part of About the role or we could put under About the role as well. But we have separate "About Harp & Sling" which is company overview. Could we put that under About the role? Might be okay. Or we could create a separate section like "About the company" but not in allowed headings. Probably we should include company description under About the role heading as it's about the role context. Or we could create a

before any heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. So we can have multiple

  sections. We need to decide which headings to include: - About the role: include company overview and role description. - Responsibilities: list of duties (Data Management & Ingestion, Editing & Story Crafting, Client Story Delivery, Pod Collaboration & Communication). Each could be a

  with
  • items; maybe each responsibility heading could be a

    ? Not allowed? Only headings allowed are those listed. But we can still use

    or

    inside. We could make each responsibility a

    but not in list; maybe better to keep as

    with bold? But we need to use

    • for any list of duties/requirements/benefits. So we can make a
      where each
      • contains the responsibility heading and description. Eg
      • Data Management & Ingestion: ...
      . That satisfies. - Requirements / Qualifications / Skills: The posting has "Required Skills And Experience" broken into Technical & Post-Production, Editorial & Story, Collaboration & Process. Also "Who You Are" and "Core Values". We could put all under Skills heading as a list. Or we could separate into Qualifications (for experience/requirements) and Skills (for abilities). But we have limited headings; we can choose to include Skills and maybe Qualifications if we have distinct content. Let's see: "Required Skills And Experience" includes both skills and experience. Could treat as Skills. "Who You Are" is more about cultural fit; could be Qualifications. "Core Values" maybe also Qualifications. But we can just put everything under Skills heading as a list; that'll capture all. - Schedule: we have schedule info. We should not include Benefits, Pay. We need to ensure we don't include filler like "Competitive". We'll omit compensation. We need to preserve all substantive information: company description, role description, responsibilities details, required skills/experience, who you are, core values, schedule/location. Let's craft HTML. Structure:

      About the role

      Company description...

      Role description...

      Responsibilities

      • Data Management & Ingestion: Own all aspects of post-production data management: ingestion, organization, backup, and file integrity from first card pull to final archive; build and maintain a consistent, clearly labeled project file structure that the entire pod can navigate; verify footage quality, audio sync, and file completeness upon every handoff from the Director of Photography; maintain organized project libraries across all active client accounts with zero tolerance for missing or mislabeled assets; serve as the post-production system expert – the team comes to you when they need to find something, and you always know where it is.
      • Editing & Story Crafting: Ingest all production material and approach it with fresh eyes – seeing through the volume and finding the story inside it; execute the full editing lifecycle: assembly cut, rough cut, fine cut, color, audio polish, and final delivery; follow the Creative Director’s vision precisely while bringing your own editorial instincts to serve the story; craft narrative-driven edits that feel intentional, emotionally resonant, and built for the client’s audience; manage multiple project timelines simultaneously without losing detail or quality on any of them.
      • Client Story Delivery: Ensure every deliverable reflects the client’s original intent and the Creative Director’s creative direction; prepare and export final deliverables to exact client specifications: format, resolution, aspect ratio, and platform requirements; manage revision rounds with clarity and patience – tracking feedback, implementing changes accurately, and communicating status to the pod; deliver work that makes the client feel like the story they always imagined finally exists.
      • Pod Collaboration & Communication: Work closely with the Editing Specialist to delegate supporting tasks and maintain post-production momentum; communicate proactively with the Creative Director on timeline status, revision progress, and any technical flags; collaborate with the Director of Photography to ensure the editorial intent aligns with what was captured on set; show up as a steady, reliable presence in the pod – the person everyone knows will follow through without being asked twice.

      Skills

      • Technical & Post‑Production: 3+ years of professional editing experience in a production or agency environment; expert‑level proficiency in Adobe Premiere Pro and/or DaVinci Resolve; strong working knowledge of After Effects, color grading workflows, and audio mixing basics; deep familiarity with post‑production data management: file structures, codecs, proxies, backups, and archiving; experience delivering across multiple formats and platforms: broadcast, social, web, and internal.
      • Editorial & Story: Proven ability to take raw footage and craft a compelling, emotionally driven narrative; strong sense of pacing, rhythm, and visual storytelling; ability to receive and implement creative direction clearly and accurately; comfortable managing multiple concurrent projects without losing precision on any of them.
      • Collaboration & Process: Natural team player – you work best when the whole pod is moving in the same direction; clear communicator who surfaces problems early and brings proposed solutions; highly organized and methodical – your system is something others can rely on, not just something that works for you; patient, steady, and consistent – the kind of person that raises the trust level of everyone around them.
      • Who You Are (cultural fit): You are the person the pod exhales around – not because you are loud or fast or flashy, but because when you are on a project everyone knows the back end is handled; files are organized, timeline is clean, story is being found; you bring steadiness to post‑production; you are deeply collaborative, communicate, ask the right questions before you start, check in when something feels off, treat the Creative Director’s vision like it matters and honor it in every frame; you are a data hawk – you know where every file lives, what is backed up and what is not, you know the status of every project in the queue; nothing slips through your system.
      • Core Values Alignment: Own the Outcome – Takes responsibility from start to finish; Wash Feet – Serves clients and internal partners with humility; Live No Lies – Communicates with honesty, clarity, and integrity; Make It Gold – Brings excellence and thoughtfulness into every detail; Let the Light Leak – Works with purpose, hope, and a strong inner conviction.

      Schedule

      Full‑time or freelance (fractional) options available; hybrid work model; based in Dallas–Fort Worth or fully remote.

      We need to ensure we didn't include any boilerplate like "How to apply". We removed that. Check for any repeated lines: we have not duplicated. Check for any filler: we didn't include "Competitive". Good. Check for any missing substantive info: we included company description, role description, responsibilities, skills/experience, who you are, core values, schedule/location. Did we miss "About Harp & Sling" specifics? We included in About the role paragraph. Let's capture exact wording: "Harp & Sling is a storytelling-first creative agency that helps brands cut through mediocrity through cinematic video, photography, and strategic storytelling campaigns. We serve industries where trust, people, and real-world impact matter—construction, engineering, architecture, design, nonprofits, and thought leadership. We don’t just “shoot content.” We lead stories—from strategy to execution—capturing people, projects, and purpose with clarity, excellence, and heart. As we scale our Storytelling Team model, we’re looking for a Lead Editor —a seasoned visual leader who can own projects, lead teams, and deliver consistently excellent work in demanding environments." That's the About Harp & Sling plus lead-in. Then "About The Role" paragraph: "Shooting great footage is one thing. Knowing what to do with it is another. The Lead Editor at Harp & Sling is not just someone who cuts clips together. They are the person who takes everything the team captures – hours of footage, multiple cameras, layers of audio, b-roll, interviews, moments – and sees through all of it with clarity and purpose. They find the thread. They build the arc. They deliver the story the client always hoped someone could tell. You will own the full editing lifecycle – from the moment footage comes off the drive to the moment the final deliverable is approved and delivered. That means data management is not a side task. It is a core competency. You know exactly where every file lives, how it is organized, and what its status is at any given moment. Nothing gets lost. Nothing gets missed. Nothing gets sent that is not ready. You report to the Creative Director and take clear creative direction from them – translating their