Pharmaceutical Contracts Lawyers
Axiom · San Francisco, CA · 1 mo ago
RemoteRemoteLegal$105k–$325k/yrContract
We need to output HTML fragment with sections: About the role? Actually the posting includes "Join Our Team as a Pharmaceutical Contracts Counsel at Axiom Location: United States (remote or flexible on-site/hybrid depending on engagement)". Then responsibilities, qualifications, preferred skills, compensation, about Axiom. Also maybe "About the role" is not present; but we can create sections based on headings present: Responsibilities, Qualifications, Preferred Skills, Compensation, About Axiom. Also maybe "Location" is metadata; we can fold into a short for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings only if content exists. We have Responsibilities, Qualifications, Preferred Skills (maybe Skills), Compensation (Pay), Benefits (maybe part of compensation description), About Axiom (maybe About the role? but we can use About Axiom as a heading? The allowed headings list includes "About the role". Not "About Axiom". But we could treat "About Axiom" as "About the role"? Not exactly. However we could still use
. The instruction: 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 we can include a
for location. We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings only if content exists. We have Responsibilities, Qualifications, Preferred Skills (maybe Skills), Compensation (Pay), Benefits (maybe part of compensation description), About Axiom (maybe About the role? but we can use About Axiom as a heading? The allowed headings list includes "About the role". Not "About Axiom". But we could treat "About Axiom" as "About the role"? Not exactly. However we could still use for any section heading we want, but the instruction says: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. Likely we should stick to those headings where appropriate. We have Responsibilities, Qualifications, Skills (Preferred Skills), Pay (Compensation), Benefits (maybe part of compensation). About the role could be a short description of the role (maybe the initial paragraph). We could use "About the role" heading for the introductory description (Join Our Team...). That seems appropriate.
Thus sections:
- About the role: introductory paragraph (including location maybe).
- Responsibilities: list.
- Qualifications: list (maybe split into required qualifications and preferred skills? But we have Qualifications and Preferred Skills separate. Could combine Qualifications as required, and Skills as preferred. Use headings Qualifications and Skills.
- Pay: compensation details.
- Benefits: maybe mention health, dental, vision insurance; paid holidays and PTO; flexible work arrangements; professional development opportunities and tools. That is benefits.
- About Axiom: maybe not needed if we already have About the role. But we could include a section "About Axiom" as a heading? Not in list but could be okay. However instruction: "Prefer a few substantive sections over many thin ones." Could combine About Axiom into About the role? But About the role is about the position; About Axiom is about company. Could be separate but maybe we can omit if not needed. However we need to preserve ALL substantive information; we cannot drop the About Axiom paragraph. So we need a section for it. Could use heading "About Axiom" even if not in examples; it's still a section heading. The instruction didn't forbid other headings, just gave examples. So we can use for About Axiom.
Thus output:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. Likely we should stick to those headings where appropriate. We have Responsibilities, Qualifications, Skills (Preferred Skills), Pay (Compensation), Benefits (maybe part of compensation). About the role could be a short description of the role (maybe the initial paragraph). We could use "About the role" heading for the introductory description (Join Our Team...). That seems appropriate.
Thus sections:
- About the role: introductory paragraph (including location maybe).
- Responsibilities: list.
- Qualifications: list (maybe split into required qualifications and preferred skills? But we have Qualifications and Preferred Skills separate. Could combine Qualifications as required, and Skills as preferred. Use headings Qualifications and Skills.
- Pay: compensation details.
- Benefits: maybe mention health, dental, vision insurance; paid holidays and PTO; flexible work arrangements; professional development opportunities and tools. That is benefits.
- About Axiom: maybe not needed if we already have About the role. But we could include a section "About Axiom" as a heading? Not in list but could be okay. However instruction: "Prefer a few substantive sections over many thin ones." Could combine About Axiom into About the role? But About the role is about the position; About Axiom is about company. Could be separate but maybe we can omit if not needed. However we need to preserve ALL substantive information; we cannot drop the About Axiom paragraph. So we need a section for it. Could use heading "About Axiom" even if not in examples; it's still a section heading. The instruction didn't forbid other headings, just gave examples. So we can use for About Axiom.
Thus output:
About the role
About the role
Join Our Team as a Pharmaceutical Contracts Counsel at Axiom Location: United States (remote or flexible on-site/hybrid depending on engagement)
Then responsibilities list. Then qualifications list. Then skills list (Preferred Skills). Then Pay section: compensation range. Then Benefits section: list of benefits. Then About Axiom section: paragraph(s). Make sure to use- for any list of duties/requirements/benefits. For qualifications, we have a list of items; we can put each qualification as
- . For preferred skills similarly.
We must not include boilerplate like EEO, scam warning, etc. Remove those.
We must preserve all substantive information: responsibilities, qualifications, preferred skills, compensation, benefits, about Axiom.
Let's extract details.
Responsibilities (bullet points):
- Draft, review, and negotiate a high volume of commercial agreements, including Master Services Agreements (MSAs), Statements of Work (SOWs), work orders, and change orders.
- Support a wide range of business functions by handling diverse contract types, including IT licenses and SaaS subscriptions, event and sponsorship agreements, and material transfer agreements (MTAs).
- Provide practical, business-oriented legal advice on contract terms, risk allocation, and negotiation strategy.
- Partner cross-functionally with Legal, Procurement, IT, Commercial, and Supply Chain teams to support day-to-day contracting needs.
- Support manufacturing and supply chain-related agreements, including those involving CMOs, CDMOs, and distribution partners, as part of a broader commercial practice.
- Ensure contracts align with internal policies and applicable regulatory requirements within the pharmaceutical industry.
- Contribute to contract process improvements, including development of templates, playbooks, and scalable workflows.
- Manage multiple concurrent matters with competing deadlines in a high-volume environment.
Qualifications (required):
- 4–12+ years of experience in commercial contracting, preferably within pharmaceutical, biotech, or life sciences companies.
- Strong, hands-on experience drafting and negotiating MSAs, SOWs, work orders, and related commercial agreements in a high-volume setting.
- Demonstrated experience across a variety of agreement types, including IT/software agreements, vendor contracts, event/sponsorship agreements, and MTAs.
- Ability to operate as a generalist supporting multiple business units, with comfort shifting across different contract types and stakeholders.
- Familiarity with manufacturing, supply, or distribution agreements is preferred but not required as a primary focus.
- Proven ability to independently manage a large pipeline of contracts with efficiency and sound judgment.
- Excellent communication skills, with a pragmatic, solutions-oriented approach to advising business teams.
- Juris Doctor (JD) or equivalent and active license to practice law in at least one U.S. jurisdiction.
Preferred Skills:
- Prior in-house experience within a pharmaceutical, biotech, or life sciences company.
- Experience supporting procurement, IT, and commercial teams in a centralized legal function.
- Familiarity with regulatory considerations impacting pharma contracts (e.g., FDA, GMP, GxP environments).
- Exposure to biologics or large-molecule manufacturing and distribution environments.
- Ability to quickly integrate into new teams and deliver value in dynamic client settings.
Compensation:
- The estimated total compensation for full-time Axiom attorney roles is $104,500-325,000 per year and for non-attorney roles is $71,250-309,750 per year. Compensation decisions are based on various factors, including, but not limited to, experience, skills, certifications, location, and business needs. Employees may be eligible for additional benefits, including health, dental, and vision insurance; paid holidays and PTO; flexible work arrangements; and professional development opportunities and tools.
We need separate Pay and Benefits sections. Pay: compensation range. Benefits: list of benefits.
Thus Pay section:
Pay
The estimated total compensation for full-time Axiom attorney roles is $104,500-325,000 per year and for non-attorney roles is $71,250-309,750 per year. Compensation decisions are based on various factors, including, but not limited to, experience, skills, certifications, location, and business needs.
Benefits section:Benefits
- health, dental, and vision insurance
- paid holidays and PTO
- flexible work arrangements
- professional development opportunities and tools