Senior Counsel - Litigation & Product
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. 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to parse the posting and extract sections: About the role (the description after "About The Role"), Responsibilities (What You'll Do), Requirements (What You'll Need to Succeed), Preferred Qualifications, Work Location and Travel (maybe schedule?), Perks (Benefits), Pay (Hiring Range), maybe other.
We must not include sections that are not substantive. For Pay we have a range: $221,900– $266,300 USD. That's specific, so include Pay section.
Schedule: Not explicitly given; only mention occasional evenings/weekends, occasional travel. Not a schedule like full-time/part-time. So we should not create Schedule section unless posting actually states them. It does not state a schedule like "Full-time" etc. So skip Schedule.
Benefits: The perks list includes compensation package, medical, dental, vision, 401K, flexibility, vacation, holiday closures, AD&D and Life Insurance. That's benefits. So include Benefits section.
We also have Work Location and Travel: mention fully remote, occasional travel 5-10%, occasional international travel, passport required. That could be considered "Work Location" but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put location under About the role? Or maybe we can create a "Qualifications" section for preferred qualifications, and "Requirements" for required qualifications. "Skills" maybe not needed. We'll stick to the allowed headings.
Thus sections:
- About the role: include the paragraph(s) describing the role (the "About The Role" block). Should we include the introductory "About Torc" paragraph? That's company overview, not role. Probably not needed for role section. But we could include it as part of About the role? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have an About the role section that contains the role description. The "About Torc" is company overview; maybe we can omit as not required? But we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company overview? It's substantive but not part of role. However the allowed headings list does not include a company overview heading. Could we include it as a
before any heading? The instruction says output ONLY the HTML fragment; we can include
elements not under headings? It didn't forbid that. It says use
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. So we can have prose paragraphs outside headings. So we can include a brief intro about Torc as a
before the About the role heading.
Similarly, we may include Work Location and Travel as a
under maybe a heading? Not in list. Could be placed as a
after Benefits or before Pay. But we need to preserve it. We'll include it as a
after Benefits maybe.
We must not include Job ID or requisition numbers as headings; we can fold minor metadata into a short
or drop it. The Job ID: R-102984 and Hiring Range for Job Opening US Pay Range: $221,900– $266,300 USD. The Pay range we will include in Pay section. The Job ID we can drop or put in a short
. Probably drop it as minor metadata.
We must remove boilerplate like EEO statement, diversity statement, etc. The posting includes an EEO paragraph at end: "At Torc, we're committed to building a diverse and inclusive workplace..." That's boilerplate; remove.
Also remove "Even if you don't meet 100% of the qualifications..." that's also boilerplate? Might be considered encouraging but could be kept? It's generic; but it's not a list; it's a statement encouraging applicants. Might be considered boilerplate; but it's not EEO. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Even if you don't meet 100%..." is not exactly EEO but it's a generic encouraging statement; could be considered boilerplate? I'd remove it to be safe.
Also remove "Our compensation reflects the cost of labor across several geographic markets. Pay is based on a number of factors and may vary depending on job-related knowledge, skills, and experience. Torc's total compensation package will also include our corporate bonus and stock option plan. Dependent on the position offered, sign-on payments, relocation, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits." That's somewhat generic but includes details about compensation beyond the range. Might be considered boilerplate but also substantive? It's generic; but we already have Pay section with range; we could keep extra compensation details as part of Pay section prose. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info as it adds detail about compensation. However it's somewhat generic but still substantive. We'll include it in Pay section.
Now, let's extract content.
First, company overview: "About Torc At Torc, we have always believed that autonomous vehicle technology will transform how we travel, move freight, and do business. A leader in autonomous driving since 2007, Torc has spent over a decade commercializing our solutions with experienced partners. Now a part of the Daimler family, we are focused solely on developing software for automated trucks to transform how the world moves freight. Join us and catapult your career with the company that helped pioneer autonomous technology, and the first AV software company with the vision to partner directly with a truck manufacturer."
We'll put that as a
before About the role heading.
Next, About The Role heading: content after "About The Role" until "What You'll Do:" (maybe include that as part of About the role? Actually "About The Role" is a heading; the paragraph after it describes the role. Then "What You'll Do:" is a separate heading for responsibilities. So we should treat "About The Role" as About the role section. The paragraph:
"As Torc advances toward commercial deployment of its Level 4 autonomous trucking platform, we're looking for an experienced litigator and product counselor to own our litigation function and serve as a key product counseling partner. Reporting to the Associate General Counsel – Litigation & Commercial, you'll manage Torc's active litigation, build the processes that keep the company litigation-ready, and serve as a trusted legal partner to our Engineering, Product, and Safety & Regulatory teams (including Government Affairs). This is an ownership role on a lean, high-performing legal team at a pivotal moment in the company's history. Beyond managing the docket, you'll build and maintain Torc's litigation readiness infrastructure, including the playbooks and protocols needed for driver-out operations. Over time, you'll also grow into Torc's regulatory legal work, partnering with our Safety & Regulatory team and outside regulatory counsel on NHTSA and FMCSA matters. Deep AV regulatory expertise isn't required on day one, but curiosity and a willingness to learn are."
We'll put that as prose
under
About the role
.
Next, Responsibilities: "What You'll Do:" followed by bullet points (actually sentences separated by line breaks). We need to turn each duty into - . The content:
- Litigation and incident response Own Torc's litigation docket end to end: oversee outside counsel, manage budgets, set strategy, and drive resolution in alignment with the General Counsel and business stakeholders
- Build and run Torc's litigation readiness program, including legal hold procedures (issuance, custodian communication, and releases), litigation response playbooks, and evidence preservation protocols
- Serve as the legal lead on Torc's cross-functional incident response team, coordinating with Safety & Regulatory, Engineering, Communications, and others when incidents occur
- Develop litigation readiness frameworks for driver-out commercial operations, including protocols for incidents involving the autonomous driving system and for recalls
- Manage Torc's outside litigation counsel panel, including selection, engagement terms, billing guideline compliance, and performance
- Report on litigation exposure and trends to the General Counsel and senior leadership
- Advise on how record retention, insurance, and cybersecurity intersect with litigation readiness and incident response
- Product counseling Partner with Product, Engineering, and Safety & Regulatory teams to spot and mitigate legal risk early in the development cycle, including in safety case documentation and commercial launch activities
- Advise on product liability exposure arising from Torc's autonomous driving system
- Support regulatory reporting, including NHTSA Standing General Order crash reporting, defect and recall reporting, and Early Warning Reporting
- Provide legal analysis to Torc's safety governance bodies on product release decisions and safety artifact requirements
- Work with Government Affairs and outside regulatory counsel to turn evolving federal, state, and international AV regulation into practical guidance for internal teams, and assess what it means for litigation risk
- Advise on go-to-market issues as Torc moves from testing to commercial freight operations, including operational design domain limitations, risk allocation in customer agreements, and fleet partner requirements
- Review external communications, technical publications, and customer-facing materials for legal risk
- Build working expertise over time in Federal Motor Vehicle Safety Standards, ADS exemption processes, and FMCSA commercial vehicle safety requirements, in partnership with Government Affairs and outside counsel
- Supporting the Legal team Contribute to legal department process improvements, playbook development, and knowledge management
We need to split each bullet. Some sentences contain multiple duties separated by colon; but we can treat each line as a bullet. We'll produce
- for each.
Next, Requirements: "What You'll Need to Succeed:" followed by bullet points:
- J.D. from an accredited law school and active membership in good standing of at least one U.S. state bar
- 7+ years of legal experience, with meaningful exposure to litigation management, product liability, or related practice areas
- A track record of managing litigation and outside counsel, including budgeting, strategy, and resolution
- Experience building or maintaining litigation readiness infrastructure, such as legal hold programs and incident response protocols
- Sound judgment and the ability to give clear, practical advice in a fast-moving, technically complex environment
- Excellent written and verbal communication
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. 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and extract sections: About the role (the description after "About The Role"), Responsibilities (What You'll Do), Requirements (What You'll Need to Succeed), Preferred Qualifications, Work Location and Travel (maybe schedule?), Perks (Benefits), Pay (Hiring Range), maybe other. We must not include sections that are not substantive. For Pay we have a range: $221,900– $266,300 USD. That's specific, so include Pay section. Schedule: Not explicitly given; only mention occasional evenings/weekends, occasional travel. Not a schedule like full-time/part-time. So we should not create Schedule section unless posting actually states them. It does not state a schedule like "Full-time" etc. So skip Schedule. Benefits: The perks list includes compensation package, medical, dental, vision, 401K, flexibility, vacation, holiday closures, AD&D and Life Insurance. That's benefits. So include Benefits section. We also have Work Location and Travel: mention fully remote, occasional travel 5-10%, occasional international travel, passport required. That could be considered "Work Location" but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put location under About the role? Or maybe we can create a "Qualifications" section for preferred qualifications, and "Requirements" for required qualifications. "Skills" maybe not needed. We'll stick to the allowed headings. Thus sections: - About the role: include the paragraph(s) describing the role (the "About The Role" block). Should we include the introductory "About Torc" paragraph? That's company overview, not role. Probably not needed for role section. But we could include it as part of About the role? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have an About the role section that contains the role description. The "About Torc" is company overview; maybe we can omit as not required? But we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company overview? It's substantive but not part of role. However the allowed headings list does not include a company overview heading. Could we include it as a
before any heading? The instruction says output ONLY the HTML fragment; we can include
elements not under headings? It didn't forbid that. It says use
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. So we can have prose paragraphs outside headings. So we can include a brief intro about Torc as a
before the About the role heading.
Similarly, we may include Work Location and Travel as a
under maybe a heading? Not in list. Could be placed as a
after Benefits or before Pay. But we need to preserve it. We'll include it as a
after Benefits maybe.
We must not include Job ID or requisition numbers as headings; we can fold minor metadata into a short
or drop it. The Job ID: R-102984 and Hiring Range for Job Opening US Pay Range: $221,900– $266,300 USD. The Pay range we will include in Pay section. The Job ID we can drop or put in a short
. Probably drop it as minor metadata.
We must remove boilerplate like EEO statement, diversity statement, etc. The posting includes an EEO paragraph at end: "At Torc, we're committed to building a diverse and inclusive workplace..." That's boilerplate; remove.
Also remove "Even if you don't meet 100% of the qualifications..." that's also boilerplate? Might be considered encouraging but could be kept? It's generic; but it's not a list; it's a statement encouraging applicants. Might be considered boilerplate; but it's not EEO. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Even if you don't meet 100%..." is not exactly EEO but it's a generic encouraging statement; could be considered boilerplate? I'd remove it to be safe.
Also remove "Our compensation reflects the cost of labor across several geographic markets. Pay is based on a number of factors and may vary depending on job-related knowledge, skills, and experience. Torc's total compensation package will also include our corporate bonus and stock option plan. Dependent on the position offered, sign-on payments, relocation, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits." That's somewhat generic but includes details about compensation beyond the range. Might be considered boilerplate but also substantive? It's generic; but we already have Pay section with range; we could keep extra compensation details as part of Pay section prose. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info as it adds detail about compensation. However it's somewhat generic but still substantive. We'll include it in Pay section.
Now, let's extract content.
First, company overview: "About Torc At Torc, we have always believed that autonomous vehicle technology will transform how we travel, move freight, and do business. A leader in autonomous driving since 2007, Torc has spent over a decade commercializing our solutions with experienced partners. Now a part of the Daimler family, we are focused solely on developing software for automated trucks to transform how the world moves freight. Join us and catapult your career with the company that helped pioneer autonomous technology, and the first AV software company with the vision to partner directly with a truck manufacturer."
We'll put that as a
before About the role heading.
Next, About The Role heading: content after "About The Role" until "What You'll Do:" (maybe include that as part of About the role? Actually "About The Role" is a heading; the paragraph after it describes the role. Then "What You'll Do:" is a separate heading for responsibilities. So we should treat "About The Role" as About the role section. The paragraph:
"As Torc advances toward commercial deployment of its Level 4 autonomous trucking platform, we're looking for an experienced litigator and product counselor to own our litigation function and serve as a key product counseling partner. Reporting to the Associate General Counsel – Litigation & Commercial, you'll manage Torc's active litigation, build the processes that keep the company litigation-ready, and serve as a trusted legal partner to our Engineering, Product, and Safety & Regulatory teams (including Government Affairs). This is an ownership role on a lean, high-performing legal team at a pivotal moment in the company's history. Beyond managing the docket, you'll build and maintain Torc's litigation readiness infrastructure, including the playbooks and protocols needed for driver-out operations. Over time, you'll also grow into Torc's regulatory legal work, partnering with our Safety & Regulatory team and outside regulatory counsel on NHTSA and FMCSA matters. Deep AV regulatory expertise isn't required on day one, but curiosity and a willingness to learn are."
We'll put that as prose
under
About the role
.
Next, Responsibilities: "What You'll Do:" followed by bullet points (actually sentences separated by line breaks). We need to turn each duty into - . The content:
- Litigation and incident response Own Torc's litigation docket end to end: oversee outside counsel, manage budgets, set strategy, and drive resolution in alignment with the General Counsel and business stakeholders
- Build and run Torc's litigation readiness program, including legal hold procedures (issuance, custodian communication, and releases), litigation response playbooks, and evidence preservation protocols
- Serve as the legal lead on Torc's cross-functional incident response team, coordinating with Safety & Regulatory, Engineering, Communications, and others when incidents occur
- Develop litigation readiness frameworks for driver-out commercial operations, including protocols for incidents involving the autonomous driving system and for recalls
- Manage Torc's outside litigation counsel panel, including selection, engagement terms, billing guideline compliance, and performance
- Report on litigation exposure and trends to the General Counsel and senior leadership
- Advise on how record retention, insurance, and cybersecurity intersect with litigation readiness and incident response
- Product counseling Partner with Product, Engineering, and Safety & Regulatory teams to spot and mitigate legal risk early in the development cycle, including in safety case documentation and commercial launch activities
- Advise on product liability exposure arising from Torc's autonomous driving system
- Support regulatory reporting, including NHTSA Standing General Order crash reporting, defect and recall reporting, and Early Warning Reporting
- Provide legal analysis to Torc's safety governance bodies on product release decisions and safety artifact requirements
- Work with Government Affairs and outside regulatory counsel to turn evolving federal, state, and international AV regulation into practical guidance for internal teams, and assess what it means for litigation risk
- Advise on go-to-market issues as Torc moves from testing to commercial freight operations, including operational design domain limitations, risk allocation in customer agreements, and fleet partner requirements
- Review external communications, technical publications, and customer-facing materials for legal risk
- Build working expertise over time in Federal Motor Vehicle Safety Standards, ADS exemption processes, and FMCSA commercial vehicle safety requirements, in partnership with Government Affairs and outside counsel
- Supporting the Legal team Contribute to legal department process improvements, playbook development, and knowledge management
We need to split each bullet. Some sentences contain multiple duties separated by colon; but we can treat each line as a bullet. We'll produce
- for each.
Next, Requirements: "What You'll Need to Succeed:" followed by bullet points:
- J.D. from an accredited law school and active membership in good standing of at least one U.S. state bar
- 7+ years of legal experience, with meaningful exposure to litigation management, product liability, or related practice areas
- A track record of managing litigation and outside counsel, including budgeting, strategy, and resolution
- Experience building or maintaining litigation readiness infrastructure, such as legal hold programs and incident response protocols
- Sound judgment and the ability to give clear, practical advice in a fast-moving, technically complex environment
- Excellent written and verbal communication
for prose. So we can have prose paragraphs outside headings. So we can include a brief intro about Torc as a
before the About the role heading. Similarly, we may include Work Location and Travel as a
under maybe a heading? Not in list. Could be placed as a
after Benefits or before Pay. But we need to preserve it. We'll include it as a
after Benefits maybe. We must not include Job ID or requisition numbers as headings; we can fold minor metadata into a short
or drop it. The Job ID: R-102984 and Hiring Range for Job Opening US Pay Range: $221,900– $266,300 USD. The Pay range we will include in Pay section. The Job ID we can drop or put in a short
. Probably drop it as minor metadata. We must remove boilerplate like EEO statement, diversity statement, etc. The posting includes an EEO paragraph at end: "At Torc, we're committed to building a diverse and inclusive workplace..." That's boilerplate; remove. Also remove "Even if you don't meet 100% of the qualifications..." that's also boilerplate? Might be considered encouraging but could be kept? It's generic; but it's not a list; it's a statement encouraging applicants. Might be considered boilerplate; but it's not EEO. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Even if you don't meet 100%..." is not exactly EEO but it's a generic encouraging statement; could be considered boilerplate? I'd remove it to be safe. Also remove "Our compensation reflects the cost of labor across several geographic markets. Pay is based on a number of factors and may vary depending on job-related knowledge, skills, and experience. Torc's total compensation package will also include our corporate bonus and stock option plan. Dependent on the position offered, sign-on payments, relocation, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits." That's somewhat generic but includes details about compensation beyond the range. Might be considered boilerplate but also substantive? It's generic; but we already have Pay section with range; we could keep extra compensation details as part of Pay section prose. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info as it adds detail about compensation. However it's somewhat generic but still substantive. We'll include it in Pay section. Now, let's extract content. First, company overview: "About Torc At Torc, we have always believed that autonomous vehicle technology will transform how we travel, move freight, and do business. A leader in autonomous driving since 2007, Torc has spent over a decade commercializing our solutions with experienced partners. Now a part of the Daimler family, we are focused solely on developing software for automated trucks to transform how the world moves freight. Join us and catapult your career with the company that helped pioneer autonomous technology, and the first AV software company with the vision to partner directly with a truck manufacturer." We'll put that as a
before About the role heading. Next, About The Role heading: content after "About The Role" until "What You'll Do:" (maybe include that as part of About the role? Actually "About The Role" is a heading; the paragraph after it describes the role. Then "What You'll Do:" is a separate heading for responsibilities. So we should treat "About The Role" as About the role section. The paragraph: "As Torc advances toward commercial deployment of its Level 4 autonomous trucking platform, we're looking for an experienced litigator and product counselor to own our litigation function and serve as a key product counseling partner. Reporting to the Associate General Counsel – Litigation & Commercial, you'll manage Torc's active litigation, build the processes that keep the company litigation-ready, and serve as a trusted legal partner to our Engineering, Product, and Safety & Regulatory teams (including Government Affairs). This is an ownership role on a lean, high-performing legal team at a pivotal moment in the company's history. Beyond managing the docket, you'll build and maintain Torc's litigation readiness infrastructure, including the playbooks and protocols needed for driver-out operations. Over time, you'll also grow into Torc's regulatory legal work, partnering with our Safety & Regulatory team and outside regulatory counsel on NHTSA and FMCSA matters. Deep AV regulatory expertise isn't required on day one, but curiosity and a willingness to learn are." We'll put that as prose
under
About the role
. Next, Responsibilities: "What You'll Do:" followed by bullet points (actually sentences separated by line breaks). We need to turn each duty into- . The content:
- Litigation and incident response Own Torc's litigation docket end to end: oversee outside counsel, manage budgets, set strategy, and drive resolution in alignment with the General Counsel and business stakeholders
- Build and run Torc's litigation readiness program, including legal hold procedures (issuance, custodian communication, and releases), litigation response playbooks, and evidence preservation protocols
- Serve as the legal lead on Torc's cross-functional incident response team, coordinating with Safety & Regulatory, Engineering, Communications, and others when incidents occur
- Develop litigation readiness frameworks for driver-out commercial operations, including protocols for incidents involving the autonomous driving system and for recalls
- Manage Torc's outside litigation counsel panel, including selection, engagement terms, billing guideline compliance, and performance
- Report on litigation exposure and trends to the General Counsel and senior leadership
- Advise on how record retention, insurance, and cybersecurity intersect with litigation readiness and incident response
- Product counseling Partner with Product, Engineering, and Safety & Regulatory teams to spot and mitigate legal risk early in the development cycle, including in safety case documentation and commercial launch activities
- Advise on product liability exposure arising from Torc's autonomous driving system
- Support regulatory reporting, including NHTSA Standing General Order crash reporting, defect and recall reporting, and Early Warning Reporting
- Provide legal analysis to Torc's safety governance bodies on product release decisions and safety artifact requirements
- Work with Government Affairs and outside regulatory counsel to turn evolving federal, state, and international AV regulation into practical guidance for internal teams, and assess what it means for litigation risk
- Advise on go-to-market issues as Torc moves from testing to commercial freight operations, including operational design domain limitations, risk allocation in customer agreements, and fleet partner requirements
- Review external communications, technical publications, and customer-facing materials for legal risk
- Build working expertise over time in Federal Motor Vehicle Safety Standards, ADS exemption processes, and FMCSA commercial vehicle safety requirements, in partnership with Government Affairs and outside counsel
- Supporting the Legal team Contribute to legal department process improvements, playbook development, and knowledge management
We need to split each bullet. Some sentences contain multiple duties separated by colon; but we can treat each line as a bullet. We'll produce
- for each. Next, Requirements: "What You'll Need to Succeed:" followed by bullet points: - J.D. from an accredited law school and active membership in good standing of at least one U.S. state bar - 7+ years of legal experience, with meaningful exposure to litigation management, product liability, or related practice areas - A track record of managing litigation and outside counsel, including budgeting, strategy, and resolution - Experience building or maintaining litigation readiness infrastructure, such as legal hold programs and incident response protocols - Sound judgment and the ability to give clear, practical advice in a fast-moving, technically complex environment - Excellent written and verbal communication