Product Counsel
Grindr · New York, United States · 1 mo ago
HybridLegal$300k/yrFull-time
We need to output HTML fragment with sections: About the team? Actually the posting includes "About The Team" and "About The Job". The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say do NOT repeat the job title as a heading. They say include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections are present.
We have content: About The Team (description of team). About The Job (role description). Role Requirements (requirements). You May Thrive In This Role If (maybe skills/qualities). Benefits And Perks (benefits). About Grindr (company overview). Also there is mention of hybrid role location and schedule (Tuesdays and Thursdays in person). That could be Schedule? They said include Schedule section only if posting actually states them. It does state hybrid role based in LA, SF, NYC or offices and will require you to be in person Tuesdays and Thursdays. That's schedule info. So we could include a Schedule section.
Pay: they mention "Industry-competitive compensation, company bonus, and equity for every employee." That's compensation info. So we could include Pay section.
Benefits: we have Benefits And Perks section with details.
Qualifications: Role Requirements includes qualifications (experience, JD, bar admission). Could be Requirements or Qualifications. We'll use Requirements for experience and qualifications.
Skills: maybe "You May Thrive In This Role If" includes skills/attributes. Could be Skills.
We need to avoid boilerplate like EEO, privacy policy, etc. Remove duplicated lines.
We must preserve all substantive information. Not invent or summarize away detail. So we need to keep details.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Probably we should stick to those headings; but we could include About Grindr as a paragraph under About the Role? Might be better to include as a separate section "About the Company". However not in examples; but we can still use
.
Now Benefits And Perks:
List:
- Health, Dental & Vision: Full premium coverage for you. Partial coverage for dependents.
- Family Formation: Up to $300,000 in fertility and family-building support, covering IVF, surrogacy, egg freezing, and adoption.
- Retirement: 401(k) with 6% match and immediate vesting.
- Compensation: Industry-competitive compensation, company bonus, and equity for every employee. (But we might move compensation to Pay section; but it's also under Benefits. We'll keep compensation in Pay section and maybe not duplicate.)
- Gender-Affirming Care: Industry-leading gender-affirming offerings with up to 90% cost coverage, access to Included Health, monthly stipends for HRT, and more.
- Time Off & Rest: Flexible vacation policy. Two company-wide rest weeks per year.
- Other Benefits: Monthly stipends for cell phone, internet, wellness, food, and commuting, breakfast/lunch.
We'll separate Pay.
Pay section: "Industry-competitive compensation, company bonus, and equity for every employee."
Schedule section: "Hybrid role based in our Los Angeles, SF, NYC or offices; required in‑person Tuesdays and Thursdays."
About Grindr section: we have paragraph about Grindr building Global Gayborhood etc. Let's extract:
"Grindr is building the Global Gayborhood in your Pocket. With more than 15 million monthly active users, Grindr has become a fundamental part of the gay community and is charting a path to make the world more free, equal, and just. As a public company, we're moving into the next chapter: becoming an AI-native organization that's redefining what's possible for our community. We're embedding AI into our product and operations, moving with startup speed while operating at scale. Everything we do is rooted in impact for our users and outcomes for the business. This isn't social work, it’s impact through excellence. Business success is what gives us the power to serve our community and the seat at tables others can't reach. How we work is defined by Grindr Mode, our operating model that's moderately hardcore day-to-day and truly hardcore when it counts. We think like owners, drive real outcomes, create clarity through action, and push each other to go further than we thought possible. We’re headquartered in West Hollywood with offices in the Bay Area
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They say do NOT repeat the job title as a heading. They say include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide which sections are present.
We have content: About The Team (description of team). About The Job (role description). Role Requirements (requirements). You May Thrive In This Role If (maybe skills/qualities). Benefits And Perks (benefits). About Grindr (company overview). Also there is mention of hybrid role location and schedule (Tuesdays and Thursdays in person). That could be Schedule? They said include Schedule section only if posting actually states them. It does state hybrid role based in LA, SF, NYC or offices and will require you to be in person Tuesdays and Thursdays. That's schedule info. So we could include a Schedule section.
Pay: they mention "Industry-competitive compensation, company bonus, and equity for every employee." That's compensation info. So we could include Pay section.
Benefits: we have Benefits And Perks section with details.
Qualifications: Role Requirements includes qualifications (experience, JD, bar admission). Could be Requirements or Qualifications. We'll use Requirements for experience and qualifications.
Skills: maybe "You May Thrive In This Role If" includes skills/attributes. Could be Skills.
We need to avoid boilerplate like EEO, privacy policy, etc. Remove duplicated lines.
We must preserve all substantive information. Not invent or summarize away detail. So we need to keep details.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the Team
... content from About The Team ...
About the Role
... content from About The Job ...
Requirements
- ... each requirement ...
Skills
- ... each "You May Thrive In This Role If" bullet ...
Benefits
- ... each benefit ...
Pay
... compensation description ...
Schedule
... hybrid role location and in‑person days ...
We might also include About Grindr as a section? Could be "About the Company". But not in list of headings; but we could still use