Founding Marketer

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Sela (company description), Why this is a huge opportunity, Why Join, What Will You Do, What Will You Own, What Are We Looking For (must haves, nice to haves), Benefits. Also maybe Pay? Benefits includes salary range. So we need sections: About the role? Not exactly; we have company description. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The posting does not have explicit "Responsibilities" but we have "What Will You Do" and "What Will You Own". Those could be responsibilities. "What Are We Looking For" is requirements/qualifications. Benefits section present. Pay is included in benefits line: "$150k - $200k + equity". So we could have a Pay section or include in Benefits. The instruction: only include a section when posting has real, specific content. Pay is present: salary range. So we should create a Pay section with that info. Benefits section also present with details. Schedule: "Hybrid in-office schedule: four days a week together in SF, with a flexible remote day on Wednesdays". So we can have Schedule section. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive information. So include company description (About Sela) maybe as a paragraph under About the role? Or maybe we can have an "About the company" but not in list of headings. 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. Probably we should stick to those headings where applicable. So we can have:

About the role

containing description of role? The posting includes "What Will You Do", "What Will You Own". That's responsibilities. So maybe About the role could be a brief summary: "Build Sela into a recognizable brand..." etc. But we need to preserve all info; we can put the responsibilities under Responsibilities heading. And maybe About the role could be a short paragraph summarizing the role: "As the first marketing hire, you will..." but that's essentially same as responsibilities. To avoid duplication, we could put the company description under About the role? Not ideal. Better: Use headings that match content: About the role (maybe a brief intro), Responsibilities (What Will You Do + What Will You Own), Requirements (What Are We Looking For), Benefits, Pay, Schedule. Also maybe Skills? Not explicitly listed but could be inferred from requirements. But we should not create sections without content. So we skip Skills. We need to include all substantive info: company description (About Sela, Why this is a huge opportunity, Why Join) maybe could go under About the role? Or we could add a section "About the company" but not in list; but 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

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Likely they expect us to use those headings where appropriate. So we can put company description under About the role? Might be okay. But we must not repeat job title as heading. No job title given explicitly; it's implied "first marketing hire". Not needed. Let's craft:

About the role

Sela is the market-leading AI voice agent for mortgage lenders. Founded in 2024, we’ve grown like crazy (~$0->13M in 20 months), and currently count 5 of the 10 largest independent mortgage banks in the U.S. as enterprise customers. If we’re successful, the cost of owning a home in the US will become ~1% cheaper. We’ve raised $21M across our Seed and Series A from top investors.

Why this is a huge opportunity: Around 1% of the U.S. labor force works in phone sales, representing roughly $100B of annual salary, and the industry is poised at the brink of complete disruption. We are at the cutting edge of this economic transformation, one of the first companies creating real, durable economic value through applied AI. Buying a house is the largest financial decision most people make in their lives, and homeownership is tied to many other purchases, including life insurance, homeowners insurance, alarm systems, home renovations, solar panels, and more. By owning the mortgage vertical, we will own the relationship with the consumer, allowing us to serve as the essential AI infrastructure for high consideration consumer sales.

Why Join: Crazy growth: The market pull is exhilarating - we’ve grown 10x in the past 12 months and more than 100x since our seed round, all without a dedicated sales or marketing team. Building something that people want so badly is the best feeling you can have in a startup. Team and Culture: We are a high-agency team where the bar is high and everyone makes the people around them better. Collaboration and intensity are core team values: people truly care about their work and their coworkers. At the same time, we don't take ourselves too seriously. Challenging problems: Outperforming human sales teams on half a million daily calls is not easy. Low-latency, real-time infra. 99.9% uptime. Enterprise-grade privacy and security. Advanced simulation and evaluation systems. Flexible A/B testing. AI scheduler and dialer. We own the whole stack and we do not compromise on quality. Well-funded: We’ve raised $21M+ in total funding, most recently a $15M Series A in June 2026.

Then Responsibilities:

Responsibilities

