Corporate Counsel - Commercial, Privacy & Data

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Seamless (company description), The Opportunity (role description), What You'll Own (responsibilities), What You'll Bring (qualifications), Why This Role (maybe benefits? Actually it's more about opportunity), Compensation Benefits & Compensation (pay), Benefits (benefits). We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content to these headings appropriately. The instruction: "use

for section headings (e.g. About the role, About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? It says e.g., meaning examples. We should use headings that match the content. Likely we should use headings like About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Not include Schedule if not present. Also we should not create sections with placeholder text. So we need to include only sections where we have real content. We need to preserve all substantive information, remove boilerplate: Equal Employment Opportunity, Visa sponsorship, etc. Also remove "Apply Here:" line and URL. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Seamless is building the future of AI-powered sales and revenue technology... (the About Seamless paragraph).

But "About the role" maybe should be about the role, not company. However we have "About Seamless" describing company. Could treat as About the role? The instruction says use

for section headings (e.g. About the role, Responsibilities...). So we can use About the role to include company description and role overview. Or we could split: About Seamless as About the role? Might be okay. Then Responsibilities: from "What You'll Own" bullet points. Then Requirements: from "What You'll Bring" Required Qualifications. Then Qualifications: maybe Preferred Qualification? Could combine? But we have Required and Preferred. Could put Required under Requirements, Preferred under Qualifications? Or Skills? The instruction list includes Qualifications, Skills. We could put Required Qualifications under Requirements, and Preferred Qualification under Qualifications. Or we could put all under Requirements. But better to follow headings: Requirements (required), Qualifications (preferred), Skills (maybe skills from required). However we have skills listed in required: analytical, problem-solving, contract drafting, negotiation skills. Could put under Skills. But we need to avoid thin sections. Let's think: We have substantial content for Responsibilities, Requirements (required qualifications), Benefits, Pay. Also we have "Why This Role" which is more about opportunity; could be part of About the role or separate but maybe not needed. Could incorporate into About the role. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: anticipated annual base salary range $125,000 - $175,000 USD. Benefits are listed. So we can have Pay and Benefits sections. Schedule not mentioned, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Check each for real content. About the role: combine About Seamless paragraph and The Opportunity paragraph (role description). That's substantive. Responsibilities: What You'll Own bullet points (multiple). Use

• . Requirements: Required Qualifications bullet points (list). Use
  • . Qualifications: Preferred Qualification (CIPP). Could be a

    or

    • . Since only one item, could be

      but better to use

      • for consistency? The instruction: Use
        • for any list of duties/requirements/benefits. For a single item, still a list? Could be

          . But we can still use

          • . It's okay. Skills: from Required Qualifications: "Excellent time management and a proven ability to operate autonomously in a fast-paced environment.Strong analytical, problem-solving, contract drafting, and negotiation skills." Could be a
            • list. Benefits: list from Benefits section. Pay: paragraph with salary range. We must not include boilerplate like Equal Employment Opportunity, Visa sponsorship, Apply Here. Also remove duplicated lines: The posting includes "The Opportunity" and then later "Why This Role" etc. We'll keep only needed. Now craft HTML. We need to ensure we preserve all substantive information. Let's extract text. About Seamless paragraph: "About Seamless Seamless is building the future of AI-powered sales and revenue technology. Our platform combines real-time B2B data, artificial intelligence, sales engagement, and automation to help revenue teams find the right buyers, improve contact and company data, personalize outreach, and create pipeline more efficiently. Seamless brings data and execution together through an integrated platform spanning sales intelligence, prospecting, buyer signals, data enrichment, AI-powered engagement, AI agents, APIs, integrations, and automated workflows. Our technology helps sales and go-to-market teams turn accurate data and actionable insights into more connections, meetings, pipeline, and revenue. We operate at the intersection of AI, data, automation, and revenue technology, solving complex problems around data quality, accuracy, scale, intelligent workflows, and how businesses identify and engage prospective customers. As AI continues to transform how companies go to market, Seamless is investing in our platform, data capabilities, AI products, and people to help define the next generation of sales technology." The Opportunity paragraph: "The Opportunity Seamless is looking for a strategic, execution-focused Corporate Counsel – Commercial, Privacy & Data to help protect the business, accelerate commercial execution, and build legal and compliance practices that scale with the company. This role will serve as a key legal partner across the organization, working closely with the COO and leaders across Sales, Finance, Product, Engineering, Security, IT, and People, while coordinating with outside counsel on specialized matters. You will own high-impact legal work across commercial contracting, SaaS transactions, global privacy and data compliance, product counseling, employment matters, corporate governance, and legal operations. A core part of the role is translating complex legal and regulatory requirements into practical business guidance—helping teams move quickly while appropriately managing legal, commercial, privacy, and compliance risk. For an attorney interested in working at the intersection of SaaS, artificial intelligence, B2B data, privacy, commercial transactions, APIs, and emerging technology, this role offers broad ownership, meaningful cross-functional influence, and the opportunity to help shape how legal supports the continued growth of the business." We can combine these two paragraphs under About the role. Now Responsibilities: "What You'll Own" sections with bullet points: - Privacy & Data Compliance: Lead global privacy and data protection compliance efforts, including GDPR and CCPA/CPRA, and develop data processing frameworks, privacy policies, and Data Processing Agreements (DPAs).Own day-to-day privacy operations, including Data Protection Impact Assessments (DPIAs), Data Subject Access Requests (DSARs), and internal privacy guidance.Partner with Product, Security, and IT to align privacy and data practices with business objectives, product capabilities, data use, and applicable regulatory requirements.Identify privacy risks and customer or vendor data obligations, escalating high-risk matters to executive leadership as appropriate. - Commercial Contracts & SaaS Transactions: Lead the review and negotiation of commercial contracts, SaaS agreements, technology agreements, and data licenses while protecting intellectual property, appropriately managing liability, and supporting business outcomes.Develop and maintain internal redline standards, fallback clauses, contract templates, and negotiation playbooks.Optimize contract lifecycle management (CLM) processes in partnership with Sales and Finance to reduce inefficiencies and support efficient deal cycles.Review and negotiate vendor agreements, evaluate third-party risk, and support contract compliance.Partner with business stakeholders throughout customer, vendor, and commercial negotiations to provide practical legal guidance and facilitate resolution. - Product & Platform Legal Support: Advise Product and Engineering teams on legal implications associated with new products and features, artificial intelligence and AI agents, public APIs and integrations, data use, automated workflows, platform policies, and emerging technology.Develop and maintain public-facing terms of service, API use policies, acceptable use standards, and related legal documentation.Partner with business and technical teams to translate legal and regulatory requirements into scalable product and operating practices. - Employment & Corporate Governance: Advise the People team on employment matters, including contractor classification, company policies, and global employment frameworks.Support corporate governance requirements, including board documentation preparation and compliance reporting. - Legal Operations & Team Coordination: Own and continuously improve legal operations infrastructure, including legal tools, templates, contract processes, and matter-management tracking.Develop and deliver internal training programs, particularly related to data privacy and compliance.Coordinate workflows with external legal administrative support and specialized outside counsel on complex matters.Identify and implement opportunities to make legal processes more scalable, efficient, and effective for internal business partners. We need to preserve all substantive information; we can break into separate
            • items for each bullet heading. The text includes no line breaks but we can split by the headings. We'll produce
              • Privacy & Data Compliance: ...
              etc. Now Requirements: Required Qualifications bullet list: - J.D. from an accredited law school and an active license to practice law in at least one U.S. state. - 3–5+ years of relevant legal experience, with at least 1–2 years of in-house experience at a SaaS or technology company preferred. - Deep experience in SaaS commercial law, data privacy, and basic employment law. - Deep knowledge of federal, state, and global privacy laws, including GDPR and CCPA/CPRA. - Familiarity with SaaS procurement models, SOC 2 requirements, or vendor security review processes. - Experience with, or strong understanding of, public APIs and open-access data terms. - Exposure to managing legal technology tools, including contract lifecycle management (CLM) software, and coordinating with outside counsel. - Demonstrated success building internal trust and strong relationships with business partners. - Excellent time management and a proven ability to operate autonomously in a fast-paced environment. - Strong analytical, problem-solving, contract drafting, and negotiation skills. We'll put each as
              • . Now Qualifications: Preferred Qualification: - Certified Information Privacy Professional (CIPP) certification is a strong plus. We'll put as
                • ...
                . Now Skills: Could extract from Required Qualifications: "Excellent time management and a proven ability to operate autonomously in a fast-paced environment.Strong analytical, problem-solving, contract drafting, and negotiation skills." But we already included time management and analytical etc in Requirements. Might be redundant. Better to not duplicate. Perhaps we can treat Skills as those specific skills: time management, autonomous operation, analytical, problem-solving, contract drafting, negotiation. But they are already in Requirements. To avoid duplication, maybe we skip Skills section. However instruction says we can use Skills heading if we have content. But we risk duplicating. Could we move those specific skills to Skills and keep Requirements more about experience/education? Let's see: Required Qualifications includes both experience and skills. We could split: Requirements: education, experience, knowledge. Skills: time management, analytical, problem-solving, contract drafting, negotiation. But the instruction says preserve ALL substantive information; not required to avoid duplication but we should not invent or summarize away detail. Duplicating is okay as long as we preserve. But better to avoid redundancy. However we can keep Requirements as all required qualifications, and omit Skills. That's fine because we are not required to use all headings. The instruction: "Prefer a few substantive sections over many thin ones." So we can skip Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: list from Benefits section: - Medical, dental, and vision insurance - Health