Jobs · Art & Creative

Senior Scriptwriter

Ethos · United States · 1 mo ago
RemoteRemoteArt & Creative$127k–$223k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications and Skills), Benefits, Pay, Schedule only if present. The posting includes: About Ethos (company description) – we can include as maybe a short paragraph? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). So we need to strip out the sections about Ethos being equal opportunity, scam warning, California Candidate Privacy Notice, recruitment notice, etc. Also remove "About Ethos" maybe? It's company overview, substantive? It's about the company, maybe we keep as a paragraph under a heading? The instruction says include a section ONLY when the posting has real, specific content for it. The posting has "About Ethos" which is company description. Should we include a section? Possibly we can include a

about Ethos without a heading? The 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 suggests those as examples. We could include a heading "About Ethos" as

if we want. But they said "include a section ONLY when the posting has real, specific content for it". About Ethos has content, so we could include. However they gave examples of section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About Ethos, but we could still use

for any section heading. Safer to follow their examples: maybe we should not create a heading for About Ethos, just include it as a

before the sections. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected sections. It doesn't forbid other headings, but to be safe we can just put the Ethos description as a

without a heading. We need to include About the role heading (

About the role

) with the prose from "About The Role". Then Responsibilities (

Responsibilities

) with list from Duties And Responsibilities. Then Qualifications and Skills (

Qualifications and Skills

) maybe combine Qualifications and Skills as one heading? They gave separate Qualifications and Skills as possible headings. We could do

Qualifications

and

Skills

but they said prefer a few substantive sections over many thin ones. So combine into one heading "Qualifications and Skills". Then Pay (

Pay

) with salary range. Benefits? Not mentioned besides link to benefits page; no specific benefits listed. So we should not create Benefits section because no specific content. Schedule? Not mentioned. So omit. We need to preserve all substantive information: include the salary range text exactly. Also include the link to benefits? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The link to benefits is substantive? It's a URL. Could include as a

with the link. However they said "Do NOT repeat the job title as a heading ... fold minor metadata into a short

or drop it." The link to benefits is maybe minor metadata; we could include as a

. But they also said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits section not stated, but we could still include the link as a paragraph elsewhere (maybe under About the role?). But better to include as a

after Pay? However that might be considered Benefits section? Not exactly. Safer to include the link as a

after Pay, maybe under a heading "Benefits"? But they said not to create Benefits unless posting actually states them. The posting does state benefits link: "You can find further details of our US benefits at https://www.ethoslife.com/careers/". That is a statement about benefits. So we could include a Benefits section with that link. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state that you can find further details of our US benefits at that URL. So we can create a Benefits section with that link. But we need to avoid filler like "commensurate with experience". The link is specific. Thus we will have sections: About the role, Responsibilities, Qualifications and Skills, Pay, Benefits. We need to remove boilerplate: the EEO, scam warning, etc. Also remove "About Ethos" maybe keep as a paragraph before sections. Let's extract content. About Ethos paragraph: "Ethos is a leading life insurance technology company on a mission to protect families by democratizing access to life insurance and empowering agents at scale. With its robust three-sided technology platform, Ethos is transforming the life insurance experience for consumers, agents, and carriers alike. Ethos offers instant, accessible products and a seamless online process that requires no medical exams and just a few health questions; it eliminates traditional barriers, making it easier than ever for everyone to protect their families. Ethos is redefining how life insurance is bought, sold, and underwritten." We'll keep that as a

. About The Role: The paragraph after "About The Role". Let's copy: "Life insurance has spent over a century talking at people through fear. Ethos was built to talk with them, and the way we do that is through work that's genuinely good: a 15 second TV spot that lands like a gut punch, a radio read that sounds like a friend talking, a UGC clip that doesn't feel like an ad. We're looking for a writer who can bring real creative craft to formats that live and die by whether they convert. This role is focused on TV, radio, and podcast, including direct response scripts built for 15 and 30 second formats, along with UGC scripts we capture during TV production shoots so they can also run across paid social channels like Meta, TikTok, and YouTube. It also supports our influencer efforts, so scripts and talking points need to hold up when they're handed to a creator, not just an actor on set. It's for someone who can hold two things at once: the instinct to write something people actually feel, and the discipline to know why a script will or won't perform. This role reports into the Creative Director of Offline." We'll put that as

under

About the role

