Product Counsel

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate like EEO, legal, navigation, cookie, duplicated lines, application instructions. Also remove sections like "What makes us Qlik?" maybe part of About the role? The posting includes a description of Qlik, then "The Product Counsel Role", then "What makes this role interesting?" then "Here’s How You’ll Be Making An Impact", then "We’re Looking For a Teammate With", then location, then "More About Qlik And Who We Are", then "What else do we offer?" then Salary and Benefits, then Application Window, then Massachusetts notice, EEO, etc. We need to extract substantive content and organize into sections: About the role (maybe description of role), Responsibilities (list of duties), Requirements/Qualifications (maybe combined?), Skills (maybe list of skills), Benefits, Pay, Schedule (if present). The posting does not mention schedule explicitly (maybe hybrid). It mentions hybrid position based in King of Prussia, PA. That could be schedule? Not exactly schedule. Could include "Hybrid" under Schedule? But schedule section only if posting actually states schedule details like full-time, hours, etc. Not present. So we may omit Schedule. We need to include Pay section because salary range and bonus mentioned. Benefits section because benefits listed. About the role: we can include description of Qlik and role purpose. Responsibilities: list of duties from "Here’s How You’ll Be Making An Impact" and also earlier responsibilities like "support for AI, new product features and services, advising on general IP matters", "work closely across multiple business units", etc. We need to preserve all substantive info, not summarize away detail. That means we need to keep the bullet points as they are, but we can format as

