Don't see the right opportunity? Apply here!

We need to output HTML fragment with sections only if content present. The posting includes About Us (but not a heading we need? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if applicable. The posting includes "ABOUT US" which is about company, not role. Not listed as a standard heading but could be considered "About the role"? Actually "About the role" is typical. But we have "ABOUT US" describing company. The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect only those headings. So we should map content to appropriate sections: Benefits & Perks -> Benefits section. Position location & office details maybe could be Schedule? Not exactly. Could be "Schedule" if they mention hybrid days. They mention Hybrid roles required in office T/W/TH and office optional M/F. That's schedule info. So we can put that under Schedule heading. Also location could be included in Schedule or maybe not needed. There's no explicit Pay, Responsibilities, Requirements, Qualifications, Skills. So we should not create those sections. Also we should not repeat job title. There's no job title given in snippet. So we output only Benefits and Schedule sections (maybe also About the role? Not present). The "ABOUT US" could be considered "About the role"? Not really. Better to omit if not matching headings. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include Benefits and Schedule. We need to format Benefits as

• items. The benefits list includes: - Medical, Dental, and Vision plans - 80% covered by the company - Flexible PTO & 11 paid holidays/year - Subsidized ClassPass membership - 401k Plan - Paid parental leave - Pre-tax commuter benefits - In-office breakfast and snacks daily - Happy hours, team outings, & annual off-sites - Complete laptop workstation & more to come! We should preserve all. Use
  • each. Schedule: Hybrid roles required in office T/W/TH and office optional M/F. Also location: New York City (HQ- Midtown). Could include location in schedule paragraph. We'll put schedule heading and then

    with that info. We must not include boilerplate like AI tools etc. That's not a section heading; it's just prose. Should we include it? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools paragraph is not exactly boilerplate but it's about hiring process. It's not a standard section; but we could keep as prose under maybe no heading? But we only output sections with headings. If we include prose without heading, that would violate using

    for section headings? The instruction says use

    for section headings (e.g...). It doesn't forbid plain

    without heading? It says use

    for section headings,

    • for any list, and

      for prose. So we can have

      prose outside headings. But they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". That suggests we can have headings only for sections we have content. But we can also have

      not under a heading? The typical output would be something like:

      Benefits

      ...

      Schedule

      ...

      We could also include a

      for the "ABOUT US" company description? Not a standard heading but could be considered "About the role"? Might be okay to include as

      without heading? But they said use

      for section headings (e.g...). It doesn't say you must have a heading for every piece of content, just that if you use a heading it must be one of those. So we could include a

      for the company overview without heading. However, they said "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." So they allow

      for minor metadata. So we could include a

      for the company overview. But the instruction also says "Prefer a few substantive sections over many thin ones." So maybe better to just have Benefits and Schedule sections, and ignore the rest as not fitting headings. However, the company overview is substantive but not a standard heading; we could drop it? Might lose info. But maybe it's okay to drop because not required headings. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must preserve all substantive information. That means we need to include the company overview somewhere. Since we cannot create a heading not in the list, we can put it in a

      without a heading. That's allowed. Similarly, the "POSITION LOCATION & OFFICE DETAILS" includes location and hybrid schedule; we already used schedule for hybrid days, but location could be included in same

      under Schedule or separate

      . We'll include location in the Schedule

      . Also the line "We are always hiring for great talent!" is fluff, maybe minor metadata; could be omitted? It's not substantive? It's a statement but maybe minor. Could be omitted as filler? It's not boilerplate but it's generic. Might be considered filler. Safer to include as

      maybe? But it's not substantive detail. I'd omit. Also the line about AI tools in hiring process: that's substantive about hiring process; could be included as

      under maybe no heading. But it's not a standard section; we could include as

      . However, it's about hiring process, not about job. Might be considered metadata. The instruction says fold minor metadata into a short

      or drop it. This is maybe minor metadata. Could drop. Thus we will output:

      Founded in 2020, Regal is the AI Agent Platform. Regal gives every company the tools to transform customer communications with delightful AI Agents that are connected to your data, easy to customize and monitor, always available, and ready to take action. Power better support, sales, and operations - with way less effort. Our founders, Alex Levin and Rebecca Greene, helped build Angi (Angie’s List, HomeAdvisor, and Handy) to over $1.5B in revenue. Based in Manhattan, we’re building an in-person culture of entrepreneurs who want to win and build something meaningful. We’re backed by top investors including Founder Collective, Homebrew, and Emergence Capital. Come join us as we create a category-defining company, and follow Regal's company page on LinkedIn to stay up-to-date on our journey and current job openings! We’re moving fast, and the numbers speak for themselves: Partnered with enterprise brands like Google, AAA, Ro, Coursera Raised $82M (top tier investors including Emergence & Homebrew) Completed 500M+ calls Driven $7B revenue for customers Scaled to $##M ARR Built amazing NYC (Midtown) in office culture

      But note that includes "$##M ARR" which is placeholder; we should not include placeholder text. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It doesn't say we must drop placeholder within prose. However, "$##M ARR" is placeholder; maybe we should drop that part? It's not a heading, but it's placeholder. Might be considered filler. Safer to remove that specific phrase. We could keep the rest but remove "$##M ARR". The sentence: "Scaled to $##M ARR". We could change to "Scaled to $##M ARR" but that's still placeholder. Better to remove that clause entirely. So we could rewrite: "Scaled to ..."? But we cannot invent. We could drop that clause. So we can keep the sentence before and after? The original: "Partnered with enterprise brands like Google, AAA, Ro, Coursera Raised $82M (top tier investors including Emergence & Homebrew) Completed 500M+ calls Driven $7B revenue for customers Scaled to $##M ARR Built amazing NYC (Midtown) in office culture". If we drop "Scaled to $##M ARR", we get "... Driven $7B revenue for customers Built amazing NYC (Midtown) in office culture". That loses the connection; maybe we can keep "Scaled to ..."? But it's placeholder. I'd drop it. Thus the company overview paragraph will be: Founded in 2020, Regal is the AI Agent Platform. Regal gives every company the tools to transform customer communications with delightful AI Agents that are connected to your data, easy to customize and monitor, always available, and ready to take action. Power better support, sales, and operations - with way less effort. Our founders, Alex Levin and Rebecca Greene, helped build Angi (Angie’s List, HomeAdvisor, and Handy) to over $1.5B in revenue. Based in Manhattan, we’re building an in-person culture of entrepreneurs who want to win and build something meaningful. We’re backed by top investors including Founder Collective, Homebrew, and Emergence Capital. Come join us as we create a category-defining company, and follow Regal's company page on LinkedIn to stay up-to-date on our journey and current job openings! We’re moving fast, and the numbers speak for themselves: Partnered with enterprise brands like Google, AAA, Ro, Coursera Raised $82M (top tier investors including Emergence & Homebrew) Completed 500M+ calls Driven $7B revenue for customers Built amazing NYC (Midtown) in office culture. Now Benefits section. Schedule section: Hybrid roles required in office T/W/TH and office optional M/F. Also location: New York City (HQ- Midtown). We'll combine. Thus final HTML:

      Founded in 2020, Regal is the AI Agent Platform. Regal gives every company the tools to transform customer communications with delightful AI Agents that are connected to your data, easy to customize and monitor, always available, and ready to take action. Power better support, sales, and operations - with way less effort. Our founders, Alex Levin and Rebecca Greene, helped build Angi (Angie’s List, HomeAdvisor, and Handy) to over $1.5B in revenue. Based in Manhattan, we’re building an in-person culture of entrepreneurs who want to win and build something meaningful. We’re backed by top investors including Founder Collective, Homebrew, and Emergence Capital. Come join us as we create a category-defining company, and follow Regal's company page on LinkedIn to stay up-to-date on our journey and current job openings! We’re moving fast, and the numbers speak for themselves: Partnered with enterprise brands like Google, AAA, Ro, Coursera Raised $82M (top tier investors including Emergence & Homebrew) Completed 500M+ calls Driven $7B revenue for customers Built amazing NYC (Midtown) in office culture.

      Benefits

      • Medical, Dental, and Vision plans - 80% covered by the company