. Duties And Responsibilities: list bullet points. We'll convert each line to
  • . List: - Concept and write scripts for TV, radio, and podcast, including direct response formats built for 15 and 30 second spots, from brief through final delivery - Write UGC scripts captured during our TV production shoots, and adapt them so they also work as standalone paid social content across Meta, TikTok, and YouTube - Support our influencer efforts with scripts, talking points, and creative direction that give creators a clear angle without making the content feel scripted - Develop original creative territories and angles that push beyond what's already running and make Ethos feel urgent across broadcast and digital formats - Show up to TV and UGC shoots and help bring concepts to life on the day, you're not just handing off a script, you're in the room making it better - Collaborate closely with the CD of Offline, producers, video editors, and performance marketing to understand what's working and use those insights to inform what to write next - Use AI tools where they genuinely help you move faster, but the writing, the judgment, and the taste are yours - Stay current on direct response best practices, broadcast and radio trends, and what's resonating in creator culture across paid social - Write with a performance lens: every script needs a clear hook, a compelling narrative arc, and a reason to act, whether it's a 30 second TV spot or a UGC clip for TikTok We'll put under

    Responsibilities

    with
      . Qualifications And Skills: list bullet points. List: - 8+ years of experience writing for TV, radio, podcast, and paid social or UGC channels, with a portfolio spanning broadcast direct response and digital creator content - Deep understanding of direct response creative for TV and radio, you know how to build a hook and a call to action into a 15 or 30 second format and can write both - Experience writing UGC and paid social scripts for Meta, TikTok, and YouTube - Experience writing for influencer partnerships, including giving creators direction that reads as their own voice rather than a brand script - Experience at TV and UGC shoots, you're comfortable on set and know how to adapt a script in the moment when it needs to change - Strong instinct for what makes performance creative convert, paired with genuine creative taste. You know the difference between a hook that stops someone and one that sells - Fluent in AI tools for concepting and drafting, you use them to move fast, but your judgment is the filter - Ability to generate a high volume of concepts without losing creative sharpness - Collaborative and fast moving, you work well with producers, editors, directors, and performance teams and don't need a lot of hand holding to deliver We'll put under

      Qualifications and Skills

      with
        . Pay: The paragraph: "The US national base salary range for this full-time position is $127,000 - $223,000. Our salary ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries for the position across all US locations. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Please note that the compensation details listed in US role postings reflect the base salary only and do not include applicable bonus, equity, or benefits. You can find further details of our US benefits at https://www.ethoslife.com/careers/" We'll put that as

        under

        Pay

        . The benefits link is inside that paragraph; we could keep it there. But we might also create a Benefits section with just the link. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits link, but it's inside the Pay paragraph. Could we keep it there? That's fine. We'll not create separate Benefits section to avoid duplication. The Pay section already includes the benefits link. That satisfies. We must not include boilerplate like "Don’t meet every single requirement? ...", "At Ethos we are dedicated to building a diverse, inclusive and authentic workplace. We are an equal opportunity employer....", "Pursuant to the SF Fair Chance Ordinance...", "Recruitment Notice: Please be aware of recruitment scams....". Remove those. Also remove "About Ethos" maybe we keep as a paragraph without heading. Thus final HTML fragment:

        Ethos is a leading life insurance technology company on a mission to protect families by democratizing access to life insurance and empowering agents at scale. With its robust three-sided technology platform, Ethos is transforming the life insurance experience for consumers, agents, and carriers alike. Ethos offers instant, accessible products and a seamless online process that requires no medical exams and just a few health questions; it eliminates traditional barriers, making it easier than ever for everyone to protect their families. Ethos is redefining how life insurance is bought, sold, and underwritten.

        About the role

        Life insurance has spent over a century talking at people through fear. Ethos was built to talk

  • Similar jobs

    Senior Software Engineer

    HaystackAustin, Texas Metropolitan Area· 1 mo ago
    Information Technology$168k–$227k/yrapply on haystack.cv

    Senior Software Engineer

    ETAP SoftwareHouston, TX· 3 mo ago
    Information Technology$105k–$175k/yrapply on aveva.wd3.myworkdayjobs.com

    Senior Software Engineer

    Global Technical Talent, an Inc. 5000 CompanyFort Mill, SC· 3 mo ago
    Information Technology$50–$70/hrapply on www1.jobdiva.com