Legal, Partnerships & Strategic Transactions
for section headings (e.g., 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 (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; do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO paragraph, the "Apply now to embark..." and the equal opportunity statement, maybe also the "If you are a motivated individual..." etc. Also remove the "Compensation Range:"? Actually compensation is a substantive detail; we need to include Pay section if posting actually states them. It does: "Compensation Range: $275K - $350K". So we need a Pay section with that.
We need Benefits section: they list benefits. So include Benefits.
We need Schedule? Not mentioned; so omit.
We need Qualifications? Could be Requirements; but we have Requirements section already. Could also have Skills? Not explicit; but we have "What We Value" which could be considered Skills? But we should only include sections when posting has real, specific content. "What We Value" is a section with bullet points? It's a list of values. We could treat that as Skills or Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. "About Baseten" is about the company; maybe we can put that under "About the role"? Actually "About the role" is a heading for role description. The posting has "THE ROLE" paragraph describing role. So we can put that under About the role. The "THE QUESTIONS YOU WILL WORK ON" could be part of Responsibilities? Or maybe we can treat as Responsibilities. The "WHY THIS MATTERS TO BASETEN" could be part of About the role? But we need to avoid duplication. Perhaps we can have sections: About the role (includes THE ROLE, THE QUESTIONS YOU WILL WORK ON, WHY THIS MATTERS TO BASETEN). Responsibilities (list). Requirements (list). Benefits (list). Pay (compensation). Also maybe Skills? Could incorporate "What We Value" as Skills? But it's more about values/qualities. Could treat as Skills. Or we could omit Skills if not needed. The instruction: Prefer a few substantive sections over many thin ones. So we could combine What We Value into Requirements or Skills? But we already have Requirements. Could add a Skills section for those values. However we need to avoid thin sections. Maybe we can incorporate What We Value into Requirements as bullet points? But they are not requirements; they are values. Could treat as a separate section "Skills". That seems appropriate.
We must not repeat the job title as a heading. The job title is "Senior Attorney" maybe? Not given explicitly but implied. We'll not add.
We must not include Job ID etc.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
... (combined paragraphs)
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
Compensation Range: $275K - $350K
We need to ensure we preserve all substantive information from the posting. Let's extract.
About Baseten paragraph: "Baseten powers mission-critical inference for the world's most dynamic AI companies, like Cursor, Notion, OpenEvidence, Abridge, Clay, Gamma, and Writer. By uniting applied AI research, flexible infrastructure, and seamless developer tooling, we enable companies operating at the frontier of AI to bring cutting-edge models into production. We're growing quickly and recently raised our $1.5B Series F, led by Altimeter Capital, Conviction Partners, and Spark Capital. Join us and help build the platform engineers turn to ship AI products."
THE ROLE paragraph: "We are hiring a senior attorney to lead the legal work behind Baseten's partnerships and strategic transactions. This is the seat where model labs, hyperscalers, distribution platforms, and our largest customers meet, and where the licenses that govern open weight models get read, negotiated, and turned into commitments we can stand behind. Reports to the Chief Legal Officer, works directly with the founders and partnerships leads, and shares the deal surface with the rest of the legal team. Not every partnership is about revenue. Some are about awareness and being the place a lab launches. Some are about compute, capacity, and maintaining optionality. Some are about market share and developer adoption, and some are about not being locked out of a channel a competitor is building. This role has to see which game each deal is playing, structure for that, and know when a relationship that looks strategic is really a dependency. The paper is the output. The judgment is the job."
THE QUESTIONS YOU WILL WORK ON: four bullet-like paragraphs:
- "Open weight licenses are becoming a market of their own The permissive licenses that built open source software are giving way to model licenses with usage thresholds, attribution triggers, certified partner exemptions, geographic carve outs, and commercial only distribution terms, many written by labs outside the United States. Each release is a new instrument. You will read them first and help the market read them right."
- "Rights follow the license, responsibility follows role The same model can be a shared API, a dedicated deployment, a customer supplied checkpoint, or a fine tune, and who holds what right changes with each. Whether Baseten is licensee, host, distributor, or acting on a customer's behalf determines what we can promise, what we can indemnify, and what no one in this market can honestly underwrite. Getting that allocation right, and explaining it plainly to a customer's outside counsel, is the core craft."
- "Partners who are also channels, customers, and competitors A lab can be supplier, customer, and rival for the same workload. A hyperscaler can be our compute vendor, our distribution channel, and our competitor in one quarter. You will structure for channel conflict, exclusivity, and information flow so Baseten stays independent and customer centric."
- "Cross border by default Labs, compute providers, and customers sit in different jurisdictions with different rules on export controls, sanctions, data residency, and what a license permits. Partnership paper and compliance posture have to move together, and you will work with our regulatory and policy leads to make sure they do."
WHY THIS MATTERS TO BASETEN paragraph: "Our model catalog, distribution relationships, and partner channels are a large part of why customers choose us and why labs launch with us. A license question that stalls a dedicated capacity deal, a distribution term that limits how we serve a customer, or a partnership that creates a conflict we did not see coming has direct revenue and strategic consequences. This role exists to get ahead of those questions and to make Baseten the counterparty labs, platforms, and enterprises trust to get the model layer right."
Responsibilities list (bullet points after "Responsibilities" heading):
- Lead the legal workstream for model lab relationships: distribution agreements, hosted API and early access arrangements, token and capacity commitments, coalition and joint development agreements, and renegotiations as models and licenses evolve.
- Lead strategic platform and channel deals: hyperscaler marketplace and gateway agreements, white label and reseller structures, co-sell and referral arrangements, and enterprise partnerships that combine a customer relationship with a distribution one.
- Build and own Baseten's framework for open weight and custom model licenses: how we read them, how they apply across shared, dedicated, customer supplied, and fine-tuned deployments, what we confirm to customers before deployment, and where our indemnities begin and end.
- Serve as the legal voice on model licensing questions in customer deals, including direct engagement with customer counsel on license interpretation, attribution and threshold mechanics, and the allocation of responsibility between Baseten, the lab, and the customer.
- Advise leadership on channel strategy, conflict, and competition: exclusivity, most favored terms, information flow to partners who compete with us, and the structural protections that keep Baseten independent and customer centric.
- Partner with our regulatory, policy, and security leads on the cross-border dimensions of partnership paper, including export controls, sanctions, KYC, and data residency, so that compliance posture and commercial terms move together.
- Build the templates, playbooks, and per release licensing statements that let the business self-serve on standard arrangements and escalate the novel ones, and keep them current as the market changes.
- Support M&A, acquihires, and other strategic or one-off transactions as needed, including diligence on inherited licenses and partner agreements.
- Help build the partnerships legal function as it grows, and contribute across whatever the team needs.
What We Value bullet points (after "What We Value" heading):
- Reads the license. You start with the text the grant actually uses, not with what everyone assumes it says, and you can explain what it means to an engineer, a CFO, and a lab's general counsel in the same afternoon.
- A point of view. You take a position, defend it, and change it when the facts change. We are not hiring someone to summarize both sides.
- Structural thinking. You see how a distribution term today shapes a customer negotiation next year, and you design for the second order effects.
- Technical fluency. You can hold your own on inference, model weights, fine tuning, multi tenancy, and dedicated versus shared deployments, and you know why the distinction matters for rights and responsibility.
- Commercial grounding. Partnership legal work serves the business. You know which terms to hold, which to trade, and how to say so without slowing the deal down.
- Builder mentality. You operate independently, build from scratch, and have low ego. You are as comfortable drafting a per release licensing statement as you are negotiating with a hyperscaler.
Requirements list (after "Requirements" heading):
- JD and active bar membership in good standing.
- 8+ years of technology transactions or partnerships experience, with meaningful in-house time leading partnership, licensing, or platform deals at an AI, cloud, or developer infrastructure company.
- Deep familiarity with open source and open weight model licenses, including the newer custom licenses from frontier and international labs, and the ability to interpret them across deployment models.
- Experience structuring strategic partnerships with counterparties who are also customers or competitors, including channel, reseller, marketplace, and co sell arrangements.
- Direct experience allocating IP and indemnity risk in AI or platform agreements and explaining that allocation to sophisticated counterparties.
- Clear, direct communicator who can translate license text and deal structure for founders, partnerships leads, and customer counsel.
- The ability to learn, build, and master AI tooling and systems to self-serve and operate at breakneck speed.
- A desire to become a recognized thought leader in your field.
YOU MIGHT EXCEL IF YOU list (after that heading):
- Have led AI partnerships or model licensing legal work at a frontier lab, hyperscaler, or AI platform company.
- Have negotiated with or on behalf of model labs and understand how
for prose. 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; do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO paragraph, the "Apply now to embark..." and the equal opportunity statement, maybe also the "If you are a motivated individual..." etc. Also remove the "Compensation Range:"? Actually compensation is a substantive detail; we need to include Pay section if posting actually states them. It does: "Compensation Range: $275K - $350K". So we need a Pay section with that. We need Benefits section: they list benefits. So include Benefits. We need Schedule? Not mentioned; so omit. We need Qualifications? Could be Requirements; but we have Requirements section already. Could also have Skills? Not explicit; but we have "What We Value" which could be considered Skills? But we should only include sections when posting has real, specific content. "What We Value" is a section with bullet points? It's a list of values. We could treat that as Skills or Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. "About Baseten" is about the company; maybe we can put that under "About the role"? Actually "About the role" is a heading for role description. The posting has "THE ROLE" paragraph describing role. So we can put that under About the role. The "THE QUESTIONS YOU WILL WORK ON" could be part of Responsibilities? Or maybe we can treat as Responsibilities. The "WHY THIS MATTERS TO BASETEN" could be part of About the role? But we need to avoid duplication. Perhaps we can have sections: About the role (includes THE ROLE, THE QUESTIONS YOU WILL WORK ON, WHY THIS MATTERS TO BASETEN). Responsibilities (list). Requirements (list). Benefits (list). Pay (compensation). Also maybe Skills? Could incorporate "What We Value" as Skills? But it's more about values/qualities. Could treat as Skills. Or we could omit Skills if not needed. The instruction: Prefer a few substantive sections over many thin ones. So we could combine What We Value into Requirements or Skills? But we already have Requirements. Could add a Skills section for those values. However we need to avoid thin sections. Maybe we can incorporate What We Value into Requirements as bullet points? But they are not requirements; they are values. Could treat as a separate section "Skills". That seems appropriate. We must not repeat the job title as a heading. The job title is "Senior Attorney" maybe? Not given explicitly but implied. We'll not add. We must not include Job ID etc. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:
About the role
... (combined paragraphs)
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
Compensation Range: $275K - $350K
We need to ensure we preserve all substantive information from the posting. Let's extract. About Baseten paragraph: "Baseten powers mission-critical inference for the world's most dynamic AI companies, like Cursor, Notion, OpenEvidence, Abridge, Clay, Gamma, and Writer. By uniting applied AI research, flexible infrastructure, and seamless developer tooling, we enable companies operating at the frontier of AI to bring cutting-edge models into production. We're growing quickly and recently raised our $1.5B Series F, led by Altimeter Capital, Conviction Partners, and Spark Capital. Join us and help build the platform engineers turn to ship AI products." THE ROLE paragraph: "We are hiring a senior attorney to lead the legal work behind Baseten's partnerships and strategic transactions. This is the seat where model labs, hyperscalers, distribution platforms, and our largest customers meet, and where the licenses that govern open weight models get read, negotiated, and turned into commitments we can stand behind. Reports to the Chief Legal Officer, works directly with the founders and partnerships leads, and shares the deal surface with the rest of the legal team. Not every partnership is about revenue. Some are about awareness and being the place a lab launches. Some are about compute, capacity, and maintaining optionality. Some are about market share and developer adoption, and some are about not being locked out of a channel a competitor is building. This role has to see which game each deal is playing, structure for that, and know when a relationship that looks strategic is really a dependency. The paper is the output. The judgment is the job." THE QUESTIONS YOU WILL WORK ON: four bullet-like paragraphs: - "Open weight licenses are becoming a market of their own The permissive licenses that built open source software are giving way to model licenses with usage thresholds, attribution triggers, certified partner exemptions, geographic carve outs, and commercial only distribution terms, many written by labs outside the United States. Each release is a new instrument. You will read them first and help the market read them right." - "Rights follow the license, responsibility follows role The same model can be a shared API, a dedicated deployment, a customer supplied checkpoint, or a fine tune, and who holds what right changes with each. Whether Baseten is licensee, host, distributor, or acting on a customer's behalf determines what we can promise, what we can indemnify, and what no one in this market can honestly underwrite. Getting that allocation right, and explaining it plainly to a customer's outside counsel, is the core craft." - "Partners who are also channels, customers, and competitors A lab can be supplier, customer, and rival for the same workload. A hyperscaler can be our compute vendor, our distribution channel, and our competitor in one quarter. You will structure for channel conflict, exclusivity, and information flow so Baseten stays independent and customer centric." - "Cross border by default Labs, compute providers, and customers sit in different jurisdictions with different rules on export controls, sanctions, data residency, and what a license permits. Partnership paper and compliance posture have to move together, and you will work with our regulatory and policy leads to make sure they do." WHY THIS MATTERS TO BASETEN paragraph: "Our model catalog, distribution relationships, and partner channels are a large part of why customers choose us and why labs launch with us. A license question that stalls a dedicated capacity deal, a distribution term that limits how we serve a customer, or a partnership that creates a conflict we did not see coming has direct revenue and strategic consequences. This role exists to get ahead of those questions and to make Baseten the counterparty labs, platforms, and enterprises trust to get the model layer right." Responsibilities list (bullet points after "Responsibilities" heading): - Lead the legal workstream for model lab relationships: distribution agreements, hosted API and early access arrangements, token and capacity commitments, coalition and joint development agreements, and renegotiations as models and licenses evolve. - Lead strategic platform and channel deals: hyperscaler marketplace and gateway agreements, white label and reseller structures, co-sell and referral arrangements, and enterprise partnerships that combine a customer relationship with a distribution one. - Build and own Baseten's framework for open weight and custom model licenses: how we read them, how they apply across shared, dedicated, customer supplied, and fine-tuned deployments, what we confirm to customers before deployment, and where our indemnities begin and end. - Serve as the legal voice on model licensing questions in customer deals, including direct engagement with customer counsel on license interpretation, attribution and threshold mechanics, and the allocation of responsibility between Baseten, the lab, and the customer. - Advise leadership on channel strategy, conflict, and competition: exclusivity, most favored terms, information flow to partners who compete with us, and the structural protections that keep Baseten independent and customer centric. - Partner with our regulatory, policy, and security leads on the cross-border dimensions of partnership paper, including export controls, sanctions, KYC, and data residency, so that compliance posture and commercial terms move together. - Build the templates, playbooks, and per release licensing statements that let the business self-serve on standard arrangements and escalate the novel ones, and keep them current as the market changes. - Support M&A, acquihires, and other strategic or one-off transactions as needed, including diligence on inherited licenses and partner agreements. - Help build the partnerships legal function as it grows, and contribute across whatever the team needs. What We Value bullet points (after "What We Value" heading): - Reads the license. You start with the text the grant actually uses, not with what everyone assumes it says, and you can explain what it means to an engineer, a CFO, and a lab's general counsel in the same afternoon. - A point of view. You take a position, defend it, and change it when the facts change. We are not hiring someone to summarize both sides. - Structural thinking. You see how a distribution term today shapes a customer negotiation next year, and you design for the second order effects. - Technical fluency. You can hold your own on inference, model weights, fine tuning, multi tenancy, and dedicated versus shared deployments, and you know why the distinction matters for rights and responsibility. - Commercial grounding. Partnership legal work serves the business. You know which terms to hold, which to trade, and how to say so without slowing the deal down. - Builder mentality. You operate independently, build from scratch, and have low ego. You are as comfortable drafting a per release licensing statement as you are negotiating with a hyperscaler. Requirements list (after "Requirements" heading): - JD and active bar membership in good standing. - 8+ years of technology transactions or partnerships experience, with meaningful in-house time leading partnership, licensing, or platform deals at an AI, cloud, or developer infrastructure company. - Deep familiarity with open source and open weight model licenses, including the newer custom licenses from frontier and international labs, and the ability to interpret them across deployment models. - Experience structuring strategic partnerships with counterparties who are also customers or competitors, including channel, reseller, marketplace, and co sell arrangements. - Direct experience allocating IP and indemnity risk in AI or platform agreements and explaining that allocation to sophisticated counterparties. - Clear, direct communicator who can translate license text and deal structure for founders, partnerships leads, and customer counsel. - The ability to learn, build, and master AI tooling and systems to self-serve and operate at breakneck speed. - A desire to become a recognized thought leader in your field. YOU MIGHT EXCEL IF YOU list (after that heading): - Have led AI partnerships or model licensing legal work at a frontier lab, hyperscaler, or AI platform company. - Have negotiated with or on behalf of model labs and understand how