• . Must not invent or summarize away detail. So we need to keep each responsibility as a separate list item, preserving the wording. However some sentences are long; we can keep them as is. Similarly for Requirements/Qualifications: list of qualifications from "We’re Looking For a Teammate With". Must keep each bullet. Skills: maybe we can extract from responsibilities or qualifications? But we can also create a Skills section if there is explicit list of skills like "Strong written and communication skills", "Strong negotiation, documentation and presentation skills", "Interpersonal skills", etc. Those are skills. Could put them under Skills. Benefits: list from "This position is eligible for comprehensive benefits, including - but not limited to - medical, dental, and vision coverage life and AD&D, short and long-term disability coverage, paid time off, paid parental / maternity leave, participation in a 401(k) program that includes company match, and many other additional voluntary benefits." Also earlier "Genuine career progression pathways and mentoring programs. Culture of innovation, technology, collaboration, and openness. Flexible, diverse, and international work environment. Giving back is a huge part of our culture. Alongside an extra “change the world” day plus another for personal development, we also highly encourage participation in our Corporate Responsibility Employee Programs." Those are benefits/perks. So we can include them. Pay: salary range and bonus. We must not include boilerplate like EEO, Massachusetts notice, application window, etc. Also remove "More About Qlik And Who We Are" maybe part of About the role? But we can incorporate some of that into About the role if it's substantive. However "More About Qlik And Who We Are" includes generic statements about culture etc. Might be considered boilerplate? It's somewhat generic but still part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "More About Qlik And Who We Are" is not exactly boilerplate but could be considered generic marketing. However it's still substantive about culture. Might keep as part of About the role or Benefits. Safer to include relevant parts under Benefits or About the role. We must not repeat job title as heading. So no heading for "Product Counsel". We'll start with

  About the role

  then a paragraph summarizing the role description (the initial paragraphs about Qlik and the role). Must preserve all substantive info; we cannot summarize away detail. That means we cannot condense the description; we need to keep the details. But we can put them in paragraphs; we must not omit any detail. However we can combine multiple sentences into a paragraph as long as we keep all info. That's acceptable. We need to be careful not to invent or summarize away detail. So we must keep all facts: Qlik is a Gartner Magic Quadrant Leader for 16 years, serves over 40k customers, portfolio leverages data quality and AI/ML, integration and governance solutions, real-time analytics, etc. Then the role description: experienced attorney to join global legal team, support fast-growing business on complex and emerging issues including AI, new product features/services, advising on general IP matters, responsible for working closely across multiple business units to help achieve business goals within acceptable risk tolerances and in accordance with corporate policies, help product and technology leaders navigate legal, regulatory, commercial and trust considerations, bring legal and regulatory thinking into product roadmap discussions. Also "What makes this role interesting?" includes bullet points: serve as proactive embedded advisor through product lifecycle, ability to build trust and influence with senior executives, develop strong relationships with Product and Engineering leadership, foster culture of partnership, innovation and accountability, work closely on go-to-market launch readiness, anticipate legal issues impacting use of Qlik products and services, identify solutions and assist with implementation, collaborate with technology professionals to align legal strategy with technical realities. We need to keep all those as list items under Responsibilities maybe. But some of those are more about role interesting aspects; could be responsibilities. We'll treat them as responsibilities. Then "Here’s How You’ll Be Making An Impact" includes a list of responsibilities (strong business judgment, solutions-oriented approach, open source issues, AI concepts, review marketing materials, provide guidance, work with cross-functional stakeholders, work with Americas Sales team to negotiate contracts, work with finance and sales ops, identify and leverage technology automation AI tools, support engineering on patent programs, draft/review/negotiate tech vendor agreements, support development of resources for procurement, develop strong working knowledge of legal and sales systems, contribute to process improvement and contract templates, excellent communication skills). Those are responsibilities. We need to ensure we don't duplicate. We'll combine all responsibility bullets into one list under Responsibilities. Then Requirements/Qualifications: list from "We’re Looking For a Teammate With": Must have JD with demonstrated achievement from accredited law school and admitted to state bar. Minimum 7 years’ experience, including experience at a technology company or in a technology-related practice at a reputable law firm. Experience negotiating software and SaaS agreements. Preference for experience counseling on product legal issues or IP rights while collaborating with technology professionals. Preference for business-oriented candidates with background in computer/software tech or demonstrable interest in field, coupled with experience advising on open source, licensing, IP, AI matters. Strong interest in learning about emerging technologies. Proactive problem-solver with commitment to executing miscellaneous projects from inception to completion as business needs evolve. Hybrid position based in King of Prussia, PA (Greater Philadelphia). Strong written and communication skills as well as strong negotiation, documentation and presentation skills in a cross-functional and global role. Interpersonal skills with ability to build strong relationships in cross-functional teams. Desire to be a strategic partner to the business. Efficient and organized professional with ability to multitask on a multitude of matters under significant time pressure and attention to detail. Independent thinking, strong analytical skills and business acumen, while adhering to corporate policies and risk tolerances. Ability to deliver clear and concise legal counsel within deadlines. We need to keep all these as list items under Requirements (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills. We could have Requirements and Qualifications separate but we can combine if content overlaps. Better to have Requirements (maybe for mandatory) and Qualifications (for preferred). But we can just have one section "Requirements" and include all. However we need to follow instruction: use headings for those categories if they exist. The posting does not explicitly separate mandatory vs preferred; it's mixed. We could create a "Requirements" section for mandatory items and a "Qualifications" for preferred items. But that may be splitting hairs. Safer to have one section "Requirements" and include all bullet points. Or we could have "Requirements" for mandatory (JD, bar, 7 years experience, tech company experience, negotiating SaaS) and "Qualifications" for preferences (product legal counseling, background in computer science, interest in emerging tech, proactive problem-solver, etc). But the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one section "Requirements". We'll do that. Skills: we could extract skills like "Strong written and verbal communication skills", "Strong negotiation, documentation and presentation skills", "Interpersonal skills", "Ability to build strong relationships", "Strategic partner", "Efficient and organized", "Multitask", "Independent thinking", "Strong analytical skills", "Business acumen", "Ability to deliver clear and concise legal counsel". Those are skills. But many overlap with requirements. Might be redundant. Perhaps better to have a Skills section for soft skills like communication, negotiation, presentation, interpersonal, etc. But we risk duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we put same content in two sections, that's duplication but not invented. However duplication may be considered redundant but not prohibited. However we should avoid unnecessary duplication? Not explicitly prohibited. But better to avoid repeating same bullet points in multiple sections. We'll decide to put skills in a separate section only if there are explicit skill statements not already captured elsewhere. The posting includes "Strong written and communication skills as well as strong negotiation, documentation and presentation skills in a cross-functional and global role." and "Interpersonal skills with the ability to build strong relationships in cross-functional teams." and "Desire to be a strategic partner to the business." and "Efficient and organized professional with an ability to multitask on a multitude of matters under significant time pressure and attention to detail." and "Independent thinking, strong analytical skills and business acumen, while adhering to corporate policies and risk tolerances." and "Ability to deliver clear and concise legal counsel within deadlines." Those could be considered skills. We'll put them under Skills. But we also have responsibilities list that includes "Excellent written, verbal, and presentation communication skills, with the ability to translate complex issues into practical business guidance." That's similar. To avoid duplication, we could keep responsibilities list as is, and not duplicate in Skills. Instead, Skills could include items not already in responsibilities: maybe "Strong interest in learning about emerging technologies", "Proactive problem-solver", etc. But those are also in requirements. Hmm. Given the instruction to prefer few substantive sections over many thin ones, maybe we should have only About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. Skills could be omitted because its content overlaps with Responsibilities/Requirements. Benefits and Pay are distinct. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We must not include Schedule. Now we need to format. We'll produce:

  About the role

  ... (all descriptive paragraphs about Qlik and the role, preserving details). Must not omit any detail. We'll need to include all sentences from the initial description up to "What makes this role interesting?" maybe we incorporate that into responsibilities. But we need to ensure we don't lose any detail. Let's extract the descriptive text: "What makes us Qlik? A Gartner® Magic Quadrant™ Leader for 16 years in a row, Qlik transforms complex data landscapes into actionable insights, driving strategic business