Legal Counsel (Contract)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to parse the posting: It includes location line: "Location: US Remote, preference San Francisco Bay Area". Then "About super{set}" description. Then "The Role" description. Then "Why This Role Matters". Then "What You’ll Own" with bullet points (Corporate & Company Matters, Commercial Contracts, Fundraising & Transactions, Equity & Cap Table Support, Privacy, Data & AI, Fund & Compliance Support, Legal Operations). Then "What Success Looks Like" with bullet points (first 6 months). Then "What You Bring" with Must Have bullet list and Nice to Have bullet list. Then "The Opportunity" paragraph.
We need to map to sections: About the role (maybe "About the role" heading). Responsibilities (maybe "Responsibilities" heading). Requirements (maybe "Requirements" heading). Qualifications (maybe "Qualifications" heading). Skills (maybe "Skills" heading). Benefits, Pay, Schedule only if present. The posting does not mention benefits, pay, schedule explicitly. So we should not include those sections.
We need to decide which sections to include: About the role (the description about super{set} and the role). Responsibilities (the "What You’ll Own" list). Requirements (the "What You Bring" Must Have list). Qualifications maybe overlapping with Requirements? Could combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple if content exists. We need to avoid thin sections. Let's think: "About the role" could include the initial description about super{set} and the role overview (the "About super{set}" and "The Role" and "Why This Role Matters"). That's substantive.
"Responsibilities" could be the "What You’ll Own" list.
"Requirements" could be the "What You Bring" Must Have list.
"Qualifications" could be the "Nice to Have" list? Or maybe we treat Nice to Have as "Qualifications" or "Skills". The instruction says we can use Skills heading for skills. Could put Nice to Have under Skills. But we need to avoid filler. The Nice to Have list is substantive. Could put under "Qualifications" or "Skills". Let's decide: Use "Qualifications" for Must Have (required). Use "Skills" for Nice to Have (preferred). Or we could combine Must Have and Nice to Have under "Requirements". But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose.
We need to preserve all substantive information. So we need to include the location line somewhere. It's minor metadata; we can fold into a short
at top.
We also need to include the "What Success Looks Like" section. That could be part of Responsibilities? Or maybe a separate section like "Expectations" but not in allowed headings. Could incorporate into Responsibilities or About the role. But we need to preserve all info. Could add a section "What Success Looks Like" but not in allowed headings; we should not create new headings outside the list. So we need to fit it under existing headings. Perhaps under "Responsibilities" we can include both the duties and success metrics. Or under "About the role". But we need to keep it clear.
Better: Use "Responsibilities" for duties (What You’ll Own). Use "Expectations" not allowed. Could put success metrics under "Responsibilities" as additional bullet points.
Alternatively, we could create a section "What Success Looks Like" but that's not in the allowed list; instruction says use those 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; but we could still use other headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could still use other headings if needed, but they want us to use those for sections. Safer to stick to those.
Thus we need to map all content to those sections.
Let's outline:
- About the role: includes About super{set}, The Role, Why This Role Matters, What Success Looks Like (maybe as part of role description). Could also include The Opportunity? The Opportunity is more about growth; could be part of About the role.
- Responsibilities: What You’ll Own list.
- Requirements: What You Bring Must Have list.
- Qualifications: What You Bring Nice to Have list (or maybe Skills). But we have both Qualifications and Skills headings available. Could put Nice to Have under Skills, and Qualifications under Qualifications. Or we could treat Must Have as Qualifications and Nice to Have as Skills.
- Benefits, Pay, Schedule: not present, so omit.
We also need to include location line: maybe a short
at top:
Location: US Remote, preference San Francisco Bay Area
.
We must not repeat job title as heading. The job title is "Legal Counsel". Not used.
We must not include boilerplate like EEO etc. Not present.
We must not include application instructions. Not present.
We must preserve all substantive information: need to include all bullet points under What You’ll Own, What You Bring Must Have, Nice to Have, The Opportunity paragraph, etc.
We need to format lists with - . For prose, use
.
We need to avoid filler like "commensurate with experience". Not present.
Now craft HTML.
Start with location paragraph.
Then
About the role
then paragraphs covering About super{set}, The Role, Why This Role Matters, What Success Looks Like, The Opportunity.
We need to ensure we don't lose any detail.
Let's extract the text:
About super{set}:
"super{set} is a company builder that founds, funds, and builds data and AI-native startups. We’re not a traditional VC, we co-found and build alongside product-driven founders from ideation through scale, providing hands-on support and seed funding from day one. You’ll join a lean, high-output team of experienced builders who have founded, built, and scaled companies from the ground up. They bring grit, humility, and unapologetic nerdiness to solving hard problems. The learning curve is vertical."
The Role:
"We’re looking for a practical, hands-on Legal Counsel to support super{set} and its portfolio companies across day-to-day corporate and commercial legal work. This is a role for an attorney who can independently handle routine-to-moderate legal matters, keep work moving, and exercise good judgment about when an issue can be handled directly and when it requires more senior counsel. You’ll work closely with the super{set} team, portfolio founders, investors, and external advisors across a range of legal and corporate matters. You’ll take ownership of recurring legal workflows and help make the day-to-day legal function more efficient, while more complex and strategic matters are handled with senior counsel. The role is particularly well suited to someone who enjoys being close to the business, solving practical problems, and having meaningful ownership without needing to be the most senior lawyer in the room."
Why This Role Matters:
"The legal work behind a growing company is rarely just about answering legal questions. It is about helping the business move quickly without creating problems that surface later. A well-structured company is easier to finance. Clean equity records prevent painful surprises. A well-negotiated contract protects the business without unnecessarily slowing a deal. Good legal processes mean founders spend less time figuring out how to navigate recurring issues and more time building their companies. At super{set}, you’ll work across these decisions at the point where they are actually happening. You’ll see a wide range of legal and operational questions across companies at different stages, and you’ll have the opportunity to bring practical judgment to each one. You’ll also help create leverage. When the same question comes up twice, there should be a better answer the second time. Whether that means improving a template, creating a playbook, tightening a workflow, or simply establishing a better default, you’ll help make the legal function more efficient over time."
What Success Looks Like (first 6 months):
"In the first 6 months, you will have:
- Become a trusted first point of contact for routine-to-moderate legal matters across super{set} and its portfolio.
- Independently managed a meaningful volume of corporate and commercial work from intake through resolution.
- Helped founders and the broader team move contracts, corporate matters, and other legal workflows forward with speed and sound judgment.
- Built strong working relationships with the super{set} team, portfolio founders, investors, and external advisors.
- Kept corporate records, equity documentation, contracts, and recurring legal obligations organized and up to date.
- Improved templates, processes, and workflows so recurring legal work is handled more efficiently and escalated appropriately when senior counsel is needed."
The Opportunity:
"Work across the full lifecycle of early-stage companies, from formation and equity through commercial contracts, fundraising, and ongoing corporate matters.
Partner directly with founders and operators who are building companies from the ground up, helping them navigate legal questions that arise as the businesses evolve.
Own meaningful legal work from day one, with the autonomy to independently handle routine-to-moderate matters while working alongside senior counsel on more complex and strategic issues.
Build leverage beyond individual matters, turning recurring legal questions into better templates, processes, and systems that help the team move faster.
Develop broad, practical legal judgment by seeing how legal, commercial, and operational decisions intersect across multiple companies.
If you’re the kind of lawyer who likes being close to the business, trusted to figure things out, and useful beyond simply giving legal advice, let’s talk."
Now Responsibilities: What You’ll Own list:
- Corporate & Company Matters: Support company formations, entity management, governance, and ongoing corporate housekeeping across super{set} and its portfolio. Prepare and manage routine corporate documents, filings, resolutions, and related materials. Maintain organized corporate records and identify issues that require attention. Coordinate with outside counsel on matters requiring specialized expertise.
- Commercial Contracts: Draft, review, and negotiate NDAs, employee agreements, vendor agreements, customer agreements, and other routine commercial contracts. Maintain and improve standard contract templates. Help business teams move agreements through review and execution efficiently. Use sound commercial judgment to distinguish between standard issues and matters that require escalation.
- Fundraising & Transactions: Support fundraising, financing, and other transactions across the portfolio. Assist with diligence, document review, closing processes, and coordination with investors and outside counsel. Help keep legal workstreams organized and moving toward completion.
- Equity & Cap Table Support: Support the super{set} Head of Finance with
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting: It includes location line: "Location: US Remote, preference San Francisco Bay Area". Then "About super{set}" description. Then "The Role" description. Then "Why This Role Matters". Then "What You’ll Own" with bullet points (Corporate & Company Matters, Commercial Contracts, Fundraising & Transactions, Equity & Cap Table Support, Privacy, Data & AI, Fund & Compliance Support, Legal Operations). Then "What Success Looks Like" with bullet points (first 6 months). Then "What You Bring" with Must Have bullet list and Nice to Have bullet list. Then "The Opportunity" paragraph. We need to map to sections: About the role (maybe "About the role" heading). Responsibilities (maybe "Responsibilities" heading). Requirements (maybe "Requirements" heading). Qualifications (maybe "Qualifications" heading). Skills (maybe "Skills" heading). Benefits, Pay, Schedule only if present. The posting does not mention benefits, pay, schedule explicitly. So we should not include those sections. We need to decide which sections to include: About the role (the description about super{set} and the role). Responsibilities (the "What You’ll Own" list). Requirements (the "What You Bring" Must Have list). Qualifications maybe overlapping with Requirements? Could combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple if content exists. We need to avoid thin sections. Let's think: "About the role" could include the initial description about super{set} and the role overview (the "About super{set}" and "The Role" and "Why This Role Matters"). That's substantive. "Responsibilities" could be the "What You’ll Own" list. "Requirements" could be the "What You Bring" Must Have list. "Qualifications" could be the "Nice to Have" list? Or maybe we treat Nice to Have as "Qualifications" or "Skills". The instruction says we can use Skills heading for skills. Could put Nice to Have under Skills. But we need to avoid filler. The Nice to Have list is substantive. Could put under "Qualifications" or "Skills". Let's decide: Use "Qualifications" for Must Have (required). Use "Skills" for Nice to Have (preferred). Or we could combine Must Have and Nice to Have under "Requirements". But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; we can choose. We need to preserve all substantive information. So we need to include the location line somewhere. It's minor metadata; we can fold into a short
at top. We also need to include the "What Success Looks Like" section. That could be part of Responsibilities? Or maybe a separate section like "Expectations" but not in allowed headings. Could incorporate into Responsibilities or About the role. But we need to preserve all info. Could add a section "What Success Looks Like" but not in allowed headings; we should not create new headings outside the list. So we need to fit it under existing headings. Perhaps under "Responsibilities" we can include both the duties and success metrics. Or under "About the role". But we need to keep it clear. Better: Use "Responsibilities" for duties (What You’ll Own). Use "Expectations" not allowed. Could put success metrics under "Responsibilities" as additional bullet points. Alternatively, we could create a section "What Success Looks Like" but that's not in the allowed list; instruction says use those 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; but we could still use other headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could still use other headings if needed, but they want us to use those for sections. Safer to stick to those.
Thus we need to map all content to those sections.
Let's outline:
- About the role: includes About super{set}, The Role, Why This Role Matters, What Success Looks Like (maybe as part of role description). Could also include The Opportunity? The Opportunity is more about growth; could be part of About the role.
- Responsibilities: What You’ll Own list.
- Requirements: What You Bring Must Have list.
- Qualifications: What You Bring Nice to Have list (or maybe Skills). But we have both Qualifications and Skills headings available. Could put Nice to Have under Skills, and Qualifications under Qualifications. Or we could treat Must Have as Qualifications and Nice to Have as Skills.
- Benefits, Pay, Schedule: not present, so omit.
We also need to include location line: maybe a short
at top:
Location: US Remote, preference San Francisco Bay Area
. We must not repeat job title as heading. The job title is "Legal Counsel". Not used. We must not include boilerplate like EEO etc. Not present. We must not include application instructions. Not present. We must preserve all substantive information: need to include all bullet points under What You’ll Own, What You Bring Must Have, Nice to Have, The Opportunity paragraph, etc. We need to format lists with- . For prose, use
. We need to avoid filler like "commensurate with experience". Not present. Now craft HTML. Start with location paragraph. Then
About the role
then paragraphs covering About super{set}, The Role, Why This Role Matters, What Success Looks Like, The Opportunity. We need to ensure we don't lose any detail. Let's extract the text: About super{set}: "super{set} is a company builder that founds, funds, and builds data and AI-native startups. We’re not a traditional VC, we co-found and build alongside product-driven founders from ideation through scale, providing hands-on support and seed funding from day one. You’ll join a lean, high-output team of experienced builders who have founded, built, and scaled companies from the ground up. They bring grit, humility, and unapologetic nerdiness to solving hard problems. The learning curve is vertical." The Role: "We’re looking for a practical, hands-on Legal Counsel to support super{set} and its portfolio companies across day-to-day corporate and commercial legal work. This is a role for an attorney who can independently handle routine-to-moderate legal matters, keep work moving, and exercise good judgment about when an issue can be handled directly and when it requires more senior counsel. You’ll work closely with the super{set} team, portfolio founders, investors, and external advisors across a range of legal and corporate matters. You’ll take ownership of recurring legal workflows and help make the day-to-day legal function more efficient, while more complex and strategic matters are handled with senior counsel. The role is particularly well suited to someone who enjoys being close to the business, solving practical problems, and having meaningful ownership without needing to be the most senior lawyer in the room." Why This Role Matters: "The legal work behind a growing company is rarely just about answering legal questions. It is about helping the business move quickly without creating problems that surface later. A well-structured company is easier to finance. Clean equity records prevent painful surprises. A well-negotiated contract protects the business without unnecessarily slowing a deal. Good legal processes mean founders spend less time figuring out how to navigate recurring issues and more time building their companies. At super{set}, you’ll work across these decisions at the point where they are actually happening. You’ll see a wide range of legal and operational questions across companies at different stages, and you’ll have the opportunity to bring practical judgment to each one. You’ll also help create leverage. When the same question comes up twice, there should be a better answer the second time. Whether that means improving a template, creating a playbook, tightening a workflow, or simply establishing a better default, you’ll help make the legal function more efficient over time." What Success Looks Like (first 6 months): "In the first 6 months, you will have: - Become a trusted first point of contact for routine-to-moderate legal matters across super{set} and its portfolio. - Independently managed a meaningful volume of corporate and commercial work from intake through resolution. - Helped founders and the broader team move contracts, corporate matters, and other legal workflows forward with speed and sound judgment. - Built strong working relationships with the super{set} team, portfolio founders, investors, and external advisors. - Kept corporate records, equity documentation, contracts, and recurring legal obligations organized and up to date. - Improved templates, processes, and workflows so recurring legal work is handled more efficiently and escalated appropriately when senior counsel is needed." The Opportunity: "Work across the full lifecycle of early-stage companies, from formation and equity through commercial contracts, fundraising, and ongoing corporate matters. Partner directly with founders and operators who are building companies from the ground up, helping them navigate legal questions that arise as the businesses evolve. Own meaningful legal work from day one, with the autonomy to independently handle routine-to-moderate matters while working alongside senior counsel on more complex and strategic issues. Build leverage beyond individual matters, turning recurring legal questions into better templates, processes, and systems that help the team move faster. Develop broad, practical legal judgment by seeing how legal, commercial, and operational decisions intersect across multiple companies. If you’re the kind of lawyer who likes being close to the business, trusted to figure things out, and useful beyond simply giving legal advice, let’s talk." Now Responsibilities: What You’ll Own list: - Corporate & Company Matters: Support company formations, entity management, governance, and ongoing corporate housekeeping across super{set} and its portfolio. Prepare and manage routine corporate documents, filings, resolutions, and related materials. Maintain organized corporate records and identify issues that require attention. Coordinate with outside counsel on matters requiring specialized expertise. - Commercial Contracts: Draft, review, and negotiate NDAs, employee agreements, vendor agreements, customer agreements, and other routine commercial contracts. Maintain and improve standard contract templates. Help business teams move agreements through review and execution efficiently. Use sound commercial judgment to distinguish between standard issues and matters that require escalation. - Fundraising & Transactions: Support fundraising, financing, and other transactions across the portfolio. Assist with diligence, document review, closing processes, and coordination with investors and outside counsel. Help keep legal workstreams organized and moving toward completion. - Equity & Cap Table Support: Support the super{set} Head of Finance with