Podcast and Multimedia Producer

for section headings. Use

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

  for prose. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO etc. Remove lines like "All applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time. We are not accepting unsolicited resumes from agencies and/or search firms for this job posting. The above statements are intended to describe the general nature and level of work being performed by people assigned to this job. They are not intended to be an exhaustive list of all responsibilities, duties, and skills required of the incumbent in this position. Any combination of equivalent education and work experience will be considered. Savant Capital LLC, is an Equal Opportunity Employer". Also remove "What Sets Savant Apart" maybe not needed but could be part of About the role? It's descriptive but not required headings. However we must preserve ALL substantive information; we cannot invent or summarize away detail. The "What Sets Savant Apart" is substantive about company culture. Should we include it? It doesn't fit headings exactly but could be part of About the role or maybe a separate section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also add other headings if needed, but better to stick to those. However we must preserve all substantive information; we could incorporate "What Sets Savant Apart" into About the role paragraph as prose. Similarly "Our Total Rewards" etc we will put under Benefits. Now craft HTML. Structure:

  About the role

  ... (combined intro and maybe What Sets Savant Apart)

  Responsibilities

  • ...
  ...

  Requirements

  Maybe we can put the core qualifications as Requirements? But we already have Qualifications heading. The instruction includes both Requirements and Qualifications. We need to decide what goes where. The posting has "Qualifications" section. Could treat that as Qualifications. Requirements could be maybe the "Experience That Would Help You Stand Out"? But that's more like preferred qualifications. However we have Skills heading for skills. Let's map: - Requirements: maybe the mandatory qualifications (the bullet list under Qualifications). But then Qualifications heading would be duplicate. Hmm. Better: Use Requirements for the mandatory qualifications (the bullet list). Use Qualifications for the education/experience requirements? Actually the posting's "Qualifications" includes both education and experience. So we could put that under Qualifications. Then Requirements could be something else like "Experience That Would Help You Stand Out"? But that's not requirements; it's preferred. However we have Skills heading for skills. Could put the "Experience That Would Help You Stand Out" under Skills. Then Requirements could be left empty? But we must not emit a heading followed by filler/placeholder text. So we should only include sections when posting has real, specific content for it. If we don't have distinct content for Requirements separate from Qualifications, we could omit Requirements heading. But the instruction says we can prefer a few substantive sections over many thin ones. So we can omit Requirements if not distinct. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We'll not include Requirements. Now content: About the role paragraph: combine intro and What Sets Savant Apart. Let's write: "Build the Show. Shape the Story. Grow the Audience. Savant Wealth Management is looking for an experienced Podcast and Multimedia Producer to take ownership of our flagship podcast and help shape what comes next. This is a newly created role for someone who knows how to turn an idea into an engaging, polished show and is ready to do more than simply execute a production checklist. You will develop the editorial vision, recruit compelling guests, prepare hosts, manage recordings, edit and publish episodes, and find smart ways to extend each conversation across video, social media, written content, and other channels. The right person brings the creative instincts of a storyteller, the organization of a seasoned producer, and the professionalism that comes from producing content within a corporate or professional-services environment. You understand that creating a great podcast is only part of the job. Success also requires navigating stakeholder expectations, balancing competing priorities, coordinating busy executives, meeting deadlines, and producing content that aligns with a larger business strategy. If you have owned professional podcast, broadcast, or interview-based programming from concept through publication and have the work to show for it, this is an opportunity to build something meaningful rather than step into a program that is already fully defined. We're not simply looking for someone who can produce a podcast. We're looking for someone who can successfully produce a podcast inside a growing, collaborative business environment. Savant’s collaborative, integrated model across advisory, tax, and planning—no silos; growth-oriented firm offering meaningful opportunities for career development and long-term impact; values-driven culture grounded in excellence, integrity, lifelong learning, respect, growth, and servant leadership; majority employee-owned, giving our team a shared stake in our long-term success." Now Responsibilities: list items from "In this role, you can expect to focus in the following areas:" plus the later sub-sections. Let's extract bullet points: - Lead