Vice President & Assistant General Counsel, Mergers & Acquisitions

We need to output HTML fragment with sections: 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. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions, duplicated lines. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Compensation (base salary range) and Benefits details. No explicit schedule (like work hours) but mentions hybrid work environment, regular on-site presence up to 2 days per week, travel up to 25%. That could be considered schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation and benefits, so we can include Pay and Benefits sections. Schedule? It mentions hybrid work environment, regular on-site presence up to 2 days per week, travel up to 25%. That's about work arrangement, maybe schedule. Could be considered schedule content. The instruction says include a section ONLY when posting has real, specific content for it. It does have hybrid work environment etc. So we could include a Schedule section with that info. However we need to be careful not to create placeholder. It's specific: "Ability to thrive in a hybrid work environment, with regular on-site presence of up to 2 days per week. Flexibility to travel up to 25%, with the potential for increased travel or in-office presence as business needs evolve." That's schedule-related. So we can include a Schedule section. Now we need sections: About the role (maybe from the role description), Responsibilities (Duties), Requirements (Education/Experience), Knowledge, Skills & Abilities could be Skills, maybe also Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have: - About CoreSite: description of company. Could be About the role? Actually About the role likely includes role description. The posting includes "Role:" paragraph describing role. Also "About CoreSite:" is company overview. Could be placed under About the role? Might be better to put company overview under About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put the role description under About the role. The company overview could be maybe omitted? But we must preserve ALL substantive information. So we need to include company overview somewhere. Could be under About the role as well, or maybe we create a separate section? Not in allowed headings. Could incorporate into About the role. Thus About the role: combine CoreSite description and role description. Responsibilities: Duties list. Requirements: Education/Experience (JD, bar, 5+ years M&A, etc.) Qualifications: maybe we could combine with Requirements? But we need to decide. The posting has "Knowledge, Skills & Abilities:" which is Skills. Also "Education/Experience:" which could be Requirements. Qualifications maybe not distinct; but we could put Education/Experience under Requirements, and Knowledge, Skills & Abilities under Skills. Qualifications maybe we could omit if no specific content besides those. But we need to preserve all substantive info; we can put Education/Experience under Requirements, and Knowledge, Skills & Abilities under Skills. Qualifications could be omitted if no separate content. However we must not create a heading with filler. So we skip Qualifications if no distinct content. But we have also "Physical Demands" etc. That's substantive; where to put? Could be under Requirements? Or maybe under a separate section not in list; but we must not create extra headings. Could we incorporate Physical Demands into Requirements? It's not exactly requirement but could be considered part of job requirements. The instruction says preserve ALL substantive information; we can embed it under Requirements as a list. Also "Other projects and duties as assigned." is part of duties. Also "General Statements:" about work authorization, background check, drug test. That's substantive; where to put? Could be under Requirements? Or maybe under a separate section like "Eligibility". Not in allowed headings. Could incorporate into Requirements as well. Also "Applicant Privacy Notice" etc is boilerplate legal; we should remove cookie/navigation/legal/EEO etc. The Applicant Privacy Notice is legal; we should remove. Also "General Statements:" about work authorization, background check, drug test - that is not boilerplate? It's substantive eligibility requirement. We should keep. Also "Job Post Timeline:" etc is metadata; we can drop minor metadata. Also "Compensation:" we need Pay section. Also "Benefits:" we need Benefits section. Also "Schedule:" we need Schedule section (hybrid work, travel). Now we need to output HTML fragment only, using

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We must not include markdown code fences. We must not include /. We need to ensure we preserve all substantive info. Let's extract content: Company overview: "CoreSite is a leading colocation data center company providing the space, power, cooling and connectivity that businesses rely on to operate and grow. Our data centers bring dozens of organizations together under one roof, supporting the technology and services that keep our world connected. Our people are at the heart of everything we do, bringing the expertise, ideas and commitment that power our business and help our customers succeed. With a culture built on collaboration, ownership, and operational excellence, CoreSite is a place to make an impact." Role description: "As a member of the Company’s Legal team, the Vice President, Legal - Mergers & Acquisitions serves as a senior legal leader responsible for supporting the company's strategic growth initiatives through acquisitions, joint ventures, and other corporate transactions. This executive will lead the legal aspects of M&A transactions involving data centers and digital infrastructure assets. This executive will also support other company priorities, including customer contracting, data center development, litigation and advising management, and other internal stakeholders. CoreSite develops and operates essential multi-tenant data centers for our customers across the U.S. to deploy their compute infrastructure to support our daily digital lives. This role reports to CoreSite’s SVP and General Counsel and is an exciting opportunity for an expert candidate to build CoreSite’s public policy and community engagement agenda and to develop and implement strategies to advance this agenda at community, local, state and federal levels. The ideal candidate combines deep M&A expertise with strong commercial judgment and the ability to navigate legal, regulatory, real estate, infrastructure, and operational considerations unique to the data center sector." We can combine these into About the role. Now Duties list (from "Duties:"): bullet points: - Lead all legal aspects of acquisitions, mergers, and strategic transactions. - Structure and negotiate purchase agreements, merger agreements, JV agreements, investment agreements, and ancillary transaction documents. - Lead legal due diligence efforts and manage transaction risk assessments. - Advise executive leadership regarding transaction structure, diligence outcomes, valuation risks, contractual protections, and post-closing obligations. - Support acquisitions and development of data centers. - Coordinate outside counsel and cross-functional stakeholders through transaction execution and closing. - Lead negotiation and drafting of major tenant office space leases and major telecom licenses; negotiate, draft, or review drafts prepared by other Legal Department personnel of telecom cabinet and space licenses. - Negotiate and draft acquisition agreements and letters of intent. - Manage outside counsel in matters referred for litigation and set litigation strategy. - Analyze and resolve disputes with contractors, vendors, suppliers, and third parties; manage representation by outside counsel where necessary. - Promote and demonstrate the behaviors consistent with CoreSite’s culture and values - Other projects and duties as assigned. We need to preserve all. Also note there is a semicolon inside a bullet; we keep as is. Now Education/Experience: - Juris Doctor (JD) from an accredited law school. - Active membership in at least one U.S. state bar. - 5+ years of legal experience in M&A and corporate transactions. - Major law firm M&A practices preferred. - Significant experience leading transactions valued above $100 million. - Experience with private equity, REITs, technology companies, or digital infrastructure businesses preferred. - Data center, real estate, telecommunications, digital infrastructure, or technology sector experience preferred. Now Knowledge, Skills & Abilities: - Exceptional negotiation and influencing skills. - Strong executive presence and communication abilities. - Ability to balance legal risk with commercial objectives. - Strategic mindset and proven business judgment. - Ability to manage multiple high-value transactions simultaneously. - Collaborative leadership style and ability to build trusted relationships with senior executives. - Ability to thrive in a hybrid work environment, with regular on-site presence of up to 2 days per week. - Flexibility to travel up to 25%, with the potential for increased travel or in-office presence as business needs evolve. - Excellent written and verbal communication to internal and external audiences Note: The hybrid work and travel items appear here; but we also plan to have a Schedule section. However these are part of Skills & Abilities. We could keep them there, but also we might create a Schedule section with that info. To avoid duplication, we should not duplicate content. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but could be considered redundant. Better to keep them in Skills section and not create Schedule section if it duplicates. However the instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid duplication, but we should avoid unnecessary sections. Since we already have hybrid work and travel in Skills, we could still create a Schedule section but would need to move that content there to avoid duplication? The instruction says preserve ALL substantive information; we can keep it in both places but that would be duplication. Not prohibited but maybe not ideal. However we could decide to not create a Schedule section and instead keep hybrid/travel under Skills. But the instruction says we should include Pay, Schedule, Benefits sections only if posting actually states them. It does state hybrid work and travel, which is schedule-related. So we could create a Schedule section with that info, and remove it from Skills to avoid duplication. But then we would lose that info from Skills unless we keep it there too. The instruction does not forbid duplication, but we should aim for a few substantive sections over many thin ones. Duplication would create thin sections? Not necessarily. However we could keep it in Skills and not create Schedule; but then we would not have a Schedule section despite having schedule info. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not say we must create them if they are stated. It says we should not create them unless the posting actually states them. So we can optionally create them if we want, but we should not create them if the posting does not state them. Since posting does state schedule info, we could create a Schedule section. It's allowed. However we also need to preserve all substantive info; we could place schedule info in Schedule section and also keep it in Skills? That would be duplication but still preserving. Might be okay but could be considered redundant. I'd rather move schedule info to Schedule section and remove from Skills to avoid duplication, but then we lose some skills content (negotiation etc). However the Skills section would still have other skills. The hybrid/travel is more about work arrangement than skill; it's okay to move. Thus we will create: - About the role (prose) - Responsibilities (ul) - Requirements (ul) (Education/Experience + maybe Physical Demands + General Statements) - Skills (ul) (Knowledge, Skills & Abilities minus schedule items) - Benefits (ul) - Pay (p or ul? It's a prose statement; we can use

  ) - Schedule (ul) (hybrid work, travel) We also need to include Physical Demands and General Statements somewhere. Could be under Requirements as additional list items