• Build Sela into a recognizable brand in our industry.
• Own our website, social media, customer stories, and other content.
• Create campaigns that generate qualified inbound for the sales team.
• Run webinars with customers, partners, and industry leaders.
• Own our presence at key conferences — from sponsorships and booths to dinners and side events.
• Organize customer and industry events that build relationships and brand awareness.
• Own company announcements, press releases, and relevant media relationships.
• Experiment with new channels and creative ways to get Sela in front of the right people.
• Own the Sela brand and how we show up in the market.
• Own our website, social media, content, and customer stories.
• Own conferences, webinars, customer events, and other industry gatherings.
• Turn brand awareness and marketing campaigns into qualified inbound.
• As our first marketing hire, help define our marketing strategy and eventually the team we build.

But note some duplication: "Own our website, social media, customer stories, and other content." appears twice; we can keep both but maybe combine. However we must preserve all substantive information; duplication is okay but we could deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid deduplication, but removing duplicate lines could be considered summarizing away detail? It's still same info; removing duplicate might be okay but safer to keep both? Might be redundant but still substantive. I'd deduplicate to avoid repetition but still keep the meaning. However the two bullet points are identical; we can keep one. Let's list responsibilities uniquely: - Build Sela into a recognizable brand in our industry. - Own our website, social media, customer stories, and other content. - Create campaigns that generate qualified inbound for the sales team. - Run webinars with customers, partners, and industry leaders. - Own our presence at key conferences — from sponsorships and booths to dinners and side events. - Organize customer and industry events that build relationships and brand awareness. - Own company announcements, press releases, and relevant media relationships. - Experiment with new channels and creative ways to get Sela in front of the right people. - Turn brand awareness and marketing campaigns into qualified inbound. - As our first marketing hire, help define our marketing strategy and eventually the team we build. That covers. Now Requirements/Qualifications:

Requirements

• 4+ years of experience in B2B marketing, with a track record of owning brand, content, or demand generation initiatives end-to-end.
• Exceptional writing and communication skills, with strong taste for what makes great content and a great brand.
• A builder mentality - you're comfortable starting from scratch and figuring out what needs to exist.
• Ability to both set strategy and execute, whether that's writing copy, launching a campaign, or running an event.
• High agency and the ability to move quickly without an established playbook.

Nice to haves could be under Qualifications or Skills. Since we have Requirements heading, we could add a Qualifications heading for nice-to-haves. But we could also include them under Requirements as "Nice to have". Better to have separate headings: Requirements and Qualifications. Let's do:

Requirements

(must haves)

Qualifications

(nice to haves) Qualifications list:

• Experience at a fast-growing B2B startup.
• Experience as an early or first marketing hire.
• Experience marketing to enterprise customers or a specific industry.
• Experience owning conferences, events, or field marketing.

Now Benefits:

Benefits

• $150k - $200k + equity
• Top-of-market medical, dental, and vision coverage for you and your dependents
• 401(k) with a top-of-market employer match
• Unlimited PTO
• Snacks, weekly team lunches, and dinner on Sela

Pay: we already included salary in benefits; but we could also have a Pay section with salary range. However we already have salary in benefits list; but the instruction says only create Pay section if posting actually states them. It does state salary range. We could either keep salary in Benefits and not have Pay section, or create Pay section with salary and keep benefits without salary. Which is better? The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine salary into Benefits to avoid thin Pay section. But they gave example of Pay as a possible heading. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create Benefits section (we have) and we could also create Pay section if we want, but that would be thin (just salary). Better to include salary in Benefits to keep fewer sections. So we will not create separate Pay section. Schedule:

Schedule

Hybrid in-office schedule: four days a week together in SF, with a flexible remote day on Wednesdays.

Now we need to ensure we didn't include any boilerplate like EEO etc. Not present. We must output only HTML fragment, no markdown fences. Let's craft final HTML. Check for any missing info: The "Why Join" section includes many bullet-like sentences; we turned them into paragraphs under About the role. That's fine. We also included "Well-funded: We’ve raised $21M+ in total funding, most recently a $15M Series A in June 2026."